HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


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.
 

Attachments

  • log.zip
    1.9 MB · Views: 29
Last edited:
  • Like
Reactions: Ramin Majidi
rednotec said:
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.
Click to expand...
You would have to record a log as the reboot happens, not after the device already rebooted.
 
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.
 

Attachments

  • received_1315531166125312.jpeg
    received_1315531166125312.jpeg
    173.4 KB · Views: 51
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...
xiaomitime.com

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

Is this a beta?
 
Jason Lin said:
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.
Click to expand...
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.
 
Igor Eisberg said:
You would have to record a log as the reboot happens, not after the device already rebooted.
Click to expand...
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?
 
rednotec said:
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?
Click to expand...
xiaomi.eu

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 xiaomi.eu
rednotec said:
Does the device need to be connected to a computer using adb to monitor the logs in real-time?
Click to expand...
Yes.
 
Igor Eisberg said:
xiaomi.eu

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

Yes.
Click to expand...
Thank you for your guidance. I have started recording the logs as instructed and am now waiting for the device to experience the automatic reboot. Since the issue occurs consistently after two hours of screen lock, I will upload the logs once the reboot happens.
 
Hello,

I am in Os 2.0.3.0, I want to update to Os 2.0.100.0, I do the download, but when it restarts in Twrp it does not ask me for the password and the phone memory is in Omb (no access to files). Do you know where the problem comes from?

Thank you, greetings.

Julio
 
bpjulio7 said:
Hello,

I am in Os 2.0.3.0, I want to update to Os 2.0.100.0, I do the download, but when it restarts in Twrp it does not ask me for the password and the phone memory is in Omb (no access to files). Do you know where the problem comes from?

Thank you, greetings.

Julio
Click to expand...
Your TWRP is outdated. Flash newer recovery.
 
AlexvdHorst said:
I just got this OTA Update bit Xiaomi 13Pro Nuwa OS2.0.100.0.VMBCNXM
Is this Xiaomi EU from or China?

xiaomitime.com

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 xiaomitime.com
Click to expand...
Updated Nuwa and works like a charm for me. Happy with the icon grid change. Although i also hope for 5x7 ☺️
Thanks a lot devs
 
Last edited:
  • Like
Reactions: Cedric42
Igor Eisberg said:
xiaomi.eu

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

Yes.
Click to expand...
The link to the forum post with details about the issue is:
https://xiaomi.eu/community/threads/hyperos-2-0-stable-release.74372/page-54#post-741352

I have record the logs during the automatic reboot event and uploaded it as an attachment for your analysis.

Please review the attached logs and let me know if further data or specific actions are needed to assist in resolving the issue.
 

Attachments

  • log_dada_OS2.0.103.0.VOCCNXM.7z.zip
    1.2 MB · Views: 18
I previously asked if anyone with a POCO F6 is experiencing frequent freezes followed by reboots. For those with the same problem, it was caused by the fact that every time I have reset the phone, I restored apps using the Google Backup. I previously had a Poco F3 and most likely Google Backup overwrote some stuff from the factory apps (like the launcher) and caused crashes.

Now I can happily say all I had to do was do a reset and skip reinstalling the apps from a backup. Works very well.
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
376K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
45K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
49K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
60K
HyperOS
KGVER
KGVER
ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
35K
HyperOS
emre_66
E
Top Bottom
Back