Question PixelFlasher for Google Pixel 6 Support Thread.

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
I can't seem to get the EXE to open up on Win 11. I run it even as an admin and it just shows me the Pixel Flasher boot screen, but no GUI comes after that on 3.3.4.
Don't run it as admin.
Have you used the program previously, or is this the first time you're using?
Navigate to %APPDATA% directory
See if there is a PixelFlasher directory
If there is, zip it up and send it to me, and then delete it the folder and try again, let me know if it still does the same thing.

If there is no PixelFlasher directory, see if Anti Virus or something else is blocking the application.
Run it from command line and see if the command line displays any message.
 

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
Hey!

My Pixel 6 is bootlooping after an update from SP2 to SQ3. The phone goes from the "Google" screen to the animated "G" screen with the loading bar below for about three seconds, then restarts.

What am i doing wrong?

1. I select the folder with ADB
2. I select oriole-sq3a.220605.009.b1-factory-80f98167.zip
3. I process it and then patch the boot file
4. I select the patched boot file
5. I select Keep data
6. I click Flash



Selected Device on 2022-06-14 10:20:12: Device ID: 1C041FDF6000G1 Device Model: oriole Device is Rooted: True Device Build: SP2A.220505.002 Device Active Slot: a Device Mode: adb Magisk Version: 24.3:MAGISK (24300) Magisk Modules: ViPER4AndroidFX safetynet-fix ============================================================================== 2022-06-14 10:26:52 PixelFlasher 3.3.4.0 Flashing Phone ============================================================================== Rebooting device 1C041FDF6000G1 to bootloader ... Waiting 10 seconds ... Selected Device on 2022-06-14 10:27:09: Device ID: 1C041FDF6000G1 Device Model: oriole Device is Rooted: None Device Build: Device Active Slot: a Device Mode: f.b Device Unlocked: True 2022-06-14 10:27:09 Flashing device 1C041FDF6000G1 ... C:\Users\Robin\AppData\Roaming\PixelFlasher\factory_images\oriole-sq3a.220605.009.b1>chcp 850 Active code page: 850 Sending 'bootloader_a' (11506 KB) OKAY [ 0.249s] Writing 'bootloader_a' (bootloader) Flashing pack version slider-1.2-8318357 (bootloader) flashing platform gs101 (bootloader) Validating partition ufs (bootloader) Validating partition ufs (bootloader) Validating partition partition:0 (bootloader) Validating partition partition:1 (bootloader) Validating partition partition:2 (bootloader) Validating partition partition:3 (bootloader) Validating partition bl1_a (bootloader) Validating partition pbl_a (bootloader) Validating partition bl2_a (bootloader) Validating partition abl_a (bootloader) Validating partition bl31_a (bootloader) Validating partition tzsw_a (bootloader) Validating partition gsa_a (bootloader) Validating partition ldfw_a (bootloader) Flashing partition ufs (bootloader) Flashing partition ufs (bootloader) Flashing partition partition:0 (bootloader) Flashing partition partition:1 (bootloader) Flashing partition partition:2 (bootloader) Flashing partition partition:3 (bootloader) Flashing partition bl1_a (bootloader) Flashing partition pbl_a (bootloader) Flashing partition bl2_a (bootloader) Flashing partition abl_a (bootloader) Flashing partition bl31_a (bootloader) Flashing partition tzsw_a (bootloader) Flashing partition gsa_a (bootloader) Flashing partition ldfw_a (bootloader) Loading sideload ufsfwupdate OKAY [ 2.727s] Finished. Total time: 2.977s Rebooting into bootloader OKAY [ 0.000s] Finished. Total time: 0.001s Sending 'radio_a' (81952 KB) OKAY [ 1.775s] Writing 'radio_a' (bootloader) Flashing pack version g5123b-100840-220505-M-8544885 (bootloader) Flashing partition modem_a OKAY [ 0.102s] Finished. Total time: 1.880s Rebooting into bootloader OKAY [ 0.001s] Finished. Total time: 0.001s -------------------------------------------- Bootloader Version...: slider-1.2-8318357 Baseband Version.....: g5123b-100840-220505-B-8544885 Serial Number........: 1C041FDF6000G1 -------------------------------------------- extracting android-info.txt (0 MB) to RAM... Checking 'product' OKAY [ 0.000s] Checking 'version-bootloader' OKAY [ 0.000s] Checking 'version-baseband' OKAY [ 0.000s] Setting current slot to 'a' OKAY [ 0.058s] extracting boot.img (64 MB) to disk... took 0.152s archive does not contain 'boot.sig' Sending 'boot_a' (65536 KB) OKAY [ 1.419s] Writing 'boot_a' OKAY [ 0.076s] archive does not contain 'init_boot.img' extracting dtbo.img (16 MB) to disk... took 0.023s archive does not contain 'dtbo.sig' Sending 'dtbo_a' (16384 KB) OKAY [ 0.355s] Writing 'dtbo_a' OKAY [ 0.021s] archive does not contain 'dt.img' archive does not contain 'pvmfw.img' archive does not contain 'recovery.img' extracting vbmeta.img (0 MB) to disk... took 0.001s archive does not contain 'vbmeta.sig' Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s] Writing 'vbmeta_a' OKAY [ 0.002s] extracting vbmeta_system.img (0 MB) to disk... took 0.000s archive does not contain 'vbmeta_system.sig' Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s] Writing 'vbmeta_system_a' OKAY [ 0.002s] extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s archive does not contain 'vbmeta_vendor.sig' Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s] Writing 'vbmeta_vendor_a' OKAY [ 0.003s] extracting vendor_boot.img (64 MB) to disk... took 0.162s archive does not contain 'vendor_boot.sig' Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.418s] Writing 'vendor_boot_a' OKAY [ 0.075s] extracting super_empty.img (0 MB) to disk... took 0.000s Rebooting into fastboot OKAY [ 0.000s] < waiting for 1C041FDF6000G1 > Sending 'super' (4 KB) OKAY [ 0.001s] Updating super partition OKAY [ 0.010s] Resizing 'product_a' OKAY [ 0.004s] Resizing 'system_a' OKAY [ 0.004s] Resizing 'system_ext_a' OKAY [ 0.006s] Resizing 'system_b' OKAY [ 0.005s] Resizing 'vendor_a' OKAY [ 0.003s] Resizing 'vendor_dlkm_a' OKAY [ 0.006s] Resizing 'vendor_b' OKAY [ 0.003s] archive does not contain 'boot_other.img' archive does not contain 'odm.img' archive does not contain 'odm_dlkm.img' extracting product.img (2685 MB) to disk... took 8.045s archive does not contain 'product.sig' Resizing 'product_a' OKAY [ 0.006s] Sending sparse 'product_a' 1/11 (262140 KB) OKAY [ 5.872s] Writing 'product_a' OKAY [ 1.231s] Sending sparse 'product_a' 2/11 (262140 KB) OKAY [ 5.790s] Writing 'product_a' OKAY [ 1.186s] Sending sparse 'product_a' 3/11 (262140 KB) OKAY [ 5.799s] Writing 'product_a' OKAY [ 1.260s] Sending sparse 'product_a' 4/11 (262140 KB) OKAY [ 5.800s] Writing 'product_a' OKAY [ 1.144s] Sending sparse 'product_a' 5/11 (262140 KB) OKAY [ 5.778s] Writing 'product_a' OKAY [ 1.250s] Sending sparse 'product_a' 6/11 (262140 KB) OKAY [ 5.804s] Writing 'product_a' OKAY [ 1.236s] Sending sparse 'product_a' 7/11 (262140 KB) OKAY [ 5.791s] Writing 'product_a' OKAY [ 1.214s] Sending sparse 'product_a' 8/11 (262140 KB) OKAY [ 5.806s] Writing 'product_a' OKAY [ 1.242s] Sending sparse 'product_a' 9/11 (262140 KB) OKAY [ 5.787s] Writing 'product_a' OKAY [ 1.229s] Sending sparse 'product_a' 10/11 (262140 KB) OKAY [ 5.803s] Writing 'product_a' OKAY [ 1.243s] Sending sparse 'product_a' 11/11 (129000 KB) OKAY [ 2.913s] Writing 'product_a' OKAY [ 0.628s] extracting system.img (856 MB) to disk... took 2.876s archive does not contain 'system.sig' Resizing 'system_a' OKAY [ 0.006s] Sending sparse 'system_a' 1/4 (262140 KB) OKAY [ 5.877s] Writing 'system_a' OKAY [ 1.239s] Sending sparse 'system_a' 2/4 (262140 KB) OKAY [ 5.829s] Writing 'system_a' OKAY [ 1.231s] Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 5.770s] Writing 'system_a' OKAY [ 1.235s] Sending sparse 'system_a' 4/4 (90720 KB) OKAY [ 2.009s] Writing 'system_a' OKAY [ 0.447s] archive does not contain 'system_dlkm.img' extracting system_ext.img (238 MB) to disk... took 0.744s archive does not contain 'system_ext.sig' Resizing 'system_ext_a' OKAY [ 0.005s] Sending 'system_ext_a' (243764 KB) OKAY [ 5.433s] Writing 'system_ext_a' OKAY [ 1.141s] extracting system_other.img (22 MB) to disk... took 0.083s archive does not contain 'system.sig' Resizing 'system_b' OKAY [ 0.008s] Sending 'system_b' (23288 KB) OKAY [ 0.520s] Writing 'system_b' OKAY [ 0.174s] extracting vendor.img (469 MB) to disk... took 1.489s archive does not contain 'vendor.sig' Resizing 'vendor_a' OKAY [ 0.009s] Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 5.867s] Writing 'vendor_a' OKAY [ 1.209s] Sending sparse 'vendor_a' 2/2 (218392 KB) OKAY [ 4.809s] Writing 'vendor_a' OKAY [ 1.066s] extracting vendor_dlkm.img (53 MB) to disk... took 0.117s archive does not contain 'vendor_dlkm.sig' Resizing 'vendor_dlkm_a' OKAY [ 0.007s] Sending 'vendor_dlkm_a' (54632 KB) OKAY [ 1.213s] Writing 'vendor_dlkm_a' OKAY [ 0.305s] archive does not contain 'vendor_other.img' Finished. Total time: 152.919s rebooting to bootloader ... Rebooting into bootloader OKAY [ 0.001s] Finished. Total time: 0.001s Sleeping 5-10 seconds ... flashing pf_boot ... Sending 'boot_a' (65536 KB) OKAY [ 1.421s] Writing 'boot_a' OKAY [ 0.075s] Finished. Total time: 1.498s rebooting to system ... Rebooting OKAY [ 0.001s] Finished. Total time: 0.001s 2022-06-14 10:30:05 Done! Flashing elapsed time: 193 seconds
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
Hey!

