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!

Stuck at boot screen after twrp install MIUI 9

the problem im having is after upgrading to the latest 9.2.3 firmware when i try to install TWRP everything goes fine but the phone refuses to go past boot screen. I i can boot into TWRP with no problem at all but if i try booting the phone it just gets stuck at the boot logo.. So then i reverted back to the 9.1.1 firmware and now the problem has started there as well. anyone have any idea what im doing wrong?
PS: iv used 3.0.3, 3.1.1 and 3.2.1 none work

Hey after flashing TWRP your supposed to flash lazyflasher.zip if your running MIUI or you'll be stuck at the MI logo. This is a completely normal problem, nothing to worry about. Boot into TWRP and flash the lazyfalsher zip and your MIUI will be up and running. You can download it here

Bro after flashing twrp. Go inside twrp, options/settings, advanced, click on fix boot/disable verification something like that. Thats all It will boot.

hey thank man i just followed what you said and its working fine now

hey thanks for the reply i got it working

Glad it worked. Happy flashing!

SM-G920T on Nougat...won't boot past logo

I'm not sure if I triggered OEM unlock, but the phone wouldn't boot past logo after flashing Magisk, I reflashed the stock but it still won't boot past the logo despite stock binary. Any ideas?

Have you got the stock flash? Backed up existing?

i flashed superSU via TWRP. I have the same problem like yours before then I flashed superSU. it booted up well.

I updated Magisk and it worked. Without logcat, I have no idea what was going on to lag the phone on the bootanim.

MIUI update bricked my phone?!

My Mi 8 got bricked by the latest MIUI update. I installed the software update from settings and clicked reboot and it booted straight to TWRP (more on that in a bit). I tried rebooting to system but it just went straight back to TWRP. I have unlocked the bootloader and also rooted my phone but as I kept the stock ROM I wouldn't think this would break it. In hindsight, after doing a bit of looking around it seems like people tend to reflash stock.img before updating or something when they've rooted their phone? Wish I'd known that before I clicked update.
I tried flashing a different ROM but when I go to reboot it just says "no OS installed. Are you sure you want to reboot?" and just goes into bootloop stuck on the Mi logo
using fastboot adb tools I can boot it into TWRP (has never worked using the volume and power buttons) and flashing ROMs seems to go okay but reboot says no OS installed and it bootloops, as I said.
I've tried flashing the latest MIUI build for my device, pixel experience, lineage OS and all of them yield the same results. Happy to answer any questions and try out any suggestions that anyone has. I'm really quite desperate!
SOLUTION: I flashed the stock firmware using the xiaomi mi flash tool. This fixed pretty much everything apart from now the camera doesn't work lol

What twrp you are using?

dimitrisverlis said:
what twrp you are using?
Click to expand...
Click to collapse
twrp-3.2.1-0611

Wipe everything, FORMAT data and update xiaomi firmware.

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.