Database Develop

A Bit of a Complex Issues Involving TWRP, SuperSU, and not being able to restore OS

So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)

Lucarje said:
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Click to expand...
Click to collapse
This has been posted a million times all over the forum. A quick search here or Google would have revealed the answer
You need to flash a revision 2 firmware. So that would be something like t813xxu2 in the firmware build number.

Sorry for being late with reply. Your advice helped me fix my tablet! Thanks so much!

Custom ROMs are not able to boot

Hi everyone,
I'm right now facing the issue that none of the flashed custom ROMs can boot.
I'm right now on MIUI 10.0.2.0, the bootloader is unlocked and TWRP was installed, but since I returned to the original global ROMs via XiaomiMiFlash Tool I think it's not on the decide anymore.
I tried to install Havoc and Pixel Experience.
What is the correct procedure to flashed the roms ?
I followed the instructions on the Havoc OS Thread for "Coming from MIUI 10.0.2.0". After installing the device kept boot looping and basically "flashing" the MI Logo with the "Unlocked" Label at the bottom.
Thank you for your time and help.

This could be a problem with your data partition and encryption. You need to full wipe your data (you loose all your sdcard data, so backup as much as possible) with twrp.

I used "Format Data" under "Wipe" in TWRP.
And I tried to run the decryption zip.
Same thing.

Lighthex said:
Hi everyone,
I'm right now facing the issue that none of the flashed custom ROMs can boot.
I'm right now on MIUI 10.0.2.0, the bootloader is unlocked and TWRP was installed, but since I returned to the original global ROMs via XiaomiMiFlash Tool I think it's not on the decide anymore.
I tried to install Havoc and Pixel Experience.
What is the correct procedure to flashed the roms ?
I followed the instructions on the Havoc OS Thread for "Coming from MIUI 10.0.2.0". After installing the device kept boot looping and basically "flashing" the MI Logo with the "Unlocked" Label at the bottom.
Thank you for your time and help.
Click to expand...
Click to collapse
Try this:
1. Flash MIUI PIE 8.12.20 global Rom DON'T REBOOT
2. Flash Disable_Dm-Verity_ForceEncrypt Here DON'T REBOOT
3. Wipe Data,System,Cache Your Data will be lost
4. Flash HavocRom + Gapps
5. Reboot and Enjoy
the link to the post is here: https://forum.xda-developers.com/mi-8/development/prepare-t3841106

I followed that instructions and now I'm at least seeing the boot logo, but its stuck at the animation.
I left it for 1 hour and it's not booting...
What can I do ?

Stuck on boot loop after installing official Oxygen OS Pie Community build

I was running a custom ROM (Skydragon) earlier. I simply booted into TWRP, did the basic wipe then flashed the official zip file. Then after booting, its stuck on the boot animation for more than 20 minutes now. Any ideas how to resolve this?

I too faced the same issue. formating the data partition and flashing community beta build booted successfully for me. before you do this, completely back your phone contents to pc

You must flash with TWRP 3.2.3.0 or older!

i had the same issue. formated data had 3.3.0 twrp but still bootloop so i used unbrick tool to put my phone back to stock and then updated to last build though stock recovery and then unlocked bootloader, installed twrp, magisk and done.

Redmi Note 9 Bootloop to recovery - help needed

Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?

ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out

Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?

I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again

If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.

For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.

Stuck in bootloop after flashing TWRP on stock rom

Hi, i had installed TWRP and magisk in few months ago, and for some reason, i installed stock rom file on my device. But I realized that my device got unrooted.
So, i flashed the same twrp.tar that i used before, now my device keeps booting into twrp (even when i select reboot>system)
Help me, thx