Soft reboot after logging in


vient

Members
Jan 5, 2021
5
3
Hello! I tried to upgrade from 11.0.2.0 to 12.0.6.0 but now MIUI is soft rebooting ~20 seconds after logging in. I tried removing SIM card, wiping caches, nothing changed. What can I do to debug this issue? I would prefer not to do complete wipe.

Edit: I saw info about incompatible Magisk version (I had 20.4), so I tried to upgrade it to 21.2, then to delete it, still have reboots.
 
Last edited:

vient

Members
Jan 5, 2021
5
3
Does not look good, I guess

Code:
01-06 04:40:59.716 15027 15065 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
01-06 04:40:59.716 15027 15065 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=91; index=10004
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at android.app.AppOpsManager$1.opChanged(Unknown Source:15)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.server.appop.AppOpsService.notifyOpChanged(Unknown Source:18)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.server.appop.AppOpsService.notifyOpChanged(Unknown Source:13)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.server.appop.AppOpsService.lambda$NDUi03ZZuuR42-RDEIQ0UELKycc(Unknown Source:0)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.server.appop.-$$Lambda$AppOpsService$NDUi03ZZuuR42-RDEIQ0UELKycc.accept(Unknown Source:18)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.internal.util.function.pooled.PooledLambdaImpl.doInvoke(Unknown Source:655)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.internal.util.function.pooled.PooledLambdaImpl.invoke(Unknown Source:125)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.internal.util.function.pooled.OmniFunction.run(Unknown Source:10)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at android.os.Handler.handleCallback(Unknown Source:2)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Unknown Source:4)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at android.os.Looper.loop(Unknown Source:242)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at android.os.HandlerThread.run(Unknown Source:28)
01-06 04:40:59.716 15027 15065 E AndroidRuntime:        at com.android.server.ServiceThread.run(Unknown Source:12)
Besides that, there is a ton of messages regarding missing permissions. Speaking of exactly this thread, I also found

Code:
01-06 04:40:56.605 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver
01-06 04:40:56.605 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-06 04:40:56.606 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.broadcastreceiver.external.ExternalCommonBroadcastReceiver
01-06 04:40:56.606 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.apps.emergencyassist/.DeviceMonitorBroadcastReceiver
01-06 04:40:56.606 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.apps.maps/com.google.android.apps.gmm.locationsharing.usr.LocationAvailabilityChecker$LocationProvidersChangedBroadcastReceiver
01-06 04:40:56.606 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver
01-06 04:40:56.606 15027 15065 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
and couple of similar errors 01-06 04:40:50.727 15027 15065 W BroadcastQueueInjector: Unable to launch app com.viber.voip/10291 for broadcast Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/emulated/0 flg=0x5000010 (has extras) }: process is not permitted to auto start

I don't know how to resolve those errors. Delete all mentioned applications? ArrayIndexOutOfBoundsException looks really strange.

Edit: it happens here?
 
Last edited:

LoneFox

Members
May 21, 2021
3
3
*** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
Yep, that does indeed not look good
One thing you could try is to make a backup with either adb backup (with the apk option) or use titanium backup, then reflash the latest official firmware with the xiaomi mi flash tool
This doesn't look like the kind of issue to be solved with a factory reset, looks like something went wrong at system level while upgrading the firmware

Edit: Regarding the permission errors, I think those are intended behaviour, those logs are basically saying that X app tried to do Y thing but you have not given said app the permission to do it