System UI keeps stopping, lockscreen loop, adb available, Signal Backup

[dreamflasher 120]

After the battery ran out my Fxtec Pro1 stock Android (rooted) is in a lockscreen loop: I enter my PIN, the screen turns black and then it's back to the lockscreen.
Occasionally it manages to go a step further and show a dialogue "System UI keeps stopping". Any touch event or keyboard event returns it to the lockscreen. The same behaviour happens in Safe Mode.
I have debugging enabled and adb authorized, I have TitaniumBackup and was able to pull the TitaniumBackup files, as well as the internal storage. So mostly everything is good, except that I'd like to get a backup of my Signal Messenger chat history.

My questions:
1) What are my options to rescue my phone without needing to flash and install everything again? (Just asking in case I overlooked any options here, that would be the easiest to just fix the "SystemUI keeps stopping")
2) With `am start -n com.termux/.HomeActivity` I can start things, I also see that they are started, but then I can't do `input text` to actually do something. What are my options from adb? Can I send inputs directly to an app starting?

3) I can start Termux in this way, but not Signal Messenger – it shows just a black screen in the back of the error message. It seems to be BOOT_COMPLETED is not being sent, I expect a bunch more apps to run (eg. Signal itself, I don't receive calls there, also Tasker – on the other hand gmail and text messages are working)
4) Incoming phone calls work, so I am wondering: Could I create an app that runs in front of the lock screen, ideally sth like Termux, then I could do everything?

5) How can I wipe the cache? Doesn't seem to be possible from fastboot nor recovery (I have the standard recovery)

6) Can I flash anything to fix this without destroying userdata? (phone is encrypted).

Thanks a lot for your help!

[EskeRahn 5,471]

Just a crazy idea, you can try key input from ADB by the key events, one by one. e.g.

• adb shell input keyevent 29

https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_FUNCTION

[VaZso 1,998]

@dreamflasher, have you tried leaving the phone for example on charger for a few hours?

I am experiencing a reboot loop after each reboot (now also after each charger connections).
This is the second time I have this problem, it used to be solved after factory reset.

So for me, it looks like the phone was started. PIN request comes up, lock screen comes up, but not all applications are exists.
Software keyboard is the default instead of "Hacker's keyboard" I use, saved WLAN connections are unavailable, SD-Card is absent, etc.
So there are unavailable applications where not even the name of the specific application is displayed.
Also, sometimes I have an application not responding-like toast message.

...but if I leave the phone alone for a while, it finally starts and it works correctly.
Anyway, I use Nova launcher and not the standard one, I don't know if that is available during this problem.

During the time I first ran into this issue, I was in our capital city and wanted to drive home and I wanted to use GPS assistance.
I have looked my battery state and it was a bit below 25 % of charge, so I have decided to charge it during navigation.
...but I forgot about the problem and my phone has started its reboot loop giving about an additional hour of delay for me.
(I had also my old Motorola G6 with me which also did not work because it has a software bug but in GPS handling what can be solved but I did not know how.)

So it is just a tip, but you may have the very same issue as it seems to be a software bug somewhere.
Anyway, my reboot loop is soft-reboot, so Linux kernel does not restart, only Android on top of that.

[dreamflasher 120]

@VaZsoYes, I tried multiple restarts, leaving on the charger, too. Now I also removed a bunch of apps and resetted the cache for systemui, play store, play services.

Left it on charger, running over the night – nothing 😞

[dreamflasher 120]

Could I do this? https://harrisonsand.com/posts/patching-adb-root/ → I guess it doesn't work because I do not have the current boot.img (gets changed with OTA updates and I have it patched with magisk). I guess with a second phone I could go through the steps of patching the magisk file and doing one OTA upgrade after the other and then extracting the boot.img? Would that create identic boot.img files? Or is the encryption key tight to the boot.img so that I wouldn't be able to boot from that anymore?

 

 

[Rob. S. 1,664]

Just on a side note, it may or may not have anything to do with this – I have experienced anomalous behaviour with my Moto Z3 Play a few times which seemed to relate to either SIM card or SD card not being properly (physically) connected. Removing and reinserting the card tray and rebooting usually returned things to normal. This came to my mind now as I remembered the Pro1's card tray to be quite flimsy (not that other phones' card trays would always be more sturdy).

[dreamflasher 120]

Thank you, good idea, but unfortunately this didn't change anything. Removed the tray.

My highest hopes are with flashing, but my problem is that I don't understand what I am destroying when flashing.

[EskeRahn 5,471]

Well if the purpose 'merely' is to have it booting long enough to get data out, I would continue your path and disable anything that are not essential.

