Resolved Sweet K6A (redmi note 12 pro 4G) keeps rebooting after flashing rom 1.0.15.0
- Thread starter MrGusRH
- Start date
- 6 Oct 2016
- 10,140
- 322
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
Welp the problem is, i couldn't even reach the OS version number on the About Phone section on the Settings, since the ROM would let us interact with the screen just a few seconds before it soft-rebooting again.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...
Plus, when i do see the main About Phone settings, looked at the version number, i see something like this:
"1.0.15.0 Unknown
by xiaomi.eu"
Meanwhile the previous version it said:
"1.0.13.0 Stable
by xiaomi.eu"
I am experiencing the same issue. After updating to version 1.0.15.0, I am stuck in an infinite reboot loop. If I downgrade to version 1.0.13.0, the Settings, Phone, Weather, and Clock apps work fine, but all other apps fail to launch.
Regarding the infinite reboot issue, let me explain in more detail. From what I understand, the boot process can be divided into two main phases:
After phase 1, the device transitions to phase 2.
In phase 1, you can see whether the device is unlocked or not in the upper part of the screen. In phase 2, if you have applied a theme, the boot animation appears.
The infinite reboot issue begins at phase 2. That is, once the boot process completes, the device runs for a short time (a few seconds) and then goes back to phase 2 to attempt to boot again.
One peculiar thing is that if I press and hold the power button to forcefully shut down the device and then reboot it, the process starts from phase 1. In this case, at least in my experience (though I cannot speak for others), the device does not reboot until I unlock it by entering the password. Interestingly, the Always On Display (AOD) functions normally during this time.
However, as soon as I unlock the device by entering the password, the reboot loop (phase 2) resumes. Once the reboot loop in phase 2 starts, the device continues to reboot infinitely even if I do not unlock it again.
Regarding the infinite reboot issue, let me explain in more detail. From what I understand, the boot process can be divided into two main phases:
- Android Boot
- Post-Boot Phase
After phase 1, the device transitions to phase 2.
In phase 1, you can see whether the device is unlocked or not in the upper part of the screen. In phase 2, if you have applied a theme, the boot animation appears.
The infinite reboot issue begins at phase 2. That is, once the boot process completes, the device runs for a short time (a few seconds) and then goes back to phase 2 to attempt to boot again.
One peculiar thing is that if I press and hold the power button to forcefully shut down the device and then reboot it, the process starts from phase 1. In this case, at least in my experience (though I cannot speak for others), the device does not reboot until I unlock it by entering the password. Interestingly, the Always On Display (AOD) functions normally during this time.
However, as soon as I unlock the device by entering the password, the reboot loop (phase 2) resumes. Once the reboot loop in phase 2 starts, the device continues to reboot infinitely even if I do not unlock it again.
- 6 Oct 2016
- 10,140
- 322
A lot of text and no logs to be found here...
Enable USB debugging using the previous build if you haven't done so previously.
Then you can record a log during booting of the newer build.
Enable USB debugging using the previous build if you haven't done so previously.
Then you can record a log during booting of the newer build.
After a forced shutdown, I logged the process from booting up again, entering the password to unlock, and then rebooting two to three times.
(I'm not sure why, but it says "sweet." However, "sweet k6a" is correct.)
log_sweet_OS1.0.15.0.THGMIXM.txt
drive.google.com
If it is possible to make a patch in order for version 1.0.13 to work, I ask the developers to do so.
- 6 Oct 2016
- 10,140
- 322
Fixed and ROM reuploaded, thanks.
"sweet" is correct. I won't go into details, it's irrelevant.
Similar threads
