jamiehawman said:

hi brettroth do i just fastboot boot this file img will this have all the file names normal, but then what twrp zip do i install :/

Genlead said:

When I flash this twrp.img, I can't permanently install twrp from the zip because the internal storage is encrypted.

This zip should decrypt on a11. If not let me know I have others I know one of them works.

Brettroth said:

This zip should decrypt on a11. If not let me know I have others I know one of them works.

I just installed via sideload and my internal storage is still encrypted.

Brettroth said:

Try this one lol. I am on a13 and this decrypts. I don't wanna go back and test things but I'm pretty sure there was a twrp that decrypted a11. A12 and 13 works no prob

It worked, thank you!

Brettroth said:

does this decrypt lineage-20.0-20230223-nightly-fajita-signed.zip ? (last nightly)
I asking because Siddik's version (https://forum.xda-developers.com/t/recovery-11-12-13-unofficial-twrp-for-oneplus-6-6t.4382121/)
stopped decrypting since this one

I'm looking for help recovering from my own stupidity. I was planning to update the LineageOS on my phone. It also has/had Lineage Recovery installed. I wanted to make a backup using TWRP and for that I wanted to boot briefly into TWRP's recovery.

I tried booting TWRP using fastboot boot twrp-3.7.0_9-0-fajita.img.

Sending the image went through, but booting failed with FAILED (remote: 'Unrecognized command boot').

So, I decided to flash the image instead with fastboot flash boot twrp-3.7.0_9-0-fajita.img. That worked. But after rebooting an error was shown. Something like "init exited". I didn't take a note. I rebooted again, expecting it to fall back to the other partition. But it didn't. Same error was shown again.

Finally, I attempted to reboot into recovery, holding VOL DOWN + POWER. The phone/screen would turn off, but it wouldn't reboot at all. Now it doesn't show any sign of activity no matter what buttons I use to try to boot it.

Have I successfully bricked my phone? Or is there something else I could try? I'm hoping for the latter.

UPDATE:

I managed to start the phone with VOL UP + POWER (holding for an unusual long time). The error message reads:

QUALCOMM CrashDump Mode ----------------------- Attempted to kill init! exitcode=0x0000000b complete_and_exit

Penguinpee said:

I'm looking for help recovering from my own stupidity. I was planning to update the LineageOS on my phone. It also has/had Lineage Recovery installed. I wanted to make a backup using TWRP and for that I wanted to boot briefly into TWRP's recovery.

I tried booting TWRP using fastboot boot twrp-3.7.0_9-0-fajita.img.

Sending the image went through, but booting failed with FAILED (remote: 'Unrecognized command boot').

So, I decided to flash the image instead with fastboot flash boot twrp-3.7.0_9-0-fajita.img. That worked. But after rebooting an error was shown. Something like "init exited". I didn't take a note. I rebooted again, expecting it to fall back to the other partition. But it didn't. Same error was shown again.

Finally, I attempted to reboot into recovery, holding VOL DOWN + POWER. The phone/screen would turn off, but it wouldn't reboot at all. Now it doesn't show any sign of activity no matter what buttons I use to try to boot it.

Have I successfully bricked my phone? Or is there something else I could try? I'm hoping for the latter.

UPDATE:

I managed to start the phone with VOL UP + POWER (holding for an unusual long time). The error message reads:

QUALCOMM CrashDump Mode ----------------------- Attempted to kill init! exitcode=0x0000000b complete_and_exit

Click to expand...

Lesson learned: don't flash a recovery img that doesn't boot. Have you managed to send fastboot commands to the device? If at all possible, flash another TWRP version. Otherwise, try this Msm tool (for T-Mobile, use this one instead).

Timmmmaaahh! said:

Lesson learned: don't flash a recovery img that doesn't boot. Have you managed to send fastboot commands to the device? If at all possible, flash another TWRP version. Otherwise, try this Msm tool (for T-Mobile, use this one instead).

Penguinpee said:

I'm not quite sure what you mean by "a recovery img that doesn't boot". Is that what the FAILED (remote: 'Unrecognized command boot') was trying to tell me? That the image cannot be booted? That would indeed be a hard learned lesson.

Yes, that would've been the cue for me to try another image.

Penguinpee said:

Should I be able to get into fastboot, I could go back to flashing Lineage Recovery image or an older version of TWRP (provided that works. Or maybe switch the device to the other slot?

Actually, yeah, fastboot should still work but things can go wrong I guess. That's the entire idea: when the recovery partition gets corrupted it should be possible to flash another one via fastboot. You may need to flash an official 1+ image first. Not sure how you'd switch partitions without fastboot. I'm afraid msm only works in Windows, nothing a VM can't handle.