REMEMBER the silly thing that since about Android 4 you will also have to explicitly STOP the stuff you disabled! Yes I know it is absurd, but it will NOT be stopped by disabling it... see e.g. this. (And it autostarts even with a deep boot, if it was not stopped before the boot )

You mentioned Magisk. I'm not familiar with its details, but it is complex and powerful, so might complicate the whole task.

[dreamflasher 120]

Okay, I will continue this. It is strange because many apps are running, just Signal doesn't want to run.

I was able to install https://wiki.termux.com/wiki/Termux:Boot but I have the problem without root I can't access `~/.termux/boot/` so I can't place something there that would be executed elevated. Just anything that would allow me to run a command with su rights would be enough, then I could do https://community.signalusers.org/t/wiki-howto-manual-backup-restore-if-full-backup-does-not-work/2462 where I need to copy one file from a place to a user-readible location.

I can even start Termux:Boot as well as Termux and I see it running behind the error message, but for Signal the screen turns black behind the error message – the activity gets started, but then it stalls.

[EskeRahn 5,471]

And I assume adb root (& adb unroot) does not work either?

You could also stop those you do not want disabled (e.g. Signal) Stop would not normally lead to data-loss.

[dreamflasher 120]

`adb root` → `adbd cannot run as root in production builds`

`adb shell su` → `Permission denied`

I disabled/uninstalled everything I could, but still not working.

The two main ways I see 1) get Signal to run, 2) get one command being run as `su` (even temporary root is fine)

[Benni 184]

Never mind: Read the original comment again

You can also try to boot in safe mode: https://technastic.com/turn-off-safe-mode-android/

 

Edited March 28, 2021 by Benni
overlooked safe mode in the original comment

[EskeRahn 5,471]

12 minutes ago, Benni said:

You can also try to boot in safe mode: https://technastic.com/turn-off-safe-mode-android/

(See line 3 of the original post)

[dreamflasher 120]

Just had trouble finding the safemode again, wanted to test it again with bloatware removed, so it's poweroff + longtap on poweroff. But no, still nothing :(((

Edited March 28, 2021 by dreamflasher

[dreamflasher 120]

For a brief second the following toast error message appears, does that give a hint for the problem?

An error occurred: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/file from pid=6390, uid=10167 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()

I tried to quickly run top, but couldn't find that PID.

 

 

Quote

An error occurred: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/file from pid=6390, uid=10167 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()

 

Edited March 28, 2021 by dreamflasher

[EskeRahn 5,471]

36 minutes ago, dreamflasher said:

For a brief second the following toast error message appears, does that give a hint for the problem?

An error occurred: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/file from pid=6390, uid=10167 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()

I tried to quickly run top, but couldn't find that PID.

Could sound like a 'vital' app has been moved (or had its storage moved  to SD, and then the SD removed, leaving the system confused. So  guess the hunt is to find and disable that app....

Any of these that might help?

[EskeRahn 5,471]

...Perhaps the launcher saving wallpapers there?

[dreamflasher 120]

Just had the idea to run logcat (why didn't I come up with that earlier?^^), and there are a bunch of exceptions in there:

Quote

03-28 18:45:22.115  1488  1488 E LockSettingsService: Failed to decrypt child profile key
03-28 18:45:22.115  1488  1488 E LockSettingsService: java.security.InvalidKeyException: Only SecretKey is supported
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.org.conscrypt.OpenSSLCipher.checkAndSetEncodedKey(OpenSSLCipher.java:462)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.org.conscrypt.OpenSSLCipher.engineInit(OpenSSLCipher.java:296)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2980)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher.tryCombinations(Cipher.java:2891)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2796)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher.chooseProvider(Cipher.java:773)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher.init(Cipher.java:1288)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at javax.crypto.Cipher.init(Cipher.java:1223)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.locksettings.LockSettingsService.getDecryptedPasswordForTiedProfile(LockSettingsService.java:1175)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.locksettings.LockSettingsService.unlockChildProfile(LockSettingsService.java:1183)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.locksettings.LockSettingsService.ensureProfileKeystoreUnlocked(LockSettingsService.java:554)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.locksettings.LockSettingsService.access$200(LockSettingsService.java:155)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.locksettings.LockSettingsService$1.run(LockSettingsService.java:567)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at android.os.Handler.handleCallback(Handler.java:873)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at android.os.Handler.dispatchMessage(Handler.java:99)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at android.os.Looper.loop(Looper.java:193)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.SystemServer.run(SystemServer.java:466)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.server.SystemServer.main(SystemServer.java:302)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at java.lang.reflect.Method.invoke(Native Method)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
03-28 18:45:22.115  1488  1488 E LockSettingsService:   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)

