[ROM][13.0][OFFICIAL][Rolex/Riva] crDroid 9.x

[enjoy_life]

you're the only one. Probably currupted .zip, check hash sum.

The thing is I updated via OTA and the process went smoothly (no errors during update in logs), it's just the device didn't boot up afterwards. Then I wiped the phone in recovery, did a format, downloaded the latest build on PC, transferred it to the phone and installed from scratch from recovery. The phone didn't boot up. There where no errors in the logs during installation.

I can open the archive and view/extract all files, so it's definitely not corrupted.

Then I downloaded the previous build from November 19, installed it from scratch and it did boot up, just as I expected.

I'm not sure what's going on but I guess I'll just wait till the next update.

 

[iusmac]

This build is unbootable. The phone didn't boot up after OTA; stuck on a black screen. I did a clean install and it still didn't boot up. I had to revert to the previous (November 19) build, which boots just fine.

Redmi 5A.

then, what does it mean "stuck on a black screen"? The only "black screen" you may see is when the phone is completely off, otherwise you should see the Mi logo or crDroid bootanimation. Clarify, please.

 

[enjoy_life]

then, what does it mean "stuck on a black screen"? The only "black screen" you may see is when the phone is completely off, otherwise you should see the Mi logo or crDroid bootanimation. Clarify, please.

I can see the MI logo with "Unlocked" status when the phone boots up. Then it transitions into black screen and nothing else happens. Normally we should see the CrDroid boot animation at that point, but not in my case. I need to press Volume up + Power to force the phone to reboot to recovery. Booting to fastboot also works.

The previous build from November works just fine right now. If I proceed with the OTA, Local Update, or even clean flashing this new December build again, the issue will be reproduced 100%. I spent like 3 hours yesterday trying to figure out what's going on. I ended up flashing the previous build for now, which doesn't have any issues.

 

[iusmac]

I can see the MI logo with "Unlocked" status when the phone boots up. Then it transitions into black screen and nothing else happens. Normally we should see the CrDroid boot animation at that point, but not in my case. I need to press Volume up + Power to force the phone to reboot to recovery. Booting to fastboot also works.

The previous build from November works just fine right now. If I proceed with the OTA, Local Update, or even clean flashing this new December build again, the issue will be reproduced 100%. I spent like 3 hours yesterday trying to figure out what's going on. I ended up flashing the previous build for now, which doesn't have any issues.

Yeah, as I thought, for some reason the kernel panics and shuts down the phone. This is critical issue. Can be due to some peripherals (ex. bad MicroSD card filesystem). Anyway, this most likely won't be fixed, as you're the only one with this issue. I need logs to help you. When the phone goes off, boot directly to recovery and send me the file in path /sys/fs/pstore/console-ramoops-0

 

[nitinule]

Gone through the whole thread and flashed both the above given file 5 times whole format and clean install and almost all the things

NO Network at all. Not even for single SIM.

Any final solution?

 

[iusmac]

Gone through the whole thread and flashed both the above given file 5 times whole format and clean install and almost all the things

NO Network at all. Not even for single SIM.

Any final solution?

ofc I assume you strictly followed the flushing instructions, using correct recovery and getting no errors when flashing firmware, persist etc, otherwise you have some that you ignored or the device has hardware issues (bad sim, bad slot, motherboard damage etc.). Try other ROMs based on different android versions, also try stock. Isolate the problem, so far no one in telegram group has complained about this issue, everything is working fine.

 

[nitinule]

ofc I assume you strictly followed the flushing instructions, using correct recovery and getting no errors when flashing firmware, persist etc, otherwise you have some that you ignored or the device has hardware issues (bad sim, bad slot, motherboard damage etc.). Try other ROMs based on different android versions, also try stock. Isolate the problem, so far no one in telegram group has complained about this issue, everything is working fine.

Thanks Bro.. Shall try old releases to check if there is harware issue
I am using Orange Fox recovery
best

 

[insadf]

Hi, just reporting issues faced flashing this ROM:
-Latest build resulted in same behaviour as described by enjoy_life:

I can see the MI logo with "Unlocked" status when the phone boots up. Then it transitions into black screen and nothing else happens. Normally we should see the CrDroid boot animation at that point, but not in my case. I need to press Volume up + Power to force the phone to reboot to recovery. Booting to fastboot also works.

The previous build from November works just fine right now. If I proceed with the OTA, Local Update, or even clean flashing this new December build again, the issue will be reproduced 100%. I spent like 3 hours yesterday trying to figure out what's going on. I ended up flashing the previous build for now, which doesn't have any issues.

-Previous build crDroidAndroid-13.0-20221119-rova-v9.0.zip booted ok.
-Next I found MAC address for Wifi or Bluetooth was missing so neither of them worked. Tried flashing back to MIUI10 stock ROM resulted with WIFI and Bluetooth working again. After flashing again crDroid and then an image of the persist partition both Wifi and Bluetooth started working. I don't have a clue how this goes but it seems OrangeFox Recovery touches something in the persist partition that "breaks" at least Wifi and Bluetooth. In fact OrangeFox complains about some dependencies after flashing the persist partition. Don't know whether it is a known behaviour or I have done something wrong.

Either way thanks for keeping this phone alive

 

[iusmac]

Hi, just reporting issues faced flashing this ROM:
-Latest build resulted in same behaviour as described by enjoy_life:

-Previous build crDroidAndroid-13.0-20221119-rova-v9.0.zip booted ok.
-Next I found MAC address for Wifi or Bluetooth was missing so neither of them worked. Tried flashing back to MIUI10 stock ROM resulted with WIFI and Bluetooth working again. After flashing again crDroid and then an image of the persist partition both Wifi and Bluetooth started working. I don't have a clue how this goes but it seems OrangeFox Recovery touches something in the persist partition that "breaks" at least Wifi and Bluetooth. In fact OrangeFox complains about some dependencies after flashing the persist partition. Don't know whether it is a known behaviour or I have done something wrong.

