In case someone missed it, there was a second canary magisik pushed yesterday, my guess is that it fixes something wrong with the first release
How To Guide January 3, 2022 firmware (TQ1A.230105.002) - Unlock bootloader / Root Pixel 6 Pro [Raven] / all relevant links
- Thread starter roirraW "edor" ehT
- Start date
When things were working fine as is on Magisk Stable, I highly recommend not "fixing" it.
Try this: Flash the stock unrooted boot.img to your phone. Then with the Magisk Canary 25205 rooted boot.img on your computer:
Code:
fastboot boot boot-magisk_patched-25200_1a2B3c.imgThen when the phone boots, hopefully normally and rooted, then click Install beside Magisk in the app and choose direct install. I hope that works for you.
If that doesn't help, I'd suggest dirty flashing using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). The flash site can fix problems that even the factory image zip can't. Just make sure you have the following options unchecked:
- Wipe
- Force flash all partitions
- Re-lock bootloader
Good luck!
Can you please look at my screen shot above and tell me if I have the latest Canary build installed? What is the build number?
When I opened Magisk recently, it wasn't prompting me to automatically update.
There is an issue opened up for the "upgrade to the full Magisk Manager to finish the setup" bug. Check out the workarounds posted in there.
Looks like latest to me. Here's mine
25205 is the latest Canary release.
How come TWRP is always so far behind now? Is it technical difficulties? Or because people are not really asking for it nowadays?Now we have to wait for Android 13 support, but...
TWRP 3.7.0 lands with long-awaited Android 12 support and various other fixes
The Team Win Recovery Project (TWRP) has been updated to version 3.7.0 with Android 12 support and many other improvements. Read on!www.xda-developers.com
Although I have to say I do miss it sometimes.
I don't really have any insight into it. Any combination of all of those plus that it's just voluntary work, so as time allows. Everyone has real life and real jobs. Despite that there are users who still want it, I feel that there must be less demand for it than ever. I haven't missed out on anything, not having TWRP.
For those that were able to install Magisk correctly, and have it hidden, can you please tell me what the hidden app is typically called and/or where it is stored?
I've received a lot of good tips, and I'll have a chance to troubleshoot tonight, but I also want to make sure Magisk, if it is still hidden, is completely uninstalled.
I've received a lot of good tips, and I'll have a chance to troubleshoot tonight, but I also want to make sure Magisk, if it is still hidden, is completely uninstalled.
You have to name it whatever you want, I believe, if you want to know what it's called. At least, that's what I've always done. When you go to hide it, you have the opportunity to choose what it's called. Hopefully, someone has a better answer for you - about what happens if you don't choose a name for it.
At the bottom of the app section in magisk it says the package name (e.g. Com.freefall.flyzone)
But that doesn't help if you have two magisks one hidden and one not
I appreciate your detailed directions, and willingness to help me. However, I tried everything, including the dirty flash, and patched boot image, and still can't get Magisk installed. On the plus side, I also realized I don't really have root access, even though it says I do.When things were working fine as is on Magisk Stable, I highly recommend not "fixing" it.
Try this: Flash the stock unrooted boot.img to your phone. Then with the Magisk Canary 25205 rooted boot.img on your computer:
Code:fastboot boot boot-magisk_patched-25200_1a2B3c.img
Then when the phone boots, hopefully normally and rooted, then click Install beside Magisk in the app and choose direct install. I hope that works for you.
If that doesn't help, I'd suggest dirty flashing using the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). The flash site can fix problems that even the factory image zip can't. Just make sure you have the following options unchecked:
After that, then try the directions I gave above starting with "Then with the Magisk Canary 25205 rooted boot.img on your computer".
- Wipe
- Force flash all partitions
- Re-lock bootloader
Good luck!
At this point, one of my primary reasons for retaining root is to run SWIFT backup, so I can easily transfer apps and data to my upcoming Pixel 7 Pro.
I definitely have the latest adb and fastboot images, an unlocked bootloader, and the latest October Android 13 firmware installed. Is there anything, short of a full wipe, that I can try, or flash in adb/fastboot to try and get root back?
It looks like I am somehow missing the SuperUser Binary files. If anyone is willing to posted an already patched boot image of Android 13, I can try flashing that.
In the future, I'll always remember to unhide Magisk before updating, assuming that is part of the problem.
I am open to any ideas at this point...LOL
Last edited by a moderator:
You can try the attached patched boot to this post.I appreciate your detailed directions, and willingness to help me. However, I tried everything, including the dirty flash, and patched boot image, and still can't get Magisk installed. On the plus side, I also realized I don't really have root access, even though it says I do.
At this point, one of my primary reasons for retaining root is to run SWIFT backup, so I can easily transfer apps and data to my upcoming Pixel 7 Pro.
I definitely have the latest adb and fastboot images, an unlocked bootloader, and the latest October Android 13 firmware installed. Is there anything, short of a full wipe, that I can try, or flash in adb/fastboot to try and get root back?
It looks like I am somehow missing the SuperUser Binary files. If anyone is willing to posted an already patched boot image of Android 13, I can try flashing that.
In the future, I'll always remember to unhide Magisk before updating, assuming that is part of the problem.
I am open to any ideas at this point...LOL
View attachment 5733565 View attachment 5733567
I think you have two versions of Magisk manager installed, one hidden and one not, and they are not playing nice to each other.
You probably are rooted, what do you get when you do adb shell, and then do su ? (assuming that you had previously granted root access to adb shell)
The hidden Magisk's default name is Settings, unless you changed that, look for an app on your phone that is named Settings, and launch it and see what you get.
I highly suggest the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own), but this time I suggest a full wipe and force flash all partitions (but don't re-lock bootloader). Obviously, this will wipe everything, but this may be the only way to recover root on your device - to start from scratch. Sorry for the bad news.I appreciate your detailed directions, and willingness to help me. However, I tried everything, including the dirty flash, and patched boot image, and still can't get Magisk installed. On the plus side, I also realized I don't really have root access, even though it says I do.
At this point, one of my primary reasons for retaining root is to run SWIFT backup, so I can easily transfer apps and data to my upcoming Pixel 7 Pro.
I definitely have the latest adb and fastboot images, an unlocked bootloader, and the latest October Android 13 firmware installed. Is there anything, short of a full wipe, that I can try, or flash in adb/fastboot to try and get root back?
It looks like I am somehow missing the SuperUser Binary files. If anyone is willing to posted an already patched boot image of Android 13, I can try flashing that.
In the future, I'll always remember to unhide Magisk before updating, assuming that is part of the problem.
I am open to any ideas at this point...LOL
View attachment 5733565 View attachment 5733567
Edit: I believe I had to do this once for the exact same or a similar reason.
Don't you want to exhaust all possibilities before resorting to that?
Wipe should be the last resort.
Of course it's a personal choice, but a sheer determination of @gecowa6967 here trying to avoid a wipe came up with a ingenious solution, and it was far worse for him as he would bootloop with a patched image.
I couldn't think of anything else to try, which is why I suggested the flash tool.
Just wanted to publicly thank badabing2003 and Edor for all their suggestions and advice. I wasn't ready to wipe my device and kept thinking about when badabing2003 said I may still be rooted....
I used a couple of file managers and searched for anything MAGISK-related and deleted as much as I could. Then I uninstalled the Magisk App that I could still see.
I noticed 2 files system/bin/magisk and system/bin/magiskpolicy and was unable to delete them, so I tried using the adb shell rm command and was DENIED.
Then I went into fastboot and tried to use the erase and format commands to delete those same READ-ONLY FILES, and was also DENIED.
However, I still had a patched boot image on my computer and decided to reflash it to see what would happen.,,,,
After I rebooted the phone, I went back in to ADB SHELL and attempted to execute the SU command.
My phone perked up immediately and I got the message that Magisk was not fully installed, prompting me to download the FULL VERSION.
I did, and rebooted again. Everything works!!!! Magisk is fully installed!!!! All of my root apps began prompting me for root access, including SWIFT BACKUP.
Now that I got this fixed, I can really look forward to setting up my new Pixel 7 Pro!!!
Thanks again guys...You definitely didn't have to take the time to respond, but gave me the motivation to keep plugging along.... I really appreciate it.
@diesteldorf
Love it that you managed to salvage without a wipe.
Love it that you managed to salvage without a wipe.
Paranoid Android Topaz based on Android 13 is here for the Nothing Phone 1 and Google Pixel 6 series
The Paranoid Android custom ROM team has released the first wave of "Topaz" based on Android 13 for the Nothing Phone 1 and Pixel 6/6 Pro.
Top Liked Posts
-
There are no posts matching your filters.
-
6@kdrag0n has some interesting work going on for the official Universal SafetyNet Fix (USNF) v2.4.0, that's now in testing.5
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
13.0.0 (TQ1A.230105.002, Jan 2023) Flash Link 924ad4baa13f6611a85bf3d1b2f26f8f61e4e90230b7b69618208323e47a94bb
Android Security Bulletin—January 2023 | Android Open Source Project
source.android.com
54 -
62
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
13.0.0 (TQ1A.230105.002, Jan 2023) Flash Link 924ad4baa13f6611a85bf3d1b2f26f8f61e4e90230b7b69618208323e47a94bb
Android Security Bulletin—January 2023 | Android Open Source Project
source.android.com
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google searchDeveloper Support Android imagesif you want to find them.
Platform Tools has been updated slightly to v33.0.3:
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Release Notes https://developer.android.com/studio/releases/platform-tools:
TL;DR regarding the PSA. If you update one slot to Android 13, you canfastboot reboot bootloaderafter and thenfastboot --set-active=otherto change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first:fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img(change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
Here there be dragons.
I am not responsible for anything at all. 
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)
Google's Help Page for 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.
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
Rooting-related
No longer applies -Things that make rooting more complicated on Android 12
A list of the other important guides - be sure to thank the respective OPs
For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
TWRP (not made for the Pixel 6 Pro yet - will update when it has)
Custom kernels for stock ROM(s)
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader)
The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.
Regarding P6P 5G model numbers and capabilities - post #3 below.
List of all Pixel monthly security bulletins and Play System Updates - post #4 below.
How I root and update (which is identical whether rooting the first time or updating):
1515The unlock process works like this;
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.13Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.
Canary 23014
EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4
12
Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both useupdate_engine. I did boot into Android 13 so the ARB counter did get incremented.
Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:
Android 12 doesn't work properly on the Android 13 bootloader.
It boots up just fine, appears to work just fine, made and received calls and texts, however the issue @bush911 had with WebView crashing is true. It's more than just WebView, the media DRM APEX immediately crashes. WebView crashes sometime after launch when it tries to find out if ClearPlay or WideVine are functional, and DRM Info crashes immediately when I try to launch it. Without DRM working that means you won't be able to play some music or movies and won't be able to use Netflix or any other streaming app.
There might be more systems or modules nonfunctional, but without working browsers your smartphone isn't going to be more useful than a dumbphone.
@roirraW "edor" ehT
So I guess it's time to retract that you can revert to Android 12, because until a modder comes along to cook up a custom Android 12 ROM with Android 13 APEXs or patched ones it won't work.
