Stuck in loop after reboot

dentistofdoom

Hi
After restarting my phone, it is stuck in a loop showing the logo animation. I can connect to the device with adb and get the log. I pasted the last few lines below since the whole log is to long to post.

Any help on how to proceed would be greatly appreciated!

$adb logcat 
<removed text>
02-26 00:31:41.231   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.239  1008  1147 I CHRE    : @  10.357: Nanoapp loaded: SD (0x476f6f676c001030) version 0x10 (nanoapp=sd@9082132) uimg 0 system 0
02-26 00:31:41.239  1008  1147 I CHRE    : @  10.357: Nanoapp permissions: 0x1
02-26 00:31:41.239  1008  1147 I CHRE    : @  10.357: [SOUND_DETECTION] audio model initialization
02-26 00:31:41.239  1008  1147 D CHRE    : @  10.357: Finished loading nanoapp cb on fragment ID: 2
02-26 00:31:41.239  1008  1147 D CHRE    : @  10.357: Instance ID 14 assigned to app ID 0x476f6f676c001012
02-26 00:31:41.250  1008  1147 I CHRE    : @  10.368: Nanoapp loaded: Smartbatching (0x476f6f676c001012) version 0xa (nanoapp=smartbatching@8565796) uimg 0 system 0
02-26 00:31:41.250  1008  1147 I CHRE    : @  10.369: Nanoapp permissions: 0x4
02-26 00:31:41.250  1008  1147 I CHRE    : @  10.369: [ChreWifiScanner] chre wifi scanner created
02-26 00:31:41.250  1008  1147 E CHRE    : @  10.369: CHRE: Client not ready (everInit=0, init=0, open=0)
02-26 00:31:41.250  1008  1147 D CHRE    : @  10.369: Finished loading nanoapp cb on fragment ID: 1
02-26 00:31:41.250  1008  1147 D CHRE    : @  10.369: Instance ID 15 assigned to app ID 0x476f6f676c001021
02-26 00:31:41.260   775  1410 I suez-nanoapp-clients: Enabling drop_detect nanoapp.
02-26 00:31:41.261   775  1553 I suez-nanoapp-clients: Enabling ip_health nanoapp.
02-26 00:31:41.261  1008  1147 I CHRE    : @  10.379: Nanoapp loaded: UV Exposure Reporter (0x476f6f676c001021) version 0x1000000 (nanoapp=uv_exposure@8565796) uimg 0 system 1
02-26 00:31:41.261  1008  1147 I CHRE    : @  10.379: Nanoapp permissions: 0x0
02-26 00:31:41.261  1008  1147 I CHRE    : @  10.379: [UV] Ready
02-26 00:31:41.261  1008  1147 I CHRE    : @  10.379: CHRE: Enqueue TX: len=15 H#16 type=0x0 ID=2 err=0 cmd=0x3 pending=1
02-26 00:31:41.261  1008  1147 D CHRE    : @  10.379: Configured GNSS Location: enable 0
02-26 00:31:41.261  1008  1147 I CHRE    : @  10.379: CHRE: Enqueue TX: len=11 H#16 type=0x0 ID=3 err=0 cmd=0x4 pending=2
02-26 00:31:41.261  1008  1147 D CHRE    : @  10.379: Configured GNSS Measurement: enable 0
02-26 00:31:41.261  1008  1147 D CHRE    : @  10.381: Parsed nanoapp message from host: app ID 0x476f6f676c001010 endpoint 0x9010 msgType 1 payload size 0
02-26 00:31:41.262   398   398 I servicemanager: Found android.frameworks.stats.IStats/default in framework VINTF manifest.
02-26 00:31:41.263   775  1553 I suez-nanoapp-clients: Vendor atom [id = 100046] reported.
02-26 00:31:41.263  1004  1004 D AOC     : A3:MSG: usf_sensor.cc, 1357: USF: Received start sampling request for ICP10101 Pressure Sensor.
02-26 00:31:41.263  1004  1004 D AOC     : A3:MSG: icp10101_device.cc, 160: USF: ICP10101: Barometer stops sampling.
02-26 00:31:41.263  1004  1004 D AOC     : A3:MSG: icp10101_device.cc, 146: USF: ICP10101: Barometer starts sampling: period_ns = 40000000, max_latency_ns = 10000
02-26 00:31:41.264  1008  1147 I CHRE    : @  10.381: [HEALTH] OnSoundReady
02-26 00:31:41.264  1008  1147 D CHRE    : @  10.381: Parsed nanoapp message from host: app ID 0x476f6f676c001022 endpoint 0x9022 msgType 1 payload size 0
02-26 00:31:41.264   775  1410 I suez-nanoapp-clients: drop_detect nanoapp enabled.
02-26 00:31:41.264  1008  1147 I CHRE    : @  10.382: [dd] Got message from host with type 1 size 0 data @ (nil) hostEndpoint 0x9010
02-26 00:31:41.264  1008  1147 I CHRE    : @  10.382: [dd] enable
02-26 00:31:41.264  1008  1147 I CHRE    : @  10.382: [dd] Result of sending enable reply: 1
02-26 00:31:41.265  1008  1147 I CHRE    : @  10.382: [ip] Received message from host endpoint 0x9022 of type 1 and size 0.
02-26 00:31:41.265  1008  1147 I CHRE    : @  10.382: [ip] App enabled by host.
02-26 00:31:41.265   740   752 D ContextHubHal: Got message from nanoapp: ID 0x476f6f676c001010
02-26 00:31:41.313   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.350   905   905 W HidlServiceManagement: Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default
02-26 00:31:41.350   399   399 I hwservicemanager: Since android.frameworks.sensorservice@1.0::ISensorManager/default is not registered, trying to start it as a lazy HAL.
02-26 00:31:41.350   905   905 I HidlServiceManagement: getService: Trying again for android.frameworks.sensorservice@1.0::ISensorManager/default...
02-26 00:31:41.351   399  1555 W libc    : Unable to set property "ctl.interface_start" to "android.frameworks.sensorservice@1.0::ISensorManager/default": error code: 0x20
02-26 00:31:41.351   399  1555 I hwservicemanager: Tried to start android.frameworks.sensorservice@1.0::ISensorManager/default as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
02-26 00:31:41.396   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.480   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.564   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.646   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.730   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 00:31:41.813   446   573 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback

r3g_5z

You need to submit the full logcat. These lines alone are not enough to indicate any clear problem. If it's stuck at the logo, it definitely would not show the cause at the end here.

Please submit them to something like gist.github.com.

You also need to give more details, what device is this? What GrapheneOS versions are you on?

dentistofdoom

It is a Google Pixel 6, oriole:13/TQ1A.230205.002/2023021000
I also added the output of adb shell getprop along with adb logcat to this gist:
https://gist.github.com/dentistofdoom/a6065d838d5f8cd652af22f6691711e7

muhomorr

dentistofdoom

https://gist.github.com/dentistofdoom/a6065d838d5f8cd652af22f6691711e7

Is this the complete logcat? It stops abruptly.

muhomorr

An unusual part of the log is:

02-26 00:31:32.516  1371  1446 E CriticalEventLog: com.android.framework.protobuf.nano.InvalidProtocolBufferNanoException: Protocol message contained an invalid tag (zero).
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.framework.protobuf.nano.CodedInputByteBufferNano.readTag(CodedInputByteBufferNano.java:79)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.nano.CriticalEventLogStorageProto.mergeFrom(CriticalEventLogStorageProto.java:70)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.nano.CriticalEventLogStorageProto.mergeFrom(CriticalEventLogStorageProto.java:5)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.framework.protobuf.nano.MessageNano.mergeFrom(MessageNano.java:143)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.framework.protobuf.nano.MessageNano.mergeFrom(MessageNano.java:131)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.nano.CriticalEventLogStorageProto.parseFrom(CriticalEventLogStorageProto.java:106)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.CriticalEventLog$LogLoader.loadLogFromFile(CriticalEventLog.java:427)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.CriticalEventLog$LogLoader.load(CriticalEventLog.java:415)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.CriticalEventLog.lambda$new$0(CriticalEventLog.java:101)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.CriticalEventLog.$r8$lambda$NdrLCZrStsgnIGA45Mjgzd66lK8(Unknown Source:0)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at com.android.server.criticalevents.CriticalEventLog$$ExternalSyntheticLambda1.run(Unknown Source:4)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at android.os.Handler.handleCallback(Handler.java:942)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at android.os.Handler.dispatchMessage(Handler.java:99)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at android.os.Looper.loopOnce(Looper.java:201)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at android.os.Looper.loop(Looper.java:288)
02-26 00:31:32.516  1371  1446 E CriticalEventLog:      at android.os.HandlerThread.run(HandlerThread.java:67)

This indicates a file system corruption.
Did you force restart your device previously (by holding the power button for > 30 seconds)?

dentistofdoom

I did a regular restart of the phone because it was behaving weirdly, I was connected to it with ADB and it was disconnecting several times. I hoped a restart would fix it.

I've tried to search for a way verify or repair the filesystem but I've not found a way to do it, at least not using ADB, is there a wai?

dentistofdoom

