Database Info

[10/14/2012][RELEASE][UNOFFICIAL]Stock 67.21.125 ICS FXZ[Minimal/Minimal-Standard]

Do you want the fastboot files for ics (official AT&T US)?
well its all (or almost all) here!!!
Note: This is the minimal standard that is just missing the system.img and the junk apps in the preinstall partition, we should get it with the %100 OEM official .
Also: I'm not responsible if this brick's your Atrix 2!!!
And finally, the download link:
Minimal
Minimal Standard
Cheers,
TCF38012
PS: Don't flash your own system.img this WILL SOFT BRICK YOUR DEVICE.
List of Images Needed(by priority):
1. System (DON'T USE THE SOUTH AFRICIAN ONE AND SOFT BRICK)

Reserved.

Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app

sad_but_cool1 said:
Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but it is incomplete so don't totally rely on it.

So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.

jimbridgman said:
So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.
Click to expand...
Click to collapse
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)

tcf38012 said:
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)
Click to expand...
Click to collapse
You can grab it off the phone and use the ext4utils to package it up, there are few guides on how to do it for the og atrix, and you can figure the rest out from there.... that is similar to how I have done it.

Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
whirleyes said:
Next time you got it back from service, do
Code:
cat /dev/block/system > /mnt/sdcard/system.img
& put it somewhere safe.
It seems that you can restore own system partition backup from fastboot.
Condition :
bootloader won't check security certificate when restored from own backup
you must used moto-fastboot.exe & not fasboot.exe
Click to expand...
Click to collapse
I would really like to see this fxz come to life though... keep it up.

alteredlikeness said:
Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
I would really like to see this fxz come to life though... keep it up.
Click to expand...
Click to collapse
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.

jimbridgman said:
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.
Click to expand...
Click to collapse
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?

alteredlikeness said:
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?
Click to expand...
Click to collapse
Right, that is why I was saying that flashing is easy, but booting is much harder with the locked bootloader checking the signature before booting, hence the cg errors from MY image on someone else's phone.

Updated 10/14/2012!!!
Cheers!!!

tcf38012 said:
Updated 10/14/2012!!!
Cheers!!!
Click to expand...
Click to collapse
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium

tmease1 said:
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is the partial fastboot files for ATT US 4.0.4. Nothing like a bootloader unlock or jellybean. When you are softbricked, just use these in AP fastboot and you are back to normal
Cheers!!!

I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.

Andr3s said:
I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.
Click to expand...
Click to collapse
This may help you since it sounds like you are softbricked. At this point you have nothing to lose and the boot.img is already there on your phone. Give it a shot and if it doesn't work you may be able to take it to AT&T since it was the official OTA that bricked ya. Good luck!!!

Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards

Andr3s said:
Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards
Click to expand...
Click to collapse
Minimal Standard. All you need from the South Africa FXZ is the system.img and flash with "moto-fastboot flash system system.img". Don't flash anything else from the South Africa FXZ.
Cheers!!!

Ok to get this straight, first put the phone in Fastboot bike, then unzip the file 4.0.4_67.21.125_edison_fxz_minimal_standard, run the file and then run flash.bat "moto-fastboot flash system system.img" with the system.img? That is so true?
if this is so I could include the system.img file in the same folder and add the file. bat line "moto-fastboot flash system system.img"?

