Bug Fix Release:
June 01, 2023 v5.2.0.1 release
June 01, 2023 v5.2.0.1 release
- Bug fix #78 Error when opening a shell console on Linux / Mac
To be clear on the terminology.Thanks for you ongoing updates and improvements,
Does that mean if I do a factory update(to my rooted slot) next time I could update one slot with rooted factory image and the other(after booting into it) with the same non rooted factory image.
Does that sound about right?
- When we talk about Factory Image, we're talking about the files posted by Google here.
- When to talk about Full OTA image, we're talking about files posted by Google here.
On the other hand, Full OTA image, always flashes to the inactive slot, and if something goes wrong it goes back to the current slot, which means it doesn't modify the current slot in such a way that it becomes unbootable.
If you want to be able to boot to both slots, then you should be flashing Full OTA images and not factory images.
Things to keep in mind.
- Because the way OTA image is flashed (streamed) it is slower than factory flashing.
- You cannot flash OTA to both slots simultaneously, you have to do it one at a time.
- Keep in mind this is mainly for having both slots bootable in case something goes wrong and you want to have functional system without having to flash something immediately.
- Also keep in mind that data partition is common, so if you change something in one slot, don't expect it to be different in the other slot (you can have one rooted and one not, and that's because there are two boot partitions)
- You also don't want to be running different OS versions or security patch versions on the slots, and alternating between the two, although you might get away with it if it is slightly different, it is not recommended.
Last edited:
Update:
June 03, 2003 v5.2.0.2 release
June 03, 2003 v5.2.0.2 release
- #76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
New Release:
June 06, 2003 v5.3.0.0 release
June 06, 2003 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.
shoey63
Recognized Contributor
Wrong platform tools. Use 33.03
Edit: For context, above user showed a screenshot of PF using platform tools 34.03, and being stuck whilst attempting to boot into fastbootd.
Edit: For context, above user showed a screenshot of PF using platform tools 34.03, and being stuck whilst attempting to boot into fastbootd.
Last edited:
normally updating from may to june like every month via pixelflasher with adb 33.0.3 and keeping data and disabled verity and verification, device wont boot and shows corrupted data message after it finished updating
reflashed may firmware also same message
help please any ideas how can i boot the device ? i dont want to lose my data asi dont have a backup
reflashed may firmware also same message
help please any ideas how can i boot the device ? i dont want to lose my data asi dont have a backup
Last edited:
incase this might be of any help at all i didnt flash both slots + i have a magisk patched boot image of june update on my pc
also im using magisk alpha (the patched boot image is by magisk alpha)
here it is attached
Last edited:
Actually you flashed both slots, you were on slot a, when you flashed and then you were on slot b.
Either way don't worry, as long as you get into fastboot or recovery mode, you should be fine.
On the last flash I see this error
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.Cable , port, driver ...
I suggest you make sure you have the latest USB drivers
Make sure you use USB port 2 and a good cable.
Please do not flash a patched boot, with the number of modules you have enabled, I'd be surprised if it survives.
Don't worry about the corrupt message, that can be fixed later, let's focus on getting you to boot to system.
if you can put the phone in recover / sideload mode, It would be better if you flash stock full OTA June version, at least that won't have to use fastboot in user space.
If you can't get into sideload mode, then after changing port / cable / driver
Flash full factory with stock boot selected.
Report back, and if you encounter any errors, stop and post support file.
im using a type c to type c cable from my laptop, changed the cable im using now with another and reflashed may full factory image but also wont boot and got to the android recovery system page
here my steps i follow evey month when updating
downlaod the update full image firmware
extract the boot image and patch it via magisk and keep it
update via pxielflasher keeing data and disabling verity and verification
now device updated without root
i fastboot boot to the magisk patchec image created earlier
now device is udpated and with temp root , i reinstall magisk from inside the magisk app
done
(i know its a long prcoedure but thats what im doing for along time now and it works)
i thinking of fastbooting to a may update magisk patched boot image,will the device boot the system up ? but i need a patched image
While in recovery
Please try this
Download full OTA June image for your device.
Select it as firmware in PF
Process it
PF should select Full OTA
don't try to patch it yet.
Flash Pixel Phone.
Report back.
same result it boots to the android rec. cannot load android system ..., note that while on rec. mode it shows no command and in PF before flashing the ota it says your mobile model error i ignore it and press ok to continue, i want anyway to boot the device up (for ex. updating to a14 beta or something) and take notes of my apps and backup my imp. data and i have then no problem resetting the device from scratch
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1New Release:
Sep 19, 2023 v5.8.0.0 release
- Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.
- Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.
- For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.
- Added a button to reboot to userspace fastboot (fastbootd).
- Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)
- When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.
- On Linux, display a message when terminal app is not set and open shell feature is used.
- For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.
- Miscellaneous fixes and improvements.
-
19
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.6New Release:
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.
6
To be clear on the terminology.Thanks for you ongoing updates and improvements,
Does that mean if I do a factory update(to my rooted slot) next time I could update one slot with rooted factory image and the other(after booting into it) with the same non rooted factory image.
Does that sound about right?
- When we talk about Factory Image, we're talking about the files posted by Google here.
- When to talk about Full OTA image, we're talking about files posted by Google here.
On the other hand, Full OTA image, always flashes to the inactive slot, and if something goes wrong it goes back to the current slot, which means it doesn't modify the current slot in such a way that it becomes unbootable.
If you want to be able to boot to both slots, then you should be flashing Full OTA images and not factory images.
Things to keep in mind.
- Because the way OTA image is flashed (streamed) it is slower than factory flashing.
- You cannot flash OTA to both slots simultaneously, you have to do it one at a time.
- Keep in mind this is mainly for having both slots bootable in case something goes wrong and you want to have functional system without having to flash something immediately.
- Also keep in mind that data partition is common, so if you change something in one slot, don't expect it to be different in the other slot (you can have one rooted and one not, and that's because there are two boot partitions)
- You also don't want to be running different OS versions or security patch versions on the slots, and alternating between the two, although you might get away with it if it is slightly different, it is not recommended.
5
Thank you for the consideration.
No donation, this is simply giving back to the community that has given me a lot over the years.5New Release:
April 17, 2022 v2.3.0 release
- Optional automatic check for updates feature.
- Added help menu links to:
- Report an issue
- Feature Request
- PixelFlasher Project Page
- PixelFlasher Community (Forum)
- Homeboy76's Guide
- V0latyle's Guide
- Open Configuration Folder
- Check for New Version - Icons for menu items.
- Link to download Pixel Firmware.
- Link to download Android Platform Tools.
- Unlock Bootloader.
- Lock Bootloader.
- SOS (experimental) - disable Magisk modules to get out of bootloop.
- Additional flashing options:
- product
- system
- system_ext
- system_other
- vbmeta_system
- vbmeta_vendor - Added sideload flashing option.
- Updated documentation.
- Further improved console messages for troubleshooting.
- Linux build using Github Actions.
- Manual build for Kali Linux.
- Added Magisk Backup Manager:
New posts
-
Question Is there a way to get 90 FPS on pubg mobile on my POCO X5 pro?- Latest: Abdul Kareem Seyal
-
-
-
