Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
djy said:
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
Click to expand...
Click to collapse
The SafetyNet issue had nothing to do with March update and occurred Thursday night into Friday morning on devices of all varieties and versions. There are plenty of other conversations going on including on the thread you linked. Looks like Google is finding unlocked BL again, and Play Store fails certification on reinstall even dirty from what I have seen. You can't flash back to Feb dirty. Going back to previous updates requires a full device reset as far as I know.
I just went in to magisk manager and saw that I also failed cts. I am on the lastest patch, patched with magisk; on beta. It was fine when I was on February
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
TonikJDK said:
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
Click to expand...
Click to collapse
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
I personally had to factory reset my Pixel 3 XL and root it again. I'm passing SafetyNet but the Play store is not certified.
TonikJDK said:
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
Click to expand...
Click to collapse
I paid with GPay at two vendors this morning with filed CTS and "not certified" Play Store. Of course that did not include adding a card, but can't be certified since a couple of dirty flashes this week.,
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
fonixmunkee said:
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
Click to expand...
Click to collapse
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
sliding_billy said:
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
Click to expand...
Click to collapse
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Nope, stock kernel, rooted. Still fails.
Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Again, this did not happen as a result of anything March update related. Tons of devices that were not updated (including two of mine that haven't seen an update in almost a year and a half) started failing CTS as something that Google pushed automatically like Play services or whatever. Nothing to do with Magisk or able to be fixed with Magisk right now. Looks like they are searching for unlocked BL, and nothing is able to obscure it or know what exactly it is looking at yet (kernel, Magisk).
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Exokan said:
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
Click to expand...
Click to collapse
bobby janow said:
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Click to expand...
Click to collapse
I was just posting this because I saw it a lot earlier than others and was trying to quash any more threads about CTS failing. I find the whole thing funny how Google tries to placate app vendors who don't really want fake security but want ad revenue (IMO of course).
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
djy said:
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
Click to expand...
Click to collapse
This is odd. I flashed my 3 XL also with the April update, patched boot.img with Magisk 20.4 last night. Safety Net failed until I deleted the Safety Patch module. I rebooted and was able to have Google Pay working again (used it this morning to make sure). I'm thankful it's working again. Now I can't update MagiskHide Props Config in Magisk. And if I remember correctly, the quick access to GPay with the power button was a feature drop a while ago.
Related
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
sliding_billy said:
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
Click to expand...
Click to collapse
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
bcradu69 said:
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
Click to expand...
Click to collapse
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
ndd53 said:
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
Click to expand...
Click to collapse
I don't, but to make sure... I am using 16.0 of Magisk.
ndd53 said:
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
Click to expand...
Click to collapse
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
bcradu69 said:
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
Click to expand...
Click to collapse
that was it! I turned off Crossbreeder lite (didn't have Greenify) and now bluetooth is working again. thanks!
EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!
NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.
Works! Thanks for keeping this alive!
(I'm on Jan. 2021)
newkydawg said:
Works! Thanks for keeping this alive!
(I'm on Jan. 2021)
Click to expand...
Click to collapse
Thanks for the feedback! Like I said, I don't own these devices so it's good to know that it's working properly.
Btw, fyi the current installer will install the correct mod for either patch level (Jan or Feb). I'll update one of the posts to reflect this. Like the old official installer, it will detect your current patch level and install the correct needed file. The major differences between this and the official mod installer (in terms of the installation process) is that I pulled out support for some of the devices (older Pixels and HTC), and it won't install for anything before 01-2021. I mean, I guess I could clone the official mod's files repo, which would also allow installs for older patch levels, but I didn't see the point seeing as how the official installer will still work fine for them as well as those other devices (afaik - don't think they've had system updates in a while).
Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.
newkydawg said:
Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.
Click to expand...
Click to collapse
Hmm, somehow the MD5 filename had the .apk stripped off before getting pushed to github, so the installer couldn't find the MD5 to compare with. Updated the github repo with the proper name; should flash now! No need to redownload, just try flashing again.
Yay! I have my squeeze for flashlight back! And just like you said "No need to redownload, just try flashing again." Thanks so much!
hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.
raisins said:
hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.
Click to expand...
Click to collapse
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.
i5lee8bit said:
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.
Click to expand...
Click to collapse
Oh yeah - i am on a Pixel Experience custom ROM. Dang I really liked the long squeeze.. oh well. Thanks for the info
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
There were changes to the SystemUI so I wouldn't use the previous module.
CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
Looks like Mikhail hasn't updated the official repository yet. I'll shoot him a reminder. I sent the files a few days ago. He must be busy lately.
Meanwhile, here's another unofficial update (even though the official version will have identical modded files). Gonna only edit the Pixel 4 XL thread from now on. It's too much of a PITA to edit every single post for each variant. The installer is the same for all devices anyway. Here's a link to the thread, and download link will be there too: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks for updating!
August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.
Rumsfield said:
August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.
Click to expand...
Click to collapse
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.
Soft bricked here too. Did exactly what @CSX321 did to get back to normal.
CSX321 said:
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.
Click to expand...
Click to collapse
What is the process for flashing to a slot? Is this done with adb?
Rumsfield said:
What is the process for flashing to a slot? Is this done with adb?
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.
CSX321 said:
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.
Click to expand...
Click to collapse
Thanks I'll give it a shot.
My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?
Yes
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?
old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.
NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?
old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.
Do I need to root my phone before manually updating using the OTA file?
speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No
Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal
From Orange France is 036, from Google store is 037
Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
My wife uses 3-button navigation (I use gestures). She's unrooted and using Nova Launcher. She said she hasn't had that issue.
swieder711 said:
I'm on the January update. I'm using 3 button navigation. In the last day, the buttons have stopped working multiple times. When I reboot my phone then the buttons work again.
I am rooted and using Magisk add ons by @Typhus with ROM control.
Anyone else seeing this?
Click to expand...
Click to collapse
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
almahix said:
I'm still on December and the 3 button navigation is broken as you describe it. Since you're seeing it in January I'm not in such a big hurry to update now. I am so pissed off at Google!
Click to expand...
Click to collapse
Are you running any magisk modules? I thought that might be related to what I am seeing.
swieder711 said:
Are you running any magisk modules? I thought that might be related to what I am seeing.
Click to expand...
Click to collapse
Magisk for root but no other modules
I think it's not magisk related
And I'm also experiencing this on gestures
Swiping up sometimes just does nothing and is really annoying
Edit: stock on Jan update
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
superman25 said:
Iam on standard January update phone no root i have no working navigaton buttons few times per week its normal issue on pixel 6 pro for now just wait for update
Click to expand...
Click to collapse
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
almahix said:
That's what they said in December! How long will we wait until they get things working?
Even though I had no confidence that it would be resolved in the January release I tried unsuccessfully to side load the Jan OTA. The system update failed to update and for some reason I could never get adb sideload to work so I used the Android Flash Tool to install January, which of course wiped my phone. After all these years I have procedures in place that allow me to recover when that happens, which require me to root. (I miss my reliable OnePlus 7 pro.)
Click to expand...
Click to collapse
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
roirraW edor ehT said:
I've been under the impression from others who used the Official Google Android Flash Tool that there is an option to prevent wiping you can select. I haven't used the site myself, I do it using the script in the full factory image using the latest Platform Tools each month, editing the script first to eliminate the "-w " so the phone isn't wiped.
I never use OTAs while rooted, just flash the full factory image instead.
Click to expand...
Click to collapse
I'll try that way next time I can't update.
My 6 will do that. They just stop responding. Myself I don't need to reboot though. Either I can wait for a few seconds and they'll start working again, or at most lock then unlock the phone.
I had the same issue all the time on December update. A reboot would fix it but I have not seen it all on January update..
I had that problem with December's build, but so far it hasn't happened with January's.
Using 3 button myself on Jan update. Also use Nova and have had no issues. It was a clean install though.
I have a OP8 with a custom a11 ROM on it that 3 button navigation has worked flawlessly on. I upgraded it to 12 over the weekend and have had the buttons lock up a couple of times since. So it would appear to be a a12 thing, and not just a a12 on Pixel issue.
Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
cmh714 said:
Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
Click to expand...
Click to collapse
Magisk support thread
No issue on my Pixel 5, stock kernel, only SafetyNet/systemless host modules.
atm I am struggling to get the device into Recovery mode...wont power down...
cmh714 said:
atm I am struggling to get the device into Recovery mode...wont power down...
Click to expand...
Click to collapse
Hold the power and volume up buttons together for over 30 seconds, maybe longer, and it should force it to power down.
Then if you haven't already, Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Good luck, let us know how you did. I had no trouble updating although at the moment I happen to be on the stock kernel - I don't plan on remaining stock and have previously updated at least one custom kernel.
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
CleanSlate worked well for me when I've been using a custom kernel. I know Kiriaskura is based on CleanSlate, but there are differences.
Glad you got it fixed.
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
But that's no fun
But seriously, that is probably wise. I've stayed on Canary to make it easier if Google decides to play with us again like they did in December with their load fstab shenanigans and of course earlier with their vbmeta shenanigans. Those were fixed quickly in Canary but took a while to make it to Stable. But with that comes the cons, of course, as evidence by today. But Stable is good advice.
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Lughnasadh said:
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
Click to expand...
Click to collapse
Sounds likely for what kept you safe to me.
Lughnasadh said:
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Click to expand...
Click to collapse
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
I might give that a try later, already wasted too much energy on fixing myself but yes, still on Canary
roirraW edor ehT said:
Sounds likely for what kept you safe to me.
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
Click to expand...
Click to collapse
Mama Queen meets Mama Manfred Mann's Earth Band... I love it!
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
Same happened to me, but can't get rid of corrupt system at boot...
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Blade22222 said:
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
Click to expand...
Click to collapse
cmh714 said:
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
Click to expand...
Click to collapse
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Sek0n said:
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Click to expand...
Click to collapse
that worked for me, thanks!
Tulsadiver said:
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
Click to expand...
Click to collapse
sounds like something might be wonky with that new canary.
Freak07 said:
sounds like something might be wonky with that new canary.
Click to expand...
Click to collapse
Even more weird, I tried going back to an earlier version and the problem persisted. Bootloop. It doesn't bootloop until I unlock my phone though.
Tried to Fastboot flash boot boot.img with the mid-Feb release. I am still getting "Your device is corrupt". Going to "flash-nowipe"
Edit: While running flash-nowipe, got the same "device is corrupt" message. Thankfully when I hit resume the device went into fastbootd and is getting the image. Still getting device corrupt, but device booted and apps are still intack.
Rolled back Magisk to 24.3.10 with Kiris kernel 1.8.4. Everything is working fine, but still get the corrupt device message. Requires an extra "resume" when rebooting.
Hopefully tomorrow we will get the March release and an updated Magisk which make the problem go away. Hoping!