yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Guides, News, & Discussion] NathanTan:
I'm not using adapters, just straight cable. I have changed three already but same result. Tomorrow I can still try another one.

Ota I can only sideload from recovery right? Or is there any other way that I'm missing? Because in that case, I cannot access recovery mode unfortunately

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

I'm using the platform tools, version r28.0.2. jus inzip it in a folder with the files from the recovery and start cmd from there. Is there any additional package to use or install?
[Google Pixel 3 XL Guides, News, & Discussion] dd805bb:
I know there is a problem using USB 3.0 cable. If it has our round adapter on both end don't use that. Get a USB 2.0 with a 3.0 adapter. Or try the cord one way and then unplug and turn one end over and replug in. I am was in the soft brick mode like you. Nothing would work. And I mean nothing. I kept just trying everything I could find. But if you can rma, go for it. You can just mess it up more before you rma it. I paid the preferred care and alomst did an RMA. No joke was about lose it because I have had this phone with no problems and then I had this same issue. I was on the phone with them getting it done and somehow got it to recovery. I tried it all. Fastboot was failing. No recovery. I just kept trying and trying and finally it worked. I had it happen again and the steps I provided got me going. I went back to pie. Relocked my bootloader to check itself with it's device protection. Let it be for a few days before I reroooted. Used the pie ota to flash both sides at the very end. But I could get to recovery after I fastboot the full image. You can not even get fastboot to flash anything. That sucks man. Well RMA and have fun trying to get it going until your device comes
[Google Pixel 3 XL Guides, News, & Discussion] EMJI79:
I have downloaded the driver like in the OP but when I choose it it is "Samsung" and not Google probably due to the fact that I use an old USB cable from a Samsung phone because the pixel cable is USB C to USB C (which I cannot understand why?).

I should probably buy another cable, but how to be sure it is a "Google" one?

Has someone bought one from Amazon that fits and could give a link?
[Google Pixel 3 XL Guides, News, & Discussion] SacredDeviL666:
Thread Cleaned.

Stay on topic please, if you don't like each others post please ignore or if its a rule violation hit report button than going back and forth to make it more worse.

Thanks

SacredDeviL666.
[Google Pixel 3 XL Guides, News, & Discussion] fredgar75:
Holy crap! Thank you for this guide! I installed TWRP and then decided to root. That was easy so I decided to flash a custom rom. That's where things went bad.

It wouldn't boot into system so I went back into TWRP to flash again but it failed. Tried to reboot into recovery and it got stuck in bootloader. No recovery, system, nothing.

I tried following the guide several times and multiple factory image downloads to no avail.

Finally after reading the entire thread I decided to try a different USB cable, as suggested earlier in the thread.

I am an over the road trucker and have been up since 4am yesterday. It's now 3am but my phone is working again.

So again thank you!

Everyone, if all else fails, change your cable.
[Google Pixel 3 XL Guides, News, & Discussion] NathanTan:
What messages were you getting while trying to flash?
[Google Pixel 3 XL Guides, News, & Discussion] fredgar75:
The same messages you were getting. My command screen looked identical to the one you posted.
[Google Pixel 3 XL Guides, News, & Discussion] NathanTan:
I've already tried 3 different cables, but ok I'll try to grab a new one and try again...

What is bugging me is that now I cannot manage to unlock the bootloader anymore.
[Google Pixel 3 XL Guides, News, & Discussion] fredgar75:
I would switch cables and close everything out one more time and restart your computer as well as your phone. The only other thing I did was when running the flash all bat file I right clicked and chose run as administrator rather than double clicking it.

But you will definitely have to unlock your bootloader before you can do anything.
[Google Pixel 3 XL Guides, News, & Discussion] fredgar75:
[MENTION=9832599]NathanTan[/MENTION] have you had any luck yet?
[Google Pixel 3 XL Guides, News, & Discussion] NathanTan:
No luck yet unfortunately...