muhomorr
There seems to be no more interesting happening and the last "block" is just repeating. I did another logcat with a longer time span and pasted it here:
https://gist.github.com/dentistofdoom/957497801df877a728ae4ad5024cb781

I tried to see if I could find anything suspicious in the second log file as well.

Not sure if this is:

02-26 22:44:15.122   451   451 E libdisplaycolor: failed to get input binary /vendor/etc/display_colordata_samsung-s6e3fc3_cal0.pb
02-26 22:44:15.122   451   451 E libdisplaycolor: failed to load /vendor/etc/display_colordata_samsung-s6e3fc3_cal0.txt
02-26 22:44:15.122   451   451 E libdisplaycolor: failed to load proto: /vendor/etc/display_colordata_samsung-s6e3fc3_cal0 error: -2

or this (that muhomorr already listed):

02-26 22:44:22.201  1357  1461 W PackageParsing: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.REQUEST_INSTALL_PACKAGES in package: org.telegram.messenger at: Binary XML file line #108
02-26 22:44:22.237  1357  1463 W PackageParsing: No actions in intent-filter at /data/app/~~QzEmYhWtmaC2-57wY9EG1Q==/com.ichi2.anki-kCYLbm71DhsdegLFo-XNyg==/base.apk Binary XML file line #269
02-26 22:44:22.244  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.244  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.245  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.246  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.247  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.247  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.247  1357  1464 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #8
02-26 22:44:22.247  1357  1464 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~7qWVuj4oclclMXTvCBqz4w==/com.google.android.GoogleCamera-h2NH9DYqJ8v9Zp8SjDAXPA==/base.apk Binary XML file line #10
02-26 22:44:22.263   443   443 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 22:44:22.318  1357  1462 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~xYvIEZlEMmt509EbM2Rq0g==/com.android.vending-1BTtUiUPX6APQCqtkfuzBA==/base.apk Binary XML file line #9
02-26 22:44:22.319  1357  1462 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~xYvIEZlEMmt509EbM2Rq0g==/com.android.vending-1BTtUiUPX6APQCqtkfuzBA==/base.apk Binary XML file line #11
02-26 22:44:22.347   443   443 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback
02-26 22:44:22.367  1357  1462 W PackageParsing: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.USE_FINGERPRINT in package: org.mozilla.focus at: Binary XML file line #52
02-26 22:44:22.384  1357  1461 W PackageParsing: Unknown element under <manifest>: uses-sdk at /data/app/~~jpCxZNGoRvyVcfzs-A-O3w==/com.google.android.gms-8win2tXJo815z81X3NH9jQ==/base.apk Binary XML file line #10
02-26 22:44:22.384  1357  1461 W PackageParsing: Unknown element under <manifest>: module at /data/app/~~jpCxZNGoRvyVcfzs-A-O3w==/com.google.android.gms-8win2tXJo815z81X3NH9jQ==/base.apk Binary XML file line #14
02-26 22:44:22.384  1357  1461 W PackageParsing: Unknown element under <manifest>: permission at /data/app/~~jpCxZNGoRvyVcfzs-A-O3w==/com.google.android.gms-8win2tXJo815z81X3NH9jQ==/base.apk Binary XML file line #22
02-26 22:44:22.431   443   443 E BLASTBufferQueue: [bbq-adapter#0](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback

is suspicious enough to assume there is filesystem corruption, but I'm not sure how to test for that.

When I list the binaries in /system/bin/ the output looks like this

1|oriole:/ $ ls -l /system/bin/  
...
lrwxr-xr-x 1 root shell       6 2009-01-01 08:00 free -> toybox   
-rwxr-xr-x 1 root shell  111264 2009-01-01 08:00 fsck.erofs                  
-????????? ? ?    ?           ?                ? fsck.exfat                                               
-????????? ? ?    ?           ?                ? fsck.f2fs           
-????????? ? ?    ?           ?                ? fsck_msdos                            
-????????? ? ?    ?           ?                ? fsverity_init             
lrwxr-xr-x 1 root shell       6 2009-01-01 08:00 fsync -> toybox              
-????????? ? ?    ?           ?                ? gatekeeperd                                              
lrwxr-xr-x 1 root shell       6 2009-01-01 08:00 getconf -> toybox     
...

but perhaps this expected?

muhomorr

dentistofdoom The output you've quoted is normal.

Capture a full bugreport (adb bugreport) and send it to my e-mail: muhomor.dmitry@gmail.com

dentistofdoom

Thanks to muhomorr I managed to get my running again (thanks again!).

What worked for me was to do a sideload update following these instructions:
https://grapheneos.org/usage#updates-sideloading
https://grapheneos.org/releases