My Pixel 6 is bootlooping after an update from SP2 to SQ3. The phone goes from the "Google" screen to the animated "G" screen with the loading bar below for about three seconds, then restarts.

What am i doing wrong?

1. I select the folder with ADB
2. I select oriole-sq3a.220605.009.b1-factory-80f98167.zip
3. I process it and then patch the boot file
4. I select the patched boot file
5. I select Keep data
6. I click Flash



Selected Device on 2022-06-14 10:20:12: Device ID: 1C041FDF6000G1 Device Model: oriole Device is Rooted: True Device Build: SP2A.220505.002 Device Active Slot: a Device Mode: adb Magisk Version: 24.3:MAGISK (24300) Magisk Modules: ViPER4AndroidFX safetynet-fix ============================================================================== 2022-06-14 10:26:52 PixelFlasher 3.3.4.0 Flashing Phone ============================================================================== Rebooting device 1C041FDF6000G1 to bootloader ... Waiting 10 seconds ... Selected Device on 2022-06-14 10:27:09: Device ID: 1C041FDF6000G1 Device Model: oriole Device is Rooted: None Device Build: Device Active Slot: a Device Mode: f.b Device Unlocked: True 2022-06-14 10:27:09 Flashing device 1C041FDF6000G1 ... C:\Users\Robin\AppData\Roaming\PixelFlasher\factory_images\oriole-sq3a.220605.009.b1>chcp 850 Active code page: 850 Sending 'bootloader_a' (11506 KB) OKAY [ 0.249s] Writing 'bootloader_a' (bootloader) Flashing pack version slider-1.2-8318357 (bootloader) flashing platform gs101 (bootloader) Validating partition ufs (bootloader) Validating partition ufs (bootloader) Validating partition partition:0 (bootloader) Validating partition partition:1 (bootloader) Validating partition partition:2 (bootloader) Validating partition partition:3 (bootloader) Validating partition bl1_a (bootloader) Validating partition pbl_a (bootloader) Validating partition bl2_a (bootloader) Validating partition abl_a (bootloader) Validating partition bl31_a (bootloader) Validating partition tzsw_a (bootloader) Validating partition gsa_a (bootloader) Validating partition ldfw_a (bootloader) Flashing partition ufs (bootloader) Flashing partition ufs (bootloader) Flashing partition partition:0 (bootloader) Flashing partition partition:1 (bootloader) Flashing partition partition:2 (bootloader) Flashing partition partition:3 (bootloader) Flashing partition bl1_a (bootloader) Flashing partition pbl_a (bootloader) Flashing partition bl2_a (bootloader) Flashing partition abl_a (bootloader) Flashing partition bl31_a (bootloader) Flashing partition tzsw_a (bootloader) Flashing partition gsa_a (bootloader) Flashing partition ldfw_a (bootloader) Loading sideload ufsfwupdate OKAY [ 2.727s] Finished. Total time: 2.977s Rebooting into bootloader OKAY [ 0.000s] Finished. Total time: 0.001s Sending 'radio_a' (81952 KB) OKAY [ 1.775s] Writing 'radio_a' (bootloader) Flashing pack version g5123b-100840-220505-M-8544885 (bootloader) Flashing partition modem_a OKAY [ 0.102s] Finished. Total time: 1.880s Rebooting into bootloader OKAY [ 0.001s] Finished. Total time: 0.001s -------------------------------------------- Bootloader Version...: slider-1.2-8318357 Baseband Version.....: g5123b-100840-220505-B-8544885 Serial Number........: 1C041FDF6000G1 -------------------------------------------- extracting android-info.txt (0 MB) to RAM... Checking 'product' OKAY [ 0.000s] Checking 'version-bootloader' OKAY [ 0.000s] Checking 'version-baseband' OKAY [ 0.000s] Setting current slot to 'a' OKAY [ 0.058s] extracting boot.img (64 MB) to disk... took 0.152s archive does not contain 'boot.sig' Sending 'boot_a' (65536 KB) OKAY [ 1.419s] Writing 'boot_a' OKAY [ 0.076s] archive does not contain 'init_boot.img' extracting dtbo.img (16 MB) to disk... took 0.023s archive does not contain 'dtbo.sig' Sending 'dtbo_a' (16384 KB) OKAY [ 0.355s] Writing 'dtbo_a' OKAY [ 0.021s] archive does not contain 'dt.img' archive does not contain 'pvmfw.img' archive does not contain 'recovery.img' extracting vbmeta.img (0 MB) to disk... took 0.001s archive does not contain 'vbmeta.sig' Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s] Writing 'vbmeta_a' OKAY [ 0.002s] extracting vbmeta_system.img (0 MB) to disk... took 0.000s archive does not contain 'vbmeta_system.sig' Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s] Writing 'vbmeta_system_a' OKAY [ 0.002s] extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s archive does not contain 'vbmeta_vendor.sig' Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s] Writing 'vbmeta_vendor_a' OKAY [ 0.003s] extracting vendor_boot.img (64 MB) to disk... took 0.162s archive does not contain 'vendor_boot.sig' Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.418s] Writing 'vendor_boot_a' OKAY [ 0.075s] extracting super_empty.img (0 MB) to disk... took 0.000s Rebooting into fastboot OKAY [ 0.000s] < waiting for 1C041FDF6000G1 > Sending 'super' (4 KB) OKAY [ 0.001s] Updating super partition OKAY [ 0.010s] Resizing 'product_a' OKAY [ 0.004s] Resizing 'system_a' OKAY [ 0.004s] Resizing 'system_ext_a' OKAY [ 0.006s] Resizing 'system_b' OKAY [ 0.005s] Resizing 'vendor_a' OKAY [ 0.003s] Resizing 'vendor_dlkm_a' OKAY [ 0.006s] Resizing 'vendor_b' OKAY [ 0.003s] archive does not contain 'boot_other.img' archive does not contain 'odm.img' archive does not contain 'odm_dlkm.img' extracting product.img (2685 MB) to disk... took 8.045s archive does not contain 'product.sig' Resizing 'product_a' OKAY [ 0.006s] Sending sparse 'product_a' 1/11 (262140 KB) OKAY [ 5.872s] Writing 'product_a' OKAY [ 1.231s] Sending sparse 'product_a' 2/11 (262140 KB) OKAY [ 5.790s] Writing 'product_a' OKAY [ 1.186s] Sending sparse 'product_a' 3/11 (262140 KB) OKAY [ 5.799s] Writing 'product_a' OKAY [ 1.260s] Sending sparse 'product_a' 4/11 (262140 KB) OKAY [ 5.800s] Writing 'product_a' OKAY [ 1.144s] Sending sparse 'product_a' 5/11 (262140 KB) OKAY [ 5.778s] Writing 'product_a' OKAY [ 1.250s] Sending sparse 'product_a' 6/11 (262140 KB) OKAY [ 5.804s] Writing 'product_a' OKAY [ 1.236s] Sending sparse 'product_a' 7/11 (262140 KB) OKAY [ 5.791s] Writing 'product_a' OKAY [ 1.214s] Sending sparse 'product_a' 8/11 (262140 KB) OKAY [ 5.806s] Writing 'product_a' OKAY [ 1.242s] Sending sparse 'product_a' 9/11 (262140 KB) OKAY [ 5.787s] Writing 'product_a' OKAY [ 1.229s] Sending sparse 'product_a' 10/11 (262140 KB) OKAY [ 5.803s] Writing 'product_a' OKAY [ 1.243s] Sending sparse 'product_a' 11/11 (129000 KB) OKAY [ 2.913s] Writing 'product_a' OKAY [ 0.628s] extracting system.img (856 MB) to disk... took 2.876s archive does not contain 'system.sig' Resizing 'system_a' OKAY [ 0.006s] Sending sparse 'system_a' 1/4 (262140 KB) OKAY [ 5.877s] Writing 'system_a' OKAY [ 1.239s] Sending sparse 'system_a' 2/4 (262140 KB) OKAY [ 5.829s] Writing 'system_a' OKAY [ 1.231s] Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 5.770s] Writing 'system_a' OKAY [ 1.235s] Sending sparse 'system_a' 4/4 (90720 KB) OKAY [ 2.009s] Writing 'system_a' OKAY [ 0.447s] archive does not contain 'system_dlkm.img' extracting system_ext.img (238 MB) to disk... took 0.744s archive does not contain 'system_ext.sig' Resizing 'system_ext_a' OKAY [ 0.005s] Sending 'system_ext_a' (243764 KB) OKAY [ 5.433s] Writing 'system_ext_a' OKAY [ 1.141s] extracting system_other.img (22 MB) to disk... took 0.083s archive does not contain 'system.sig' Resizing 'system_b' OKAY [ 0.008s] Sending 'system_b' (23288 KB) OKAY [ 0.520s] Writing 'system_b' OKAY [ 0.174s] extracting vendor.img (469 MB) to disk... took 1.489s archive does not contain 'vendor.sig' Resizing 'vendor_a' OKAY [ 0.009s] Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 5.867s] Writing 'vendor_a' OKAY [ 1.209s] Sending sparse 'vendor_a' 2/2 (218392 KB) OKAY [ 4.809s] Writing 'vendor_a' OKAY [ 1.066s] extracting vendor_dlkm.img (53 MB) to disk... took 0.117s archive does not contain 'vendor_dlkm.sig' Resizing 'vendor_dlkm_a' OKAY [ 0.007s] Sending 'vendor_dlkm_a' (54632 KB) OKAY [ 1.213s] Writing 'vendor_dlkm_a' OKAY [ 0.305s] archive does not contain 'vendor_other.img' Finished. Total time: 152.919s rebooting to bootloader ... Rebooting into bootloader OKAY [ 0.001s] Finished. Total time: 0.001s Sleeping 5-10 seconds ... flashing pf_boot ... Sending 'boot_a' (65536 KB) OKAY [ 1.421s] Writing 'boot_a' OKAY [ 0.075s] Finished. Total time: 1.498s rebooting to system ... Rebooting OKAY [ 0.001s] Finished. Total time: 0.001s 2022-06-14 10:30:05 Done! Flashing elapsed time: 193 seconds
You're doing everything correctly, but you have a suspect Magisk module in ViPER4AndroidFX that has caused bootloops in the past during updates.
If you're phone is getting adb briefly, you can try the disable Magisk button, if no adb, there is a key combination, I think volume down when you see the logo (can't remember, double check).
 

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
You're doing everything correctly, but you have a suspect Magisk module in ViPER4AndroidFX that has caused bootloops in the past during updates.
If you're phone is getting adb briefly, you can try the disable Magisk button, if no adb, there is a key combination, I think volume down when you see the logo (can't remember, double check).
Flashing the non-patched boot file solved the problem.