Quote

03-28 18:45:22.976  3440  3440 E AndroidRuntime: Process: org.thoughtcrime.securesms, PID: 3440
03-28 18:45:22.976  3440  3440 E AndroidRuntime: java.lang.RuntimeException: Unable to create application org.thoughtcrime.securesms.ApplicationContext: java.lang.NullPointerException: Attempt to invoke virtual method 'javax.crypto.SecretKey java.security.KeyStore$SecretKeyEntry.getSecretKey()' on a null object reference
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5944)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.ActivityThread.access$1100(ActivityThread.java:201)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1657)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:193)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6746)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
03-28 18:45:22.976  3440  3440 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'javax.crypto.SecretKey java.security.KeyStore$SecretKeyEntry.getSecretKey()' on a null object reference
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.crypto.KeyStoreHelper.getSecretKey(KeyStoreHelper.java:122)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.crypto.KeyStoreHelper.getKeyStoreEntry(KeyStoreHelper.java:108)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.crypto.KeyStoreHelper.unseal(KeyStoreHelper.java:67)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.logging.LogSecretProvider.parseEncryptedSecret(LogSecretProvider.java:37)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.logging.LogSecretProvider.getOrCreateAttachmentSecret(LogSecretProvider.java:22)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.ApplicationContext.initializeLogging(ApplicationContext.java:246)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.ApplicationContext.lambda$onCreate$0(ApplicationContext.java:123)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.ApplicationContext.lambda$onCreate$0$ApplicationContext(Unknown Source:0)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.-$$Lambda$ApplicationContext$FUG4OX_0WYia1ROK536avz_A-eY.run(Unknown Source:2)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.util.AppStartup.execute(AppStartup.java:142)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at org.thoughtcrime.securesms.ApplicationContext.onCreate(ApplicationContext.java:162)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1155)
03-28 18:45:22.976  3440  3440 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5939)

Quote

03-28 18:45:26.189  2108  2380 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #3
03-28 18:45:26.189  2108  2380 E AndroidRuntime: Process: com.android.systemui, PID: 2108
03-28 18:45:26.189  2108  2380 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at android.os.AsyncTask$3.done(AsyncTask.java:354)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:764)
03-28 18:45:26.189  2108  2380 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int com.android.internal.widget.VerifyCredentialResponse.getResponseCode()' on a null object reference
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:377)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at com.android.internal.widget.LockPatternUtils.checkPassword(LockPatternUtils.java:496)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at com.android.internal.widget.LockPatternChecker$5.doInBackground(LockPatternChecker.java:236)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at com.android.internal.widget.LockPatternChecker$5.doInBackground(LockPatternChecker.java:230)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at android.os.AsyncTask$2.call(AsyncTask.java:333)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
03-28 18:45:26.189  2108  2380 E AndroidRuntime:        ... 4 more

 

Quote

03-28 18:45:56.951  7357  7357 E AndroidRuntime: Process: com.qualcomm.qti.qdma, PID: 7357
03-28 18:45:56.951  7357  7357 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.qualcomm.qti.qdma.app.ApplicationManager: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.qualcomm.qti.qdma/.job.QDMAJobService }: app is in background uid UidRecord{d727924 u10s1000 RCVR idle change:uncached procs:2 seq(0,0,0)}
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5944)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ActivityThread.access$1100(ActivityThread.java:201)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1657)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:193)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6746)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
03-28 18:45:56.951  7357  7357 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.qualcomm.qti.qdma/.job.QDMAJobService }: app is in background uid UidRecord{d727924 u10s1000 RCVR idle change:uncached procs:2 seq(0,0,0)}
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ContextImpl.startService(ContextImpl.java:1532)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.content.ContextWrapper.startService(ContextWrapper.java:664)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at com.qualcomm.qti.qdma.app.ApplicationManager.onCreate(ApplicationManager.java:357)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1155)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5939)
03-28 18:45:56.951  7357  7357 E AndroidRuntime:        ... 8 more

 

Quote

