Question [HELP] Pixel 6 Pro freezing shortly after booting [SOLVED]

[Flyview]

Hey guys,

Need some help troubleshooting what's going on with my Pixel 6 Pro.

Short version:

It's freezing up ~30-60s after booting and unlocking the phone, and then soft-rebooting some time after. If i don't unlock the phone it doesn't reboot. Safe mode also works but with lots of scary errors in logcat.

ROM: Stock, May 2023
Magisk: Yes
Kernel: Kirisakura Ravianth 1.0.5_6

Long version:

I rebooted manually to check something and then shortly after the screen froze up. It rebooted on its own and then it froze again. I then rebooted into safe mode and although it doesn't freeze up in safe mode, there are a lot of errors in the logcat (maybe these are normal for safe mode). Rebooting normally again, it freezes up every time 30-60s after unlocking, but is fine if I don't unlock. I then flashed the stock May 2023 image, without -w, so data was not wiped. I assume this means that Magisk and Kirisakura kernel is gone. The problem is still happening! Yikes!

What should I try? Can I clear data of the system without actually clearing all data on the phone (factory reset)?

We'll get to speculations on what could have caused this after I recover it...

I'm attaching two error level logcats:

1) During regular boot:

--------- beginning of kernel--------- beginning of system2023-06-06 22:35:2 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

2) During safe mode boot: Freeze_safe_mode_boot.txt

--------- beginning of main--------- beginning of kernel--------- beginning - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

 

[simplepinoi177]

I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...

 

[Flyview]

I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...

Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.

 

[simplepinoi177]

Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.

My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.

FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....

 

[Flyview]

My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.

FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....

Thanks! The files must have been too big. I edited the post with external links to the logs.

I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?

 

[simplepinoi177]

Thanks! The files must have been too big. I edited the post with external links to the logs.

I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?

Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).

 

[Kris Chen]

Your whole system has been broken. I would recommend you reflash all new system.

 

[Flyview]

Your whole system has been broken. I would recommend you reflash all new system.

How can you tell?

Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).

Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

 

[simplepinoi177]

Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

If you wish to do what Kris Chen suggests (he may have gotten to his conclusion by reading your logs), you could simply flash the Full Factory image that you linked -- you could do it manually or there are multiple tools that can do it for you; you were able to root, so I imagine you already have a method. Try to back up as much as you can.

If you wish to completely unroot, there are guides and methods I imagine.

If I found myself in your situation, this is what I would do...

• update every module
  • a bug may be what's causing glitching and corrected in newer version
• disable every module
• update/establish Magisk stable version -- this may mean downgrading if on canary or delta
  • unhide Magisk if hidden
• reboot
• enable one module and reboot and see if the system loads up correctly
  • see if can't narrow down if it is a specific module
    
• if that does result in a stable loading system,
  • it was a buggy module
• if that doesn't result in a stable loading of system,
  • take a photo of installed modules
  • I would remove/delete the Magisk subdirectory from the root directory
  • flash the stock init_boot

*I'm sure there are more official, better ways to "remove root"

• if that does result in a stable loading of system
  • install Magisk stable version
  • patch stock init_boot; flash it
  • install single module -- rebooting right after each one & confirm system stability before installing next one
  • maybe Magisk just needed to be intensively re-initialized
• if that does not result in a stable loading system
  • remove Magisk
  • flash stock init_boot
  • flash stock kernel
    
• if that does result in stable loading of system
  • it's your kernel, not Magisk
• if that does not result in stable loading of system
  • lost cause
  • back everything up
  • flash Full Factory image with wipe included

Those are just things I, personally, would do -- take it as much as a suggestion as you will (as you probably did many of them already anyways). Good luck to you!

 

[Flyview]

Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.

I am seeing some scary things in the logs:

"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."

and there are a lot of com.google.android.gms errors as if it doesn't even exist:

"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"

 

[simplepinoi177]

Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.

I am seeing some scary things in the logs:

"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."

and there are a lot of com.google.android.gms errors as if it doesn't even exist:

"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"

I'm unsure, I don't know too much about "safe mode", but I just assume that if it all works in safe mode, it usually means it's a module -- in my experience, rooted users only enter that mode when there's an issue with Magisk and/or its modules.
And in the quintessential rooting guide in the P7P forum (and all his other guides), roirraW "edor" ehT suggests to disable modules before flashing the update (even if you are losing root) -- which I infer that modules can still mess with the system even if you don't have root access....

I'm unsure what else safe-mode disables -- if you research and figure that out, maybe you can narrow down what safe-mode is disabling that is causing your issue. Maybe uninstall the last 5-10 apps/modules you installed (if it's not Magisk related)? I doubt running in safe-mode reverts the kernel as well (so I can't imagine that's proving it), but maybe its the custom kernel (like something the custom kernel is interacting with it doesn't like and causing a glitch)?

 

[Rachid.Ala]

I think the best thing would be to backup all your data and do a clean flash.

 

[Flyview]

I think the best thing would be to backup all your data and do a clean flash.

Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:

1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.

[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]

/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...

forum.xda-developers.com

I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?

 

[Kris Chen]

Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:

1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.

[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]

/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...

forum.xda-developers.com

I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?

Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?

 

[Flyview]

Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?

Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.

I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?

 

[simplepinoi177]

Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.

I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?

I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....

 

[Kris Chen]

Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.

I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?

Well, it seems that you live in the past... Until now, no twrp support for A13.
So you cannot manage to wipe specific partition.

I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....

Yes!
Until now, no TWRP support for A13.

 

[simplepinoi177]

I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....

Google Pixel - Update and Software Repair

With this or anything else, good luck!

 

[Flyview]

I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....

Google Pixel - Update and Software Repair

With this or anything else, good luck!

Interesting! I might give that a shot but I have an

UPDATE:

I was up until 4AMtrying different things and somehow got it working again!?

Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?

After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.

Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?

So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.

 

[simplepinoi177]

Interesting! I might give that a shot but I have an

UPDATE:

I was up until 4AMtrying different things and somehow got it working again!?

Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?

After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.

Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?

So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.

Curious/Interesting.... I always assumed clicking on the trash icon and rebooting simply but effectively uninstalled the module. But it's also why I stated that you should remove each module and reboot after each time....*very important the rebooting

I imagine somewhere between this

so I went back into safe mode. After some more time trying different things in safe mode

may be what corrected what was causing it to glitch...? That or, again, getting the module properly/completely removed or re-initialized properly corrected it -- we told you that it was most likely the modules; when things run smoothly in safe-mode, it's usually the culprit...
Tweaking with frequencies & thermal often end up with random glitches -- from my very limited experience of overclocking my CPU and GPU, the way to go about it is to tweak those things until just riiight about the system doing random reboots....It's easy to imagine this all being a symptom of such things...it's why I suggested even going back to stock kernel after removing all Magisk & modules....

Glad you stabilized your device though!