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
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...
simplepinoi177 said:
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...
Click to expand...
Click to collapse
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.
Flyview said:
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.
Click to expand...
Click to collapse
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....
simplepinoi177 said:
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....
Click to expand...
Click to collapse
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?
Flyview said:
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?
Click to expand...
Click to collapse
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).
Your whole system has been broken. I would recommend you reflash all new system.
Kris Chen said:
Your whole system has been broken. I would recommend you reflash all new system.
Click to expand...
Click to collapse
How can you tell?
simplepinoi177 said:
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).
Click to expand...
Click to collapse
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
Flyview said:
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
Click to expand...
Click to collapse
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!
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"
Flyview said:
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"
Click to expand...
Click to collapse
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)?
I think the best thing would be to backup all your data and do a clean flash.
Rachid.Ala said:
I think the best thing would be to backup all your data and do a clean flash.
Click to expand...
Click to collapse
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?
Flyview said:
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?
Click to expand...
Click to collapse
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 ?
Kris Chen said:
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 ?
Click to expand...
Click to collapse
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?
Flyview said:
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?
Click to expand...
Click to collapse
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....
Flyview said:
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?
Click to expand...
Click to collapse
Well, it seems that you live in the past... Until now, no twrp support for A13.
So you cannot manage to wipe specific partition.
simplepinoi177 said:
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....
Click to expand...
Click to collapse
Yes!
Until now, no TWRP support for A13.
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!
simplepinoi177 said:
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!
Click to expand...
Click to collapse
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.
Flyview said:
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.
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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!
Related
Hello,
I clicked wrongly in Titanium Backup.
I clicked Freeze All.
Now I'm in Bootloop. I can start Fastboot mode, but not Recovery or Rescue.
Pixel was rooted with the November update.
With "Fastboot Devices" I see the phone on the PC.
How do I get the apps working again?
Or how do I start a complete new installation?
Translated with the Google Translator ...
Help...
Chris
Try "fastboot erase userdata" or "fastboot format userdata". Yes, its going to wipe the phone. Sorry, no alternative I'm aware of.
F***!
Thank you...
V-Ripper said:
F***!
Thank you...
Click to expand...
Click to collapse
Did you get yourself out of the boot loop?
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. To use a root level backup app that wasn't optimized/made for Android 12. There's a reason why people have been recommending Swift for years now.
Morgrain said:
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. Do use a root level backup app that wasn't optimized/made for Titanium. There's a reason why people have been recommending Swift for years now.
Click to expand...
Click to collapse
I used to use TB wayyyyy back when. I think I still have a paid license for it somewhere.
I'm not totally sure how this could happen; an educated guess is that OP froze a bunch of system apps, causing a kernel panic. No idea why it would mess up /boot though, screwing up /system to the point of a kernel panic would generally result in a bootloop where the kernel starts to load, but hits the same panic and restarts the device.
It's certainly risky using root backup apps that aren't updated for use on modern Android systems...
V0latyle said:
causing a kernel panic
Click to expand...
Click to collapse
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
Click to expand...
Click to collapse
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
I wonder if op could have booted to safe mode. That should have disabled all the apps. Including TB I think.
Sorry for the OP's problem, but I thought Titanium Backup stopped working a year or so ago. Does it work on the P6 and P6 Pro now?
Az Biker said:
Did you get yourself out of the boot loop?
Click to expand...
Click to collapse
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I tried to re-flash. Did nothing.
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
Click to expand...
Click to collapse
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
V-Ripper said:
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
I tried to re-flash. Did nothing.
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
Click to expand...
Click to collapse
It's nice to hear that your device is working again!
V0latyle said:
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
Click to expand...
Click to collapse
Yes, but based on what he said, its not a kernel panic.
New including my solution without wiping:
I have great news, everyone:
First, a very brief summary of what didn't fix the issue:
I had tried flashing the full February factory image, both manually and using the Google Pixel Flash site without wiping, without any luck.
What just fixed the issue now:
I flashed the new (2nd) February full factory image without wiping. When I noticed I didn't get the corruption paused boot screen during one or more parts of the flash-all.bat flashing process, the phone booted normally after it was completely done.
So at the most, if this issue happens again, hopefully I'd only have to wait until the next full factory image is available.
Not pertinent to the solution, but:
Normally in the past, I go ahead and sign in, and let everything load, and then go back into Fastboot and flash my manually Magisk'd boot.img, but this time when it got to the lock screen, I went back into Fastboot right from there and flashed the Magisk'd boot.img I had prepared from before flashing the factory image. I then shut the phone off. I turned the phone on, and still, no corruption paused boot screen.
I haven't flashed a kernel yet. No idea if any need or can be updated for the 2nd February update - I just haven't checked and don't know if there is updated source code available, or if there will be before the March update.
Click to expand...
Click to collapse
Old:
Yes, I know there's a hair on the screen of my images taken with my original Pixel 1 of my Pixel 6 Pro.
Click to expand...
Click to collapse
I know there are other related threads such as this question thread Unlocked Pixel 6 Pro - "Your Device is corrupted and cannot be trusted" error after trying to manually flash Dec 2021 factory image, and other individual posts in various threads, but I wanted to create a thread where I will maintain the OP with what we figure out about this issue.
Click to expand...
Click to collapse
TL;DR:
So far, it seems the only full way to eliminate the issue includes flashing (via Flash-All.bat from the full firmware zip or Official Google Android Flash Tool) with a full wipe, so losing all user data and system settings. When these flashing methods require temporary rebooting in order to start flashing in a different mode, you may have to manually get the phone past the corruption screen for the flashing method to continue where it left off.Temporary workarounds are to use either of those two flashing methods while not wiping (in Android Flash Tool, have all the checkboxes unchecked) - this doesn't keep this screen from showing every time you reboot or turn the phone on after being off, but the phone is useable, even with a rooted stock kernel - I haven't tested a custom kernel again.
Click to expand...
Click to collapse
Back to the details you may or may not want to know...
This is the corruption screen in question, it precedes the normal bootloader unlocked screen, but in this case, it always requires a manual press of the power button to proceed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The g.co/ABH link takes you to Understand warning about operating system safety. It's not very helpful in my opinion as it doesn't tell a way to fix the issue without a full wipe. Below are the contents of the page:
Understand warning about operating system safetyWhen you turn on an Android device, it checks the operating system to make sure it's safe to use. This means the code comes from a trusted source and hasn't been changed or corrupted.
If your operating system could have a problem, you can get a warning message that brings you to this page (g.co/ABH).
If you changed the operating system on purposeYou can continue using your device. But you acknowledge that your device might not work properly and your data could be exposed to corruption and security risks.
We recommend restoring your device's operating system. If you have a Pixel or Nexus, learn how to flash your device with the latest factory image.
If you didn't change the operating system yourself
If your device is a Pixel, learn how to get help.
If it's a different Android device, contact your device manufacturer.
Click to expand...
Click to collapse
Spoiler: My original post from another related thread, in response to someone else's question about the solution.
sybor said:
Did you managed to do it using Android Flash Tool without wipping the device?
Click to expand...
Click to collapse
roirraW edor ehT said:
I'm preparing to create a catch-all thread just for this issue. I just experienced the issue for the first time, although I've observed the others who have encountered it under various circumstances.
For myself, it wasn't flashing the February image that caused the error, it was after I flashed a certain custom kernel.zip through EXKM (EX Kernel Manager) that I had the issue. I won't name the kernel as I don't think it's any particular kernel that's the issue, although I don't know what the cause is.
Previous to updating to the February firmware, I was on the January (and with Verity and Verity NOT disabled either time) and was using a different custom kernel zip without any issue. I went through the process pretty much identically to how I had previously. Using the stock kernel worked fine, and using the stock kernel rooted with Magisk 24.1 worked just fine as well. I first had the issue after rebooting from flashing a kernel.zip through EXKM, and I still have it.
I'm not 100% sure this was necessary but using the Android Flash Tool or the manual firmware flash-all.bat (both without wiping, and the Android Flash Tool with no checkboxes checked) both resulted in the phone being usable again, however when I reboot I still get that first (and different than the bootloader unlocked screen) corruption screen.
I will create my thread with images very soon, but I wanted to share what little I know so far, and at least the phone works, it's just a slight PITA that when I reboot or boot from the phone being off that I get that error which requires a manual power button press to go past. Note that during the re-flashing process that I sometimes had to manually press the button during the times the flash process reboots the phone into a different mode before it would continue the flashing process.
Click to expand...
Click to collapse
As you can see below, after flashing (but without wiping) I'm able to boot as normal (only tested with the stock February kernel, rooted with Magisk 24.1), with the only exception being the third screenshot from the top-left, about corruption, and requiring manually pressing the power button to get past the screen.
In case I need this post #2.
In case I need this post #3.
In case I need this post #4. (Last one of these)
It happened to me once when I sideloaded January's OTA and a full wipe with the Android Flash Tool worked, manually flashing via adb did not. However, I got that corrupt boot screen when flashing February's update via AFT. It was worse trying to fix the problem this go-around because I wiped the phone multiple times via AFT with various options (wiped, disable verity, even relocked the bootloader and returned to stock). It finally stuck but I'm not sure what I did.
I tried all the suggestions on XDA and around the Internet but nothing helped. Closest thing I could figure out was maybe one of the boot slots had had encryption and the other didn't so the update failed? It sucked, because now I'm hesitant to flash any kernels or even a patched magisk image because that damn corrupt boot screen appears way too easily.
Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle
Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Beat you to it, thanks for the additional explanation
V0latyle said:
Beat you to it, thanks for the additional explanation
Click to expand...
Click to collapse
I edited my post to reflect your Ninja prowess
Lughnasadh said:
I edited my post to reflect your Ninja prowess
Click to expand...
Click to collapse
It happened to me back in December when I first got my P6P and was rooting it. I couldn't get it to boot though. I tried using the repair tool, but it wouldnt find my device. I tried manual flashing via adb, but it would fail. I was about to send it back to google when I figured I would try to switch boot partitions and that fixed it.
dunno how I got this message as I only got it after flashing a custom kernel which dev said includes the magisk version that does not veed verity disabled.
i hope in march ota when I flash that it will go back to previous boot slot it dont say that.
I will probably do a full wipe and flash when I get some time as the message is annoying as it adds delay to boot
V0latyle said:
Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
Click to expand...
Click to collapse
Thank you! Sideloading just now didn't fix it for me. I tried it while I was already on the February full firmware.
Spoiler: The details of my sideloading
I just sideloaded the full February OTA after I manually restored the unrooted stock February kernel. This might have been the first time I've sideloaded an OTA, or only the second time - I might have done it once on the Pixel 1. The Result code was 0 (zero) for both verification and installation, which appears to mean success where 1 would mean failure.
After success, I booted Android, unlocked the phone, kept it unlocked, and I waited at least 10 minutes since your instructions say:
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Click to expand...
Click to collapse
I never actually saw a notification regarding it, however - like I would if I tried an actual over-the-air update - "Finishing Update" or something like that. I rebooted after than 10+ minutes and still got the paused-boot corruption screen. After unlocking I waited again and then rebooted and same result.
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle
Click to expand...
Click to collapse
Thank you! I appreciate the details and the additional link to relevant information.
roirraW edor ehT said:
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Click to expand...
Click to collapse
Well, this is how things went wrong on my wife's Pixel 5a:
Restored boot image in Magisk, installed OTA. Rebooted. Successful boot, no root (because she rebooted it before I had a chance to install to inactive slot)
Switched active slot to the "old" slot. Bootlooped.
Dirty flashed January factory image on old slot. Verity EIO corrupt warning. Bootlooped.
Dirty flashed January factory image to both slots. Bootlooped, Rescue Party data corrupt warning.
Downloaded and dirty flashed February factory image to both slots. Bootlooped, Rescue Party.
Sideloaded the February OTA to the "new" slot. Successful boot. Attempted to live boot previously patched image, I believe January patched with 23017. Rescue Party.
Patched February boot image in Magisk Stable 24, rebooted to bootloader and live booted. Successful. Performed Direct Install in Magisk, and rebooted. Successful boot with root.
There is something to do with the OTA mechanism that will bork everything if you try to mess with it. I do know that if it doesn't successfully boot the updated slot, it will mark that slot "unsuccessful" and won't try to boot it again, and will then revert to the old slot. I don't know why it didn't just boot the old slot in my case.
Going forward, at least until we figure out the problem with automatic OTAs, the safest method of update is either dirty flashing the factory image (can use Android Flash Tool as well), or sideloading the OTA.
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the 'device is corrupt' message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
searching for 'corrupt' on reddit's GooglePixel sub shows this problem was mostly prevalent from November-December, Pixels 4-6.
Alekos said:
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Click to expand...
Click to collapse
Interesting experience. Thank you for sharing the details.
Alekos said:
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the crop message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Click to expand...
Click to collapse
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
Alekos said:
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
Click to expand...
Click to collapse
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
roirraW edor ehT said:
Interesting experience. Thank you for sharing the details.
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
Click to expand...
Click to collapse
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
Alekos said:
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
Click to expand...
Click to collapse
Very interesting. Maybe there's a slight difference in the cause or some other detail we don't know yet, since the problem on mine wasn't preceded by wired or wireless headphones being used. Very interesting! Your link "this" became garbled. Here's the fixed link. this
Alekos said:
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
Click to expand...
Click to collapse
That's quite alright, not your fault. I've only recently started fooling with safe mode so it's still a slight surprise to me each time, but I think it won't stay a surprise for much longer.
Alekos said:
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
Click to expand...
Click to collapse
You're welcome!
I had this error after a non-wipe upgrade, coupled with bootloops. I had everything backed up so I did a complete factory image install and re-rooted. The phone runs like new again and all rooting conflicts are resolved.
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like the .img ending so I had to rename it to .zip - just remove that and you'll be good.
Click to expand...
Click to collapse
I've never done it that way myself. By just restoring images in magisk, I can do a "normal" update, from settings, and it will download just the update, in this case, about 700MB, then Install to inactive slot in Magisk and done.
This avoids me needing to find the full update to download. Probably not a big deal, but this has always worked fine in the past.
I guess i just installed Magisk incorrectly the last time I wiped, which is now causing me this issue.
I appreciate your suggestion, and perhaps that is the better way moving forward.
I didn't see your attachment, but as I'm typing this, i see you edited to say you renamed it, so I'll see if I see it now.
Thank you for your help.
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Click to expand...
Click to collapse
I just downloaded it, thank you again!
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Primokorn said:
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Click to expand...
Click to collapse
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
JustinChase said:
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
Click to expand...
Click to collapse
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Primokorn said:
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Click to expand...
Click to collapse
It normally does, but I apparently installed it 'abnormally' last time, so I didn't have/save the stock boot image.
I just need to research the best way to get the downloaded stock image onto my phone so that Magisk knows and can use it, without screwing something up, and having to wipe and reinstall everything (again).
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
JustinChase said:
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
Click to expand...
Click to collapse
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Nimueh said:
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Click to expand...
Click to collapse
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
JustinChase said:
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
Click to expand...
Click to collapse
I don't use my device much and mostly at home on my wifi, so I'm not overly worried. I'm still on the last OOS 11 version mysel, mostly because 1 mod I use only exists for OOS 11. I'm sure I'll update eventually but for now I'm ok with old security patches.
#priorities and all that
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
eduaaard said:
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
Click to expand...
Click to collapse
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Olesya13 said:
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Click to expand...
Click to collapse
Hi,
What was meant and what is the meaning of your question?
Regards,
Eduard
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
alecxs said:
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
Click to expand...
Click to collapse
Hi, no idea but from some sources this indicates that the culprit is vbmeta when installing the initial twrp. But this is still being tested. A bug with a custom font in MIUI is also possible, many people know that this caused bootloops after a while in theme manager.