Database Info

Bootloop After trying to flash TWRP 2.8.7.1

I used adb to install TWRP onto my Nexus 5. Now it is in a bootloop, and TWRP does not seem to be able to mount anything. When it reboots it looks like it automatically goes to the TWRP where it says it is running OpenRecoveryScript but it is unable to mount anything. I tried a boot start to Recovery and it worked but when i tried a factory reset it says the same thing.
Any help would be great.

Spud37 said:
I used adb to install TWRP onto my Nexus 5. Now it is in a bootloop, and TWRP does not seem to be able to mount anything. When it reboots it looks like it automatically goes to the TWRP where it says it is running OpenRecoveryScript but it is unable to mount anything. I tried a boot start to Recovery and it worked but when i tried a factory reset it says the same thing.
Any help would be great.
Click to expand...
Click to collapse
Try flashing TWRP with fastboot:
fastboot devices
fastboot flash recovery name_of_your_TWRP_file.img
fastboot reboot

How did you solve that problem?

failed to mount vendor (invalid argument) -- SOLVED

Updating partition details... Failed to mount vendor (invalid argument)
The error above is one I faced today and I resolved. I decided to share this in case anyone else runs into a similar issue. There are very few ways you could end up unable to correctly boot a partition but the most common is a bad flash. In my particular case, it was my own stupidity, and it could have been a lot worse given that I mistakenly flashed a vendor image file to /vendor/ except it was for a completely different device and not meant for the Moto x4 (basically got confused between files from another project).
The result of this was that my phone could not technically boot on its own. Neither into a GSI/ROM or into Recovery either. I saw the first "Android One" logo, followed by the message warning that my phone was unlocked, followed by the second "Android One" logo, which was all normal up to that point, but I would remain forever stuck at that screen. I could thankfully reach the bootloader screen, but again, since I could not boot at all, I could not even boot into Recovery from the bootloader screen.
Thankfully, because I could still reach bootloader I could temporarily load into TWRP using fastboot
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view and installed
Rebooted back to bootloader and while at bootloader, I loaded the Android 8.1 firmware - courtesy @ptn107 https://androidfilehost.com/?fid=890278863836292604
From bootloader, I reloaded the bootloader again
This alone did not resolve my issue. I once used fastboot to temporarily load TWRP
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Installed TWRP https://dl.twrp.me/payton/
Installed LineageOS ROM -- It must be a full ROM and not a GSI. It must be specifically made for Moto x4 and not just a generic GSI (stock rom for example)
Reinstalled TWRP
Reboot
During the installs, you may still see the error. Ignore them as they will go away after the reboot. This will resolve such issues should you ever face them.

MotoX4 said:
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oir...t2eSGKt0F/view and installed
Click to expand...
Click to collapse
Fix google drive link, pls

Comby_sk said:
Fix google drive link, pls
Click to expand...
Click to collapse
Fixed in post #1 and full URL without text formatting is also here too
Code:
https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view

Teclast M89 problem installing TWRP

Hi folks. As the title suggest I'm having problems installing TWRP recovery on teclast M89 tablet. I've tried a few different tutorials with no success. When I do it with fastboot it says that its installed, after that when I try to reboot the device, I'm stuck in bootloop. I've tried to do it a few times and its always the same problem. Does anyone have a solution? Thanks.

Hello, the same for me with my M89, I'm going crazy.... Help us please!!!! Thanks!!!

Teclast M89 TWRP 3.3.1
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
My small Teclast M89 website: https://teclast-m89.neocities.org/

M89 TWRP Worked!
ValdikSS said:
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
Click to expand...
Click to collapse
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!

Jmlanner said:
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Click to expand...
Click to collapse
Make sure to backup nvram, nvdata, private partitions.

ValdikSS said:
Make sure to backup nvram, nvdata, private partitions.
Click to expand...
Click to collapse
Will do. I did bkk nvdata, will double check if I bkk privdata. again TK!

stuck
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
Hi
I think you are going to have to reflash the original Rom using SPFlahtool. Then you must install Magisk Manage on tabletr. Copy the boot image from the ROM files to Your phone. Then use Magisk Manager to Patch the copied boot image. Transfer modified boot image to PC. Use fastboot to flash modified boot image back onto the tablet. The long and the short of it is - you need to find a way to patch the boot image with Magisk before any TWRP will work.

Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though

voland34 said:
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
Click to expand...
Click to collapse
I am glad you got your tablet running again. I had originally started out with just Magisk as root also. I do like to have a working TWRP for backing up though. You should be able now to flash the above mentioned TWRP now via SpFlashtool or fastboot.

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para

ValdikSS said:
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
Click to expand...
Click to collapse
Ok, i'll try. Thanks!

Does anybody know if this guide also works for the new Teclast M89 PRO-model???

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No, most probably it won't. PRO model has different SoC/CPU.

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.

Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!

