I see 2022-09-28 release was posted on the download page-- Any changelogs ?
crDroidAndroid-12.1-20220928-lemonadep-v8.9.zip
crDroidAndroid-12.1-20220928-lemonadep-v8.9.zip
@gwolfu Can you please respond to this. Those 2 apps are not the only ones that are effectively unusable. There are others too, and I've noticed the system backup isn't working again which I feel like is probably related.@gwolfu Still seeing these kinds of crashes:
On 09/23 build with the keymaster flash on fastbootd having been done. This is when opening the Signal app. I notice it's not the KeyStore exception anymore though but I do also see issues like Aegis reporting that "A change in my device's security settings has been detected" which removes biometric unlock from that app.
I do also get the KeyStore exception on Bitwarden Password Manager:
Basically unable to use those 2 apps at all without restarting. After restarting Aegis allows me to unlock with fingerprint as before without needing to set it up again and everything works fine with all apps for a time until the issues start to reappear.
adb reboot bootloader
sudo fastboot oem unlook
adb reboot bootloader
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash vendor_boot vendor_boot.img
sudo fastboot flash boot boot.img
adb devices
which reveals that phone is in recovery mode. adb shell
, followed by dmesg
(see attached dmesg output)I'm running Linux to. I was ready to flash but after seeing this, I will stay on rooted stock until we find a solution.Bricked phone while trying to install on new device. Stuck in QUALCOMM CrashDump Mode. I run Linux so any suggestions which do not include MSM Tools would be great!
Reproduce:
- Get new phone out of box. It's on firmware LE2123_11_C.62
- Update to latest version (using OOS OTA, ie. don't download from https://sourceforge.net/projects/crdroid/files/lemonadep/8.x/firmware/) which is LE2123_11_C.64
- Activate developer mode, enable 'OEM unlocking' and USB debugging, then run:
- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:Code:adb reboot bootloader sudo fastboot oem unlook
- While still in fastboot mode use keys on phone to boot to recovery.Code:adb reboot bootloader sudo fastboot flash dtbo dtbo.img sudo fastboot flash vendor_boot vendor_boot.img sudo fastboot flash boot boot.img
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then tryadb devices
which reveals that phone is in recovery mode.
- Runadb shell
, followed bydmesg
(see attached dmesg output)
Bricked state:
From there I tried rebooting to system which brought me to the Qualcomm CrashDump Mode. If I boot into fastboot mode from power off state it says:
PRODUCT_NAME - lahaina
VARIANT - SM_ UFS
Bricked phone while trying to install on new device. Stuck in QUALCOMM CrashDump Mode. I run Linux so any suggestions which do not include MSM Tools would be great!
Reproduce:
- Get new phone out of box. It's on firmware LE2123_11_C.62
- Update to latest version (using OOS OTA, ie. don't download from https://sourceforge.net/projects/crdroid/files/lemonadep/8.x/firmware/) which is LE2123_11_C.64
- Activate developer mode, enable 'OEM unlocking' and USB debugging, then run:
- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:Code:adb reboot bootloader sudo fastboot oem unlook
- While still in fastboot mode use keys on phone to boot to recovery.Code:adb reboot bootloader sudo fastboot flash dtbo dtbo.img sudo fastboot flash vendor_boot vendor_boot.img sudo fastboot flash boot boot.img
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then tryadb devices
which reveals that phone is in recovery mode.
- Runadb shell
, followed bydmesg
(see attached dmesg output)
Bricked state:
From there I tried rebooting to system which brought me to the Qualcomm CrashDump Mode. If I boot into fastboot mode from power off state it says:
PRODUCT_NAME - lahaina
VARIANT - SM_ UFS
This happens when you install without having C63 on both slots. There's a tool to flash everything for you correctly before the step where you reboot into recovery and install crDroid.I'm running Linux to. I was ready to flash but after seeing this, I will stay on rooted stock until we find a solution.
You can't use MSN tool in linux..This happens when you install without having C63 on both slots. There's a tool to flash everything for you correctly before the step where you reboot into recovery and install crDroid.
That should work.
- MSM tool to unbrick
- Update phone to C.62 or C.63 on stock
- Follow steps to unlock etc, reboot to bootloader
- Download "OnePlus 9 Pro C.63 Firmware flasher.zip" from OP
- Click download from the Download KIT files part, go up a directory and then click on firmware
- Run this tool from step 4 above which should flash C.63 firmware to both slots.
- Continue clean flash instructions from "Enter fastboot" bullet point
If you're telling me you can't install Windows on a separate partition and just dual boot or borrow someone's laptop running windows or anything at all then RMA the phone.
We are looking for any other solution, is that wrong? And my phone is working fine.If you're telling me you can't install Windows on a dual boot or borrow someone's laptop running windows or anything at all then RMA the phone.
You may be able to use edl tools to flash the partitions individually. I have not tested that. I have only used the tools to dump partitions from my phone, not write them.We are looking for any other solution, is that wrong? And my phone is working fine.
Cool, I'll give it a try and post back. Before I try getting VirtualBox and usb port forwarding to work I'll see if I can't pull the hopefully working images from the other slot to repair the slot I messed up...This happens when you install without having C63 on both slots. There's a tool to flash everything for you correctly before the step where you reboot into recovery and install crDroid.
UPDATE: that did not work!Cool, I'll give it a try and post back. Before I try getting VirtualBox and usb port forwarding to work I'll see if I can't pull the hopefully working images from the other slot to repair the slot I messed up...
sudo fastboot flashing unlock_critical
and confirming with sudo fastboot oem device-info
that critical partitions are unlocked, I still get FAILED (remote: Flashing is not allowed for Critical Partitions.)VirtualBox and EDL do NOT mix. There are many posts about it, don't do it! Just install Windows 8.1 on a seperate machine and be done with it.Cool, I'll give it a try and post back. Before I try getting VirtualBox and usb port forwarding to work I'll see if I can't pull the hopefully working images from the other slot to repair the slot I messed up...
It turns out Android now uses something called Dynamic Partitions which implies that vendor, product, and system are all baked into a super partition... long story short I would avoid the above method.UPDATE: that did not work!
I switched to the other slot and tried booting the system without sucess, so I figured it wouldn't help copying that to the other slot.
Next I tried downloading the stock rom from oneplus.com, extracting all the .img files from the payload.bin within the rom.zip and flashing them but ran into 3 problems:
Finally I tried flashing the LineageOS recovery following these instructions since they only specify you need to be on Android 12, not a specific firmware. The flash succeeded, but I when I try booting into recovery it just returns me to fastboot.
- Despite having run
sudo fastboot flashing unlock_critical
and confirming withsudo fastboot oem device-info
that critical partitions are unlocked, I still get FAILED (remote: Flashing is not allowed for Critical Partitions.)- Partitions vendor, product, and system fail with: FAILED (remote: Partition not found)
- Partition odm fails with: FAILED (remote: (odm_b) No such partition)
No clue why this happened, but when I got the stock ROM back it worked like normal again.I also have a new problem: the phone won't charge!
I've tried multiple chargers (both new fastcharge ones, old 1A ones, and straight into laptop usb ports) and cords, all of which work with other phones, but no luck! Using power meters (both in wall socket and in laptop usb) I can see it drawing minimal current (0.02A @ 230VAC and [email protected] respectively) but when I try booting I just get the red lightningbolt...
How could this have happened??
Bricked phone while trying to install on new device. Stuck in QUALCOMM CrashDump Mode. I run Linux so any suggestions which do not include MSM Tools would be great!
Reproduce:
- Get new phone out of box. It's on firmware LE2123_11_C.62
- Update to latest version (using OOS OTA, ie. don't download from https://sourceforge.net/projects/crdroid/files/lemonadep/8.x/firmware/) which is LE2123_11_C.64
- Activate developer mode, enable 'OEM unlocking' and USB debugging, then run:
- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:Code:adb reboot bootloader sudo fastboot oem unlook
- While still in fastboot mode use keys on phone to boot to recovery.Code:adb reboot bootloader sudo fastboot flash dtbo dtbo.img sudo fastboot flash vendor_boot vendor_boot.img sudo fastboot flash boot boot.img
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then tryadb devices
which reveals that phone is in recovery mode.
- Runadb shell
, followed bydmesg
(see attached dmesg output)
Bricked state:
From there I tried rebooting to system which brought me to the Qualcomm CrashDump Mode. If I boot into fastboot mode from power off state it says:
PRODUCT_NAME - lahaina
VARIANT - SM_ UFS
fastboot --set-active=other
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot boot twrp.img
It's a rom issue. I switched to lineage, problems solved.Some apps (Signal, Wise banking, Slack, Lastpass + Authenticator) keep crashing or loosing their Logins ever since the 23.09 build for me. I can only fix this by rebooting. Is that a rom problem or a rooting problem? Guess I would have to try the rom without root.
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot boot.img
adb sideload crDroid.zip
adb sideload crDroid.zip
guess anyone can install gapps when they want google stuff added