I'm generally curious as to why the system boots properly when manually flashing Magisk and said problematic module but not when flashed via your program. Is it a complicated procedure required tog get this to work? How is this procedure different from the process that happens when manually flashing?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
Flashing the non-patched boot file solved the problem.

I'm generally curious as to why the system boots properly when manually flashing Magisk and said problematic module but not when flashed via your program. Is it a complicated procedure required tog get this to work? How is this procedure different from the process that happens when manually flashing?
PixelFlasher flashing is really not that different from manually flashing.
Go to the following path on your PC
%AppData%\PixelFlasher\factory_images\oriole-sq3a.220605.009.b1

Compare the two files flash-all.bat (manual file) and flash-phone.bat (PixelFlasher file)
The differences are as follows:

1- PIxel flasher adds -s DeviceID to fastboot commands, this is done to reference the specific device, in case you have multiple devices connected to your phone, this addition targets the correct device, You can't have multiple devices connected using the manual flashing with flash-all.bat, you would get an error.
This is a fastboot switch, and there is no way this could cause any issues, in fact it makes it more flexible / robust.

2- If you choose flash options (example disable verity or flash to both slots), which I suppose you don't, then those options would be added to fastboot command. Again this should not be causing an issue for you, as you don't set those.

3- -w is removed if you chose Keep Data, so that your phone is not wiped. This is from all the referenced guides and standard step you would do if you were doing things manually.

4- --skip-reboot option is added to the line that flashes the image, the line:
fastboot flash radio radio-oriole-g5123b-100840-220505-b-8544885.img
This is to keep the phone in bootloader mode after flashing so that patched boot.img can be flashed before booting to system.
Again there is no way this could make a difference in the form you reported.

5- Flashing of patched boot.img is added if you are flashing patched boot.img
fastboot flash boot pf_boot.img.
The manual way you don't flash patched boot.img, you do that afterwards right? unless you manually modify the file in a similar fashion.

6- Reboot to system is added, to finally boot to system.

As you can see, there is really not much different.

If you browser the magisk general thread, you'd see many cases where people experienced bootloops by keeping certain magisk modules enabled.
It does not mean that it happens in every version, it all depends on the changes introduced in the new version that might not work well with an older module.
It's always a good idea to temporarily disable such modules and then enable them back.
That is why PixelFlasher has added a UI to manage your modules.
 
  • Like
Reactions: RobbyRobbb

miss

Senior Member
Dec 27, 2006
301
31
Xiaomi Mi 9
Google Pixel 6
In June everything went well, now with the July ota, magisk asks me to reinstall the application, and I lose root

edit. restart the phone and it works, thanks for your application
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
In June everything went well, now with the July ota, magisk asks me to reinstall the application, and I lose root
You applied OTA?

Although PixelFlasher supports flashing OTA in advanced mode, it's there for convenience for power users, the recommendation is always to use the factory image, much less issues and easier.
In any case, please provide a support.zip file (in Help menu) and I'll take a look at it to see what happened.
What image you applied in what sequence to which slot ...
 

miss

Senior Member
Dec 27, 2006
301
31
Xiaomi Mi 9
Google Pixel 6
You applied OTA?

Although PixelFlasher supports flashing OTA in advanced mode, it's there for convenience for power users, the recommendation is always to use the factory image, much less issues and easier.
In any case, please provide a support.zip file (in Help menu) and I'll take a look at it to see what happened.
What image you applied in what sequence to which slot ...
not, rom stock july
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
New release:
July 18, 2022 v3.4.0 release
  • Improvements to the boot extraction / categorization.
  • Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
  • Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
 
  • Love
Reactions: tom1807
D

Deleted member 12254421

Guest
Edit: Resolved... Turns out the damn app was patching an old magisk. I manually patched my boot.img with the latest version and my phone is fine now.
 
Last edited by a moderator:

Project_WHaT

Member
Nov 3, 2016
18
2
OnePlus 6
Google Pixel 6
I just tried to flash from patched Android 12 to patched 13, but at the end of the flash process, the console says everything finished and is rebooting into system. However, my Pixel 6 rebooted to Fastboot mode and for "Enter reason" it says "boot failure"

What should I try to do at this point? I've attached the support zip. Thanks

EDIT:
I noticed other people have had similar problems online that say "Error!", but mine is slightly different:

Code:
NOS Production: yes
Device state: unlocked
Boot slot: a
Enter reason: boot failure

I'm afraid to boot or do anything at this point since I've read a lot of articles about how downgrading to 12 after 13 can permanently brick the device, so I'm refraining from trying anything at this point

EDIT 2:
I've found the issue.


When patching using the PixelFlasher, it uses the kernel which was on a much older version.

EDIT 3:
For those who encounter a similar situation, to recover from this, I just followed the steps in "Install/Update Factory Image keep data, wipe data, or use @badabing2003 PixelFlasher", specifically the "Flash Factory Image Keep Data" category that can be found here:

 

Attachments

  • support.zip
    5.5 KB · Views: 5
Last edited:

tom1807

Senior Member
Thought I better ask before doing something wrong.
From my understanding, after updating to A13 (active slot: A) A12 should be still on slot B or minimum the previous bootloader "bootloader-oriole-slider-1.2-8318357".
For comparison the current bootloader of A13 is "bootloader-oriole-slider-1.2-8739948".
Saw some reports, if something goes wrong, mobile will boot from Slot B which still contains the previous bootloader and the mobile won't boot anymore.

To be prepared, I thought flash the bootloader also to Slot B
Would be the following steps correct?
1. Select the Image in PixelFlasher
2. Flash Mode select "Custom Flash"
3. Select bootloader, select the correct, extracted bootloader "bootloader-oriole-slider-1.2-8739948"
4. Select "Flash on both slots"

The last is not quite clear to me.
Or should I just "Set Active Slot" to A and then flash the bootloader
Or is the correct way "Flash to both slots"?

Cheers
Tom

Edit: NVM, I used fastboot and flashed by the command "fastboot flash bootloader --slot=all bootloader-oriole-slider-1.2-8739948.img"
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,005
930
Thought I better ask before doing something wrong.
From my understanding, after updating to A13 (active slot: A) A12 should be still on slot B or minimum the previous bootloader "bootloader-oriole-slider-1.2-8318357".
For comparison the current bootloader of A13 is "bootloader-oriole-slider-1.2-8739948".
Saw some reports, if something goes wrong, mobile will boot from Slot B which still contains the previous bootloader and the mobile won't boot anymore.

To be prepared, I thought flash the bootloader also to Slot B
Would be the following steps correct?
1. Select the Image in PixelFlasher
2. Flash Mode select "Custom Flash"
3. Select bootloader, select the correct, extracted bootloader "bootloader-oriole-slider-1.2-8739948"
4. Select "Flash on both slots"

The last is not quite clear to me.
Or should I just "Set Active Slot" to A and then flash the bootloader
Or is the correct way "Flash to both slots"?

Cheers
Tom

Edit: NVM, I used fastboot and flashed by the command "fastboot flash bootloader --slot=all bootloader-oriole-slider-1.2-8739948.img"
Flash to both slots does exactly what you did manually.
Switching slot and then flashing to that slot only would have worked as well, but stay in fastboot mode if the second slot is not bootable so that you can flash, otherwise the system will revert back to the good slot.

I have seen cases where flash to both slots of full image (as opposed to just boot.img) sometimes fail when resizing partitions on the older slot, I'm not sure why this actually happens, perhaps the other partition is really old and geometry is way too different, although I would have expected that Google's flashing routine would handle that gracefully, perhaps it's not meant to be used with full image.

If anyone has theories or knows why that happens please let me know if I should block flashing both slots for a full image or at least warn the user.
 
  • Like
Reactions: tom1807

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    PixelFlasher 4.0.0 pre-release:
    Sep 25, 2022 v4.0.0 pre-release
    • New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
      See Patching flow chart for details.
    • New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
    • New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
    • New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
    • New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
      Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
    • New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
    • New spinner to indicate PixelFlasher activity.
    • Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
    • PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
      This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
    • PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
      This is just an extra validation.
    • Code cleanup / refactoring, adding more validations and exception handling.
    • Print debug details when encountering non compliant Magisk modules.
    • Firmware link now takes you to the device's download page instead of just the general download page.
    • To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
    • Allow sideload even if bootloader is locked.
    1
    Yeah normal stuff, not custom rom or anything like that.
    Just follow the Basic flow in the main thread and select Flash on both slots.
    1
    I don't have share...
    No not it the settings, at the bottom, hit the Superuser icon next to the Home icon (the second from the left)
    1
    I've been curious about PixelFlasher for a while and finally tried it. Stumbled a couple times but error messages were great at coaching. This is an awesome tool. Excellent docs too.
    1
    I've been curious about PixelFlasher for a while and finally tried it. Stumbled a couple times but error messages were great at coaching. This is an awesome tool. Excellent docs too.
    Thanks for the feedback,
    I'm all ears, what could be done better or differently to minimize the stumbling blocks?
    If they're feasible I'll definitely consider it.
  • 11
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 6
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.


    Basic mode: Should suit most users. Some of the features in basic mode are:
    • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
    • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
      No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
      No more setting airplane mode and clearing storage to retain Safetynet passing.
    • Display details of boot.img.
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

    Troubleshooting:
    Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.
    5
    Thank you for the consideration.
    No donation, this is simply giving back to the community that has given me a lot over the years.
    5
    Update:
    Version 2.0.1 which includes a hotfix for issue reported here.
    5
    New Release:
    April 17, 2022 v2.3.0 release
    • Optional automatic check for updates feature.
    • Added help menu links to:
      - Report an issue
      - Feature Request
      - PixelFlasher Project Page
      - PixelFlasher Community (Forum)
      - Homeboy76's Guide
      - V0latyle's Guide
      - Open Configuration Folder
      - Check for New Version
    • Icons for menu items.
    • Link to download Pixel Firmware.
    • Link to download Android Platform Tools.
    • Unlock Bootloader.
    • Lock Bootloader.
    • SOS (experimental) - disable Magisk modules to get out of bootloop.
    • Additional flashing options:
      - product
      - system
      - system_ext
      - system_other
      - vbmeta_system
      - vbmeta_vendor
    • Added sideload flashing option.
    • Updated documentation.
    • Further improved console messages for troubleshooting.
    • Linux build using Github Actions.
    • Manual build for Kali Linux.
    4
    Just a feedback.
    Used the PixelFlasher for the update to Android 13 on my Pixel 6. No problems to report, smooth as usual.
    Great work.

    Cheers
    Tom