I'm unable to run fastboot update from an m1 Mac. It flashes the initial set of partitions fine, but when it reboots to fastbootd, it hangs and never moves on to the "waiting for device" step.
Code:
Bootloader Version...: cloudripper-1.0-9074510
Baseband Version.....: g5300g-220908-220908-B-9040061
Serial Number........: <redacted>
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.213s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.573s]
Writing 'boot_a' OKAY [ 0.086s]
extracting init_boot.img (8 MB) to disk... took 0.044s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.197s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.057s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.394s]
Writing 'dtbo_a' OKAY [ 0.023s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.006s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.025s]
Writing 'pvmfw_a' OKAY [ 0.004s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.214s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.571s]
Writing 'vendor_boot_a' OKAY [ 0.086s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.167s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 1.578s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
On my Linux computer, once it gets to "rebooting into fastboot", the next step is "waiting for device". Then the flashing continues. But on my Mac it gets stuck here. It's as though it doesn't recognize that the USB device disconnected. I tried unplugging the cable and plugging it back in, but it remains stuck and doesn't continue. I tried using a USB 2.0 cable (both USB-C to C, and a C to A adapter with an A to C cable), but that didn't help. I also tried forcing it to run in x86 mode via Rosetta 2. "Fastboot devices" correctly shows that the phone is detected.
On my Pixel 6 Pro, I was able to just interrupt fastboot update and run it again while the phone was in fastbootd, and it would flash fine. But things changed on the Pixel 7 Pro and it can't get past dtbo while in fastbootd
Code:
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.002s]
extracting boot.img (64 MB) to disk... took 0.211s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' OKAY [ 0.095s]
extracting init_boot.img (8 MB) to disk... took 0.044s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.203s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.408s]
Writing 'dtbo' FAILED (remote: 'No such file or directory')
Has anyone been able to get fastboot update to work correctly on a Mac? Or have any other suggestions or workarounds?
I am on a mac and just use the flash-all.sh shell script. I haven't had any issues. If you have any aliases set up in files like .zprofile, .zshrc (or .bash_profile .bashrc on older macs), then you might want to check to macke sure they don't conflict with any of the commands. Make sure your platform-tools are up to date in Android Studio SDK.
edit: Is your Mac Apple Silicon or Intel? I think some people have had some issues on the Apple Silicon Macs.
synesthete said:
I am on a mac and just use the flash-all.sh shell script. I haven't had any issues. If you have any aliases set up in files like .zprofile, .zshrc (or .bash_profile .bashrc on older macs), then you might want to check to macke sure they don't conflict with any of the commands. Make sure your platform-tools are up to date in Android Studio SDK.
edit: Is your Mac Apple Silicon or Intel? I think some people have had some issues on the Apple Silicon Macs.
Click to expand...
Click to collapse
I don't run the flash-all.sh script directly, I run each command individually, so there shouldn't be any alias issues. That being said, I don't have any setup that match anything in the script. The "fastboot update" command is what fails midway through.
And yes, I'm running Apple Silicon. I tried forcing x86 mode (ie, running it under Rosetta), but that didn't make a difference.
I'm running the latest version of the platform tools.
synesthete said:
I am on a mac and just use the flash-all.sh shell script.
Click to expand...
Click to collapse
Hi, pardon the quick question: Did you modify the script besides removing the -w flag to not wipe? I had to use the Android Flash Tool because I couldn't get flash-all.sh to run on my Mac. I think I was getting a command not found error. I'm on MacOS Mojave and have the latest Android SDK. All the files required for flashing were upzipped and in platform-tools folder. Platform-tools is also in my path. When I used the terminal to flash init_boot, I was noticing odd things like, "adb" command ran fine, but "fastboot" won't run unless I did "./fastboot".
vurtomatic said:
Hi, pardon the quick question: Did you modify the script besides removing the -w flag to not wipe? I had to use the Android Flash Tool because I couldn't get flash-all.sh to run on my Mac. I think I was getting a command not found error. I'm on MacOS Mojave and have the latest Android SDK. All the files required for flashing were upzipped and in platform-tools folder. Platform-tools is also in my path. When I used the terminal to flash init_boot, I was noticing odd things like, "adb" command ran fine, but "fastboot" won't run unless I did "./fastboot".
Click to expand...
Click to collapse
Try using this command:
Code:
sh flash-all.sh
Depending on how you have things set up, there are different ways of calling a shell script, but this is the normal way to call one.
If you want fastboot to run without putting anything before it, you should make sure that you add its directory to your PATH variable. This can be done by editing or creating one of several files: .zprofile, .zshenv or .zshrc. If you are on an older mac you might be using the BASH shell and in that case you would use .bash_profile or .bashrc. These scrpts are run when the terminal shell is started and you can use them to set things up. They will be in your home directory ( ~/ ) if they already exist, but they will be hidden by default in your finder.
If none of those files exist yet you can create one and just add something like this:
Code:
export PATH=/bin:/sbin:/usr/local/bin:/usr/local/sbin:~/bin:~/Library/Android/sdk/platform-tools:~/bin:~/Library/Android/sdk/build-tools/30.0.3:$PATH
If one already exists, you can append the directories pertaining to the SDK by separating each with a colon. You might not need the directories at the begining unless you use something like Homebrew (package manager). Adding directories to you PATH variable tell your terminal where to look for the executable commands that you want to use without having to type out their full path.
Ingenium13 said:
I'm unable to run fastboot update from an m1 Mac. It flashes the initial set of partitions fine, but when it reboots to fastbootd, it hangs and never moves on to the "waiting for device" step.
Click to expand...
Click to collapse
Ingenium13 said:
On my Pixel 6 Pro, I was able to just interrupt fastboot update and run it again while the phone was in fastbootd, and it would flash fine. But things changed on the Pixel 7 Pro and it can't get past dtbo while in fastbootd
Code:
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.002s]
extracting boot.img (64 MB) to disk... took 0.211s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' OKAY [ 0.095s]
extracting init_boot.img (8 MB) to disk... took 0.044s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.203s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.065s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.408s]
Writing 'dtbo' FAILED (remote: 'No such file or directory')
Has anyone been able to get fastboot update to work correctly on a Mac? Or have any other suggestions or workarounds?
Click to expand...
Click to collapse
I don't know anything about MacOS, but at the end of the output there, shouldn't it be writing to 'dtbo_a', not merely 'dtbo'....?
I do not, however, have any advice on how/why on your Pixel 7 Pro (as opposed to your Pixel 6 problem) is hanging on "waiting for device" when running fastbootd....
simplepinoi177 said:
I don't know anything about MacOS, but at the end of the output there, shouldn't it be writing to 'dtbo_a', not merely 'dtbo'....?
I do not, however, have any advice on how/why on your Pixel 7 Pro (as opposed to your Pixel 6 problem) is hanging on "waiting for device" when running fastbootd....
Click to expand...
Click to collapse
Both the Pixel 6 Pro and Pixel 7 Pro hang before "waiting for device". However, I could work around it on the Pixel 6 Pro by just pressing ctrl+c and running fastboot update again. However, on the Pixel 7 Pro, it seems that not all partitions are accessible (such as dtbo) via fastbootd, so it fails. Whereas on the Pixel 6 Pro, all partitions are accessible so it flashes to completion.
Same happened yesterday to me. I've interrupt the process and disconnect and reconnect the usb cable and the flashing process went on and finished successfully!
nobrain3000 said:
Same happened yesterday to me. I've interrupt the process and disconnect and reconnect the usb cable and the flashing process went on and finished successfully!
Click to expand...
Click to collapse
Unfortunately this doesn't seem to work for me. Disconnecting and reconnecting the cable doesn't cause it to continue. Interrupting the process implies that you started it again after reconnecting the cable? That errors out with the error in my original post.
Ingenium13 said:
Unfortunately this doesn't seem to work for me. Disconnecting and reconnecting the cable doesn't cause it to continue. Interrupting the process implies that you started it again after reconnecting the cable? That errors out with the error in my original post.
Click to expand...
Click to collapse
Have you tried using different cables and ports? People seem to have more success using an A to C cable with USB 2.0 port.
synesthete said:
Try using this command:
Code:
sh flash-all.sh
Depending on how you have things set up, there are different ways of calling a shell script, but this is the normal way to call one.
Click to expand...
Click to collapse
That worked, thank you! The instructions I read didn't say to use "sh", just to run "flash-all.sh". I thought it was something wrong with my setup since I seldom use the terminal.
Lughnasadh said:
Have you tried using different cables and ports? People seem to have more success using an A to C cable with USB 2.0 port.
Click to expand...
Click to collapse
Yes, as I said in my original post, I've tried every port and multiple cables (USB 3, Thunderbolt 4, USB 2). I've tried using a C to A adapter with an A to C cable (both USB 3.0 and USB 2.0). Note that M1 Macs only have USB-C ports, and all are on a USB 3.0 bus. Nothing seems to work.
Ingenium13 said:
Yes, as I said in my original post, I've tried every port and multiple cables (USB 3, Thunderbolt 4, USB 2). I've tried using a C to A adapter with an A to C cable (both USB 3.0 and USB 2.0). Note that M1 Macs only have USB-C ports, and all are on a USB 3.0 bus. Nothing seems to work.
Click to expand...
Click to collapse
Do you have any other/older versions of any adb/fastboot tools on your computer? This has been one cause of people running into problems when flashing. Also wondering if the inability to use a USB 2.0 port may be causing issues since this has also helped some others when running into problems when flashing. Guess you don't have a USB hub you can try?
I've had this same problem. Fastboot doesn't work properly on m1 macs. You'll need to use an Intel mac or windows computer. Hopefully apple or Google will fix it eventually.
Hey folks,
Ran into this issue as well recently while playing around with some stuff, and managed to find a workaround:
Looks like there's an issue with the USB side of things with M1 Macs and fastboot.
Unclear at this time if it's an issue with fastboot or M1 Mac's OS
You can work around it by plugging in a USB device
I've tested with both a USB hub and USB C headphones, both worked to bypass the issue
Note that the USB hub was unpowered
You do not need to plug the device into the USB hub, it can still be plugged into your Mac
GEMISIS said:
Hey folks,
Ran into this issue as well recently while playing around with some stuff, and managed to find a workaround:
Looks like there's an issue with the USB side of things with M1 Macs and fastboot.
Unclear at this time if it's an issue with fastboot or M1 Mac's OS
You can work around it by plugging in a USB device
I've tested with both a USB hub and USB C headphones, both worked to bypass the issue
Note that the USB hub was unpowered
You do not need to plug the device into the USB hub, it can still be plugged into your Mac
Click to expand...
Click to collapse
I had the same issue with my M1 macbook pro device using PixelFlasher app and managed to make it work by using a USB hub.
Related
Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!
Did you update your fastboot tools? That is needed for 8.1
TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Thanks, I'll try and report back
roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.
Currently, I'm on 8.0, build number OPR3.170623.013
cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.
Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.
Before I start, I really hope some one can help. I'm pretty good with computer stuff just not an expert. I have a Pixel XL from Verizon with an unlocked boot loader, using minimal and adb tool that is currently recognizing my device in fast-boot. i either want to get to a point where i can root and install a custom ROM or just return to a stock image for now. I hate being without a phone. I miss my nexus 6P and the NRT from wugfresh so simple and easy. Okay so here's what happened.
1. I unlocked my boot loader.
2. I was trying to root with skipsoft ( i know there's an easier way to root now) and got all the way to where I had to fine the ZIP TWRP file to flash it on the device but could not find it on the actual device no matter where I looked even in the folder the program told me where it was being copied too.
3. So I restarted my pixel XL and restarted the Skipsoft tool kit and then just boot loops.
4. I tried to "Flash-all.bat" on a factory image from google with no success. I keep getting these messages:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.845s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.024s]
finished. total time: 2.869s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.063s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.497s]
writing 'radio_a'...
OKAY [ 0.464s]
finished. total time: 1.962s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (29 MB) to disk... took 1.039s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1761 MB) to disk...W/ziparchive( 6032): Zip: unable to truncate file to 1846804736: File too large
error:
failed to extract 'system.img': I/O error
Any help would be greatly appreciated.
Thread moved to Q&A
@Chabot1987 how much free space do u have on your HDD?
Yep, check your computer's hard drive space, and check the sha-256 of the image zip.
Update, Some how i was able to flash TWRP and then install a custom rom. alot of fiddling around with stuff but i think i have it lol, thank you for the response though, also i barley had any actually i have a HP stream so barley anything on it. could that of been the problem?
Chabot1987 said:
Before I start, I really hope some one can help. I'm pretty good with computer stuff just not an expert. I have a Pixel XL from Verizon with an unlocked boot loader, using minimal and adb tool that is currently recognizing my device in fast-boot. i either want to get to a point where i can root and install a custom ROM or just return to a stock image for now. I hate being without a phone. I miss my nexus 6P and the NRT from wugfresh so simple and easy. Okay so here's what happened.
1. I unlocked my boot loader.
2. I was trying to root with skipsoft ( i know there's an easier way to root now) and got all the way to where I had to fine the ZIP TWRP file to flash it on the device but could not find it on the actual device no matter where I looked even in the folder the program told me where it was being copied too.
3. So I restarted my pixel XL and restarted the Skipsoft tool kit and then just boot loops.
4. I tried to "Flash-all.bat" on a factory image from google with no success. I keep getting these messages:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.845s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.024s]
finished. total time: 2.869s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.063s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.497s]
writing 'radio_a'...
OKAY [ 0.464s]
finished. total time: 1.962s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (29 MB) to disk... took 1.039s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1761 MB) to disk...W/ziparchive( 6032): Zip: unable to truncate file to 1846804736: File too large
error:
failed to extract 'system.img': I/O error
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I get the same error message as above. How did you get back to stock? Per other replies, I checked free space and sha-256 of the image zip, and both OK.
Idk if I searched longg enough. But I didn't see it yet. Is there any way to go back to stock when stuck at fastboot mode. Is there a firmware flash all bat ... I cannot get to recovery, I cannot boot in OS. Doesn't matter what I do. But I do know I need to see how fastboot flash the stock firmware.
If anyone has a clue or some info it would be GREATLY APPRECIATED!
Look for ADB sideload...
In fastboot? I didn't think you could do anything with adb in fastboot mode?
So if you are in fastboot mode this means you should still be able to fast boot flash.
When in fastboot don't select anything (on the screen with the option to start your phone), plug your phone into your computer and move (cd) to your platform tools folder. Open a terminal or ADMINISTRATOR powershell at this location.
You will need to download the TWRP fastboot image from on of the ROM threads below, it doesn't matter which one you get they both work. It may be easier to download the IMG from the unofficial twrp thread because there is a download link on the front page.
Now you want to run sudo fastboot flash boot twrp.img if you are using terminal or .\fastboot flash boot twrp.img if you are using powershell.
After that completes you should now select recovery mode on your screen and you SHOULD boot into twrp. My advice (it worked best for me) is in twrp complete wipe your phone then get the new TWRP installer zip and flash that. Then reboot to recovery and flash the stock ROM you download from asus.
Everything should work fine, feel free to ask me if you need more clarification. (Obligatory not responsible for bricks)
@Grom8 thank you for your detailed response. But I have tried multiple time to boot twrp. But it won't allow me to just goes right back to fastboot.. I will try to flash the official twrp tomorrow. My theory is that the partitions are messed up and won't allow me to do anything until they are sorted out. But I really don't know lol.
I had the same problem, try flashing the stock boot and system.img, then boot into twrp again
0Null0 said:
I had the same problem, try flashing the stock boot and system.img, then boot into twrp again
Click to expand...
Click to collapse
I will try tonight after work. Thank you
Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol
This was my solution
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
st3wart said:
Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol
Click to expand...
Click to collapse
i posted how i fixed mine in detail
My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?
dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
Click to expand...
Click to collapse
Thank you so much! I thought I just bricked my new phone.
st3wart said:
My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?
Click to expand...
Click to collapse
My phone shows up as "Qualcomm HS-USB QDLoader 9008" in the device manager, which I think means it is stuck in edl mode similar to your situation?
Did you manage to find a fix for that?
Nope not yet. Still looking and waiting to see if anyone has a fix.
st3wart said:
Nope not yet. Still looking and waiting to see if anyone has a fix.
Click to expand...
Click to collapse
I've found this thread: /zenfone-6-2019/how-to/qdloader-brick-t3980165
But as I am a complete noob, I don't know whether I should just run a script, of which I have no understanding of what it does.
Don't even know for sure if it could fix the issue.
Thanks man I'll check it out when home from work. I'll shoot you an update if I can get it fixed!
Yes yes YES! It fixed the phone and brought it back to life!!!! Amazing ...thank you thank you thank you.
Follow the instructions as he put them. Works like a charm!
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
Hello dperez2010,
your method seems to work, but i get the following error
fastboot flash system_a system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/5 (773136 KB) OKAY [ 17.209s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Do you or does anyone know whats going on here?
/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Here's a hint
file size too big, can't flash or boot Into TWRP
dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
i posted how i fixed mine in detail
Click to expand...
Click to collapse
"file size", basically our system.img is not being downloaded by the phone due to the large (3.6G) filesize
"fastboot flash system_a ./system.img
Sending 'system_a' (3670016 KB) FAILED (remote: 'requested download size Is more then the max allowed')
feastboot error: command failed
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Code:
C:\Users\XXXX>fastboot flash bootloader "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\bootloader-sargo-b4s4-0.2-5736883.img"
target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.586s]
finished. total time: 0.865s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\XXX>fastboot flash radio "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\radio-sargo-g670-00025-190805-b-5781381.img"
target reported max download size of 268435456 bytes
sending 'radio' (73196 KB)...
OKAY [ 1.673s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_b
OKAY [ 0.555s]
finished. total time: 2.244s
C:\Users\XXX>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.053s
C:\Users\XXX>fastboot -w update "C:\Users\XXX\smartphone\sargo-qp1a.191105.003\image-sargo-qp1a.191105.003.zip"
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ (15016): Zip: unable to truncate file to 485105848: File too large
failed to extract 'vendor.img': I/O Error
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: 97AAY1041S
--------------------------------------------
checking product...
OKAY [ 0.053s]
checking version-bootloader...
OKAY [ 0.063s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot' (65536 KB)...
OKAY [ 1.520s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.006s
Thank you in advance!
Simon
simhagen said:
Hi,
at some point I messed up the flahs of LineageOS and now I would like to get back to the stock img but it does not work anymore. I tried
flash-all.bat but with the same error as shown below.
Thank you in advance!
Simon
Click to expand...
Click to collapse
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Horgar said:
I had exactly this issue.
https://forum.xda-developers.com/pixel-3a/how-to/problem-flashing-stock-image-t3997513
You need to update adb fastboot.
Click to expand...
Click to collapse
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Code:
[[email protected] MyApplication]$ sudo fastboot flash bootloader /home/XXXX/Downloads/sargo-pd2a.190115.029/bootloader-sargo-b4s4-0.1-5262905.img
Sending 'bootloader_b' (8349 KB) OKAY [ 0.340s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b4s4-0.1-5262905
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.541s]
Finished. Total time: 1.074s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot flash radio /home/XXXX/Downloads/sargo-pd2a.190115.029/radio-sargo-g670-00011-190213-b-5306579.img
Sending 'radio_b' (72988 KB) OKAY [ 2.230s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g670-00011-190213-B-5306579
(bootloader) Flashing partition modem_b
OKAY [ 0.880s]
Finished. Total time: 3.315s
[[email protected] MyApplication]$ sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
[[email protected] MyApplication]$ sudo fastboot update -w /home/XXXX/Downloads/sargo-pd2a.190115.029/image-sargo-pd2a.190115.029.zip
--------------------------------------------
Bootloader Version...: b4s4-0.1-5262905
Baseband Version.....: g670-00011-190213-B-5306579
Serial Number........: xxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.051s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' OKAY [ 0.063s]
extracting boot.img (64 MB) to disk... took 0.284s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.990s]
Writing 'boot_b' OKAY [ 0.729s]
extracting dtbo.img (8 MB) to disk... took 0.056s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.340s]
Writing 'dtbo_b' OKAY [ 0.133s]
archive does not contain 'dt.img'
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' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.064s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2271 MB) to disk... took 11.015s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/9 (262140 KB) OKAY [ 7.389s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/9 (262140 KB) OKAY [ 7.840s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/9 (262140 KB) OKAY [ 7.830s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/9 (262140 KB) OKAY [ 7.760s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/9 (262140 KB) OKAY [ 7.870s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 6/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 7/9 (262140 KB) OKAY [ 7.810s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 8/9 (258620 KB) OKAY [ 7.690s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 9/9 (232288 KB) OKAY [ 7.020s]
Writing 'system_b' OKAY [ 1.920s]
archive does not contain 'system_ext.img'
extracting system_other.img (391 MB) to disk... took 1.914s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/2 (262140 KB) OKAY [ 7.850s]
Writing 'system_a' OKAY [ 0.370s]
Sending sparse 'system_a' 2/2 (138668 KB) OKAY [ 4.200s]
Writing 'system_a' OKAY [ 1.380s]
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
sic0048 said:
Is the drive that you have the zip file saved on nearing it's storage capacity? I suspect it is.
They key line in your log is, "Zip: unable to truncate file to 485105848: File too large" You will get this file if there isn't enough room to properly unzip the file completely. It takes up a decent amount of space on the hard drive.
Click to expand...
Click to collapse
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Horgar said:
My issue was resetting the path in windows.
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
If it helps this is what I followed.
Your phone should boot into fastbootd when flashing. That's when I realised it was flashing ok.
Click to expand...
Click to collapse
Thanks,
link does not work for me though...
simhagen said:
Should not be the issue since nothing was on the phone to begin with, other than the first running system.
Click to expand...
Click to collapse
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
For example, if you have ADB installed on your C: drive and your C: drive doesn't have several GB of storage space available, you will get this error. It won't help if you have space available on other drives, because ADB only interacts with the folder it is installed on. So having 100 GB free on another drive won't help as an example.
sic0048 said:
It's not the space on the phone. You don't download and install these factory images from your phone. You have to download them to a computer and install them that way. If you computer is short on storage space, it will give the same error when it tries to upzip the factory image during the installation process. I've had it happen to me before and had to clear up space on my computer in order to finish flashing a factory image.
Click to expand...
Click to collapse
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
simhagen said:
That as wll should not be the case or the unzip will be larger than 30 GB? That is the space left on my notebook
Click to expand...
Click to collapse
No. As long as that space is available on your main drive (see my edit above), 30 GB should be plenty of space. I'm thinking it takes around 5 GB if I remember correctly.
simhagen said:
Thanks,
link does not work for me though...
Click to expand...
Click to collapse
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Try this
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
Code:
extracting vendor.img (523 MB) to disk... took 2.502s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_b' 1/3 (262140 KB)
under Windows I didn't get this problem. So system is up and running again.
Thank you!
simhagen said:
Hi,
so with the last post the update of fastboot worked fine and the flashing went well. Thanks! Stange thing was, it did not work under Linux it stopped at flashing vendor_b (nothing happend for half an hour or so, tried it several times with different Android 10 versions):
under Windows I didn't get this problem. So system is up and running again.
Thank you!
Click to expand...
Click to collapse
Glad to hear you're sorted. It took me a while to work out I just needed to update fastboot. Someone on XDA helped me with it.
simhagen said:
Ok, so far so good. I tried it on Windows with the newest version, same problem. Than I switched to Linux and it worked up to the point "Sending sparse 'vendor_b' 1/3 (262140 KB)" than it gets stuck and nothing happens.
Click to expand...
Click to collapse
I had the exact same problem as you did. I tried different versions of the stock ROM, I tried different versions of the fastboot tool (including sdkmanager --update to get to the latest, etc.). It failed at the same time, every time: "Sending sparse 'vendor_a'"
What actually worked for me was plugging the USB cable into a port directly on the laptop, instead of a hub built into the docking station.
**** you not, worked perfectly. Same cable, same fastboot binary, same laptop, same OS, just switching to a different port did the trick. Don't plug the cable into a USB hub.
{
"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"
}
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 7 Pro 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.
Placeholder
Got Pixel 7 and Pixel 7 Pro (wife and me) on launch day. Both of us coming from 4 and 4 XL. Crazy how far things have come and continue to go. Love this community, and I'm sure I'm gonna love this tool too. Thanks OP!!
Great to see GUI Tool! Kudos
As soon as BB has my P7P in stock, I will then be taking this for a spin!! Thanks for making it compatible with P7P!!
Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.
skaforey said:
Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.
Click to expand...
Click to collapse
Thanks for the feedback, no need for files considering that it worked fine.
It helps to get the confirmation as I don't have a Pixel 7 / 7P device.
I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this
Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...
losticloud said:
I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this
Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...
Click to expand...
Click to collapse
This sounds like a flaky communication problem.
1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable
When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?
I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.
badabing2003 said:
This sounds like a flaky communication problem.
1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable
When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?
I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.
Click to expand...
Click to collapse
1. do you want me to post it here or PM to you?
2. I downloaded 33.0.3 before starting
3. drivers are good
4. I tried usb 2 connection but doesn't do anything. If i use the usb c cable that it came with it shows up as port com3
I tried scanning with PF and it doesn't detect the device at, I used both usb c and usb 2 cable.
If you can help great, if not I can always do RMA since i just got device. Thank you in advance
If you can help great, if not I can start RMA process. Thank you
Is this method keeping L1 and Safetynet?
K1nsey6 said:
Is this method keeping L1 and Safetynet?
Click to expand...
Click to collapse
Yes, the pixel no longer shows up. it also stopped booting, it's just dark.
Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.
losticloud said:
Yes, the pixel no longer shows up. it also stopped booting, it's just dark.
Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.
Click to expand...
Click to collapse
Holding down Power/Vol Up for 20 seconds isnt rebooting?
K1nsey6 said:
Holding down Power/Vol Up for 20 seconds isnt rebooting?
Click to expand...
Click to collapse
Nope, doesn't even vibrate.
badabing2003 said:
This sounds like a flaky communication problem.
...
4- USB 2 connections are more reliable
....
Click to expand...
Click to collapse
God is that still a thing?!?!?!
LOL, I remember when I first started rooting on my Pixel 2 XL, SOOOO many people were having issues using the USB-C connection, but once they used the legacy USB-A, things would suddenly work!
USB-C connections on a computer/laptop were still rather new-ish, so I figured that was the reason. I can't believe how many years later that this advice would still be relevant!
I started RMA I’ll try this again in a few weeks when I get new one.
losticloud said:
I started RMA I’ll try this again in a few weeks when I get new one.
Click to expand...
Click to collapse
Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.
badabing2003 said:
Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.
Click to expand...
Click to collapse
I did try but the phone wasn't detected. Files are attached.
losticloud said:
I did try but the phone wasn't detected. Files are attached.
Click to expand...
Click to collapse
Thanks,
It's interesting that you started with slot a, ran into the problem writing product 11/11
I'm assuming that the phone could no longer boot to slot a,
Because the next thing I see is the phone in bootloader mode with slot b being active, not sure why it would be in bootloader mode as slot b should have been intact, nothing was written to slot b yet.
I wonder if out of factory phones have both slots the same image.
Then you trying flashing again, again the exact same step of flashing product 11/11 it failed.
However unlike the first time, the phone was placed in bootloader mode on slot b.
I wonder if you were manually putting the phone into bootloader mode or it was eventually ending up in that state?
You tried yet another time, again on slot b, and again it failed on the exact same step.
After that we have no data, I suppose at that point you couldn't even put the phone in bootloader mode.
When you get your new device, I would strongly suggest that you inspect the USB cable, and also make sure the USB port is connected to the PC without a hub or anything, and preferably USB 2.
I know at this day and age it sounds silly, but the signs are failure in communication, or hardware problem.
If you search Google for similar problems, you'd find lots of cases where most of those are related to either the drivers, the cable or the USB port, here's one as an example.
Let us know how your phone goes, and best wishes.
New Release:
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.