03-28 18:46:17.887  8791  8791 E AndroidRuntime: Process: com.qualcomm.qti.smcinvokepkgmgr, PID: 8791
03-28 18:46:17.887  8791  8791 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.qualcomm.qti.smcinvokepkgmgr.SmcInvokeBroadcastReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.qualcomm.qti.smcinvokepkgmgr/.SmcInvokeService }: app is in background uid UidRecord{d727924 u10s1000 SVC  idle procs:8 seq(0,0,0)}
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ActivityThread.handleReceiver(ActivityThread.java:3427)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ActivityThread.access$1200(ActivityThread.java:201)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1668)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:193)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:6746)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
03-28 18:46:17.887  8791  8791 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.qualcomm.qti.smcinvokepkgmgr/.SmcInvokeService }: app is in background uid UidRecord{d727924 u10s1000 SVC  idle procs:8 seq(0,0,0)}
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ContextImpl.startService(ContextImpl.java:1532)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.content.ContextWrapper.startService(ContextWrapper.java:664)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.content.ContextWrapper.startService(ContextWrapper.java:664)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at com.qualcomm.qti.smcinvokepkgmgr.SmcInvokeBroadcastReceiver.onReceive(SmcInvokeBroadcastReceiver.java:22)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        at android.app.ActivityThread.handleReceiver(ActivityThread.java:3418)
03-28 18:46:17.887  8791  8791 E AndroidRuntime:        ... 8 more

 

Quote

03-28 19:30:25.852  2922 11389 E GmscoreIpa: Mediastore indexing task failed [CONTEXT service_id=255 ]
03-28 19:30:25.852  2922 11389 E GmscoreIpa: byjw: Invalid String passed as URL: '/storage/emulated/0/Android/data/com.android.providers.media/albumthumbs/1595235518496'. The invalid indexable url is: content://media/external/audio/albums/64
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at byli.a(:com.google.android.gms@210915030@21.09.15 (100408-361652764):6)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at bykn.c(:com.google.android.gms@210915030@21.09.15 (100408-361652764):2)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aeaf.a(:com.google.android.gms@210915030@21.09.15 (100408-361652764):2)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aebm.d(:com.google.android.gms@210915030@21.09.15 (100408-361652764):2)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aeaf.d(:com.google.android.gms@210915030@21.09.15 (100408-361652764):5)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aebm.e(:com.google.android.gms@210915030@21.09.15 (100408-361652764):28)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aeaf.g(:com.google.android.gms@210915030@21.09.15 (100408-361652764):0)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aeam.a(:com.google.android.gms@210915030@21.09.15 (100408-361652764):4)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at aesi.run(:com.google.android.gms@210915030@21.09.15 (100408-361652764):5)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at ucx.c(:com.google.android.gms@210915030@21.09.15 (100408-361652764):6)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at ucx.run(:com.google.android.gms@210915030@21.09.15 (100408-361652764):7)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at uiw.run(:com.google.android.gms@210915030@21.09.15 (100408-361652764):0)
03-28 19:30:25.852  2922 11389 E GmscoreIpa:    at java.lang.Thread.run(Thread.java:764)

 

[dreamflasher 120]

Can I install/flash TWRP without losing my data? Then I could make a nandroid backup there, or it seems it's possible to encrypt the disk via that?

[EskeRahn 5,471]

1 minute ago, dreamflasher said:

Can I install/flash TWRP without losing my data? Then I could make a nandroid backup there, or it seems it's possible to encrypt the disk via that?

I'm not even sure that a TWRP exists for the Pro1 except for Sailfish (see this)... We better have some with better knowledge on this stuff answer that.....

[dreamflasher 120]

You're right, on the second page of the thread it's clear that this can't encrypt /data so useless.

I am able to start (via adb) Tasker and TitaniumBackup. Unfortunately none of them allow configuration via adb/they have their configuration not in a public writeable location.

I hoped I could adb backup termux, change the user data to have a command that runs on startup, win. But the backup command requires an ok on the screen *sigh*

I wish someone would have left a hole for me 😄 Like a tasker or termux addon that allows to execute something or change the config and thus make it execute…

Edited March 28, 2021 by dreamflasher

[dreamflasher 120]

How does Magisk SU work, does it authorize based on signature/key or package name? If it were the latter I could just create an app with the right package name… (like the same I already have authorized)

[EskeRahn 5,471]

14 hours ago, dreamflasher said:

But the backup command requires an ok on the screen *sigh*

You can fake input through adb, both keyboard and touch AFAIK. Never tried the touch though, but pretty sure I've seen it describes somewhere....

ADD:

adb shell input tap x y

https://stackoverflow.com/questions/3437686/how-to-use-adb-to-send-touch-events-to-device-using-sendevent-command

[dreamflasher 120]

Unfortunately, that doesn't work either. Directly crashes back to lockscreen 😞

I am now trying to build Magisk containing a su command itself that's being run when Magisk starts, let's see how that goes.

[dreamflasher 120]

Nice, that actually worked! So yeah, if your have previously magisk installed, just in the SplashActivity add a Shell.su("cp -r /data/misc/keystore/user_0").exec() comand, and then you get all the keys. Unfortunately, it didn't help afterall in my case because the UID_Signal key is missing. So I guess that's what happened on my device, somehow some keyfiles got deleted. Wtf -.-