Hello, after doing all this, I have this problem
Invalid CG OTV (CG: systema): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0056)
Invalid CG OTV (CG: system)
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.466s]
rebooting into bootloader... OKAY [ 0.285s]
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
sending 'ebr' (16 KB)... OKAY [ 0.007s]
writing 'ebr'... OKAY [ 0.502s]
sending 'mbr' (16 KB)... OKAY [ 0.249s]
writing 'mbr'... OKAY [ 0.471s]
sending 'devtree' (512 KB)... OKAY [ 0.286s]
writing 'devtree'... OKAY [ 0.519s]
sending 'boot' (8192 KB)... OKAY [ 1.401s]
writing 'boot'... OKAY [ 0.877s]
sending 'recovery' (9216 KB)... OKAY [ 1.609s]
writing 'recovery'... OKAY [ 1.433s]
sending 'radio' (12080 KB)... OKAY [ 1.109s]
writing 'radio'... OKAY [ 1.906s]
sending 'cdrom' (12032 KB)... OKAY [ 1.049s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'preinstall' (262144 KB)... OKAY [ 17.227s]
writing 'preinstall'... OKAY [ 28.739s]
sending 'preinstall' (20480 KB)... OKAY [ 1.433s]
writing 'preinstall'... OKAY [ 1.901s]
sending 'system' (262144 KB)... OKAY [ 19.473s]
writing 'system'... OKAY [ 29.494s]
sending 'system' (229120 KB)... OKAY [ 15.423s]
writing 'system'... OKAY [ 25.304s]
erasing 'userdata'... OKAY [ 0.045s]
erasing 'cache'... OKAY [ 0.666s]
rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse

[Q] Possible softbrick... PLEASE HELP!!!

I was running just the stock ICS on an AT&T Atrix 2. I went into Root explorer, and in System/bin i deleted both logwrapper files and the safestrap file as directed by bootmanager, then i rebooted. Well, now I get past the dual core technology screen, to the AT&T "rethink possible" logo, then nothing, no reboots, nothing. I tried wiping cache and data from stock recovery but still nothing... someone please help as this is my only phone.
My computer DOES recognize the device also. can anyone point me in the right direction to restoring my device to complete stock??

Enzopreme said:
I was running just the stock ICS on an AT&T Atrix 2. I went into Root explorer, and in System/bin i deleted both logwrapper files and the safestrap file as directed by bootmanager, then i rebooted. Well, now I get past the dual core technology screen, to the AT&T "rethink possible" logo, then nothing, no reboots, nothing. I tried wiping cache and data from stock recovery but still nothing... someone please help as this is my only phone.
My computer DOES recognize the device also. can anyone point me in the right direction to restoring my device to complete stock??
Click to expand...
Click to collapse
Can you access adb? What leak are you on?

tcf38012 said:
Can you access adb? What leak are you on?
Click to expand...
Click to collapse
yes i can get into AP fastboot, i think im on the first leak, Blur_Version.55.1.3.25.MB865.ATT.en.US is the verion i flashed to get onto ICS. I tried the "get back to 2.3.5 from ICS utility but now i cant even get to the AT&T logo i only get to the initial non animated dual core technology screen.

Enzopreme said:
yes i can get into AP fastboot, i think im on the first leak, Blur_Version.55.1.3.25.MB865.ATT.en.US is the verion i flashed to get onto ICS. I tried the "get back to 2.3.5 from ICS utility but now i cant even get to the AT&T logo i only get to the initial non animated dual core technology screen.
Click to expand...
Click to collapse
OK then downgrade to gb and update again (This will erase all your installed apps).
Fastboot Files.
You MUST use these fastboot files. If you use the original ones your are hard-bricked.

yeah thats the utility i keep trying, but its not working, i keep getting stuck at the dual core logo.... this is what happens when i run the script:
Press any key to continue . . .
Erasing Boot...
sending 'mbm' (256 KB)... OKAY [ 0.047s]
writing 'mbm'... OKAY [ 0.499s]
ECHO is off.
rebooting into bootloader... OKAY [ 0.281s]
ECHO is off.
sending 'mbmloader' (39 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
rebooting into bootloader... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
ECHO is off.
erasing 'cache'... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
sending 'ebr' (16 KB)... FAILED (command write failed (No such file or
directory))
ECHO is off.
< waiting for device >
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.462s]
ECHO is off.
sending 'devtree' (512 KB)... OKAY [ 0.343s]
writing 'devtree'... OKAY [ 0.593s]
ECHO is off.
sending 'system' (262144 KB)... OKAY [ 26.816s]
writing 'system'... OKAY [ 23.884s]
sending 'system' (229120 KB)... OKAY [ 22.885s]
writing 'system'... OKAY [ 21.263s]
ECHO is off.
sending 'radio' (12080 KB)... OKAY [ 1.170s]
writing 'radio'... OKAY [ 1.498s]
ECHO is off.
sending 'cdrom' (12032 KB)... OKAY [ 1.716s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
ECHO is off.
sending 'preinstall' (262144 KB)... OKAY [ 26.629s]
writing 'preinstall'... OKAY [ 23.971s]
sending 'preinstall' (20480 KB)... OKAY [ 2.031s]
writing 'preinstall'... OKAY [ 2.093s]
Flashing Boot...
sending 'boot' (8192 KB)... OKAY [ 0.983s]
writing 'boot'... OKAY [ 1.217s]
Your phone is now back on stock firmware!
Press any key to reboot your phone!

If the script doesn't work, try placing the xml from the file in rsd.
Sent from my MB865 using xda premium

Axis_Drummer said:
If the script doesn't work, try placing the xml from the file in rsd.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
since he deleted the logwrapper file by mistake will pushing the logwrapper through adb work??

devilhunter47 said:
since he deleted the logwrapper file by mistake will pushing the logwrapper through adb work??
Click to expand...
Click to collapse
I would think as long as he was on ICS leak #1 for AT&T, then using this should fix it. Whether it be by the script or RSD.
That is if he can still get into AP fastboot with sufficient enough battery to go through the process.
HOWEVER, I'm not 100% sure on whether or not the logwrapper file will be replaced. But its worth trying.
Sent from my MB865 using xda premium

I got a feeling since he's failing on cdt.bin that he's on the second leak....
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
I got a feeling since he's failing on cdt.bin that he's on the second leak....
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
According to his post in Jim's return to GB thread, its fixed. :thumbup:
Sent from my MB865 using xda premium

Axis_Drummer said:
According to his post in Jim's return to GB thread, its fixed. :thumbup:
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
yeah Im fixed guys, thanks for everything!! It took me all night but u got it, at the end of it all i had to RSD the 2.3.5 XML 3 times, but it worked, so im satisfied!!!!

[Q] Bootloop after flashing 5.0, 4.4.4 an 4.4.2

Hi,
I got a notification today that the 5.0 OTA update is available for my Nexus 5. I tried doing the update and Clockwork Mod complained and the update didn't work. I decided to try doing a manual install. I downloaded the 5.0 stock image, adb executable and fastboot executable. I ran flash-all.sh script included with the stock image. It seemed the ROM installed fine but I was stuck on the boot animation for over an hour. I decided this was too long and tried flashing 4.4.4 with the same problem (downloaded the 4.4.4 stock image and ran it's flash-all.sh script), boot animation kept going.
I tried installing a TeamWin as a recovery because some googling told me that the Dalvik Cache may not have been wiped correctly. I tried wiping Dalvik (and everything else) but they all errored out. I completely formatted everything (had the type "yes" for TeamWin to let me). Once again I tried installing 5.0 and had the same problem.
I did some more googling and some people suggested using ClockworkMod. I flashed ClockworkMod, wiped everything (user data, cache and dalvik) and am now stuck on the boot animation of 4.4.2. I'm running out of ideas and I hope someone else knows what's going on.
Every time that I tried running the flash-all.sh script of any of the stock images I get output very similar to the following:
ERROR: could not get pipe properties
sending 'bootloader' (2508 KB)...
OKAY [ 0.191s]
writing 'bootloader'...
OKAY [ 0.478s]
finished. total time: 0.669s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
sending 'radio' (42049 KB)...
OKAY [ 1.427s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.317s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 0489450843835f19
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.745s]
sending 'recovery' (9210 KB)...
OKAY [ 0.535s]
writing 'recovery'...
OKAY [ 0.773s]
sending 'system' (702500 KB)...
OKAY [ 22.241s]
writing 'system'...
OKAY [ 48.088s]
erasing 'userdata'...
OKAY [ 14.391s]
erasing 'cache'...
OKAY [ 0.550s]
rebooting...
Also, for what it's worth, when trying to figure out my problem with TeamWin I noticed that a message to the effect of "full SELinux support is present".
Does anyone happen to know what's going on?
EDIT: I'm doing this on OS X 10.9

Did you try turning it on and off again?

Quit using custom recoverys and root, in fact, dont even try to root after you install Lollipop. If you are in Fastboot mode/bootloader and it isnt working then you should verify the integrity of the file and try a better USB cable that is dedicated for file transfer, not the cheap stock one. I flashed mine in 2 mintues no problem 5 mintues to load
EDIT: You also have to update your fastboot drivers and adb, there is a new one

Well...I fixed it. I can't say for sure but I think I may have had a bad fastboot executable. I followed this guide and installing 4.4.2 worked perfectly.

Try extracting the .img files and use fastboot to flash them manually. It installed fine for me without errors.

Soft brick help!!

I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.

Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk

ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s

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

{
"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.