Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

[Fishawy]

If it ever comes up for you guys that a bootloop happens because of a Magisk module, there's also the option to running the adb command: adb wait-for-device shell magisk --remove-modules so that it doesn't erase everything set up in Settings like it does in Safe Mode (supposedly from what I've read, haven't experienced it myself). You'll have to re-install all the modules, but for most people that's more preferable than re-initializing and setting up everything in Settings...

But I, too, am fascinated by the "Special Magisk" build!

Thanks for that. Safe mode only disables modules instead of removing them, and it doesn't mess up with settings in my case.

Special Magisk is a very good alternative.

 

[simplepinoi177]

Thanks for that. Safe mode only disables modules instead of removing them, and it doesn't mess up with settings in my case.

Special Magisk is a very good alternative.

interesting...I'll keep it in mind...I just read other users talking about how running safe mode erases the settings or something...or else the praises of that adb command wouldn't be prevalent...

EDIT: quick Google search states that some homescreen shortcuts might disappear and all non-Google login will have to be signed back in...or something...

 

[Fishawy]

interesting...I'll keep it in mind...I just read other users talking about how running safe mode erases the settings or something...or else the praises of that adb command wouldn't be prevalent...

EDIT: quick Google search states that some homescreen shortcuts might disappear and all non-Google login will have to be signed back in...or something...

Widgets do reset, yes, but I have them saved already within the respective apps (Elixir, Chronus, Digital Clock, etc). So whenever safe mode is triggered, it's the matter of a single click on the hollow widget to restore it from the saved settings.

 

[badabing2003]

I didn't even know such thing existed. Thank you so much for this! It helps to know that there's a backup option - next to safe mode - to recover bootloops and repatch at the same time.

If it ever comes up for you guys that a bootloop happens because of a Magisk module, there's also the option to running the adb command: adb wait-for-device shell magisk --remove-modules so that it doesn't erase everything set up in Settings like it does in Safe Mode (supposedly from what I've read, haven't experienced it myself). You'll have to re-install all the modules, but for most people that's more preferable than re-initializing and setting up everything in Settings...

But I, too, am fascinated by the "Special Magisk" build!

Some clarification about this.
For starters all the credit goes to @gecowa6967 (I just included it in PF), he's the one who came up withthis special build, and it's based of Magisk Canary 25203, although it's not very difficult to clone the Magisk repo and build it from any code base by merging his changes. You can read all about it here.

In any case, almost certainly the version won't matter as the use for this is just to get an opportunity to disable the modules.

adb wait-for-device shell magisk --remove-modules does not always work when you are bootlooping, unless the device gets into adb mode briefly, which would allow the execution of the magisk command, it won't work, and a lot of times a bootloop never gets into adb mode.
Furthermore, even the combo button booting to safe mode does not always work, you can read it in the linked post, it's a timing issue / Magisk issue.

I hadn't noticed the special Magisk option either! But how do you unhidde if you're in a bootloop?

This is not a cure for all bootloops, if you are bootlooping due to a Magisk modules, then you can flash stock boot and be able to boot to system, as the module won't load.
And you can't disable Modules unless you're rooted (chicken and egg situation)
If this is the case, you can uninstall Magisk Manager, install the special version, flash a patch.
Now you are rooted but modules are not loading, and you should be able to disable module,, flash a normal patch and get going again.

 

[simplepinoi177]

Some clarification about this.
...you can read it in the linked post, it's a timing issue / Magisk issue.

I am fascinated by the quoted post. I hate to pester you about it, but in the aspiration of simple better knowledge on the subject matter, what is this linked post? The link in the quoted post seems to be gecowa6967's post explaining how he came to creating the modified Magisk...
Sorry if it's totally going over my head and I'm totally missing something obvious...

 

[simplepinoi177]

...

to recover from a bootloop caused by Magisk modules you can do the following.

Unhide + Uninstall Magisk Manager
...

Good luck.

Is there a way (another) to Uninstall Magisk Manager if you've hidden Magisk but forgotten the app it was renamed to...?

 

[HipKat]

Is there a way (another) to Uninstall Magisk Manager if you've hidden Magisk but forgotten the app it was renamed to...?

 

[badabing2003]

Sorry if it's totally going over my head and I'm totally missing something obvious...

Not sure what you're trying to grasp, I linked the post so that you can see why it was needed and how it was addressed.
I mentioned that you can do the same with any Magisk codebase, but if you are asking to learn how you can build your own Magisk from Github, there are posts about that, basically you'd have to clone the repo, modify/adjust the actions and obviously make the necessary code changes you want to build from, but that's not the point of my above post.

Is there a way (another) to Uninstall Magisk Manager if you've hidden Magisk but forgotten the app it was renamed to...?

Yes you can know a hidden Magisk's package name.
Install TB Checker from play store and it would tell you.

 

[simplepinoi177]

Yes you can know a hidden Magisk's package name.
Install TB Checker from play store and it would tell you.

Yeah...sorry for the confusion and lack of clarification...i, myself, wouldn't just suddenly forget what i renamed Magisk when hiding it, but apparently another member here seemed to have lost it somehow and I'm trying to walk them through uninstalling it. That's why I couldn't be clearer in my original post asking...
I simply remembered it (unhiding and uninstalling magisk) here recently so I thought I'd shoot a shot and ask here...and you came through! So thank you!

UPDATE: just checked it, and I can't seem to find if/where the app shows what the Magisk Manager app is renamed as....

 

[HipKat]

Yeah...sorry for the confusion and lack of clarification...i, myself, wouldn't just suddenly forget what i renamed Magisk when hiding it, but apparently another member here seemed to have lost it somehow and I'm trying to walk them through uninstalling it. That's why I couldn't be clearer in my original post asking...
I simply remembered it (unhiding and uninstalling) magisk here recently so I thought I'd shoot a shot and ask here...and you came through! So thank you!

UPDATE: just checked it, and I can't seem to find if/where the app shows what the Magisk Manager app is renamed as....

You don't see an app in your app drawer that doesn't seem right?? I just name mine Settings1, fwiw.

 

[simplepinoi177]

You don't see an app in your app drawer that doesn't seem right?? I just name mine Settings1, fwiw.

yeah...it's kinda confusing and the member hasn't responded so...

FWIW, the member is on a Pixel 3, so I couldn't remember much of how Android Pie or Q worked, but IIRC, you couldn't necessarily hold down on an app (in the app drawer or homescreen) and click App Info like you can today -- you had to go into the Settings and App section or something to get into an app info. Harder still if the member doesn't remember the app name...
But the member was rather confusing as the member stated that it would force close when attempting to open -- so how could you not know the app name it was renamed as?!?!

 

[krakout]

Probably meant the package name?

 

[lexpower]

Hi guys, can I get some help please?

I have a 7 pro that is/was stucked on google logo. Phone is entering fastboot mode normally.

When I tried to flash it with flasher first few steps went fine, but then flasher froze and I got whole bunch of messages that the archive doesn't contain all kind of .sig files etc.

Unfortunately I don't know what caused this problem, I was guessing It won't be a problem flashing it since it goes to fastboot mode fine.

Here is the log if that can help.

Tnx in advance.

2023-03-27 12:42:32 PixelFlasher 4.8.1.0 Flashing Phone
==============================================================================
Android Platform Tools Version: 33.0.3-8952118
2023-03-27 12:42:32 Flashing device 2C171FDH30006A ...
Flash Mode: Wipe Data
C:\Users\CuvajNS\AppData\Roaming\PixelFlasher\factory_images\cheetah-tq1a.221205.011>chcp 437
Active code page: 437
Sending 'bootloader_b' (12332 KB) OKAY [ 0.281s]
Writing 'bootloader_b' (bootloader) Flashing pack version cloudripper-1.0-9231809
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(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_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(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_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.421s]
Finished. Total time: 0.718s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for 2C171FDH30006A >
Sending 'radio_b' (111200 KB) OKAY [ 2.477s]
Writing 'radio_b' (bootloader) Flashing pack version g5300g-220923-221028-M-9229469
(bootloader) Flashing partition modem_b
OKAY [ 0.156s]
Finished. Total time: 2.636s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for 2C171FDH30006A >
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9231809
Baseband Version.....: g5300g-220923-221028-B-9229469
Serial Number........: 2C171FDH30006A
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.010s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.492s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.482s]
Writing 'boot_b' OKAY [ 0.078s]
extracting init_boot.img (8 MB) to disk... took 0.062s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.187s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.078s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.374s]
Writing 'dtbo_b' OKAY [ 0.016s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.000s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.031s]
Writing 'pvmfw_b' OKAY [ 0.000s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.000s]
extracting vbmeta_system.img (0 MB) to disk... took 0.016s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.000s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_b' OKAY [ 0.000s]
extracting vendor_boot.img (64 MB) to disk... took 0.437s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.468s]
Writing 'vendor_boot_b' OKAY [ 0.078s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.312s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 1.466s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.095s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for 2C171FDH30006A >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.029s]
Resizing 'product_b' OKAY [ 0.000s]
Resizing 'system_b' OKAY [ 0.000s]
Resizing 'system_dlkm_b' OKAY [ 0.000s]
Resizing 'system_ext_b' OKAY [ 0.000s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_b' OKAY [ 0.000s]
Resizing 'vendor_dlkm_b' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.000s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2778 MB) to disk... took 29.404s
archive does not contain 'product.sig'
Sending 'product' (2845552 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sleeping 5-10 seconds ...
flashing pf_boot ...
< waiting for 2C171FDH30006A >
Sending 'init_boot_b' (8192 KB) OKAY [ 0.183s]
Writing 'init_boot_b' OKAY [ 0.046s]
Finished. Total time: 0.231s
rebooting to system ...
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
2023-03-27 12:49:02 Done!
Flashing elapsed time: 391 seconds
------------------------------------------------------------------------------

 

[badabing2003]

Hi guys, can I get some help please?

I have a 7 pro that is/was stucked on google logo. Phone is entering fastboot mode normally.

When I tried to flash it with flasher first few steps went fine, but then flasher froze and I got whole bunch of messages that the archive doesn't contain all kind of .sig files etc.

Unfortunately I don't know what caused this problem, I was guessing It won't be a problem flashing it since it goes to fastboot mode fine.

Here is the log if that can help.

Tnx in advance.

Looks like a communication issue.
Try another cable
Try another usb port (preferably usb2)
Make sure you don't touch the cable, phone during flashing.
Try flashing again, if it fails, provide a support file.

 

[lexpower]

It looked liked that to me as well. I don't have a type c port on my laptop, waiting a friend to bring me the adapter. I was using my oneplus cable.
Are there some things that I have to pay attention to regarding versions of boot and firmwares?
Since I don't know what was done to cause this problem I am not sure if I can flash older firmwares or not. I have downloaded november firmware btw.

Tnx one more time.

 

[badabing2003]

It looked liked that to me as well. I don't have a type c port on my laptop, waiting a friend to bring me the adapter. I was using my oneplus cable.
Are there some things that I have to pay attention to regarding versions of boot and firmwares?
Since I don't know what was done to cause this problem I am not sure if I can flash older firmwares or not. I have downloaded november firmware btw.

Tnx one more time.

Typically you don't need to flash older firmware,
You're using a good version of Android Platform tools
But without full logs, I don't know other details like Magisk version, modules used, your existing firmware, what you selected as boot image ...

 

[lexpower]

PixelFlasher 4.8.1.0 started on :2023-03-27 13:36:37
Platform: win32
System Timezone: ('Central Europe Standard Time', 'Central Europe Daylight Time') Offset: 2.0
Configuration Path: C:\Users\CuvajNS\AppData\Roaming\PixelFlasher
{
"advanced_options": false,
"boot_id": null,
"custom_codepage": null,
"custom_rom": false,
"custom_rom_path": null,
"customize_font": false,
"dev_mode": false,
"device": null,
"disable_verification": false,
"disable_verity": false,
"fastboot_force": false,
"fastboot_verbose": false,
"firmware_path": "C:\\Users\\CuvajNS\\Desktop\\adb\\cheetah-tq1a.221205.011-factory-b144b426.zip",
"flash_both_slots": false,
"flash_to_inactive_slot": false,
"force_codepage": false,
"height": 832,
"magisk": "com.topjohnwu.magisk",
"mode": "wipeData",
"pf_font_face": "Courier",
"pf_font_size": 12,
"phone_path": "/storage/emulated/0/Download",
"platform_tools_path": "C:\\Users\\CuvajNS\\Desktop\\platform-tools",
"pos_x": 246,
"pos_y": 95,
"selected_boot_md5": null,
"temporary_root": false,
"update_check": true,
"verbose": false,
"version": "4.8.1.0",
"width": 1145
}
System Default Encoding: utf-8
File System Encoding: utf-8
Active code page: 437

2023-03-27 13:37:20 Selected Platform Tools Path:
C:\Users\CuvajNS\Desktop\platform-tools.
SDK Version: 33.0.3-8952118

Please Process the firmware!

Loading Device list ...
This could take a while, please be patient.

2023-03-27 13:37:20 No Device is selected!
Load time: 47 seconds
Launching browser for Firmware download URL: https://developers.google.com/android/images#

2023-03-27 13:53:32 Scanning for Devices ...
1 Device(s) are found.
2023-03-27 13:53:33 No Device is selected!


Selected Device on 2023-03-27 13:53:35:
Device ID: 2C171FDH30006A
Device Model: cheetah
Device Active Slot: b
Device Mode: f.b
Device Unlocked: True

2023-03-27 13:53:56 The following firmware is selected:
cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip
Selected Firmware cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip SHA-256: cefc4e564cb920af510a44a9cdb982ba4e8af879f6796490e03128f12f92189e

Please Process the firmware!

==============================================================================
2023-03-27 13:54:26 PixelFlasher 4.8.1.0 Processing firmware file ...
==============================================================================
7-Zip 21.07 (x64) : Copyright (c) 1999-2021 Igor Pavlov : 2021-12-26
Scanning the drive for archives:
1 file, 2783825672 bytes (2655 MiB)
Extracting archive: C:\Users\CuvajNS\Desktop\cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip
--
Path = C:\Users\CuvajNS\Desktop\cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip
Type = zip
Physical Size = 2783825672
Everything is Ok
Folders: 1
Files: 6
Size: 2800684382
Compressed: 2783825672
Package ID: 1
Boot ID: 1
Package_Boot ID: 1

Please select a boot image!
Process firmware time: 36 seconds
------------------------------------------------------------------------------

Selected Boot:
File: init_boot.img
Path: C:\Users\CuvajNS\AppData\Roaming\PixelFlasher\boot_images4\4d938d3c7bab8b0ca7accccef2aa07eefd20602d\init_boot.img
SHA1: 4d938d3c7bab8b0ca7accccef2aa07eefd20602d
Patched: False
Date: 2023-03-27 13:55:02
Firmware Fingerprint: cheetah-tq2a.230305.008.c1
Firmware: C:\Users\CuvajNS\Desktop\cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip
Type: firmware



*** Dialog ***
Android SDK Version: 33.0.3-8952118
Device: 2C171FDH30006A cheetah
Factory Image: C:\Users\CuvajNS\Desktop\cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip

Boot image: 4d938d3c / 4d938d3c
From: C:\Users\CuvajNS\Desktop\cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip

Flash Mode: wipeData

Flash To Inactive Slot: False


Note: Pressing OK button will invoke a script that will utilize
fastboot commands, this could possibly take a long time and PixelFlasher
will appear frozen. PLEASE BE PATIENT.
In case it takes excessively long, it could possibly be due to improper or
bad fasboot drivers.
In such cases, killing the fastboot process will resume to normalcy.

Do you want to continue to flash with the above options?
Press OK to continue or CANCEL to abort.

______________

The script content that will be executed:
___________________________________________________
chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v4.8.1.0

:: cd C:\Users\CuvajNS\AppData\Roaming\PixelFlasher\factory_images\cheetah-tq2a.230305.008.c1

PATH=%PATH%;"%SYSTEMROOT%\System32"
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A flash bootloader bootloader-cheetah-cloudripper-1.0-9618366.img
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A flash radio radio-cheetah-g5300g-221229-230210-b-9589366.img
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A reboot-bootloader
ping -n 5 127.0.0.1 >nul
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A --skip-reboot -w update image-cheetah-tq2a.230305.008.c1.zip
echo rebooting to bootloader ...
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A reboot bootloader
echo Sleeping 5-10 seconds ...
ping -n 5 127.0.0.1 >nul
ping -n 5 127.0.0.1 >nul
echo flashing pf_boot ...
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A flash init_boot pf_boot.img
echo rebooting to system ...
"C:\Users\CuvajNS\Desktop\platform-tools\fastboot.exe" -s 2C171FDH30006A reboot
___________________________________________________

2023-03-27 13:55:35 User Pressed Ok.

==============================================================================
2023-03-27 13:55:35 PixelFlasher 4.8.1.0 Flashing Phone
==============================================================================
Android Platform Tools Version: 33.0.3-8952118
2023-03-27 13:55:35 Flashing device 2C171FDH30006A ...
Flash Mode: Wipe Data
C:\Users\CuvajNS\AppData\Roaming\PixelFlasher\factory_images\cheetah-tq2a.230305.008.c1>chcp 437
Active code page: 437
Sending 'bootloader_b' (12528 KB) OKAY [ 0.374s]
Writing 'bootloader_b' (bootloader) Flashing pack version cloudripper-1.0-9618366
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(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_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(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_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.421s]
Finished. Total time: 0.811s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for 2C171FDH30006A >
Sending 'radio_b' (111532 KB) OKAY [ 3.289s]
Writing 'radio_b' (bootloader) Flashing pack version g5300g-221229-230210-M-9589366
(bootloader) Flashing partition modem_b
OKAY [ 0.156s]
Finished. Total time: 3.445s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
< waiting for 2C171FDH30006A >
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9618366
Baseband Version.....: g5300g-221229-230210-B-9589366
Serial Number........: 2C171FDH30006A
--------------------------------------------
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 'b' OKAY [ 0.086s]
extracting boot.img (64 MB) to disk... took 0.480s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.933s]
Writing 'boot_b' OKAY [ 0.078s]
extracting init_boot.img (8 MB) to disk... took 0.062s
archive does not contain 'init_boot.sig'
Sending 'init_boot_b' (8192 KB) OKAY [ 0.234s]
Writing 'init_boot_b' OKAY [ 0.016s]
extracting dtbo.img (16 MB) to disk... took 0.094s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.484s]
Writing 'dtbo_b' OKAY [ 0.031s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.016s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.031s]
Writing 'pvmfw_b' OKAY [ 0.000s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.016s]
Writing 'vbmeta_b' OKAY [ 0.000s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.000s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_vendor_b' OKAY [ 0.000s]
extracting vendor_boot.img (64 MB) to disk... took 0.452s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.919s]
Writing 'vendor_boot_b' OKAY [ 0.078s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.312s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_b' (65536 KB) OKAY [ 1.919s]
Writing 'vendor_kernel_boot_b' OKAY [ 0.078s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for 2C171FDH30006A >
Sending 'super' (5 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 1.023s]
Resizing 'product_b' OKAY [ 0.000s]
Resizing 'system_b' OKAY [ 0.016s]
Resizing 'system_dlkm_b' OKAY [ 0.000s]
Resizing 'system_ext_b' OKAY [ 0.000s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_b' OKAY [ 0.000s]
Resizing 'vendor_dlkm_b' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.000s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2857 MB) to disk... took 29.896s
archive does not contain 'product.sig'
Sending 'product' (2926324 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sleeping 5-10 seconds ...
flashing pf_boot ...
< waiting for 2C171FDH30006A >
Sending 'init_boot_b' (8192 KB) OKAY [ 0.247s]
Writing 'init_boot_b' OKAY [ 0.010s]
Finished. Total time: 0.257s
rebooting to system ...
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
2023-03-27 13:57:51 Done!
Flashing elapsed time: 137 seconds
------------------------------------------------------------------------------

Here is the full log with latest firmware.
The only change is that now I don't have that red screen at the beginning saying phone is corrupted.

 

[swour]

Thanks for creating this most useful tool! The first round of flashing went flawless.


Regarding the correct procedure to flash to the inactive slot for monthly updates. Is activating the option enough or does the user have to manually switch the active slot at some point? In other words, can flashing to inactive slot be left activated for each update and PixelFlasher will do the rest?

 

[HipKat]

Thanks for creating this most useful tool! The first round of flashing went flawless.


Regarding the correct procedure to flash to the inactive slot for monthly updates. Is activating the option enough or does the user have to manually switch the active slot at some point? In other words, can flashing to inactive slot be left activated for each update and PixelFlasher will do the rest?

The default is to flash to the inactive slot. You can change it to, however you wish, but most of us just let it flash to the inactive slot each month.

 

[lexpower]

Update: manage to fix it after several tries. Not touching phone while in fastbootd mode helped

Tnx guys for such awesome tool. Keep up the good work.