Database Users

Boot Loop - ZE550KL

Hello guys,
Sorry for my bad English
My phone just turned off even if the battery is almost full. When I turned it on its stuck in a boot loop. Sometimes it's goes to a screen where it would say process not responding. It's still on the stock ROM and recovery. I didn't try to root it or flash anything on it.
I tried some troubleshooting like flashing the firmware from the Asus website but it didn't work. Please help

Have you try flashing from Micro SD card in stock recovery?

M Huzaifah said:
Have you try flashing from Micro SD card in stock recovery?
Click to expand...
Click to collapse
Thank you for the reply bro. I already did and it's still not working.

To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).

you can install custom recovery?

I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img

BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
After these commands, had to do a wipe data/factory reset prior to update from sd card (adb sideload not work at alll).
but no luck, keep boot looping...
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
sofamensch said:
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
Click to expand...
Click to collapse
this command result error:
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.802s
used this instead: fastboot flash boot boot.img (with boot.img extracted from firmware)
target reported max download size of 268435456 bytes
sending 'boot' (24547 KB)...
OKAY [ 0.813s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.550s
but my case is serious, giving up

maybe you should unlock the bootloader before trying those commands

why don't u try, adb sideload option once, give it a try

i dont know what firmware my dads ze550kl is...
and it is bootlooping continously....
what is best files to flash via recovery update from sd card method?
i want to save my dads internal memory

Try this:
fastboot boot recovery.img
Click to expand...
Click to collapse
This may result an error if you don't flash the right file,it depends on your firmware version. I have a file that works on lolipop (twrp.).

I had the same issue, as my device was on warranty period i took it to the service centre and they said the mother board is damaged

Im facing the same problem I installed a new ROM from SD card and it was successfully done but the phone is still stuck in boot loop and unfortunately my USB debugging is disabled my bootloader is locked and my phone is not rooted and it's in stock recovery can anyone please help me

BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:

I face the same bootloop problem with my mother's cellphone. The bootloader is locked and USB debug is disabled.
I tried to flash stock img via adb sideload, and although it succeed, after factory reset in Recovery (and pull battery several time) I could finally get into the "setup wizard" of Android system.
However, the system will go into bootloop again when the wizard goes to "wifi" setup. The phone will not go into setup wizard again unless I do a factory reset (and battery pull) again...
It seems there are some hardware failure at Wifi component (Since I already erase all \data, \cache), and this failure caused reboot of the system...
Any idea?

mayankarya837 said:
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
Click to expand...
Click to collapse
hey did u finnd any solution for this>???

Stuck on installing TWRP

Hello and thanks in advance to everyone,
I am trying to root my moto g4 but I am stuck on installing a recovery. I did unlock the bootloader and when I turn on the phone i am greeted with"this device is unlocked and can't be trusted"
Yet when i try to flash the recovery it states that it failed to install since the package is unsigned:
C:\Users\Jelle\Desktop\Nieuwe map>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12496 KB)...
OKAY [ 0.405s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.748s
Re-entering my unlock code also does not work as it gives me this message:
C:\Users\Jelle\Desktop\Nieuwe map>fastboot oem unlock NYRTWS*************
...
(bootloader) invalid boot state
OKAY [ -0.000s]
finished. total time: -0.000s
Does someone have any idea on what the issue is, am I missing something?
Thank you in advance!

Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk

Silesh.Nair said:
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
that totally worked! thank you very much

same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz

sauravchandela95 said:
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
Click to expand...
Click to collapse
If you're getting a screen with 'no command', that's the stock recovery on your device.
Are you rebooting to the recovery straight after flashing TWRP? Do you have an unlocked bootloader and what version of TWRP are you flashing? What commands are you using to flash?
You may wish to try booting with TWRP first:
1)On a device with an unlocked bootloader, boot to the bootloader screen.
2)Connect your device to your computer via a high quality USB data cable or the original USB cable.
3)Ensure your TWRP image is copied to your ADB folder.
4)Open an ADB terminal. Verify your device is communicating with your computer by typing 'fastboot devices' without quotes. Press Enter. You should get a serial number response.
5)If so, then type 'fastboot boot twrp.img' without quotes. Replace twrp.img with the actual full file name of your TWRP image in your ADB folder including the file extension. For example, if your TWRP image file name is shreps_twrp_3_1_1.img, the full command would be fastboot boot shreps_twrp_3_1_1.img You can type the first few letters of the file name and press Tab on your keyboard to automatically complete the file name if you so wish.
6)Press Enter, and your device should download TWRP and boot to TWRP.

Unable to flash TWRP on Moto G4 Plus

I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks

unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.

1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A

echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards

____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.

Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse

vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?

echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3

vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?

echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.

vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead

LG h918 in bootloop with only fastboot available. Help!

Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob

frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
How are you trying to boot into download mode, are you trying to do it via fastboot or the hardware buttons?

frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
im having the same problem, i dont have download more or twrp now, all i have is fastboot

