Development [ROM][Android 12L][OOS Cam][OP9Pro] crDroid v8.12 [19.12.2022]

[uses0ap]

I see 2022-09-28 release was posted on the download page-- Any changelogs ?

crDroidAndroid-12.1-20220928-lemonadep-v8.9.zip

 

[Methisfaction]

One Error i found, when switching video mode from 4k 60 to 1080p the phone freezes...

 

[uses0ap]

Experiencing a few bugs on the 30-9-2022 build:

*Split screen long press navigation actions does not work. Nothing happens when long pressed.

*Rapidly pressing app switcher causes recent apps menu to freeze/hang, sometimes nothing happens at all when pressed.

 

[hadesflames]

@gwolfu Still seeing these kinds of crashes:

crDroid paste - share logs, bugs, code and whatever else remains in plan text

paste.crdroid.net

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:

crDroid paste - share logs, bugs, code and whatever else remains in plan text

paste.crdroid.net

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.

@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.

 

[oneplus8user]

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:

adb reboot bootloader
sudo fastboot oem unlook

- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:

adb reboot bootloader
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash vendor_boot vendor_boot.img
sudo fastboot flash boot boot.img

- While still in fastboot mode use keys on phone to boot to recovery.
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then try adb devices which reveals that phone is in recovery mode.
- Run adb shell, followed by dmesg (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

 

[Smedslund]

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:

adb reboot bootloader
sudo fastboot oem unlook

- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:

adb reboot bootloader
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash vendor_boot vendor_boot.img
sudo fastboot flash boot boot.img

- While still in fastboot mode use keys on phone to boot to recovery.
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then try adb devices which reveals that phone is in recovery mode.
- Run adb shell, followed by dmesg (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

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.

 

[hadesflames]

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:

adb reboot bootloader
sudo fastboot oem unlook

- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:

adb reboot bootloader
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash vendor_boot vendor_boot.img
sudo fastboot flash boot boot.img

- While still in fastboot mode use keys on phone to boot to recovery.
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then try adb devices which reveals that phone is in recovery mode.
- Run adb shell, followed by dmesg (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

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.

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.

1. MSM tool to unbrick
2. Update phone to C.62 or C.63 on stock
3. Follow steps to unlock etc, reboot to bootloader
4. Download "OnePlus 9 Pro C.63 Firmware flasher.zip" from OP
   1. Click download from the Download KIT files part, go up a directory and then click on firmware
5. Run this tool from step 4 above which should flash C.63 firmware to both slots.
6. Continue clean flash instructions from "Enter fastboot" bullet point

That should work.

 

[Smedslund]

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.

1. MSM tool to unbrick
2. Update phone to C.62 or C.63 on stock
3. Follow steps to unlock etc, reboot to bootloader
4. Download "OnePlus 9 Pro C.63 Firmware flasher.zip" from OP
   1. Click download from the Download KIT files part, go up a directory and then click on firmware
5. Run this tool from step 4 above which should flash C.63 firmware to both slots.
6. Continue clean flash instructions from "Enter fastboot" bullet point

That should work.

You can't use MSN tool in linux..

 

[hadesflames]

You can't use MSN tool in linux..

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.

 

[Smedslund]

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.

We are looking for any other solution, is that wrong? And my phone is working fine.

 

[Appreciative]

We are looking for any other solution, is that wrong? And my phone is working fine.

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.

GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)

Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)

github.com

If link gets blocked, it's bkerler GitHub, edl


I had trouble with my laptop because of usb3. Using the livedvd and usb2 cable, I was able to dump partitions. Using the regular 9 Loader from included loaders

 

[elmasrydev]

I have oneplus 9 pro china model LE2120 and i have installed crdroid 8.9 according these steps

1. 11.2.2.2.LE15AA flash using msm-tool
name: lemonadep_22_O.05_210324.zip
size: 3.52 GB

2. 11.2.10.10.LE15AA update over ota
name: LE2125_11.C.48_1480_202204082113
size: 522 MB

3. LE2125_11_C.48 GLO update over local update
name: c25ef64fe37b632b526e0cef2f36fa046e35c032.zip
size: 4.06 GB

4. LE2125_11_C.61 GLO update over local update
name: f138da8399c3cd4479500bd5f829621ec7c6c5e1.zip
size: 1.49 GB

5. LE2125_11_C.62 GLO update over local update
name: 49b5c03b5338ea0ce5943e2b8b79cb2575a61d6a.zip
size: 128 MB

6. LE2125_11_C.63 GLO update over local update
name: 462e7319d8625be7cd2a156ebbc8651ed878760d.zip
size: 700 MB

then i used the following commands

adb reboot bootloader
fastboot flash dtbo dtbo-30.08.2022.img
fastboot flash vendor_boot vendor_boot-30.08.2022.img
fastboot flash boot boot-20221002.img
adb sideload crDroidAndroid-12.1-20220923-lemonadep-v8.9.zip
adb sideload NikGapps-core-arm64-12.1-20220908-signed.zip

as per now i have issues regarding the keystore thing

1. some apps crashes like snapchat.
2. other apps just log me out like instagram.
3. regarding google authenticator i go through importing steps and after i import accounts from other phone it shows authenticator welcome screen.
4. the most painful issue is pin unlock or pattern after few minutes or hours of using if you try to unlock screen using pin or pattern it will off screen and show you locked screen again but face and finger works fine.

so is there any procedure i should follow here ?

i have read about flashing keymaster file and by they way i didn't use c.63 firmware batch provided on the website.

i would like to keep my current setup of the rom with its app and configuration and i also noticed there are build updates of the rom available now

in short i want to fix keystore thing and update rom without losing data, how to achieve this ? thanks

 

[oneplus8user]

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.

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...

 

[oneplus8user]

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...

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:

• Despite having run 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.)
• Partitions vendor, product, and system fail with: FAILED (remote: Partition not found)
• Partition odm fails with: FAILED (remote: (odm_b) No such partition)

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.

 

