I don't follow... Use stable magisk. Then update magisk after flashing if you like. Stable magisk works fine on the March update pixel 6 pro.OK, I'm stuck. PF doesn't like the 25210 Manager version, doesn't seem to see the 25200 module. I tried installing the 25206 from the .apk but get some kind of JavaScript error.
Do I have to uninstall the 25210 manager first? I think I'm going to lose root -- will I lose all my data?
How do I proceed here?
Logs...it's all about logs...OK, I'm stuck. PF doesn't like the 25210 Manager version, doesn't seem to see the 25200 module. I tried installing the 25206 from the .apk but get some kind of JavaScript error.
Do I have to uninstall the 25210 manager first? I think I'm going to lose root -- will I lose all my data?
How do I proceed here?
You don't lose root if you uninstall the manager.OK, I'm stuck. PF doesn't like the 25210 Manager version, doesn't seem to see the 25200 module. I tried installing the 25206 from the .apk but get some kind of JavaScript error.
Do I have to uninstall the 25210 manager first? I think I'm going to lose root -- will I lose all my data?
How do I proceed here?
I didn't make it clear that the javascript error I was getting had nothing to do with PixelFlasher. It appeared when I was trying to manually install the 25206 .apk I had downloaded from the github/magisk site. (Mentioned here earlier as the newest one without issues.)
"1: java.lang.NullPointerException: Attempt to read from field 'java.lang.Strong andro..." is as much of the error message I can read.
That's Java."1: java.lang.NullPointerException: Attempt to read from field 'java.lang.Strong andro..." is as much of the error message I can read.
It's the 25206 Magisk .apk from a link (above). I'm just doule-tapping it. I get a pop-up error that just disappears when I tap it to try and read more of it. I'm on a Pixel 7 Pro, running the latest 13 beta.
You definitely downloaded an APK you were supposed to download. I don't think there are different APKs for different hardware. I don't know how to determine the Magisk version -- maybe examine the APK, it might contain a text file with a recognizable version number.
I bet you are downloading the html instead of the apk.
<!DOCTYPE html>
<html lang="en" data-color-mode="auto" data-light-theme="light" data-dark-theme="dark" data-a11y-animated-images="system">I've read you should get it more from "builds" in the Action section like from here (supposedly this is 25206): https://github.com/topjohnwu/Magisk/actions/runs/4373376674
After downloading the .apk (and NOT the html version) I was able to install 25206 (after changing ".apk" to ".zip" and flashing from within the Magisk Manager.You are 113% correct.
Correct,After downloading the .apk (and NOT the html version) I was able to install 25206 (after changing ".apk" to ".zip" and flashing from within the Magisk Manager.
But when I then changed the .zip back to .apk, and installed it like an app--it installed v 25210 of the manager.
I intentionally was going for 25206. You're saying that .apk contains 25206 and then loads the latest manager?
You're right I thought you were downloading the latest, I just checked and your link is indeed 25206.
Not sure why you would need TWRP and flash alpha in TWRP, that instruction could be for a different phone.
If you can get the phone in bootloader or recovery mode, you're not bricked.
Android Platform Tools Version: 34.0.4-10411341
Adb SHA256: 705ddc21f33ac52105d1b075b019962ad0e44fb3d560bde69ce8cb3a36bca183
Fastboot SHA256: 377ff87ec40a2a9b947e00b487f4f4a42b03e195612bdcd8a526b70a1b0a918a
extracting product.img (2895 MB) to disk...fastboot: error:
failed to extract 'product.img': I/O errorWarning: skip copying bootloader_b image avb footer (bootloader_b partition size: 0, bootloader_b image size: 12845320).
Warning: skip copying radio_b image avb footer (radio_b partition size: 0, radio_b image size: 80191628).Android SDK Version: 33.0.3-8952118Sending 'bootloader_b' (12544 KB) OKAY [ 0.275s]
Writing 'bootloader_b' (bootloader) Flashing pack version cloudripper-1.0-9894666
Sending 'radio_b' (78312 KB) OKAY [ 1.713s]
Writing 'radio_b' (bootloader) Flashing pack version g5300g-230323-230525-M-10200345extracting product.img (2895 MB) to disk...ziparchive W 09-23 01:42:28 15500 14040] Zip: unable to truncate file to 3036135424: File too large
fastboot: error:
failed to extract 'product.img': I/O error
next to it.
next to it. You can download full OTA images from here.
Indicates that the selection is patched.
*******************************************************************************
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.**
*******************************************************************************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.
), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.boot/init_boot (stock or patched) to the phone.
