Open cortjehster opened 3 years ago
I'd like to confirm that the same thing and message happens to me when I try to 'fastboot boot' the latest available TWRP for Oneplus 6T 'fajita'.
ROM I updated to is stock OxygenOS 11.1.1.1 ROM is based on Android 11.
I also have this problem
Hey guys,
Same issue here, tryed to flash TWRP "fajitas" on my OP6t with OOS 11 something and I am now stucked in QUALCOMM Crashdump mode with the following error message :
Attempted to kill init! exitcode=0x0000000b
complete_and_exit
Although I have tryed multiple times to put my phone in Fastboot mode it always reboots and crashes in this mode.
adb devices
and fastboot devices
cli do not print out any available device and I am not on Windows but on MacOS so I cannot use msm
or download qualcomm crashmode
drivers...
Anyone with any helpfull piece of advise ?
Too bad... happened for me now:
Device: OnePlus 9 (not pro) Android: 12 Build number: LE2113_11_C.64 Kernel version: 5.4.147-qgki-g2f286f199c5a
Edit: rolled back to Android 11 and it's working again. Oxygen OS 11.2.10.10.LE25BA. Will try successively to see, which update it'll break (while trying to avoid Android 12) Edit: as soon as the update with Android 12 comes, twrp wasn't possible anymore
Device codename: fajita TWRP version: 3.5.2_9-0
WHAT STEPS WILL REPRODUCE THE PROBLEM?
From bootloader: fastboot boot twrp-3.5.2_9-0-fajita.img
WHAT IS THE EXPECTED RESULT?
TWRP loads as usual.
WHAT HAPPENS INSTEAD?
Phone crashes with message on screen: Qualcomm crashdump exitcode=0x0000000b
ADDITIONAL INFORMATION
This only happened after an OTA update from OnePlus. Prior to the OTA upgrade, TWRP worked perfectly. OxygenOS 11. Build number: ONEPLUS A6013_41_210805
/tmp/recovery.log
: (there is no /tmp)dmesg
: (cannot install su to access dmesg)