HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

[rednotec]

Persistent Auto-Reboot Issue After Two Hours of Screen Lock (ro.boot.bootreason: reboot,vold-failed)

I am reporting a persistent issue encountered on my Xiaomi 15 device after installing EU ROM.

Issue Description:
The device functions normally during active use (screen on) and short periods of screen lock.
However, if the screen remains locked for two hours, the device will automatically reboot.

After rebooting, the device successfully enters the system and functions normally again, if the screen is locked for another two hours, the device will reboot once more.

Investigation Findings:
After each reboot caused by this issue, the property ro.boot.bootreason is set to:
reboot,vold-failed

I kindly request your assistance in investigating and resolving this issue. The problem is reproducible and occurs without fail after a two-hour screen lock.

Please let me know if you need additional logs, device information, or specific testing to help diagnose this problem.

 

[Igor Eisberg]

Persistent Auto-Reboot Issue After Two Hours of Screen Lock (ro.boot.bootreason: reboot,vold-failed)

I am reporting a persistent issue encountered on my Xiaomi 15 device after installing EU ROM.

Issue Description:
The device functions normally during active use (screen on) and short periods of screen lock.
However, if the screen remains locked for two hours, the device will automatically reboot.

After rebooting, the device successfully enters the system and functions normally again, if the screen is locked for another two hours, the device will reboot once more.

Investigation Findings:
After each reboot caused by this issue, the property ro.boot.bootreason is set to:
reboot,vold-failed

I kindly request your assistance in investigating and resolving this issue. The problem is reproducible and occurs without fail after a two-hour screen lock.

Please let me know if you need additional logs, device information, or specific testing to help diagnose this problem.

You would have to record a log as the reboot happens, not after the device already rebooted.

 

[Pakino2004]

F6 update successful. It seems the whitebarproblem of the navbar is gone in WhatsApp.

 

[Jason Lin]

My device is xiaomi 13 ultra, currently under hyperos 1.0.17 and TWRP 15A. i dowanloaded lateset 2.0.100 ROM through updater and soirceforge, but both files failed to pass both digest verification and zip signature verification.

Actuall i met this problem from 1.0.20 and 2.0.3, so i stayed at 1.0.17. For test purpose, i can still re-install 1.0.17succesuflly, it passed digest and zip signature verification without issue.

Please advise should I skip both digest and zip signature verification? Thanks.

 

[poweruser44]

Just dirty flashed OS2.0.100.0.VMBCNXM on my nuwa, unrooted and deleted magisk, so far the battery is the same as usual, which is actually commendable for an used device with 400 something battery cycles... Also the versioning number is different now..? In line with Xiaomis Hyperos OS2 beta apparently...

HyperOS 2.1 Beta update released for Xiaomi 13 series - XiaomiTime

On January 17, Xiaomi announced the rollout of the official HyperOS 2 internal beta for the Xiaomi 13 series. This update is only available to users with the

xiaomitime.com

Is this a beta?

 

[Igor Eisberg]

My device is xiaomi 13 ultra, currently under hyperos 1.0.17 and TWRP 15A. i dowanloaded lateset 2.0.100 ROM through updater and soirceforge, but both files failed to pass both digest verification and zip signature verification.

Actuall i met this problem from 1.0.20 and 2.0.3, so i stayed at 1.0.17. For test purpose, i can still re-install 1.0.17succesuflly, it passed digest and zip signature verification without issue.

Please advise should I skip both digest and zip signature verification? Thanks.

Only zip signature verification has to be disabled, our ZIPs are not signed.
As for digest, check that the MD5 hash matches the one on SourceForge.

 

[Pakino2004]

F6 update successful. It seems the whitebarproblem of the navbar is gone in WhatsApp

Uff reboot I did already. Hopefully updater settles down

 

[rednotec]

You would have to record a log as the reboot happens, not after the device already rebooted.

Thank you for your response.
Could you please provide detailed instructions on how to record logs as the reboot happens? Specifically:

Does the device need to be connected to a computer using adb to monitor the logs in real-time?
Are there specific adb commands or steps to set up continuous log monitoring and capture logs at the moment of reboot?

 

[Igor Eisberg]

Thank you for your response.
Could you please provide detailed instructions on how to record logs as the reboot happens? Specifically:
...
Are there specific adb commands or steps to set up continuous log monitoring and capture logs at the moment of reboot?

Logging with ADB Logcat

Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...

xiaomi.eu

Does the device need to be connected to a computer using adb to monitor the logs in real-time?

Yes.

 

[Jason Lin]

Only zip signature verification has to be disabled, our ZIPs are not signed.
As for digest, check that the MD5 hash matches the one on SourceForge.

Thanks for prompt reply, i just upgraded it succesfully. Thanks for your effort.