I still cannot manage to unlock the bootloader anymore, so not much I can do for now.

I do not think it is related to the cable because it flashed the image without faults at first, but I cannot exclude it either. I have tried 4 different ones.

If anyone has any more ideas, I can give it a try and post a feedback.
[Google Pixel 3 XL Guides, News, & Discussion] LunaticSerenade:
[MENTION=4274380]CZ Eddie[/MENTION] my man, your guide saved my ass.

Thank you for writing this up. I thought I knew what I was doing, but apparently the 3 XL is a bit different than the Nexus 6.
[Google Pixel 3 XL Guides, News, & Discussion] simack:
Oh man you saved my ass too!!!! I thought I just blew $1200 @ CZ Eddie I can't thank you enough mate :good:
[Google Pixel 3 XL Guides, News, & Discussion] STALKER18:
Hi friend, I had the same thing here, can u tell me what did u do exactly ?
[Google Pixel 3 XL Guides, News, & Discussion] skooter32:
you my friend just saved my 3 days old pixel 3 xl thanks!
[Google Pixel 3 XL Guides, News, & Discussion] nguyenmanh287:
HELP pixel 3 xl Q beta DIE

Please help me. I have pixel 3 xl joining Q beta. When the setting is pressed, the device does not work. hang like picture. My device has not been unlocked when participating in the test.[IMG="https://scontent.fhan2-4.fna.fbcdn.net/v/t1.15752-9/66348244_338134790411334_4164026993119068160_n.jpg?_nc_cat=105&_nc_oc=AQm8fzZte1TO6FtnKhPAkkqi4o7TAtDbZjA_YvoQfCfFHlMbb1P1CKizb23Q04Cada4&_nc_ht=scontent.fhan2-4.fna&oh=4efca9ce2dc4183f6249098e6ce7b2be&oe=5D783F11"]https://scontent.fhan2-4.fna.fbcdn.net/v/t1.15752-9/66348244_338134790411334_4164026993119068160_n.jpg?_nc_cat=105&_nc_oc=AQm8fzZte1TO6FtnKhPAkkqi4o7TAtDbZjA_YvoQfCfFHlMbb1P1CKizb23Q04Cada4&_nc_ht=scontent.fhan2-4.fna&oh=4efca9ce2dc4183f6249098e6ce7b2be&oe=5D783F11[/IMG]

[IMG="https://scontent.fhan2-3.fna.fbcdn.net/v/t1.15752-9/66150961_982948532051742_5159148775045857280_n.jpg?_nc_cat=107&_nc_oc=AQls8iMLr5z27M-omk5TzlBY1ASt_Gr_tVP6Efar0_qBWhGLzrIy4N_0fTeyrEGIqN4&_nc_ht=scontent.fhan2-3.fna&oh=0bd0fdb0776720cb5eab9bbca5728f40&oe=5DBEC388"]https://scontent.fhan2-3.fna.fbcdn.net/v/t1.15752-9/66150961_982948532051742_5159148775045857280_n.jpg?_nc_cat=107&_nc_oc=AQls8iMLr5z27M-omk5TzlBY1ASt_Gr_tVP6Efar0_qBWhGLzrIy4N_0fTeyrEGIqN4&_nc_ht=scontent.fhan2-3.fna&oh=0bd0fdb0776720cb5eab9bbca5728f40&oe=5DBEC388[/IMG]
[Google Pixel 3 XL Guides, News, & Discussion] zkrayem:
he said it won't work because you can't flash anything to the phone using fastboot if the bootloader is locked as i understood.

i have the same problem as yours. i think the bootloader should be unlocked first.

i have seen some commands like: fastboot flash unlocking or the same with unlocking_critical or OEM unlocking but all of them didn't work for me and i can only see the phone using fastboot and the bootloader is locked. phone is stuck at bootloader page.
[Google Pixel 3 XL Guides, News, & Discussion] zkrayem:
[MENTION=4274380]CZ Eddie[/MENTION]