i am going to assume going into download mode through fastboot is the only option for the two people posting for help here. from what i see from the posts, both hardware buttons sequence , or the plug in & down volume are the ONLY way to get to fast boot.
and fast boot is the only thing available on the phone.
i have labeled that a soft brick .
i asume one of the two help seekers have used the magisk 20.2 trap?
the release proved to be a problem , there is a tutorial on how to fix it.
i will go look for that and try to edit it into my responce later.
for now, are the two seekers already acomplished in this procedure?
TWRP Installation Tutorial for Linux Mint and Ubuntu users » AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
20.2 problem notes and fix
Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode. https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705...
forum.xda-developers.com

frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
ok i found a way to get into twrp (if ever installed)
1- turn off your phone
2- hold Volume Down + Power button until you see the LG logo
3- When you see the Logo release the power button while still holding the volume down and immediately after release press power button 3 times.
4- you will see a factory reset screen, press yes twice and it will go to twrp.
NOW WE NEED TO FIND A WAY TO FLASH A WORKING ROM THRU TWRP

TWRP boot loop after Magisk 22 upgrade

Magisk updater installed Magisk & said it needed to make a change to continue the update. I clicked the Reboot button. The phone boots into TWRP. I reboot & it goes into TWRP. Repeat.
How can I recover, preferably w/o losing apps & most preferably w/o losing data like pics?
I'm using Android 9 rooted.

kamiller42 said:
Magisk updater installed Magisk & said it needed to make a change to continue the update. I clicked the Reboot button. The phone boots into TWRP. I reboot & it goes into TWRP. Repeat.
How can I recover, preferably w/o losing apps & most preferably w/o losing data like pics?
I'm using Android 9 rooted.
Click to expand...
Click to collapse
Backup>select data and internal storage>use a computer to move the backup file out
restore then
You can also try magisk uninstaller which comes with magisk on github(seach github magisk the uninstaller is in assets)

jjgvv said:
Backup>select data and internal storage>use a computer to move the backup file out
restore then
You can also try magisk uninstaller which comes with magisk on github(seach github magisk the uninstaller is in assets)
Click to expand...
Click to collapse
Good suggestions. Came back to phone & found battery ran out. Charged up & now it boot loops to fast mode only. Argh!

fastboot flash recovery twrp.img where the recovery image should be renamed 'twrp.img' and placed in the fastboot platform tools folder.
then
fastboot reboot recovery

jjgvv said:
fastboot flash recovery twrp.img where the recovery image should be renamed 'twrp.img' and placed in the fastboot platform tools folder.
then
fastboot reboot recovery
Click to expand...
Click to collapse
Tried 3 different cables including OnePlus. Same result.
fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6t.img
downloading 'boot.img'...
OKAY [ 0.867s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.876s

kamiller42 said:
Tried 3 different cables including OnePlus. Same result.
fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6t.img
downloading 'boot.img'...
OKAY [ 0.867s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.876s
Click to expand...
Click to collapse
Sorry. I see your rename note. Same result.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.840s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.848s

I see the platform-tools note. I'm on Linux & the adb & fastboot tools are in /usr/bin, not a platform-tools folder.
Found one.
/usr/lib/android-sdk/platform-tools$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.881s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.889s

hmmmmm
fastboot oem unlock (maybe device relocked when battery rn out)

I was able to get back to TWRP by switching slots. Backup fails because Data is encrypted & TWRP is not prompting for PIN. I'll try using the Magisk uninstaller tomorrow (past bedtime). Long shot.
Open to other approaches. Thanks for your help.

kamiller42 said:
I was able to get back to TWRP by switching slots. Backup fails because Data is encrypted & TWRP is not prompting for PIN. I'll try using the Magisk uninstaller tomorrow (past bedtime). Long shot.
Open to other approaches. Thanks for your help.
Click to expand...
Click to collapse
Facing the same authenticate error when trying to boot into twrp.img. I also don't know how useful twrp will be on the other slot if it can't decrypt the data from there so stuck at this stage too.
@kamiller42 Did you manage to resolve this with the Magisk uninstaller?

spinergist said:
Facing the same authenticate error when trying to boot into twrp.img. I also don't know how useful twrp will be on the other slot if it can't decrypt the data from there so stuck at this stage too.
@kamiller42 Did you manage to resolve this with the Magisk uninstaller?
Click to expand...
Click to collapse
Nope. I tried getting by by flashing just the boot image. It erased data & everything, so I flash Android 10 again & re-rooted.

kamiller42 said:
Nope. I tried getting by by flashing just the boot image. It erased data & everything, so I flash Android 10 again & re-rooted.
Click to expand...
Click to collapse
Did you flash all partitions?
Is there a way to only flash the boot partition, then boot into twrp.img, flash that, then reboot into recovery to decrypt the data? I care more about recovering my encrypted data than getting the phone working.

spinergist said:
Did you flash all partitions?
Is there a way to only flash the boot partition, then boot into twrp.img, flash that, then reboot into recovery to decrypt the data? I care more about recovering my encrypted data than getting the phone working.
Click to expand...
Click to collapse
That's what I thought. All was lost when I flash boot image. Technically, I flashed the fast boot partition from this post. https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/