[oneplus8user]

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??

 

[oneplus8user]

UPDATE: Back to where we started! Phone is now working and running stock Oxygen OS 11.2.2.2.LE15BA (Android 11)

I finally gave up and used the MSM Tool to restore my device, it worked great. A few notes which may help others:

• Download Stock ROM+MSM Tool from here. I was confused because I though the link was only the ROM (since it had a version number), but turns out the MSM Tool was inside the archive
• Download the required Qualcomm drivers from here (.exe file for simple installation) or here (.cab file which is more manual). The first one worked for me. You know you've succeeded when you connect your phone in EDL mode to your computer and Device Manager shows Qualcomm HS-USB QDLoader 9008. If it shows QHSUSB_BULK then it's not working and you need to try the second method.
• Once you have the drivers working this guide explains the steps to using the MSM Tool with pretty pictures.
• The MSM Tool took 394 seconds to flash the stock ROM

For closure on my previous posts:

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...

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.

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:

• Despite having run 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.)
• Partitions vendor, product, and system fail with: FAILED (remote: Partition not found)
• Partition odm fails with: FAILED (remote: (odm_b) No such partition)

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.

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.

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??

No clue why this happened, but when I got the stock ROM back it worked like normal again.

 

[valtronic]

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.

 

[oneplus8user]

edit: Status [UNSOLVED] I ended up switching to LineageOS instead which worked right away

Same issue again, despite starting from correct C.63 firmware!

See new dmesg output attached.

Reproduce:
1. MSM back to stock
2. Update to LE2123_11.C.61_1610_202206141855 using OOS OTA updates.
3. Used the provided C.63 firmware flasher (btw. there is a bug in the Update-firmware.sh which is not present in the .bat: it tries to flash a 'vm' partition instead of 'vm-bootsys').
4. Then I flash dtbo, vendor_boot and boot only to get the same error I did here:

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:

adb reboot bootloader
sudo fastboot oem unlook

- Boot into system and setup again, confirming in developer options that device is now unlocked, then run:

adb reboot bootloader
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash vendor_boot vendor_boot.img
sudo fastboot flash boot boot.img

- While still in fastboot mode use keys on phone to boot to recovery.
- Screen shows regular boot screen (the oneplus "+"). This screen freezes. Wait 5 minutes then try adb devices which reveals that phone is in recovery mode.
- Run adb shell, followed by dmesg (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

 

[Bugscze]

I had same problem as you before. I managed to boot into recovery but I can't remember how because I tried so many commands...

Can you try this

fastboot --set-active=other

and reflash dtbo, vendor_boot and boot again?

You can also try:

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img

I remember that was possible to boot TWRP by

fastboot boot twrp.img

 

[hadesflames]

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.

It's a rom issue. I switched to lineage, problems solved.