Database Develop

Moto g3 Stuck on bootloop after flashing twrp.

My moto g3 1550 stuck on bootloop with massage warning bootloader unlocked:crying::crying:
It was happen when I was trying to flash twrp it's successfully flashed but after it was stuck on this bootloop
I tried to flash stock firmware with adb but there I got some errors which are pre flasg image validation failed
So I am not able to do anything now.
Please help otians.
I am still able to access that flahed twrp.

One plus 3t got boot loops in the process of rooting

Hello,
In the process of rooting when i was trying to flash TWRP recovery after unlock bootloader. The device got bootloops, now it only boots in fastboot mode. Any help will be highly appreciated.

You probably flashed wrong TWRP image or messed up with boot image

Help! I really screwed up...

It all started when I tried to temporarily boot into the TWRP img file. It didn't work so I tried flashing the file to boot_a. Then I installed TWRP through the installer (stupidly didn't wipe the caches) and... Well. When I try to boot into System through TWRP, it gets COMPLETELY stuck at the powered by Android logo screen. No amount or combination of button holding will shut it off and I actually had to let the battery (thank you SO MUCH for non-removable batteries by the way, smartphone manufacturers >_>) drain before it would actually boot again. Rebooting it into Download mode will get it stuck in there too where every time I hold the power button and shut it off, it will just reboot right back into Download mode again. And now, here's probably the worst part. I CAN'T UNLOCK the critical partition to flash when in Download mode, so I can't use the OST tool! When I try to unlock it, it just complains that flashing unlock is not allowed even though the rest of the bootloader is completely unlocked.
TL;DR - When I power the phone up it goes straight into TWRP. Booting to System totally freezes it and the Bootloader puts it in a loop when I try to power it off. Critical partition is locked for some reason. I CAN get around the bootloader loop though and get back to TWRP by switching active slots and rebooting.

Did you flash the TWRP installer to your active boot partition or your inactive one? If you flashed it to the active one, you can't get into system anymore because TWRP is your boot partition.
If you are on Oreo, and you flashed to the inactive slot, and then patched the active slot, you have to reboot into the active slot recovery and flash the Magisk installer to disable verification of the partitions.
If you can get into the bootloader, and you still have the unlock key from nokia, do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.

THMSP said:
do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
Click to expand...
Click to collapse
This unlocked it! Thank you! <3
I also did have an issue with the OST tool complaining that the updater was out of date, but changing the .mlf file and leaving it unpacked when I opened it in OST seemed to make it work perfectly. My phone is now booting just fine and back to stock!
Now I just need to solve the original problem I had. How can I install TWRP to recovery since the img file wouldn't temporarily boot last time?
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!

S5Guy said:
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
Click to expand...
Click to collapse
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.

THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Yeah looks like you're right. Letting it update back to Android 9 deleted TWRP and made fastboot boot for TWRP nonfunctional again.
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?

S5Guy said:
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
Click to expand...
Click to collapse
You have to flash it directly to your boot partition. fastboot boot will work for nothing (and even if it worked those images would just send you directly into the system)

THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Alright! fastboot flash boot_a (TWRP image) worked! Thank you so much for all the help. <333

Stuck in fastboot :(

Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!

Hello,
As long as you have access to fastboot mode, am sure you can recover your device.
You need to download the official ROM that corresponds to your specific devices. If it is global version, download the global version.
Also, before flashing, make sure you unlock the bootloader.

jaybirdxyz said:
Hello everyone!
As the title states, my Xiaomi mi 9 is stuck in fastboot mode, after i tried installing the latest unofficial port of Lineageos 17.1 for the Mi 9.
I can not exactly remember how it happened but i guess i must have wiped the phone after installing the custom rom. Silly me...
I tried the following things to try to unbrick my phone:
1. Using the Mi Flash Tool in order to flash the official Xiaomi firmware onto my device. I flashed these versions: 11.05 global fastboot, 11.08 EEA fastboot, 11.06 global fastboot. None of them worked. My phone would show up on the flash tool and the flashing itself was always marked as successfull but sadly my phone would not boot into MIUI and just stay frozen in fastboot mode. Restarting the device did not help.
2. Flashing twrp and trying to boot into it. Sadly, this also did not work out for me. Every time after i would successfully flash the .img file and reboot my device, the damn fastboot screen appeared.
So is there anything i can do? No matter what i try, my device goes into fastboot mode. I tried searching for the answer myself but those who had the similar issue did either not receive any useful answers or the Mi Flash Tool magically worked for them after a few attempts.
Thank you in advance!
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
this temporarily boots you into TWRP so you can reflash TWRP again. with this method the TWRP will be deleted once you reboot si you need to reflash TWRP in TWRP. then dont reboot, flash a Good working rom.

Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')

ai5g said:
Similar problem here.
The line fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
brings up
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
try other TWRP images? or your boot partition fried?
fastboot flash boot twrp.img and see What happens

no system partition in realme c11

hey guys! i recently unlocked the bootloader of my realme c11 to flash lineage os 17 . so to do so i installed twrp recovery and there i accidently wiped my system partition .from then on i cant mount my system and vendor partition in twrp and i'm stuck now cause nor i have any os installed , so after that there remained the option to flash oppo stock firmware image using fastboot , with fastboot i flashed boot.img successfully but when i tried to flash system.img using "fastboot flash system system.img" it said that there is no such partition as system. i mean why ......why does it happen why can't i flash system even with fastboot guys anyone who can help is gladly appreciated ,it'll be very nice of you . itll be great if anybody provide a straightforward answer to this......i'm counting on you guys........i'm on the verge of giving up//,/.;'.,//.;

You still need the fix?

najib6973 said:
You still need the fix?
Click to expand...
Click to collapse
yeah, i need the fix , i have no os installed, stuck in a recovery boot loop for i have corrupted boot.img i guess , and if anyone can provide system.img too of realme c11

HRZ110695 said:
yeah, i need the fix , i have no os installed, stuck in a recovery boot loop for i have corrupted boot.img i guess , and if anyone can provide system.img too of realme c11
Click to expand...
Click to collapse
try flashing this. wrong or outdated twrp can show the boot.img and system.img corrupted too. if the phone is in orange mode, you'll be able to fix it all with just twrp. but if red, it's gonna be a big process

this

SAME PROBLEM WHAT HAPPEN NOW?