Just realized that Ubuntu version now seems to work with Mint. I used Kali because Ubuntu version didn't work previously.
Amazing. What's the risk of dirty flashing long term?You're welcome.
This is all it took.
Code:2022-12-05 14:08:29 Done! Flashing elapsed time: 240 seconds
I've been doing in since Nexus 6P days, I don't see any added risks.
Active/inactive slot refers to the partitions, yeah? Where can I read up or what to search for to understand more what they are, how they work etc?I've been doing in since Nexus 6P days, I don't see any added risks.
recommendation: Flash to Inactive Slot, in case anything goes wrong, you're back to your working slot, if it goes well, Inactive becomes the active one.
Not partitions but two sets of partitionsActive/inactive slot refers to the partitions, yeah? Where can I read up or what to search for to understand more what they are, how they work etc?
Active/inactive slot refers to the partitions, yeah? Where can I read up or what to search for to understand more what they are, how they work etc?
Flash to Inactive Slots
PF first switches slot and then flashes it.Support.zip would helpSo after applying the last update, I'm getting into Bootloop. Any ideas are very welcome. I'm trying to disable the magisk modules without success.
Hey Thanks.
Did you boot into safe mode? Did you reboot after booting into safe mode? (Booting into safe mode sets some flag so on next boot, Magisk will not load any modules. If modules are your only problem, that gives you one chance to use Magisk to permanently disable all modules.)So after applying the last update, I'm getting into Bootloop. Any ideas are very welcome. I'm trying to disable the magisk modules without success.
Flashing is working fine.
Magisk Modules:
AOSP Mods (Full version) enabled 2.4.0
DisableFlagSecure enabled v3.0
MagiskHide Props Config enabled v6.1.2-v137
Magisk Bootloop Protector enabled v1.8.1
Android 13 QR-scanner lockscreen shortcutdisabled v1.0
Universal SafetyNet Fix enabled v2.3.1
Universal GMS Doze disabled 1.8.7
volte-properties for Pixel 6 Pro enabled 1
Zygisk - LSPosed enabled v1.8.5 (6649)
Magisk Modules:
AOSP Mods (Full version) enabled 2.4.0
DisableFlagSecure enabled v3.0
MagiskHide Props Config enabled v6.1.2-v137
Magisk Bootloop Protector enabled v1.8.1
Android 13 QR-scanner lockscreen shortcutdisabled v1.0
Universal SafetyNet Fix enabled v2.3.1
YepThat special magisk is an amazing idea. Kudos to the dev, will definitely keep that as a just in case.
Thanks for your consideration, no donation please, read about it in OP to see what's better.OK, seriously, this is probably one of the best tools I have ever used. Actually this is the only reason why I have decided to keep using my P7P. I thought that keep the phone up-to-date with root (forced to root if I want to use full potential) would be a pain in the ass. But patching to December update including the download took me exactly 315 seconds. AMAZING! THANK YOU!
I am going to donate, immediately.
WoW thanks. Worked like a charm. Now I'm running without Bootloop protector, AOSP Mods and Zygisk - LSPosed.Flashing is working fine.
So most likely as you guessed the issue has to do with Magisk modules.
At first you had the following modules
Code:Magisk Modules: AOSP Mods (Full version) enabled 2.4.0 DisableFlagSecure enabled v3.0 MagiskHide Props Config enabled v6.1.2-v137 Magisk Bootloop Protector enabled v1.8.1 Android 13 QR-scanner lockscreen shortcutdisabled v1.0 Universal SafetyNet Fix enabled v2.3.1 Universal GMS Doze disabled 1.8.7 volte-properties for Pixel 6 Pro enabled 1 Zygisk - LSPosed enabled v1.8.5 (6649)
It flashed ok, then it went into recovery, eventually to adb
You had the following modules active on next try (so you removed some)
Code:Magisk Modules: AOSP Mods (Full version) enabled 2.4.0 DisableFlagSecure enabled v3.0 MagiskHide Props Config enabled v6.1.2-v137 Magisk Bootloop Protector enabled v1.8.1 Android 13 QR-scanner lockscreen shortcutdisabled v1.0 Universal SafetyNet Fix enabled v2.3.1
And that too flashed ok, but still caused you problems.
That is why it's always a good idea to disable modules (you can do so directly in PF) before flashing.
How do you recover from this.
I see your device is either ending up in bootloader mode or recovery mode.
When in bootloader mode, SOS won't work, it needs adb mode,
In recovery mode you can issue adb commands, but I'm not certain you'd have root access to disable Magisk (I doubt it)
What you could do is flash non-patched boot.
Download the latest PF, 4.6.0 is out select the stock boot instead of patched boot, and hit the Flash Boot button
View attachment 5778365
You will be able to boot to your device, but you won't be rooted.
If you flash back patched boot, you would run into the same issue because as soon as you boot, Magisk would load the modules and cause the bootloop. And you can't disable the modules if you don't have su access.
I'm surprised that Bootloop Protector is not saving you, to be honest, although I too have it on my phone, in case of a rainy day, I never needed to use it.
Perhaps ask in the module's thread why it is not kicking in.
There is a way though.
Uninstall your Magisk Manager
Download and install this special Magisk that gives you root access but does not load any modules.
@gecowa6967 was kind enough to build a custom Magisk to get around the same problem you're running into.
You create a patched boot with that special Magisk, and flash it,
Then when you reboot, and have root access, disable all modules
You can then flash back a normal patched boot, and enable one module at a time, until you figure out which is causing you the problem.
The process is a bit tedious, but nothing serious, you can get back fully operational without losing data.
Ask questions if you are uncertain about any step.
While i understand your anger, it is likely misplaced, however without an uncut support file (which you generate in PF) it's likely you'll not get this solved.Canary is a broken piece of ****.. so got replacement phone.. flashed it like I did Magisk Beta.. took forever finally reboot. Go to open Magisk and not installed! WTF? So try to install select magisk in the download directory.. says installed but not installed.
Canary is totally and utterly broken in Pixelflasher I'm going back to beta.
You're broken.
PF and Magisk Canary work just fine.
If you're gonna take the time to post, you should follow instructions.
In your listed steps i see an error which is probably your issue but because you didnt upload a support.zip no one can help you. Not that you deserve any help.
@badabing2003 is constantly giving people instructions that say something like "push flash button (not Flash Pixel Phone)". So maybe you need to use the other button.Does not work at all.
1. Selected factory image (same as one installed)
2. Scan for phone and selected it
3. Click Patch
4. Select Magisk Canary
5. Pressed flash Pixel
6. Waited for what felt like forever until it said reboot
7. Open up Magisk and it says not installed!
Not working at all.
8. Click on install
9. Selected Magisk that is downloaded to download directory
10. Says installed (no error but no reboot either)
Not working still says not installed. Not working at all.
Install Magisk
to Install Root App
as it now supports directly installing KernelSU and Apatch through PixelFlasher.Magisk
tool options.Can you please provide a support file?So thankful for your tools!
I might be doing something wrong, but when I try to patch for Apatch for P6P I get the following error:
ERROR: Encountered an error while patching with APatch
Traceback (most recent call last):
File "Main.py", line 4091, in _on_apatch_patch_boot
File "modules.py", line 2325, in patch_boot_img
UnboundLocalError: cannot access local variable 'init_boot_img' where it is not associated with a value
boot.img
/ init_boot.img
management UI, select the boot / init_boot file to patch and click the patch button. Fully Automated patching with Magisk (without manual steps) and perform upgrades without losing root.boot
/ init_boot
)boot
/ init_boot
(temporary root).*******************************************************************************
PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE USING THIS PROGRAM
AND/OR ATTEMPTING ANY MODIFICATIONS ON YOUR DEVICE.
THIS PROGRAM ASSUMES THAT YOU ALREADY KNOW HOW TO AND HAVE ALREADY UNLOCKED
YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, AND KNOW HOW TO USE ANDROID SDK
PLATFORM-TOOLS, ETC.
THIS TOOL IS SIMPLY MY QUICK WAY OF UPDATING THE FIRMWARE WHILE ROOTED WITH
MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE.
MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY
IF YOU LOSE YOUR DATA OR BRICK YOUR DEVICE. THE TOOL I SHARE HAVE WORKED FOR ME,
BUT THAT DOESN'T MEAN THAT YOU MAY NOT RUN INTO PROBLEMS. **BACKUP YOUR DATA.**
*******************************************************************************
io.github.huskydg.magisk
Magisk zygote64_32
canary with a forked URL.Install Magisk
to Install Root App
as it now supports directly installing KernelSU and Apatch through PixelFlasher.Magisk
tool options.Extra Img Extraction
setting now additionally extracts dtbo
, vendor_boot
, vendor_kernel_boot
, super_empty
(useful for some ROMs).Paste
button will automatically paste the path to the (extra) image type selected.6.8.0.0
, 6.8.0.1
, 6.8.0.2
, 6.8.0.3
, 6.8.0.4
, the differences are in Github actions.Get TheFreeman193 Random Pif
, credit to @TheFreeman193 for the print supplies and the original logic of randomization based on device architecture.pif.json
, you can now do multi-select, PixelFlasher will process them in a priority order based on the filename. build.prop being the highest priority.Auto Copy to Clipboard
which automatically copies the generated pif.json
content to clipboard.Auto Push pif.json
which automatically pushes the file to the device and kills GMS process (after generated build.props processing).Auto Check Play Integrity
which automatically triggers the selected Play Integrity checker after editing or auto-pushing pif.json
./data/adb/modules/playintegrityfix/custom.pif.json
build.prop
, browse for the build.prop and it will extract PIF relevant fields, no fancy checking of dates or anything, if it is in there it will extract the values.pif.json
editing automatically kills the com.google.android.gms.unstable
process, no need to reboot.-c
or --config
flag followed by full file path of configuration json file.--console
(only useful on Linux / Mac) to display all PixelFlasher output to console, useful when troubleshooting.Other Magisk App
to be able to select any Magisk apk and use it to create a patch without installing Magisk, handy when a patch needs to be created with an older version of Magisk (in case the current version has issues) and Magisk daemon gets in the way and replaces the older version with a stub.Kill Application
in Package Manager
.Clear Application Data
in Package Manager
.Flash Pixel Phone
button to avoid accidental clicking.boot
/init_boot
(stock or patched) to the phone.