Development [ROM][13][OOS Cam][OP9Pro] crDroid v9.5 [26.05.2023]

[gwolfu]

:/


I can only find C.62 rom

that should it
"best bet is to flash OOS 12 c.62/63"

 

[DonnerPlays]

that should it
"best bet is to flash OOS 12 c.62/63"

yeah and then only do:
- fastboot flash dtbo dtbo.img
- fastboot flash vendor_boot vendor_boot.img
- fastboot flash boot boot.img
- reboot to recovery
- adb sideload crDroid.zip


without using the firmware updater script to go to C.63 first. Correct?

 

[DonnerPlays]

that should it
"best bet is to flash OOS 12 c.62/63"

still same error. Changed absolutely nothing

 

[DonnerPlays]

Well... It may have turned out to be the usb cable.
No idea why because I never had issues with it up until now and anything else up until sideloading also worked.

The usb cable from my oneplu 6T works it seams

 

[DonnerPlays]

interstingly changing the usb cable (or port because I did both) also fixed all the "partition does not support slot messages from the firmware flasher"

 

[TheSayaMan]

You are making it more difficult than it needs to be. I hate repeating myself but too many people ask questions without reading through the thread. READ!!!!! You don't need to update all the way. Just MSM to a11 then use the C.63 firmware flasher to install firmware and recovery then you can flash rom in custom recovery. Also you can't use stock recovery to flash custom roms, they will always result in errors.

 

[TheSayaMan]

Anyone have an idea why I'm getting "kDownloadTransferError" when trying to sideload the crDroid.zip)
It happens immediately at 0% progress.


After bringing my phone into a bootloop trying to get from DerpFest to crDroid I recovered my phone with the MSM Tool.
Updated up to Android 12 (I also got an update for C.66 but didn't do that one)
- Unlocked bootloader
- went into fastboot
- followed the guide without the firmware flasher (Thinking I wouldn't need it now)
- tried sideloading the crDroid.zip
- "kDownloadTransferError"

I tried the tool as well but always get the same error.

I'm now recovering with MSM again. Any ideas in which order I should do things now??

You are making it more difficult than it needs to be. I hate repeating myself but too many people ask questions without reading through the thread. READ!!!!! You don't need to update all the way to a12. Just MSM back to a11 then use the C.63 firmware flasher to install firmware and recovery then you can flash rom in custom recovery. Also you can't use stock recovery to flash custom roms, they will always result in errors. If you still have problems then it's a bad download. Re-download ROM.

 

[DonnerPlays]

You are making it more difficult than it needs to be. I hate repeating myself but too many people ask questions without reading through the thread. READ!!!!! You don't need to update all the way to a12. Just MSM back to a11 then use the C.63 firmware flasher to install firmware and recovery then you can flash rom in custom recovery. Also you can't use stock recovery to flash custom roms, they will always result in errors. If you still have problems then it's a bad download. Re-download ROM.

I know I don't have to update all the way to Android 12 myself but going from Android 11 didn't work either

As you can read (If you would have READ!!!!!) it was caused by the cable but only when trying to sideload.
I also never said I used a stock recovery.

 

[DirtryElectroOP3]

:/


I can only find C.62 rom

msm back to oos11, download oos c.48 full ota here (c.48 is the last full ota, later ones are all incremental), flash the zip in both slots via twrp and from there use the provided c.63 flasher. reboot to recovery, flash the rom and everything should be working. (you can actually use the c.63 flasher directly from oos11, but to be on the safe side, i flashed c.48 in between. worked for me.)

edit: nvm didn't see that it was caused by the cable sorry

 

[TheSayaMan]

msm back to oos11, download oos c.48 full ota here (c.48 is the last full ota, later ones are all incremental), flash the zip in both slots via twrp and from there use the provided c.63 flasher. reboot to recovery, flash the rom and everything should be working. (you can actually use the c.63 flasher directly from oos11, but to be on the safe side, i flashed c.48 in between. worked for me.)

edit: nvm didn't see that it was caused by the cable sorry

As I previously stated, YOU DO NOT NEED TO UPDATE TO A12!!!!! JUST MSM BACK TO A11 THEN USE THE PROVIDED C.63 FIRMWARE!!!!!

 

[DirtryElectroOP3]

As I previously stated, YOU DO NOT NEED TO UPDATE TO A12!!!!! JUST MSM BACK TO A11 THEN USE THE PROVIDED C.63 FIRMWARE!!!!!

yea i said this too but i had problems by doing so, so i flashed c.48 in between. but i aint forcing nobody to do so, it just worked for me

 

[Tierri]

yea i said this too but i had problems by doing so, so i flashed c.48 in between. but i aint forcing nobody to do so, it just worked for me

Same for me!

 

[abeloman]

As I previously stated, YOU DO NOT NEED TO UPDATE TO A12!!!!! JUST MSM BACK TO A11 THEN USE THE PROVIDED C.63 FIRMWARE!!!!!

That didnt work for me, using LE2123...

Using c.63 flasher right after MSM, bricks my phone.

Script never finish because it waits for fastbootD mode, which phone never boot (black screen).

I have to recover with MSM again.

 

[DonnerPlays]

That didnt work for me, using LE2123...

Using c.63 flasher right after MSM, bricks my phone.

Script never finish because it waits for fastbootD mode, which phone never boot (black screen).

I have to recover with MSM again.

I'm guessing you unlocked the bootloader and booted into fastboot before running the script?

 

[keshav26]

Hi, I am having an issue with the charging ( had the same issue with android 12)... After plugin the charger the phone will do a sound and start charging my problem is that my phone keeps emmiting this sound every 30 s. It's like I am plugin the phone for charging every 30s
I didn't have this issue with OOS...

 

[93zx7]

Just to be clear... Can you update CrDroid8 to CrDroid9 via the update steps method in post #1? aka dirty flash?

 

[chefcesarpr]

Just to be clear... Can you update CrDroid8 to CrDroid9 via the update steps method in post #1? aka dirty flash?

I did it that way on the first build of a13, but got some bugs. Clean Install eliminated the bugs.

 

[93zx7]

Netflix is broken. Currently looking for a work-around

 

[93zx7]

Hulu is also broken

 

[TheSayaMan]

Netflix is broken. Currently looking for a work-around

Not the case for me. Works fine.