any help for the rest of us that their bootloader is locked and their phone is soft bricked?

ADB can't recognize the phone. only fastboot can, but nothing can be flashed cause the phone bootloader is locked.

Anyone can help?
[Google Pixel 3 XL Guides, News, & Discussion] Soma1230:
Maybe someone can point me in the right direction. I was installing a ROM after installing TWRP and Magisk, but I suppose the ROM didnt flash correctly and was stuck in a bootloop. Attempting to use this guide in going back to stock, it gives me an error when using the flash-all command. when flashing system.img, it's unable to write giving me this line:

extracting system.img (2201 MB) to disk...W/ziparchive( 1044): Zip: unable to write 32768 bytes to file; No space left on device

fastboot: error:

failed to extract 'system.img': I/O error

Any ideas as to where I went wrong? I've had some issues in the past, but never something like this.

***EDIT: I found out that it was simply my main drive didnt have enough space. I thought it operated from where the files were located (my other HDD). Cleared the space and it all worked. Funny it's always the real simple things.
[Google Pixel 3 XL Guides, News, & Discussion] zkrayem:
i don't know how to get help in this, can we offer a prize on XDA or it's not allowed?
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Are you booted into recovery when trying to use adb? You need to be.
[Google Pixel 3 XL Guides, News, & Discussion] zkrayem:
can't boot into recovery. the only thing the phone does is booting into bootloader which is locked.

many others facing the same problem when trying to flash the Q beta 4 and nobody seems to have a solution for that.
[Google Pixel 3 XL Guides, News, & Discussion] spuri78:
I've recently unlocked and then tried to flash a custom rom and despair kernel on p3xl. after reboot, the phone went blank. had to manually reboot the bootloader. So, I then tried to flash July factory image. however, I'm getting this? does it mean I'm bricked?

target reported max download size of 268435456 bytes

sending 'bootloader' (8493 KB)...

OKAY [ 0.283s]

writing 'bootloader'...

(bootloader) Flashing Pack version b1c1-0.1-5578427

(bootloader) Flashing partition table for Lun = 0

(bootloader) Flashing partition table for Lun = 1

(bootloader) Flashing partition table for Lun = 2

(bootloader) Flashing partition table for Lun = 4

(bootloader) Flashing partition table for Lun = 5

(bootloader) Flashing partition msadp_b

(bootloader) Flashing partition xbl_b

(bootloader) Flashing partition xbl_config_b

(bootloader) Flashing partition aop_b

(bootloader) Flashing partition tz_b

(bootloader) Flashing partition hyp_b

(bootloader) Flashing partition abl_b

(bootloader) Flashing partition keymaster_b

(bootloader) Flashing partition cmnlib_b

(bootloader) Flashing partition cmnlib64_b

(bootloader) Flashing partition devcfg_b

(bootloader) Flashing partition qupfw_b

(bootloader) Flashing partition storsec_b

(bootloader) Flashing partition logfs

OKAY [ 0.523s]

finished. total time: 0.807s

rebooting into bootloader...

OKAY [ 0.050s]

finished. total time: 0.051s

target reported max download size of 268435456 bytes

sending 'radio' (71132 KB)...

OKAY [ 1.639s]

writing 'radio'...