Either way thanks for keeping this phone alive

You have to flash persist every time you abandon MIUI otherwise your BT, Wifi, sensors etc. will break due to missing files. This is known for years as this ROM (like many others) is unified for rolex/riva and persist is used as a storage for dependencies. Orangefox recovery is using persist for dependencies as well.
Again, I'm not a magician, either you send me logs or don't even waste time to report issues, this can't be fixed randomly.

 

[insadf]

You have to flash persist every time you abandon MIUI otherwise your BT, Wifi, sensors etc. will break due to missing files. This is known for years as this ROM (like many others) is unified for rolex/riva and persist is used as a storage for dependencies. Orangefox recovery is using persist for dependencies as well.
Again, I'm not a magician, either you send me logs or don't even waste time to report issues, this can't be fixed randomly.

Hi,
my fault then for not knowing about the persist partition issue. Other than that the ROM goes perfect
My post was intended only to help someone else having the same troubles as I had.
Thank you either way

 

[iusmac]

crDroid 9 Update

Spoiler: Changelog

- Synced with crDroid 9.0 sources (December security patches).
- Upgraded kernel to 4.9.336-3.5-iusmac
- Added Google Settings Intelligence app prebuilt
* adds some features
* fixes crashes after reboot
* allows to search XiaomiParts features in Settings
- Fixed inaccurate touchscreen interruption in-pocket mode after touchscreen
driver downgrade from k3.18
- Fixed incorrect battery usage stats
- Tweaked RAM to keep as many background apps as possible
- Switched zRAM compression algorithm to Zstandard
* more RAM due to better compression ratio
- crDroid Settings: Added Parallel Space for apps
- crDroid Settings: Dropped power menu styles (unstable for now)
- Optimized graphics render engine
- Optimized overall performance
- Updated translations

 

[nitinule]

The Rom got installed perfectly last time but both sim cards had no network. Wifi was working perfect
Then i went to local Repair market. He said he changed the IC and flashed the base MIUI 9 Oreo and Both sims were working fine. but it was MIUI 9 with hell lot of blotware.
today morning I again flashed with crDroidAndroid-13.0-20221204-rova-v9.0 and the Network both sims got disconnected.

Again today I flashed 18 December Update file but got this error. Bot sims not working now. No Network.
I have 7 Phones and all are flashed on Android 13 by me. but Something is going wrong with my this phone. I am flashing phones since 2009 (Nokis N8)

Getting this error now

 

[iusmac]

The Rom got installed perfectly last time but both sim cards had no network. Wifi was working perfect
Then i went to local Repair market. He said he changed the IC and flashed the base MIUI 9 Oreo and Both sims were working fine. but it was MIUI 9 with hell lot of blotware.
today morning I again flashed with crDroidAndroid-13.0-20221204-rova-v9.0 and the Network both sims got disconnected.

Again today I flashed 18 December Update file but got this error. Bot sims not working now. No Network.
I have 7 Phones and all are flashed on Android 13 by me. but Something is going wrong with my this phone. I am flashing phones since 2009 (Nokis N8)

Getting this error now

just flash firmware and persist when you're abandoning MIUI.

 

[nitinule]

just flash firmware and persist when you're abandoning MIUI.

Thanks

But yesterday I did clean format. all parts except MMC
then I flashed firmware
then persist
then latest firmware.
wipe cache
still got same above issue

regards
Nitin

 

[iusmac]

Thanks

But yesterday I did clean format. all parts except MMC
then I flashed firmware
then persist
then latest firmware.
wipe cache
still got same above issue

regards
Nitin

it should work. It works for all other users (me including), probably the issue is on your side.

 

[iusmac]

The thing is I updated via OTA and the process went smoothly (no errors during update in logs), it's just the device didn't boot up afterwards.
[...]
Then I downloaded the previous build from November 19, installed it from scratch and it did boot up, just as I expected.

this will be fixed in the next release after crDroidAndroid-13.0-20221218-rova-v9.0.zip. Wait for an OTA.

 

[enjoy_life]

this will be fixed in the next release after crDroidAndroid-13.0-20221218-rova-v9.0.zip. Wait for an OTA.

Thank you! I was too bloody lazy to start over and provide the logs. Happy it's fixed!

 

[liaotingwei]

you're the only one. Probably currupted .zip, check hash sum.

Hello author, I have encountered the same problem. Android 12 does not have this problem. Android 13 version will black screen and power off when booting. There is no red word error during the entire installation process. I use the Chrome browser to download. Now I try to change other downloaders to see if it’s a zip problem. Some people found this problem on Chinese forums. It’s probably not an isolated case. I’m here to comment and reply, thank you

 

[liaotingwei]

Hello author, I have encountered the same problem. Android 12 does not have this problem. Android 13 version will black screen and power off when booting. There is no red word error during the entire installation process. I use the Chrome browser to download. Now I try to change other downloaders to see if it’s a zip problem. Some people found this problem on Chinese forums. It’s probably not an isolated case. I’m here to comment and reply, thank you

After testing, it still turns on a black screen, the old version does not have this problem

 

[iusmac]

Hello author, I have encountered the same problem. Android 12 does not have this problem. Android 13 version will black screen and power off when booting. There is no red word error during the entire installation process. I use the Chrome browser to download. Now I try to change other downloaders to see if it’s a zip problem. Some people found this problem on Chinese forums. It’s probably not an isolated case. I’m here to comment and reply, thank you

you don't need to duplicate the issue. As I said it will be fixed in the next OTA update. For now use cr9 build from November 19.