w1nst0n sm1th said:
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Click to expand...
Click to collapse
The bootloop is not because you've unlocked the bootloader, but most probably because the firmware is designed to perform userdata partition setup in the recovery upon first boot, and you don't have stock recovery, that's why it can't finish formatting procedure.
This could be fixed by flashing stock recovery and booting once.
You can ask for a firmware from Teclast (I used to ask them on vkontakte because they didn't respond my mails), they will provide it.
OR you can write zeros to "para" partition using fastboot, it should do the trick too.
---------- Post added at 16:58 ---------- Previous post was at 16:56 ----------
Edgaralanmx said:
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
Click to expand...
Click to collapse
Try to unplug/plug again HDMI cable several times. It seems that the HDMI controller or drivers are buggy.
To change the resolution I use "SecondScreen" software (requires root).

Hi guys,
I´m looking for a working rooting method for my Teclast M89 Pro model ??
Any idea ?? What about the "One Click Root" Program ???
Thank´s a lot

The device was trying to root.
I get the following information when restarting:
orange state
the device has been unlocked and can't be trusted
your device will boot in 5 seconds
Click to expand...
Click to collapse
When I try TWRP via sideload or recovery menu I get the following:
Supported API:3
-- Install /sdcard/teclast_m89_twrp_311.zip ...
Finding update packacke ...
Opening update package ...
Verifying update package ...
Update package verification took 0.5 s (result 0).
Installing update ...
E:Failed to find META-INF/com/android/metadata in update package.
Installing Teclast M89 TWRP Recovery
script succeeded: result was [1.000000]
Install from SD Card complete.
Click to expand...
Click to collapse
But TWRP is not installed.
Where is the problem?

kumpi said:
But TWRP is not installed.
Where is the problem?
Click to expand...
Click to collapse
Are you trying to enter recovery right after flashing it, without booting the OS first? I think you need do enter TWRP right after flashing it.

Can't mount "system" ,"vendor", "odm".

When i try to install zip package with weekly miui12 (unnoficial TWRP) i forgot to mount partitions and now i can't mount it anymore. Try to tick it but nothing happened.
So I can't install any package. Do I brick my device?
Is there any posibbility to mount those partitions?
Twrp errors:
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/odm' (invalid argument)

Are you trying to install Chinese weekly rom?

easy way to fix is flash stock with xiaomi assiatant by fastboot mode.

ZeroSherd said:
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
Click to expand...
Click to collapse
I jist flash fastboot rom twice and everything is ok xD

Is there a solution this error? I'm having the same problem.

I have the same problem. Can anybody help?

edit file rom, extract rom .zip, edit updater-script and delete first line. save and make file zip again.
tested rom global stable beta.
how edit updater-script,
https://forum.xda-developers.com/showthread.php?t=2522762

do my tutorial to get the phone and then start again, it's in Spanish but it's simple.
https://www.htcmania.com/showthread.php?t=1565656
you have to install the recovery "TWRP-3.4.2B-0623-REDMI_K30PRO-CN-wzsx150-fastboot.zip" and with that you will not have errors, the twrp of this website gives errors

i have the same problem How i can flash miui china beta on F2 Pro from twrp?

Koziol87 said:
I jist flash fastboot rom twice and everything is ok xD
Click to expand...
Click to collapse
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN

Latin_lion_ said:
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Click to expand...
Click to collapse
Did you use miflash?

NOSS8 said:
Did you use miflash?
Click to expand...
Click to collapse
yh BUT for some strange reason i cant flash the latest stock rom on my device arb error ive tried everything hoping to find help im new to this first phone ive tried to install custom roms on

I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks

cxm05 said:
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/

NOSS8 said:
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
Click to expand...
Click to collapse
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"

cxm05 said:
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
Click to expand...
Click to collapse
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download

NOSS8 said:
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
Click to expand...
Click to collapse
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo

cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?

cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
in flash folder of rom, you have flashall.bat open it in txt format, find two rows that contain CRC and delete it, save file and than try to flash rom again. it will pass. I have the same CRC error and deleting this two row help me to flash rom

NOSS8 said:
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
Click to expand...
Click to collapse
The MI Assistant version is 3.2.522.32 beta. Once I start the Mi Assisant client on my phone and then plug my cable, the application prompts me to select a Fastboot ROM on my harddrive. ONce I select a valid imag, it flashes my phone and then reboots. After loading for 15 minutes or so, the phone reboots to the MI recovery where I can select to use Mi Assistant again.
This time, Mi Assistant detects the version of ROM I have installed and advises there is a newer ROM. On this screen I select the first button (which I believe downloads the image from MI server) or the sencond button (which allows me to select a local Recovery ROM stored on my hard drive).
Regardless of which option I choose, the 2nd flash occurs and my phone reboots again. in A cycle until I have the most recent ROM on the phone and it still sits at the MIUI boot screen for 30 minutes. I've gone from 11.2.0.9 ==> 12.2.0.4 ==> 12.2.2.4. All successfully flash to the phone but phone never boots past the MIUI logo.
I've even gone as far as flashing a beta ROM 12.2.2.5 on top of the latet stable version using MI Assistant (flash runs successfully ut phone still never boots).
I have also gone into bootloader mode & flashed the TWRP version you recommended. After botting into this recovery, I can "factory reset" the phone and the sideload the HK 12.2.0.3 rom you provided. The sideload flashes to the phone with no errors, but phone still doesn't boot past the MIUI logo

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine