{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note (this software is covered under the The Apache Software Foundation Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.html)
Code:
By flashing this custom ROM (or [I]any[/I] ROM), you have voided your warranty (rooted). I am [B]NOT[/B] responsible for bricking your phone - if that occurs, it was [I]all your fault![/I]
First and foremost, thanks goes to the following Devs (not in any particular order):
God
Mustaavalkosta
PipelinerArd
PBeeler
PartimusPrime
Second, but not least, thanks goes to the following testers (not in any particular order):
coming soon (way too much cutting/pasting right now lol)
This AOKP ROM is a beta kitkat build that I am pulling from AOKP source (to keep it up-to-date upstream), and have added my own unique goodness!
Mustaavalkosta's htc7x30-3.0 kernel (thank you Mustaavalkosta, for ALL of your hard work and investment into the Open Source Community!!!!!!)
is what I am using. Please note that Individual results may vary! I use this as my Daily Driver, but PLEASE NOTE - THIS IS STILL IN BETA!!!
Click to expand...
Click to collapse
Please checkout the Blog & Video Reviews for this ROM here (links to 2nd post)
Click to expand...
Click to collapse
Beta #1 - kitkat 4.4.2:
Initial "beta" build
Prebuilt Apps
Video Editor
Custom bootanimation (soon to come): PartimusPrime
DeskClock
ROM Control
Apollo Music Player
CyanogeMod File Manager
Calendar
Bluetooth
Wifi
Busybox (enhanced busybox - from SaberMod)
DSP Manager (music/sound eq)
AOKP Theme Manager
Performance Control (included as app in App Drawer - NOT System Settings Menu)
AOKP Torch
Sound Recorder
Swag Wallpapers
App Manager
Proximity-Sensor-Recalibrator
Supported but not enabled til next Build:
Screenrecord Toggle
[*]Screenshot Toggle
[*]Add screenshot to Power Menu
[*]Implement client-side incognito mode in stock browser
[*]Show a startup page in incognito mode in stock browser
[*]Add Screenshot delay options
[*]Power Menu customization options
[*]Camera: Add Burst mode
[*]Set default video quality to the highest
[*]Add lockscreen wallpaper
[*]Ribbons V2
[*]Mobile Network Battery Saver Mode
[*]Allows setting of some system animations.
============================================================
OTHER CHANGELOGS - 4.4.2 Beta #2 through 4.4.4 RC11 ARCHIVED (to clean up this OP/hit character limit in post)
================================================== ==========
SchutzhundAOKP RC 12 - 4.4.4:
Misc bug fixes
FRAMEWORKS BASE:
Fix delay in sending AUDIO_BECOMING_NOISY intent Themes: Only process themes that are applied during boot (Currently, the PackageManagerService will process all themes and ensure their resources are compiled and available to the system. This is highly inefficient and can bog the system down when booting. This patch will only process the themes that are currently applied durring boot and lets the ThemeService take care of queuing up the others for processing. This reduces boot time considerably, especially when the user has many themes installed.)
WallpaperCropper: respect max wallpaper width
AppWidget: Make widget update quickly
systemui: Unbreak the planet
framework: Close system windows when performing 'switch to last app' action
Add PowerManager integration for button and keyboard backlight.
Import translations from crowdin.net
Themes: Let ThemeService handle all theme processing
VENDOR AOKP:
update apns-conf.xml
added Bmobile Trinidad APN
added Boost, Credo & Ting APNs (Also changed name of Sprint MMS apn to be clearer.)
add Virgin Mobile USA apn
added Lycamobile, Aero2, and T-Mobile Poland APNs
added Claro Argentina APN
added Cambodia APNs
added ONO and Euskaltel APNs
added Public Mobile APN, corrected Rogers WAP APN
added Axis, AWCC, MTN, Etisalat, Hutch, MPT APNs.
corrected Smart APN: missing space before "type"
added Yota APN (As mentioned in CYAN-5074)
Add APN for EMOBILE (Japan)
Clean up APNs for au and SoftBank (Japan)
APNs remove trailing whitespace from Bite
corrected Telekom DE APNs
corrected Vodafone DE & Vodafone PT APNs
corrected Smarts RU APNs
added 13 Lycamobile APNs, combined TMI APN, added 48months APN
added Lycamobile APNs for NL,BE,FR,ES,CH,UK,DK,SE,DE,PT,IE,US,AU TMI APN for Internet/MMS is now the same
ROMCONTROL:
Customizable HW keys backlight and timeout
Import translations from crowdin.net
DEVICE HTC ACE:
fstab: rework and tune down some flags (errors=panic seems to be causing issues with certain S-ON devices. No clue why, just disable it for now.)
kill devlog partition and HTC logger
================================================== ==========
SchutzhundAOKP RC 13 - 4.4.4:
CM cherry picks:
build: Fix pathmap derp
build: Use project pathmap for recovery (needed to support AOKP's build commits (and "fix" my own build errors lol)
Misc CM bug fixes
AOKP cherry picks:
BUILD:
build: Add "dtbs" target when building the kernel (This is needed for 3.10)
Build: Add support for specifying build variant in brunch/breakfast (This little modification allows specifying build variant in brunch/breakfast commands. For example we can use "brunch i9300 user" to build user variant instead of default userdebug. When no extra argument is given, userdebug is default.)
build: qcom: Set QCOM_*_PATH variables for hardware/qcom-* projects (This consolidates a bunch of one-off logic scattered throughout the code base. Usage in Android.mk files is trivial: At top level, use e.g. "ifeq ($(call my-dir),$(QCOM_AUDIO_PATH))". This works for all variants, including non-variants (i.e. AOSP). Within subdirs, use e.g. hardware/qcom/audio => $(QCOM_AUDIO_PATH) )
build: Introduce project pathmap and use it for qcom variants (The project pathmap tracks the path to the top level of a project. The following functions are provided:
project-set-path adds an entry.
project-set-path-variant adds a "variant" entry.
project-path-for retrieves an entry.
To use as a guard in Android.mk:
ifeq ($(call my-dir),$(call project-path-for,projectname))
To use for include paths in Android.mk:
LOCAL_C_INCLUDES += $(call project-path-for,projectname)/...
Set project pathmap for qcom project variants.)
build: Set QCOM variants for non-QCOM_HARDWARE defined targets
Add 'addaokp' helper function (Adds a gerrit remote for the selected project)
Add 'addcm' helper function (Adds a CM remote for the selected project)
CAMERA:
Camera: Fix histogram on/off states
It made the intended behavior reverted. Histogram mode was being set as enabled by default, but the histogram graph was not shown on screen. When disabling histogram feature, then the graph was being displayed. In other words, completely opposite of how it should work.
Moving disable values before enable values seems to fix this.
Camera2: Headset shutter mode (Use play button on headset to take a picture/video/panorama Use media next/previous for zoom)
Camera: Add manual focus mode
================================================== ==========
SchutzhundAOKP RC 14 - 4.4.4:
Misc CM bug fixes
SYSTEM CORE:
charger: Use project pathmap
system: Update function to calculate bytes per sample for offload
Update function to calculate bytes per sample for offload format
init: Fix memory corruption when sanitizing platform paths
This commit fixes code that incorrectly increments s when it
hits the terminator character of the string being sanitized.
This means it will randomly start trashing memory beyond the
end of the string being sanitized until it happens to hit two
NULs (\0\0) which will break it out of the loop.
init: Allow target-specific platform device base to be specified
Add optional build-time flag, TARGET_PLATFORM_DEVICE_BASE,
to specify the base sysfs path (without the /sys prefix)
where the platform device resides. This provides support for
targets where platform devices are all under a master level
platform device (e.g. soc-bus).
init: Allow platform devices directly under soc.0 *HACK*
Allow one level of platform device to be registered right
under the /sys/devices/soc.0 platform device.
ueventd: Add bootdevice symlink
Create the /dev/block/bootdevice symlink to point to the
boot device information based on kernel command line.
This decouples references to the boot device from the
actual device nodes (e.g. eMMC, UFS).
================================================== ==========
SchutzhundAOKP RC 15 - 4.4.4:
Misc CM bug fixes
FRAMEWORKS BASE:
Add double tap sleep feature to secure lockscreens.
In its current state double tap works on the status bar on unsecure
lockscreens this adds the feature to pin, password, and pattern
lockscreens.
- pin and password: double tap the text entry view.
- pattern: double tap anywhere on the pattern view.
Patch Set 3:
- add to slide lockscreen(glowpad): double tap glow pad to sleep
- update commit message
PS2: Added double tap on gesture view
P2P:initiate provisioning on persistant group removed.
The initiator, on a response from the peer with unknown group during the persistent reinvocation has to transit to the provisioning state to handle all the config methods (PIN and PBC). This commit ensures the same.
P2P: Disable 5GHz channels in 2.4 GHz only mode
When P2P device is configured in 2.4GHz only mode supplicant should not advertize 5GHz channels in its go negotiation frames. Hence disable 5GHz band channels when 2.4 GHz band only mode selected in Wi-Fi advanced settings.
Wi-Fi: Set BTCOEXMODE_DISABLED irrespective of BT's connection state
BTCOEXMODE_DISABLE has to be triggered during the DHCP phase even on an active BT connection to ensure that Wi-Fi is given preference over the BT. This commit ensures the same CRs-Fixed: 695307
Wifi: Handle P2P-REMOVE-AND-REFORM-GROUP event in GroupNegotiationState
Framework does not handle P2P-REMOVE-AND-REFORM-GROUP event if it is in GroupNegotiationState and p2p-GO will continue to operate in unsafe channel till it gets next P2P-REMOVE-AND-REFORM-GROUP event.
This commit adds handling of above event in GroupNegotiationState.
wlan: Modify sequence of events sent during DHCP phase.
Modify sequence of events sent to driver during DHCP phase, to make sure WLAN can enter into power save only after DHCP is done.
Display live wallpaper settings instead of wallpaper picker
If the livewallpaper service declares and supports a settings activity, display it instead of the wallparper picker in runnings apps details settings activity (settings button).
Themes: Force recompiling common resources when scanning theme
If a theme is re-installed multiple times and in less time than the 3 minute timout for common resources, it is possible for the installation to fail because it does not compile the common resources.
This is not something an average user would encounter normally but theme designers that are working on there theme and constantly installing updates have a better chance of encountering this situation.
We simply remove the theme from mAvailableCommonResources which will allow them to be recompiled.
PREBUILTS MISC:
ccache-3.1.9 built against glibc-2.12 from CentOS 6
LAUNCHER3:
Use wallpaper picker added to WallpaperCropper apk.
The code is still here for easier upstream merges.
SYSTEM CORE:
audio: Unhide MP2/WMA enums
System/core: Start qrng daemon upon power up
Set root permissions to qrng daemon upon powerup
Drop all permissions except few, just enough to make ioctl calls
Permission for hardware random device is changed in this gerrit (part of Point 1(above))
CAMERA2:
Disable video HDR on devices that don't support it
BUILD:
Revert "Add the keys I used to sign the market version of Superuser."
These are obsolete. This reverts commit 0f15d18a50d721faa8dee67f763405354025e25a.
Default to dtbToolCM
The default dtbTool isn't the correct module name for the module that actually lives in device/qcom/common/dtbtool
==========================================================
Click to expand...
Click to collapse
Git:
AOKP's git (I'm pulling from source)
CyanogenMod's git
AceEnablementProject's git
Please follow these instructions:
Please make a nandroid backup BEFORE flashing this ROM!!!
Please perform a Full wipe before flashing this ROM!!!
If you DO use the "dirty flash" method, please note that you cannot list ANY bugs/issues you encounter!
Flash your preferred GAPPS package after ROM flash (can be done in same Recovery session)
Let the ROM "settle in" BEFORE listing any issues!!!
How to get ART working on KitKat
To be continued...
ROM Builds:
SchutzhundAOKP 4.4.4 Builds <== GDrive (older Betas and RCs)
SchutzhundAOKP 4.4.4 Builds <== Mega (Mirror)
SchutzhundAOKP 4.4.4 Builds <== basketbuild (Latest 4.4.4 RCs)
Support files:
InspireMod: Inspire/Desire HD audio and GPS fixes (if needed)
Gapps <== GDrive
GApps <== GApps on basketbuild.com
Included are my own modded AOKP's Full GApps, BaNks Core, and a standard GApps (Full GApps updated as of 03/10/14.)
GApps & Inspire Mods <== Mega (Mirror)
Kernel:
Source (AceEnablementProject): github
Compiler (Mustaavalkosta): Self-built GCC 4.8.x
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
QA Bot said:
Q&A for [ROM] [KITKAT] SchutzhundAOKP - Android Open Kang Project - Desire HD
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
THREAD LOCATED HERE: Desire HD Q&A, Help & Troubleshooting [Q&A] [ROM] [KITKAT] SchutzhundAOKP - Android Open Kang Project - Desire HD
Click to expand...
Click to collapse
==> Donations Appreciated!
REVIEWS:
BLOGS:
Schutzhund AOKP Android 4.4.2 Review for HTC Desire HD by coolyahya
VIDEOS:
Coming Soon
Please note that the folks at AOKP have stripped their source for (the new) kitkat. They are currently "adding back" their typically AWESOME mods that made me fall in love with this ROM. They are actually writing them from scratch...
So instead of me adding my own mods to gain them back (Ribbons, "longpress back to kill app", "volume controls cursor", etc.,) - I am simply maintaining AOKP for our device for now. Well, I HAVE added my own dev apps, but otherwise, those AWESOMELY COOL AOKP features will be pulled in from upstream....
So please - DON'T ASK FOR ETA's lol!
Upload is in progress........ Final size should be 170.5 MB
Download and check md5, everything's ok... Full wipe, format all except sd card and error:
set_metadata_recursive: some changes failed. E: error in sdcard/aokp_ace_kitkat.....zip (Status 7). Instalation aborted.
Don't know what's happend or wrong with my sd card, i always make backup and install ROM from same sd card...
gogsy1975 said:
Download and check md5, everything's ok... Full wipe, format all except sd card and error:
set_metadata_recursive: some changes failed. E: error in sdcard/aokp_ace_kitkat.....zip (Status 7). Instalation aborted.
Don't know what's happend or wrong with my sd card, i always make backup and install ROM from same sd card...
Click to expand...
Click to collapse
Try to download again, I have no ploblem in flashing this rom.
irt118 said:
Try to download again, I have no ploblem in flashing this rom.
Click to expand...
Click to collapse
With firefox it says "Sorry, an error has occured. Retrying... i have downloaded with chrome and md5 was ok... strange... will try again...
gogsy1975 said:
Download and check md5, everything's ok... Full wipe, format all except sd card and error:
set_metadata_recursive: some changes failed. E: error in sdcard/aokp_ace_kitkat.....zip (Status 7). Instalation aborted.
Don't know what's happend or wrong with my sd card, i always make backup and install ROM from same sd card...
Click to expand...
Click to collapse
Exact same error here.
irt118 said:
Try to download again, I have no ploblem in flashing this rom.
Click to expand...
Click to collapse
Downloaded again with firefox and same error...
gogsy1975 said:
Download and check md5, everything's ok... Full wipe, format all except sd card and error:
set_metadata_recursive: some changes failed. E: error in sdcard/aokp_ace_kitkat.....zip (Status 7). Instalation aborted.
Don't know what's happend or wrong with my sd card, i always make backup and install ROM from same sd card...
Click to expand...
Click to collapse
zip file flashes fine on my device.... try another browser to download. Since I'm using Google Drive to host my files, it MAY be compatibility....BUT I'm using Firefox on my Linux box, as well as my phone (downloaded and flashed from both to test).
irt118 said:
Try to download again, I have no ploblem in flashing this rom.
Click to expand...
Click to collapse
+1
gogsy1975 said:
With firefox it says "Sorry, an error has occured. Retrying... i have downloaded with chrome and md5 was ok... strange... will try again...
Click to expand...
Click to collapse
ScumDroid said:
Exact same error here.
Click to expand...
Click to collapse
I DID get this on my Firefox Beta app, but I refreshed and it worked flawlessly after...
Unless someone has a host I can use (I'm out of Dropbox space).......
I just Triple-checked and yes, I downloaded with Firefox & flashed without any issues. So I'd say try again/refresh page/another browser. Once I get a host to host my files, I will not have to use Google Drive
gogsy1975 said:
Downloaded again with firefox and same error...
Click to expand...
Click to collapse
Download on my phone with stock browser and no problem.
Tried another one, which I downloaded by opera and no problem.
Updated changelog for today's build. Features listed will be "supported/built in", but may be "enabled" in the next build. Depends on what I do tonight lol!!!
gogsy1975 said:
Download and check md5, everything's ok... Full wipe, format all except sd card and error:
set_metadata_recursive: some changes failed. E: error in sdcard/aokp_ace_kitkat.....zip (Status 7). Instalation aborted.
Don't know what's happend or wrong with my sd card, i always make backup and install ROM from same sd card...
Click to expand...
Click to collapse
Recovery lacks support for SELinux and updater-script is trying to use unimplemented functions. The newest 4ext I tested passes with those new functions but it doesn't really set the SELinux labels based on my tests so the SELinux support seems to be limited to a stub.
This issue can be circumvented also with a patch for build repo so older recoveries are compatible too. https://github.com/Mustaavalkosta/android_build/commit/bd246b4028323db259f69a521e3fb8b6e944ae39
Sent from my Nexus 7 3G using Tapatalk HD
Mustaavalkosta said:
Recovery lacks support for SELinux and updater-script is trying to use unimplemented functions. The newest 4ext I tested passes with those new functions but it doesn't really set the SELinux labels based on my tests so the SELinux support seems to be limited to a stub.
This issue can be circumvented also with a patch for build repo so older recoveries are compatible too. https://github.com/Mustaavalkosta/android_build/commit/bd246b4028323db259f69a521e3fb8b6e944ae39
Sent from my Nexus 7 3G using Tapatalk HD
Click to expand...
Click to collapse
THANKS Mustaavalkosta!!! I'll incorporate your commit into my next build!!!!!!!!!!
Mustaavalkosta said:
Recovery lacks support for SELinux and updater-script is trying to use unimplemented functions. The newest 4ext I tested passes with those new functions but it doesn't really set the SELinux labels based on my tests so the SELinux support seems to be limited to a stub.
This issue can be circumvented also with a patch for build repo so older recoveries are compatible too. https://github.com/Mustaavalkosta/android_build/commit/bd246b4028323db259f69a521e3fb8b6e944ae39
Sent from my Nexus 7 3G using Tapatalk HD
Click to expand...
Click to collapse
Actually, I'm already using this code in my build/core/Makefile:
Code:
ifneq ($(USE_SET_METADATA),false)
$(hide) echo "use_set_metadata=1" >> $(zip_root)/META/misc_info.txt
endif
Isn't that doing the same thing as "ifneq ($(SKIP_SET_METADATA),true"?
Damn - I LOVE AOKP's Ribbons!!!! lol Especially Ribbon V2!!!!!!!! You guys are gonna love them!
espmartin said:
Actually, I'm already using this code in my build/core/Makefile:
Code:
ifneq ($(USE_SET_METADATA),false)
$(hide) echo "use_set_metadata=1" >> $(zip_root)/META/misc_info.txt
endif
Isn't that doing the same thing as "ifneq ($(SKIP_SET_METADATA),true"?
Click to expand...
Click to collapse
Yeah, it's almost the same thing. You just need to change this to:
Code:
USE_SET_METADATA := false
or define it elsewhere as it defaults to using those new edify functions.
I have a few questions before flashing.
Is it booting? any hiccups? and i didn't understand the thing with aokp features ( like ribbon and etc) are they included or will be included next build?
Can anyone suggest a suitable GAPPS to install with this ROM? I've never tried an AOKP ROM before so not familiar with how things work.
Sent from my Desire HD using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DESCRIPTIONAs the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.)
PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence many of its features can be used on non Pixel devices as well. (YMMV).
The executable is self contained and does not require Python™ to be installed on the system.
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 manual steps) 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 (or init_boot.img for Pixel 7 / 7 Pro).
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 or patched image.
Flash just the boot / init_boot image.
Choose to keep data or wipe data while flashing.
Ability to flash even if multiple devices are connected to the computer.
Option to flash to inactive slot.
Display information about the phone.
ID
Hardware model.
Device architecture.
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.
Active slot.
Android OS API version.
Convenient quick links to download Android platform tools or device firmware.
Magisk Manager installation UI, screenshot. Supported versions:
stable (official)
beta (official)
canary (official)
debug (official)
alpha
delta
special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
Magisk Backup Manager, screenshot.
List all Magisk backups currently on the device.
Highlight the one that is backup of the current installed version.
Delete backups.
Manually add backup from PC.
Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
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 (an app) 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.
Package (Application) Manager, screenshot:
Disable (Freeze)
Enable
Uninstall
Install APK
Download APK
Multi-Select
Show Package Details.
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).
Prerequisites
Android SDK Platform-Tools.
Android Pixel phone factory image or Android Pixel phone full OTA image.
Bootloader unlocked phone (see excellent guide links in credits section below).
InstallationPixelFlasher doesn't have to be installed, just double-click it and it'll start.
Check the releases section for downloads.
Supported platforms
Windows
MacOSX
Linux
UsageBasic Mode
First thing to do is select Android™ Platform Tools, if Android™ Platform Tools is already in your PATH environment, the application will detect it and pre-populate it.
Otherwise you'd have to select where it is installed.
You can download the lastest Android™ Platform Tools by clicking the
next to it.
If you have multiple versions, you can select another version, although it is best to always use the most recent version (The selected version will be identified and displayed.)
Hit the Scan button to detect connected devices, the application will detect all connected devices
(in adb, fastboot, sideload, recovery modes) and populate the combo box (2).
Select your device from the list in the combo box. The following information about the connected device is displayed.
(1st field) Rooted devices will be identified with a checkmark ✓. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
(1st field) Non-Rooted devices will be identified with a ✗.
(1st field) Devices in fastboot mode will be identified with a ? (in fastboot mode, root status cannot be determined).
(2nd field) (adb), (f.b), (sid) or (rec) to indicate connection mode adb / fastboot / sideload / recovery.
(3rd field) Device ID.
(4th field) Device hardware.
(5th field) Current running firmware (in fastboot mode current firmware cannot be determined).
Next select the factory or full OTA zip file (don't unzip), the application will recognize the phone model from the image name and validate the SHA-256 checksum.
You can download factory images by clicking the
next to it. You can download full OTA images from here.
Note: Because both firmware package and full OTA are complete images, you can upgrade to any newer version without worrying about jumping versions (downgrades might work, but are not recommended).
Process the factory image. PixelFlasher will extract boot.img (or init_boot.img for Pixel 7 / 7 Pro) file from the factory image and populate it in the list below (5).
Select boot.img (or init_boot.img for Pixel 7 / 7 Pro) from the list, the selected file can be patched (6), or flashed (10).
Optional: Select this option if you want to patch the boot.img (or init_boot.img for Pixel 7 / 7 Pro) with Magisk. If Magisk is not already installed on your phone, PixelFlasher will install it for you. Your phone does not need to be rooted to create a patched file. This would be the typical choice for monthly updates.
This option will allow updating the phone without losing root (not even temporarily).
Note: See note above for granting root permissions to shell.
Whether the phone is rooted or not, the whole process is without any manual step.
If you want to flash (10) a patched boot.img (or init_boot.img for Pixel 7 / 7 Pro) select the newly added entry.
The following details are listed.
Indicates that the selection is patched.
SHA1 is (shortened for display only) sha1 of boot.img (or init_boot.img for Pixel 7 / 7 Pro)
Source SHA1 (shortened for display only) SHA1 of source boot.img extracted from the image (This should be the same as SHA1 of an unpatched boot.img)
Package Fingerprint is just the filename portion of the image (without the extension).
Patched with Magisk indicates the version of Magisk used to patch the image (if applicable).
Patched Method indicates what method PixelFlasher used to create a patch (possible options: root, app, uiautomator, manual)
Patched on Device indicates the device model that performed the patching. You should always use patched images that match the model of the device that it will be flashed on.
Date is the either the date the boot.img was extracted, or the date it was patched.
Package Path indicates the file from which boot.img (or init_boot.img for Pixel 7 / 7 Pro) was extracted.
Select the Flash Mode
If factory firmware is selected in step 4:
Keep Data: In this mode -w flag is removed from the flash scripts so that data is not wiped. This is commonly known as dirty flashing.
WIPE all data: As the text suggests, this will wipe your data, use it with caution!
If this mode is selected PixelFlasher will ask for confirmation during the flashing phase.
Dry Run: In this mode, the phone will reboot to bootloader, and then mimic the flash actions (i.e. reboot into bootloader) without actually flashing anything (it prints to the console the steps it would have performed if dry run was not chosen). This is handy for testing to check if the PixelFlasher properly is able to control fastboot commands.
If full OTA image is selected in step 4:
Full OTA: Will flash full OTA image in sideload mode. Features of this mode:
This will always flash to inactive slot similar to how OTA updates happen on the phone.
If something goes wrong during flashing, the active flash is uneffected and the phone boots back to active functional slot.
If you flash to both slots (ie flash twice in a row) then both slots would be bootable.
Your phone's bootloader does not have to be unlocked to be able to flash full OTA image (stock boot only).
Optional: Open Magisk Modules Manager and disable (uncheck) modules known to cause issues during upgrades (the below list has never caused issues for me, so I keep them enabled YMMV).
Flash Pixel Phone This is the final step, to actually flash the phone in the selected Flash Mode.
Note: Unlike the previous versions of the PixelFlasher, all the options are dynamic, i.e. depending on what you select before clicking the Flash button, there is no more concept of prepared package. PixelFlasher will first present you the selected options and ask for your confirmation if you want to proceed with flashing.
Expert Mode
To enable the export mode use the File Menu | Advanced Configuration and select Enable Advanced Options
In this mode the following additional options are exposed (green bounding boxes), below notes are more for enumeration than a guide, as they should be trivial and obvious to an expert.
Option to Change the Active Slot (the inactive slot is automatically selected).
Option to reboot to Recovery.
Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
Apply Custom ROM. This replaces the factory ROM image with the selected file.
PixelFlasher extracts boot.img from the ROM image and displays below for selection or patching. Please make sure to read the documentation of the chosen ROM, as each custom ROM instructions could be different.
To be clear, this is what PixelFlasher does internally when this mode is selected, please understand it, and don't use it if the selected ROM guide does not fit the bill. You've been warned!
Keeps stock bootloader and radio images.
Replaces the stock ROM image with the selected custom ROM image.
Flashes in the chosen Flash Mode just like a stock image, i.e. bootloader, custom ROM and radio images in the original order that they were in the stock firmware.
Patching boot.img can be performed if the option is selected. You can select any of the listed boot.img.
Flash Mode is similar to basic flash mode described above in step 7.
Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
Browse to select a a valid image file (.img or .zip). Or select a boot.img from the list above and click on the paste button to paste the selected boot.img into the file selection. Choose the dropdown to select image type.
boot (can be flashed to Live or boot) - Expected file type .img
bootloader - Expected file type .img
dtbo - Expected file type .img
product - Expected file type .img
radio - Expected file type .img
recovery - Expected file type .img
super_empty - Expected file type .img
system - Expected file type .img
system_ext - Expected file type .img
system_other - Expected file type .img
vbmeta - Expected file type .img
vbmeta_system - Expected file type .img
vbmeta_vendor - Expected file type .img
vendor - Expected file type .img
vendor_boot - Expected file type .img
vendor_dlkm (the device will be put into fastbootd mode during this operation) - Expected file type .img
image - Expected file type .zip
SIDELOAD - Expected file type .zip
Select the appropriate flash options. Note: For Tensor devices (Pixel 6, Pixel 6a, Pixel 6 Pro, Pixel 7, Pixel 7 Pro) When Flash to both slots option is selected, Pixelflasher flashes each slot individually to overcome a Google bug that fails with the option --slot=all
Credits
First and foremost Magisk by John Wu which made rooting Pixel™ phones possible, without it none of this would have mattered.
Big thanks to [ryder203], [t-ryder] for his valuable ideas, feedback and testing. Your contributions are very much appreciated.
[Homeboy76] and [v0latyle] at xda for their excellent guides [here and here] on Pixel™ series phones. This program could not have been possible without their easy to follow guides.
I strongly encourage all beginners to follow those guides rather than use this program, it is important to understand the basic steps involved before diving into one click tools or advanced tasks.
Marcel Stör's nodemcu-pyflasher source code which jump started my introduction to wxPython and eventually this program.
JackMcKew for pyinstaller Github Actions.
Endless counts of xda members and their posts that tirelessly answer questions and share tools. Too many to enumerate.
Disclaimer
Code:
*******************************************************************************
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.**
*******************************************************************************
No Donation
I've been asked quite few times about donation, (here, here ... just to list a few).
I'll put it here so that my stance is clear.
This program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that has given me years of support and joy.
You can contribute by helping the next newcomer to learn the ropes and navigate through the maze of information.
Device specific support threads:
Google Tablet
Google Pixel 7 Pro
Google Pixel 7
Google Pixel 7a
Google Pixel 6 Pro
Google Pixel 6
Google Pixel 6a
Google Pixel 5
Troubleshooting:
See this post.
Generate Sanitized support.zip file (File Menu) and submit that with your report.
Latest Release:
June 23, 2023 v5.3.3.0 release
#79 Bug-fix: Package Manager column stays unsorted when filtered.
Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.
Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3
Package manager bug fixes and improvements.
Spoiler: Older Releases
June 21, 2023 v5.3.2.0 release
Added support for Pixel tablet (tangorpro).
For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.
Disable Patch buttons if device is not in adb mode.
Reboot to system after lock / unlock bootloader if No Reboot option is not selected.
Increase sleep after reboots to various modes to assure that slow devices have time to be detected.
Updated Readme and screenshots.
Minor improvements and bug fixes.
June 16, 2023 v5.3.1.2 release
Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.
Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.
Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.
Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.
Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
June 06, 2023 v5.3.0.0 release
Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's ), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
If there was a way to pre-load odin with the extracted files, flashing could also be automated.
I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
June 03, 2023 v5.2.0.2 release
#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
June 01, 2023 v5.2.0.1 release
Bug fix #78 Error when opening a shell console on Linux / Mac
June 01, 2023 v5.2.0.0 release
Update build workflows
Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
Added rules engine code to better / easier management of the UI widgets enabling / disabling.
Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
May 25, 2023 v5.1.0.2 release
Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
v5.1.0.1 release notes:
Exception handling when device is not in the listed Pixel devices.
v5.1.0.0 release notes:
Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
Nicer looking / clearer manual patching dialog.
When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.
Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.
Boot image list box now displays the applied PixelFlasher patch method.
Auto-resize boot image list box columns for better readability.
Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
Bug fixes and improvements.
May 21, 2023 v5.0.1.0 release
Added workflow for building on MacOS 13.
ComboBox behavior on Mac is different than Windows, make adjustments.
Ability to set PixelFlasher working directory (no UI).
Speed up startup.
Popup device selection after Wifi adb connect.
Clear Device list after adb kill-server.
May 19, 2023 v5.0.0.1 release
#75 Bug fix, when device is in bootloader, type error.https://github.com/badabing2005/PixelFlasher/issues/74
#74 Added Support for Pixel 7a (lynx)
Configuration option to define the file manager to use on Linux (default: Nautilus)
Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
Support for additional types of Factory / ROM files.
Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
New advanced option, ability to choose the patching method (with recommendations).
Added Recovery Image patching option.
Advanced option to enable the use of busybox shell (default off).
Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
#66, when checking the patched files internal SHA1, provide a confidence rating.
Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
Added fastbootd testing to Dry Run.
Added Github actions to build all the targets on Github.
Code refactoring, bug fixes and improvements
Apr 30, 2023 v4.10.0 release
Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
Apr 27, 2023 v4.9.0 release
Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).
Support for recognizing Lineage firmware and extracting / patching boot.
Display 32 bit capabilities of the device.
Utilize New Magisk 26.x flags as needed (patch support for more devices).
Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.
Partition Manager can now list the partitions even if the devices is not rooted.
Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).
Added Open Folder button to open a file browser to the directory of the selected boot image.
Added Reboot to Download button (Odin mode).
Added Reboot to Safe Mode button.
Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.
Various additional validation checks.
Bug fixes and other improvements.
Apr 10, 2023 v4.8.2 release
Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
Display USNF related flag values when selecting a device.
Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
Link to download Google USB Driver is added in the help menu.
Added more visual troubleshooting event flows.
Install APK now defaults to Non Market.
Added Install APK cancel option.
You can now select an app in package manager and right click to launch it on the phone.
Minor bug fixes and other improvements.
Mar 14, 2023 v4.8.1 release
#47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
Added more visual troubleshooting event flows.
Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
Improved support.zip redactions.
Added Support.Zip generator button on the Main screen.
APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
Bug fixes and other improvements.
Feb 12, 2023 v4.8.0 release
#50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro
#48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.
Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues
Disable Magisk Backup Manager button if root access to adb shell is not granted.
Button to Open adb shell connected to the selected device.
Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
Feb 05, 2023 v4.7.0 release
Added Magisk Backup Manager:
List all Magisk backups currently on the device.
Highlight the one that is backup of the current installed version.
Delete backups.
Manually add backup from PC.
Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
Magisk installer improvements:
When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
Magisk installer window displays the package name.
You can now copy to clipboard, the download URL and package ID.
Magisk Manager columns are now wider for better readability.
Package Manager improvements:
Added Search / Filter option.
Show count of filtered packages.
Application Name (label column).
"Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
Other under the hood improvements.
When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
More verbose logging that helps with troubleshooting.
Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
Moved existing links under Help Menu | Links, and added few more handy links.
Added timestamp to support.zip filename.
On request, spinning cursor with text "Please be patient ..." is now displayed in red.
Flashing to inactive slot is now in basic configuration instead of advanced configuration.
Preparation work for version 5.0 DB improvements.
#40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.
Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.
Credit to gecowa6967 at XDA.
Dec 05, 2022 v4.6.0 release
Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.
#39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
#39 Do the Magisk backup only when rooted.
Decouple OTA sideload from needing factory image.
Other minor improvements.
Dec 04, 2022 v4.5.0 release
New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
Use latest Python updated packages.
Ubuntu 22.04 support.
Miscellaneous improvements.
Nov 09, 2022 v4.4.0 release
New feature: Font and Font size should be configurable by the user #33
New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
Handy to access a device remotely.
Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
Minor UI Improvements
If Magisk does not create a backup attempt to trigger Magisk to create one.
Update readme to include Pixel 7 / 7P specific info.
Oct 27, 2022 v4.3.1.0 release
Bug Fix: Magisk modules not listed on MacOS / Linux
Oct 16, 2022 v4.3.0.1 release
Bug fix: #30 Error during firmware processing file extraction phase.
PixelFlasher-Linux is now labeled PixelFlasher-Ubuntu (It is built on Ubuntu which is not compatible with all Linux flavors. Even though PixelFlasher-Kali is more compatible, it is still not a one size fits all solution.)
Oct 15, 2022 v4.3.0 release
New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.
Oct 13, 2022 v4.2.0 pre-release
Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
Added Pixel 7 / 7p partitions flashing options to custom flash.
Improved patching process using boot_patch, add more patch file validations.
Check for Magisk backup and trigger Magisk to backup if missing.
Add more logging messages for troubleshooting.
Code optimization / improvements.
Bug Fix #28 Error when opening download link without a device selected.
Added set_version script to easily set the product version.
Print path of the selected boot to console, for easy copy / paste.
Oct 05, 2022 v4.1.4 release
Rooted Magisk patching will now automatically back up stock-boot.img (more to come).
Bug Fix #27, handle version exception.
Oct 05, 2022 v4.1.3 release
Bug Fix: Extract Magisk Manager version properly.
Oct 04, 2022 v4.1.2 release
include busybox binaries for different Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)
don't use hidden Magisk for patching, as it is a stub only.
Oct 03, 2022 v4.1.1. release
Bug Fix: Bundle busybox with PixelFlasher to be used for unzipping Magisk.
Bug Fix #25, use the Magisk Manager version number instead of Rooted Magisk version number.
Cosmetic changes and a bit more logging.
Oct 03, 2022 v4.1.0 pre-release
Patching is now fully automatic with or without root.
PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)
UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.
Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.
Speed improvements for device property reading.
Speed improvements for Magisk modules reading.
NOTICE:
I'm marking this release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.
On my test phones they were available.
Unless you have unzip on your phone, you should avoid using this version.
Sorry about this oversight.
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.
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.
Aug 21, 2022 v3.5.1 release
Fix: Incorrect warning is displayed when Flash on both slots is selected.
The contents of the generated flash-phone.bat file will now be displayed on console even if verbose option is not selected, this helps the user know exactly what commands would be executed before clicking the OK button.
Aug 19, 2022 v3.5.0 release
Add support for fastboot --force flag (to help fix partition issues, caution it will wipe data) see this.
Split image flashing to all slots into two separate single slot flashing to bypass a Google bug on Pixel 6* devices, see this by @Namelesswonder
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.
June 26, 2022 v3.3.5 release
Fix Lock / Unlock bootloader buttons being reversed.
June 12, 2022 v3.3.4 release
Bug fix on MacOS / Linux
Improved notice message about Fastboot process.
June 06, 2022 v3.3.3 release
Bug Fix: When choosing custom ROM, the ROM file was not being copied to the package directory.
Update Documentation and screenshots.
May 25, 2022 v3.3.2 release
Handle system codepage.
Add configurable codepage setting in advanced settings to be able to override the value.
Selected boot color is now blue instead of red to avoid thinking that it has a problem.
After Flashing, clear connected device to avoid using device in case it is not yet ready.
Fix: Paste boot button should be hidden in basic mode.
Always print md5 of Magisk_patched (previously only verbose mode displayed it).
Wait 10 seconds instead of 5 seconds after reboot before issuing next command.
May 21, 2022 v3.3.1 release
Change encoding from utf8 to ISO-8859-1
Button to paste the currently selected boot.img into custom flash file selection.
Several Mac version improvements, thanks to rhetorican for reporting and testing.
UI improvements
Fix: On low resolution screens, the application startup position is high enough to clip the top part.
Fix: On low resolution screens, the patch icon is too large and dis-proportional to the rest of the UI
Better dark mode handling on Mac / Linux
Increase the wait during flashing to account for slower devices.
Further improvements on support.zip redaction process.
Other minor fixes and additional validations.
May 05, 2022 v3.3.0 release
MacOS build.
Handle Magisk module.prop with comments.
Exception handling on magisk module errors.
boot.img management improvements.
Removed old Powershell script.
More checks and validations.
support.zip now includes sanitized PixelFlasher.db
May 04, 2022 v3.2.0 release
Help menu option to create support.zip file, which sanitizes (redacts user names and device IDs) of the log files.
This makes it super easy to provide support.zip file when something goes wrong and need to report it.
In boot management, delete firmware cache of the selected boot.img if it is the last boot.img used from that firmware.
Handle space characters in username.
Console is now responsive when processing firmware file.
More checks and validations.
Update readme with instructions on how to build PixelFlasher on MacOS.
May 02, 2022 v3.1.1 release
Handle UTF-8 Encoding.
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.
April 30, 2022 v3.0.0 release
New workflow, no more package preparation, select options and flash all dynamic.
boot.img caching and management UI with details about the state of boot.img files.
Faster as there is no more need to zip a package.
Other optimizations and improvements.
Update documentation.
April 20, 2022 v2.4.1 release
Bug Fixes: Error message during flashing, introduced by code reshuffle.
It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.
April 19, 2022 v2.4.0 release
Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.
Autoscroll the console.
Code cleanup.
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.
April 11, 2022 v2.2.2 release
Linux support.
Remember last window position.
List Magisk modules, when Magisk is detected.
Added fastboot verbose option.
Added more checks and validations.
Added more details when errors are encountered.
Cleaner message box (better formatting).
Notice to the user in case fastboot drivers are not setup properly.
More plumbing work for the new upcoming workflow.
Add notes on how to build the Linux version.
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
April 03, 2022 v2.0.1.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
March 22, 2022 v1.1.5-alpha release.
Some users were having issues with 7zip, add 7z.dll to the bundle.
Add fallback mechanism to use python libraries for unzipping when 7zip fails (it would be slower)
March 22, 2022 v1.1.4-alpha release.
Bug Fix: Handle space characters in paths.
March 17, 2022 v1.1.3-alpha release.
Visual indicator if the phone is root and Magisk Tools is found.
Bug Fix: KeyError 'flash_vbmeta'
March 17, 2022 v1.1.0-alpha release.
Changelog
10x speed improvement for full package creation, down from 180 seconds to 18 seconds.
Bug Fix: When using patch option with custom ROM, the boot.img of the custom ROM is now correctly patched.
Add support for flashing vbmeta (experimental) with or without disabling verity and or verification. (This is currently only supported through preferences file)
Reserved
Is there an option to disable Verity and verification just curious
a g bell said:
Is there an option to disable Verity and verification just curious
Click to expand...
Click to collapse
Very easy to add that, curious what would be the use case?
I'm currently setting KEEPVERITY=true and KEEPFORCEENCRYPT=true
I'm not sure what you mean by disable verification though.
I have recently had problems when flashing factory images. They flash fine for me but will not boot leaving the message your device is corrupted bla bla bla disabling Verity and verification in FB fixes the issue they boot straight up.
I would find the option useful
It's this in fastboot: fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Of course the using vbmeta.img from what your flashing
a g bell said:
I have recently had problems when flashing factory images. They flash fine for me but will not boot leaving the message your device is corrupted bla bla bla disabling Verity and verification in FB fixes the issue they boot straight up.
I would find the option useful
Click to expand...
Click to collapse
I know how to disable Verity, but how do you disable verification? you know the flag for it?
badabing2003 said:
I know how to disable Verity, but how do you disable verification? you know the flag for it?
Click to expand...
Click to collapse
Sorry l just use fastboot commands
a g bell said:
It's this in fastboot: fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Of course the using vbmeta.img from what your flashing
Click to expand...
Click to collapse
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)
badabing2003 said:
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)
Click to expand...
Click to collapse
l copied the vbmeta.img then flashed with the disable commands added that was after l had the flashed the ROM of course
badabing2003 said:
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)
Click to expand...
Click to collapse
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Only the Ota updates are affected and need to be altered.
Basically if you stick to the full factory image and Magisk v24, you can forget about the extras steps.
Edit: this all was discuss in the Pixel 6 rooting guides.
vandyman said:
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Only the Ota updates are affected and need to be altered.
Basically if you stick to the full factory image and Magisk v24, you can forget about the extras steps.
Edit: this all was discuss in the Pixel 6 rooting guides.
Click to expand...
Click to collapse
Yes but l am not referring to rooting l am referring to downloading and flashing a factory then facing a Verity issue causing the flashed ROM to not boot. Nothing to do with root access.
vandyman said:
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Click to expand...
Click to collapse
It' true that my tool uses the factory image, but I don't have control over the Magisk version, it uses whatever is installed on the phone.
a g bell said:
Yes but l am not referring to rooting l am referring to downloading and flashing a factory then facing a Verity issue causing the flashed ROM to not boot. Nothing to do with root access.
Click to expand...
Click to collapse
You can use notepad++ and open your flash=all.bat file. Add your own fastboot script at the end.
The verify disable method was only needed to root back in October. There was no reason otherwise to change the flash-all script at all if you were not rooting. I must have overlooked something since then!
Is there a link on this that is new?
a g bell said:
l copied the vbmeta.img then flashed with the disable commands added that was after l had the flashed the ROM of course
Click to expand...
Click to collapse
doesn't the step `fastboot update image-oriole-sq1d.220205.004.zip` reboot to normal when it completes?
So you try to go back to fastboot mode and then flash the vbmeta with disabling options?
That's going to be tricky to automate, if I add the step after the ROM update, it will never get there.
I created a feature branch to add this (no UI, just through preferences file, this way it keeps it away from normal users, besides it complicates the UI and confuses people)
After finishing it all, I realized that the phone will not be in the bootloader mode.
I know that when the Pixel 6 / Pro first came out (Before Magisk handled it), we had to disable verity and verification, but those options were added to the ROM update line, we didn't had to flash vbmeta separately, I wonder if you do that would it work.
Actually like @vandyman why do you still need to do this if you're using the latest magisk?
Something is different on your phone?
@badabing2003 It would be great to have an opthio to disable Verity and verification flags via this UI. It could be an advanced user choice just in case.
It is true that with latest Magisk root, flags are not a matte anymore, but some times the third-party kerenl or other roms will make the phone not boot leaving the message your device is corrupted...
badabing2003 said:
doesn't the step `fastboot update image-oriole-sq1d.220205.004.zip` reboot to normal when it completes?
So you try to go back to fastboot mode and then flash the vbmeta with disabling options?
That's going to be tricky to automate, if I add the step after the ROM update, it will never get there.
I created a feature branch to add this (no UI, just through preferences file, this way it keeps it away from normal users, besides it complicates the UI and confuses people)
After finishing it all, I realized that the phone will not be in the bootloader mode.
I know that when the Pixel 6 / Pro first came out (Before Magisk handled it), we had to disable verity and verification, but those options were added to the ROM update line, we didn't had to flash vbmeta separately, I wonder if you do that would it work.
Actually like @vandyman why do you still need to do this if you're using the latest magisk?
Something is different on your phone?
Click to expand...
Click to collapse
Everytime l downloaded and flashed a factory image it wouldn't boot and gave me the message your phone is corrupted. So l tried to fix it this issue and disabling Verity and verification they way l posted worked and the flashed factory image then booted.So l thought this would be a useful option for you to add.
a g bell said:
Everytime l downloaded and flashed a factory image it wouldn't boot and gave me the message your phone is corrupted. So l tried to fix it this issue and disabling Verity and verification they way l posted worked and the flashed factory image then booted.So l thought this would be a useful option for you to add.
Click to expand...
Click to collapse
Yeah, but that was not my question, I hear you, you have a legitimate need, but I need to know an answer to this
Which you quoted but did not answer.
I'm also curious if you're using the latest Magisk 24301 because that problem should have been addressed by Magisk.
@bush911
Same concern, if the device is not in bootloader mode after applying the ROM, and the device is boot looping, and you have to manually get the phone out of boot loop and reboot to bootloader, then adding the option is kind of moot.
As for UI, is it really necessary? once you add it to the preferences file, it will remember and use it all the time.
badabing2003 said:
Yeah, but that was not my question, I hear you, you have a legitimate need, but I need to know an answer to this
Which you quoted but did not answer.
I'm also curious if you're using the latest Magisk 24301 because that problem should have been addressed by Magisk.
@bush911
Same concern, if the device is not in bootloader mode after applying the ROM, and the device is boot looping, and you have to manually get the phone out of boot loop and reboot to bootloader, then adding the option is kind of moot.
As for UI, is it really necessary? once you add it to the preferences file, it will remember and use it all the time.
Click to expand...
Click to collapse
Yeah sorry my friend using the XDA app it's a nightmaret anyway it completes the flash then just hangs on the your device is corrupted screen. I have been using the flash all .bat as well to flash.