(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743

(bootloader) Flashing partition modem_b

OKAY [ 0.401s]

finished. total time: 2.044s

rebooting into bootloader...

OKAY [ 0.049s]

finished. total time: 0.051s

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'

archive does not contain 'vendor.sig'

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...: b1c1-0.1-5578427

Baseband Version.....: g845-00017-190312-B-5369743

Serial Number........: XXXXXXXXX

--------------------------------------------

checking product...

OKAY [ 0.060s]

checking partition-exists...

FAILED (remote: variable not found)

finished. total time: 0.354s

Press any key to exit...
[Google Pixel 3 XL Guides, News, & Discussion] zkrayem:
you won't get any reply in this post. it's a one way communication. i've tried but nobody answered.

anyway, i don't think your bootloader is locked because you can flash things. but to know for sure. turn the phone off, hold the volume down button and power until it boots into bootloader, look down, you should read if your bootloader is locked or unlocked.

if it's unlocked then the easiest way is to download the latest image for your pixel, unzip it and run the flashall command, it'll do the job.

unfortunately my bootloader is locked so i can't flash anything or even load recovery mode.
[Google Pixel 3 XL Guides, News, & Discussion] viper8u2:
just wanted to say thanks for putting this together. got a new 3A XL and something went wrong when wrong after flashing magisk and when I went to reboot I said let it install twrp and I got a boot loop. followed your instructions and back to normal
[Google Pixel 3 XL Guides, News, & Discussion] nguyenmanh287:
I have a 3xl pixel. My device is currently dying due to the beta update. Before updating, I did not unlock the bloadder. Please help me ???
[Google Pixel 3 XL Guides, News, & Discussion] yoyosirchunk:
I have a regular Pixel XL. I went through all these steps and afterwards I am just getting stuck in a boot loop. I can get back to the bootloader no problem, but it will not boot the factory image I just installed. I read on another site that locking the boot loader then re-locking it supposedly fixes it and causes it to actually boot, but I am scared to do that as if I lock the boot loader I am scared I will not be able to unlock it.
[Google Pixel 3 XL Guides, News, & Discussion] mydjtl:
I had pretty much given up on fixing my phone after several hours and then came across your post. Respect. I'm back in business.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Check Settings ==> Advanced ==> System Updates. You should have an update availible, take it.
[Google Pixel 3 XL Guides, News, & Discussion] Pardess:
lol i cant even boot to android im in bootloops, somehow i managed to fix it while flashing stock to a partition of the slots... but i want the revert and going to UNROOT . thats shaeiiiittttt
[Google Pixel 3 XL Guides, News, & Discussion] mgp53:
I miss the good ole flashing methods. This slot a, slot b confuses me.
[Google Pixel 3 XL Guides, News, & Discussion] devicesupport:
Google pixel 3 xl guides, news, & discussion

Thanks for this information.
[Google Pixel 3 XL Guides, News, & Discussion] undeadtaco343:
hi, so i have bricked my pixel 3xl trying to install a custom rom. ive followed your guide up up until part E, in which when i run the erase system commands, they fail saying:

FAILED (remote: 'Partition should be erased in fastbootd')

fastboot: error: Command failed

furthermore, the flashall command gives me this error aswell (after trying to send 'boatloader_b' (8521kb) )

FAILED (Write to device failed in SendBuffer () (Unknown error))

any help would be greatly appreciated.

edit: it was the cord. switching to samsung A-C cable from wireless pad did the trick. flash-all script worked and phone is now back to working order. thank you for the guide.
[Google Pixel 3 XL Guides, News, & Discussion] phoe zay:
can i use android 10 factory image or android 9 image?
[Google Pixel 3 XL Guides, News, & Discussion] thex2:
I am by far no expert. I'd classify myself as a noob, but in my experience, I was unable to flash crosshatch-qp1a.191105.003-factory-8b53e5ec.zip but I was able to flash crosshatch-pq3a.190705.003-factory-e59cf7a4.zip. I followed OP's directions for both sets. When I flashed the Android 10, it rebooted into fastbootd. Gave me a bunch of options as far as booting into bootloader, recovery, reboot, etc... i choose to reboot, when it rebooted, it went into bootloader. At that point, I went to chose to start over with Android 9 since I had previous success with that. During the "fastboot erase system_a" commands, I got the error: failed <remote: 'Partition should be erased in fastbootd'>. I continued on with erasing boot_a and boot_b and rebooting bootloader and then installing Android 9. From there, I'm letting the phone update to Android 10 through the factory update process. I'm sure there's an easier way or that I did something wrong. Just figured I'd put my experience out there in case it helps you. Best of luck pal.
[Google Pixel 3 XL Guides, News, & Discussion] thex2:
Why does erasing system_a and system_b fail?

EDIT: got it working, not sure if it was because I was in slot b or if that's irrelevant, but if you run into my same issue, it can't hurt to change slots as far as i know:

fastboot getvar current-slot

result was current-slot: b

fastboot set_active a

fastboot getvar current-slot

result was current-slot: a

after the above, I was able to succesfully:

fastboot erase system_a

fastboot erase system_b
[Google Pixel 3 XL Guides, News, & Discussion] dv78:
Hi anyhow I have lost my stock recovery on my pixel 3xl. Bootloader is unlocked and stock rom (Q) is installed. How can I get back the stock recovery?

Thx
[Google Pixel 3 XL Guides, News, & Discussion] Slim2none4u:
Just do flash-all with -w removed to preserve user data.
[Google Pixel 3 XL Guides, News, & Discussion] dv78:
Have done so many times... Still no stock recovery...always the same picture with the "dead" Android.. could somebody share it?

[
[Google Pixel 3 XL Guides, News, & Discussion] Slim2none4u:
When you see the "dead Android", hold volume up and tap power button. That takes you to recovery.
[Google Pixel 3 XL Guides, News, & Discussion] YaboiGumby:
I have followed these instructions exactly but at the end of the flash all command it says

"extracting product.img (1980 MB) to disk...ziparchive W 05-08 20:31:39 5280 1916 Zip: unable to truncate file to 2076569832: File too large

fastboot: error:

failed to extract 'product.img': I/O error"

I don't know what to do any help would be appreciated

edit: after searching for a while I found that the problem was that I didn't have enough space on my C: drive even through I ran the Flash all bat on my D: drive problem solved, thank you for this guide !
[Google Pixel 3 XL Guides, News, & Discussion] m0h1t:
Fixed

I was getting the "No valid slot to boot" error in bootloader while upgrading from Android 10 to 11. Updating to the latest platform tools & usb driver fixed the problem.

Thanks so much!
[Google Pixel 3 XL Guides, News, & Discussion] Vio281:
bro this is a $700 fix for pixel 5 phone
[Google Pixel 3 XL Guides, News, & Discussion] Brian Tomek:
Help! Pixel 4XL stuck in Fastboot Mode.

I tried to relock my bootloader and flashed some wrong files. Now stuck in Fastboot Mode.

When I try flashing I get a "No such file or directory Rebooting into bootloader" error.

Thought?
[Google Pixel 3 XL Guides, News, & Discussion] Brian Tomek:
Got it! Not sure how, but was able to flash Android 11 and got it running. Now I am going to take my time to unroot this thing!

Thanks again!
[Google Pixel 3 XL Guides, News, & Discussion] no1cvn:
I was getting error like U

Please help me
[Google Pixel 3 XL Guides, News, & Discussion] Vibrato86:
PEOPLE. I HIGHLY RECOMMEND NEVER erasing system unless under specific circumstances. This is likely why many phones are soft bricking. only fastboot -w is needed really when flashing OS's. (optionally you can use "fastboot erase userdata"
[Google Pixel 3 XL Guides, News, & Discussion] theg00dguy:
Hi everyone,

I am new to XDA, but has provided much needed insight into the various Android phones I have had.

I know that this topic is related to Pixel 3XL, but it is the closest one that I have found that comes close to describing/fixing the problem I have ended up with. I hope one of you helpful and knowledgeable people can guide me to a fix.

Below is a brief chronology/history on how I reached this weird soft-brick situation:

I have a Pixel 4a 5G on Android 11. It suddenly started to randomly power-off every 2-10 minutes.

I noticed that the shutdown mostly (but not always) happened when the screen timeout occurred. Changing the screen-timeout to 30-minutes helped keep the phone on for longer before it randomly power-off. I concluded that it must be a software rather than hardware issue. I put the hone through all manner of (gentle) physical abuse to see if it may be in internal loose connection, but it never shut down during these tests.

Luckily lengthened screen-timeout allowed me to keep the phone on long enough to update to Android 12, but even after the update the phone would still randomly power-off.

I concluded that even after an update there must be some fundamental software that does not change, and that it was this software that was causing the random power-off.

I decided to fire up ADB/fastboot and re-flash the Android 11 factory image (bramble-rq1a.210105.003).

The flashing appeared to work, but when the phone restarted it would only restart into the bootloader, no matter which options I worked through.

So that's how I got to that stage. Subsequently I:

I Read that someone flashed different versions of the factory images and got their phone eventually work. I tried this beginning with the Android 12 update and began to work my way backward. No joy.

I read that someone tried flashing the factory image to both a and b blocks. I tried this. This is when I realised the boot_a and boot_b behaved differently when active.

Having read the the guide in this topic, I updated my ADB/FASTBOOT package to the latest, and updated the USB drivers.

I followed the guide meticulously. If boot_a is active, eventually (after some strange events) the original Android 11 factory image would flash "successfully" but the phone would end up in a boot-loop. If boot_b is active the flashing would fail because the phone will not go into fastbootd.

I have tried flashing the boot.img file that come with ADB to both boot blocks, and flashing the boot.img file contained in the factory image. Neither option makes a positive change. It just changes the variety of boot loop.

I am sure that there must be a solution to this problem, but I do not now know what to try.

Please bear in mind that my knowledge of all thing Adnroid/ADB/fastboot is need-to-know. I learnt to follow instructions to do the things I needed to do.

I am going to try to upload videos of the different boot-loops and failures. I'll post them when I've managed.

I would very grateful for any guidance.

Many, many thanks in advance.
[Google Pixel 3 XL Guides, News, & Discussion] theg00dguy:
Here's a link to a video I uploaded showing the strange boot behaviour:
[Google Pixel 3 XL Guides, News, & Discussion] Lessexpert:
Have a weird error where when it starts extracting 'system_a' the flash-all script fails and says not enough space to resize partition. Any suggestion to solve this?
[Tilt, TyTN II, MDA Vario III General] Darkmanx:
anyone know how to take faster pictures with the att tilt? i mean my girl has a iphone and as soon as she hits the button to take a pictures it takes a good clear pic. but the tilt it and focus's and does all this stuff , and by the time its ready whatever your trying to take a pic off is gone. and another thing how do i stop these annoying alerts for the email poping up? I want to know when i have a text message but i dont want the alert for the email part
[Tilt, TyTN II, MDA Vario III General] Mikulec:
for the camera try to take pictures with a half-press. It takes pictures very quickly when u are in area with good light.

for the message go to settings/personal/soounds and notif. find an option for the new email and untick to show on today
[Tilt, TyTN II, MDA Vario III General] bapssystupr3m3:
thats what autofocus is for..i dont believe iphone has autofocus
[Tilt, TyTN II, MDA Vario III General] Mikulec:
that was the first think that came to my mind. But I never worked with iPhone so was not sure if it has autofocus.
[Tilt, TyTN II, MDA Vario III General] kuraki:
well the costumer service of htc (yes i called) gave me the advise to put the phone first in a dark zone and then in a light zone. Then in the light zone it has increased fps and it takes the picture way faster..

hope it helps
[Tilt, TyTN II, MDA Vario III General] Mikulec:
u can make it easier by hitting the power button(to switch off the display) while u are in the camera app, and then switch the display on.

This "fix" was posted here on the forum a month ago. Looks like the HTC is lost without xda. :D
[Tilt, TyTN II, MDA Vario III General] xtremdremz:
iPhone does not have autofocus or any type of Zoom, plus no MMS capabilities, thats why I got my tilt