yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Yes, I've downloaded a large variety of different images multiple times, including after I freed up over 16gb. None of them have all of the .sig files flash-all.bat expects, at least not anywhere I can find them. I don't know, are they inside some if the .img files?
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I've recorvered from sot bricks before. I've never tried a variety of cables and ports to make it work. If I'm trying each rom with each port and each cable I have, downloading, unzipping, and deleting each rom each time, that'll take me hours. If I want to try that all again, but clearing the device as you described each time, it'll take me more hours. I could find myself spending days on this project the way you're describing it, and in the end, it still wouldn't work. 20 minutes is a flat lie.

I'm not expecting a magic solution anymore, but I'm expecting something more helpful than "try flipping every damn bit on your laptops hard drive one by one and see if that works."

Can you tell me how to test a port, once, and see if that port works? Or how to test a cable, once, and see if that works?
[Google Pixel 3a XL Questions & Answers] krabman:
Not true, you can do what I described and in the time I described it. And easily; or at least it would be easy if you cared to learn instead of hoping for the magic silver spoon to be delivered to your mouth. I'm not buying that you have the experience you describe because if you did you would not have posted what you did. You would also know what will be my last bit of assistance: When you flash an imagine from Google it often shows signatures and files not found even on successful flashes because the script is looking for them in case they're needed.

The last word is yours should you wish it. Good luck.
[Google Pixel 3a XL Questions & Answers] sic0048:
There are OTA update images and full factory images. The OTA images obviously won't have every file, but the factory images should. Your can probably use either image, but they are installed differently with the full image being flashed in a traditional method and the OTA image being sideload. Just be sure to follow the correct installation instructions for the type of file you are trying to install.
[Google Pixel 3a XL Questions & Answers] Milly7:
Just read a few posts. Is your adb and fastboot up to date?
[Google Pixel 3a XL Questions & Answers] krabman:
The factory image always shows that files, signatures, and the like are not found when flashed, whether successful or not. It doesn't mean that they are needed, simply that the script didn't find them, it's generic and looks for many things you may or may not need. In any event he almost certainly is not missing files as he has tried multiple downloads and Google is pretty good about vetting their DLs before they publish them. He will however require the full image as his pictures show he needs to partition. He has a flash error which is going to be the platform, a bad cable, port, or download.

If it were just flashing a boot image or something like that you can get away with a lot but Googles images are notoriously finicky flashers. A search will pull up a ton of people that failed to flash successfully with essentially the same information that he posted and they fixed it with nothing but a cable switch, different port, updating their platform, basic stuff. I know, I made such a search myself when I first got the phone because I tried to update from the full image with the C to C the phone shipped with and got stuck in a loop. With literally dozens of search results saying that you should switch to an A to C I figured I ought to try it and sure enough the flash went right through without a hitch.

He can quickly solve his problem if he stops looking for files that aren't missing and does the usual.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I've read every post I could find on the topic.

Yes, they're both up to date. I downloaded them from Google right before I did this.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Nobody told me whether or not those files meant anything. They asked for my logs, I offered them and pointed out the errors.

I've tried switching ports. That, itself, did not solve the problem. I cankeep switching and trying every single flash on each port, but that multiplies the time I spend doing this by three. Which is why I asked if there was any way at all to know, instead of continually guessing.

The other guy mentioned "known good cables," but he didn't offer any information about what cables are known to be good. I don't have a massive stockpile of A-to-C cables here, and even if I did, I wouldn't want to go trying each flash in each port with each one of those cables, so again, I'll ask: is there any way at all to know, instead of continually guessing?
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I'm starting to see that formatting issue consistently. It says

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)
....
FAILED (remote: Failed to write to partition Not Found)

This seems relevant.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
You mean the factory image? That's what I've been using. Or do you mean the OTA images? Those are smaller, and they're only supposed to be updates, right? Not sure why those would work...

I've been getting the Factory Images from here: https://developers.google.com/android/images

Those definitely require an unlocked bootloader, and all. So I'm really confused as to which you mean.
[Google Pixel 3a XL Questions & Answers] krabman:
Sorry, my bad, I meant OEM unlock switch position but said it poorly. And yeah, those are the ones you want, I recognize the link The idea of getting it again is to make sure your image is solid gold, same for the latest toolkit. What you're looking for is as much known good stuff as possible. That's why people were saying to use a known good cord. If you have one it's excellent advice because you want to make it as easy as possible. in your case you're going to have to sort that out as you flash but I wouldn't worry to much about the cord, if you've got a couple and they're not the super el cheapo Amazon type you probably have one that works. In any event if you know to a certainty that you got the image from there and the size matches you can keep the download you have, otherwise DL it again. It's a matter of a few minutes so wouldn't skimp if I were you. Solid gold is your friend. Follow the link in the thread I posted to get the toolkit. It's the easiest way to go that I'm aware of to set up your ADB platform. Don't let this stuff shake you, it's not hard at all and when it's over you're going to be thinking it was actually pretty easy.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
My cords are benson leung approved for power, but I still don't see a list anywhere of known good USB A-to-C cables. I used these: https://www.amazon.com/gp/product/B0746C244X/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1. Does anybody, anywhere know if those are good or bad?

I used the sha256 checksums, I don't think the roms are the problem.

I'll try to update ADB and fastboot and the toolkit again, but the last time I tried it just told me I'm up to date.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I should clarify, by the way, that I do not have a windows 10 device. I have windows 8.1. That's not the problem, is it?
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Okay, here's an oddity. The adb/fastboot I had from before went into c:/adb. The guide you linked to told me to unzip something similar into c:/platform tools, which, as far as I can tell, doesn't have adb, but does have fastboot.exe. That fastboot.exe gives me an error when I try to run those full wipe commands -- it doesn't seem to do what fastboot does. I've tried this with and without my c:/adb folder present. Something ain't right there. I don't know if that's the key issue, but it's there.

And yes, I tried flashing again, and no, nothing changed, it still won't partition/format.
[Google Pixel 3a XL Questions & Answers] Milly7:
If you're willing to wipe the phone, then have you tried fastboot erase prior to flashing the image?
[Google Pixel 3a XL Questions & Answers] krabman:
You'll get an error on the wipe commands if they find a system or boot to wipe, based on what you posted before that is probably the case for you. The instructions there BTW tell you to exctract the tools to C, you will then see the platform tools folder.on the root. You don't have to do that. You can place it in a folder on the desktop and extract it there where you will then find the platform tools folder. Open that folder on the path line type CMD, in the resulting box type in fastboot devices and see if it returns a serial number. If it does go ahead and try those commands. If they don't work it means the boot and system dont exist or are corrupt and you'll be skipping that step. Go ahead and keep platform tools open but you can closet the command prompt

From there what you want to do is create a folder on the desktop and put the factory image in it. Extract it in the same folder. Go ahead and take everything from the platform tools folder and drag it into the folder with the factory image you extracted. Run the flash-all from that folder.

Sometimes things are assumed that shouldn't be, you are manually putting the phone into the bootloader before you flash or try to run commands right? Sorry for asking, but you never know.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Everything I do in the newly downloaded C:\platfrom-tools gives me this error:

The procedure entry point _create_locale could not be located in the dynamic link library C:\platform-tools\fastboot.exe.

I just went back into my c:\adb, opened the shell there, ran those delete commands... the erase_a and erase_b actually worked this time -- they returned errors before -- but I still see the serial number in fastboot devices.

I *did* enter fastboot with the buttons, but lately I've entered into it just by plugging my phone, while it's off, into my laptop -- that puts it straight into fastboot for some reason. Is that weird?
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Yes, as Krabman has suggested. This is a new phone, so there's nothing precious on it, let's go nuts, just get it working.
[Google Pixel 3a XL Questions & Answers] krabman:
The platform tools from that link are designed to run in their own container, this way they don't conflict with any other platforms that may already be installed. You got the error because you made the command outside the platform tools folder. That you ran the wipe commands bodes well, and you should see a serial number return when you check devices. We're gaining.

To go back to those tools create a folder on the desktop, drag the full tools archive in there and then open that folder and extract it there. Leave it open with all the extracted files visible. Create another folder on the desktop and put the image in it. Go ahead and extract it in that same folder also leaving it open to showing all the extracted files. Now drag all of the extracted files from the platform tools into the folder with the extracted image, they should all be together in one folder. Run the flash-all. The platform tools are fully self contained and will find the image and should flash it, or at least attempt to flash it.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
No, even from inside the folder I get that error.

I tried this, and got the same error. I don't know, are those platform tools windows 10 specific or something?
[Google Pixel 3a XL Questions & Answers] krabman:
It's an interesting question but one that I cant answer, it's been years since I've screwed around on 8.1. That path is not on the desktop, it's from the root. If not finding something from the desktop it should return a not found from the location where it wasn't found (the desktop) when you ran the bath file. As an example I don't have a platform tools on my root (C.) and used that same platform from the desktop for all the updates for this phone; I use the full image with the wipe removed because I'm in a remote location and have to get updates where the internet is better than 4k, OTAs aren't possible. Also the DLL is in the archive. It really is looking more and more like the platform though, that's for sure.

Lets go back to 8.1, because it may be time for me to learn something. Those platform tools are Goog's, set up specifically to have everything you need to flash their images. I've been flashing from the desktop because of the ease of flashing there and it works fine, but I'm on 10. Lets say I'm getting away with something I'm not supposed to for reasons unknown, maybe it really needs to be on the root directory. IMO you should try extracting to C: or extracting on the desktop and moving the full extracted platform-tools folder to C;, then you would take the image, extract it, and drop the extracted contents of the image into the platform-tools folder you put on C; and execute the run-all. Remember that all the contents of both extracted files need to be in that folder together. I'm not trying to be pedantic here, I'm thinking maybe you're missing one of those steps and don't have all the extracted files together in the same folder somehow because if they are it should at least try and install.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Sorry, to clarify, the path itself changes to the path I'm using, the rest of the error message is the same. And this isn't an in-terminal error message, it's a pop-up-and-ping error message in the operating system's style.

I'll point out: I extract the initial zip file I download from Google, but not any of the zip files inside that, because that was never an instruction, and as far as I can tell, flash-all.bat is supposed to extract on the fly. Is that the problem>
[Google Pixel 3a XL Questions & Answers] krabman:
You're correct, after you extract the img there will be another zip inside that which does not need to be extracted, it's handled by the batch file during the install process. I've included a picture of what you should be seeing. If you extract the tools to the C: you have a folder called platform-tools, you would open that up and see what you see in the open folder on the right in the picture. You would then take the image extract it once and open up the new extracted folder and see what you have in the folder on the left in the picture. With those two just as they are you would take everything in the folder on the left and put it in the folder on the right so that all those files are in the platform-tools folder. They would all be visible just as they are now except together. Then you run the flash-all.bat. Make sure you're hiting the .bat and not the flash-all.sh because the latter wont work.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Lol, no screenshots? That's generally what it looks like, but I can't go file for file, I can't really even read that. Yes, I understand what you're saying about copying files over, that's definitely not the issue, considering these fastboot files don't work anywhere.

Yes, I'm running flash-all.bat.

Is there any other place I can get adb/fastboot?
[Google Pixel 3a XL Questions & Answers] :
This is what I use on both windows 8.0 and 10 - works fine on both... https://xdaforums.com/showthread.php?t=2317790
[Google Pixel 3a XL Questions & Answers] krabman:
Sorry about the picture, as I said the connection is very slow here so I had to reduce it enough to get it to go. lol That error has been fixed by downgrading to platform-tools_r28.0.1 (for some people) with windows 8.1. Same place for the download, same process to flash.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Oh, ****, this did it. At least, this allowed me to flash back to stock -- let's see if I can get to 10.0 and root with this.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I was looking at the page, actually, and the bug it said the latest version was fixing seemed to be exactly my partition error. The minimal adb & fastboot tool the other user posted is actually working for me for now -- it got me back to stock at least -- so I'm going to see if I can root with it, and if I can do that safely, I'll be happy. Thanks for the help -- I mean, it didn't really pan out, but I guess that's what tech support is, trying a bunch of your best guesses, so I still appreciate it.
[Google Pixel 3a XL Questions & Answers] :
Sweet! Congrats :highfive:

Happy flashing:good:
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Well, I'm rooted with the version of android that shipped with my device. 10.0 wouldn't flash, and I'm afraid to update it, but it's working!
[Google Pixel 3a XL Questions & Answers] :
If you really want to be on 10 I guess you could re-flash the pie stock image, don't root because I think it affects OTA capability, and then upgrade through a standard OTA update.

But if you're up and running now it may be best to just leave well enough alone. ;)
[Google Pixel 3a XL Questions & Answers] krabman:
Yeah, I searched your exact error with the thinking of verifying if it was driver related and several returns popped that some people were having issues with the latest toolkit and reverting back one version allowed them to flash successfully. You did it with a different version which is great, it's getting there that matters, not how you got there.

Now lets get you on 10! bwa ha ha <----best Dr Evil laugh. :)
[Google Pixel 3a XL Questions & Answers] thetastycat:
This just ABSOLUTELY SAVED ME. I think what may have happened is I had flashed the July 9.0, which then somehow updated to the August 9.0 without me being aware, then I rooted assuming it was July. Nothing worked - except this!!! It even hung at fastboot erase system_a - I had to close the window then run the rest of the commands, then it would erase system_a.

Now it's running 100% - I really can't adequately express my thanks for you all!!! XDA for the WIN.
[Google Pixel 3a XL Questions & Answers] krabman:
I'm not even sure how many times someone here has helped me out of a jam but I think I can fairly categorize it as many; it's a great resource.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Glad to hear my thread helped you help somebody else.

Now, as for 10...

I started from scratch, got to 10 the old fashioned way, installed magisk, patched boot.img, booted the patched boot.img, and... nothing, magisk didn't recognize it. It booted up fine, but as far as I could tell, it wasn't rooted. So then I thought... **** it, I'll flash the patched boot.img, and I did, and... same ****, magisk is telling me I'm not rooted. Magisk, you're the one who patched it!
[Google Pixel 3a XL Questions & Answers] :
You need the magisk canary build to root 10. Search the forums for instructions if you need them.
[Google Pixel 3a XL Questions & Answers] krabman:
Yeah, dont get the debug one, just the standard canary. Once you have the manager installed make sure you go in and choose the canary channel in the options. From there it's the usual for flashing the patched_boot.img.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Oh no... The word "canary" scares me. When can we hope for a magisk build worthy of the title "beta," if not stable?
[Google Pixel 3a XL Questions & Answers] krabman:
The only downside I've run into with Canary is that it updates quite often, some folks wouldn't like that. It's never left me stranded though that's always a possibility with any software out on the edge. Can't do more than guess on when it will filter down to the beta or stable; he's generally very good and sooner is more likely than later.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Is "sooner" days, weeks, or months? Weeks, I'd assume? I don't mind a beta so much, but every thread I've found for the canary so far seems to give outdated instructions about how to find it and then warns me not to install it.
[Google Pixel 3a XL Questions & Answers] krabman:
It was a matter of weeks with pie and things are going well with the Canary builds; that's a good sign but my guess wouldn't be any better than yours.
[Huawei P9 Questions & Answers] yokozuna:
I wanna rebrand my friend's EVA-L19 (3GB RAM/32 GB memory/ dual SIM) with this tool https://forum.dc-unlocker.com/forum...cker-software/172136-dc-huawei-converter-beta in order to install Oreo on her P9? What is the counterpart of this type of P9 because that are many subtypes (single and dual SIM, various RAM amount, etc.) and do not wann brick her phome. I suspect that this type is EVA-DL00 but I am not certain and prefer to ask more experienced colleagues from the forum.
[Huawei P9 Questions & Answers] zgfg:
Just use HWOTA7 method with instructions from this thread

https://xdaforums.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849

and you will rebrand to the latest Oreo EVA-AL10 c00 b540, you have separate Network patches for L09, L19 and L29 to fully utilize your hardware and to get definitions for worldwide mobile operators (also debloating your phone, making GApps fully working, ready for Google app and for Location sharing if you wish - it is blocked in the plain stock Chinese Oreo).

You have also add-on for Face unlocking, instructions (with patched Ramdisk) for Magisk and strong community (it was, now people are moving to newer phones)

From the stock Oreo you can also go to Treble Open Kirin ROMs
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
Yes, yes, it's possible to love a phone. Heck, you sleep next to it, don't you? Rate this thread to indicate your love for the Vivo Nex 3, all things considered. A higher rating indicates that the Vivo Nex 3 is an incredible phone that you enjoy tremendously. You love it. :o

Then, drop a comment if you have anything to add!
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
You're a power user. Can the Vivo Nex 3 keep up? Rate this thread to express how "healthy" the development scene is for the Vivo Nex 3. A higher rating indicates available root methods, kernels, and custom ROMs.

Then, drop a comment if you have anything to add!
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
Would you say that the Vivo Nex 3 is "fast" in day-to-day use? A higher rating indicates that you think the Vivo Nex 3 exhibits fantastic performance. Like, is it as fast as your tears when you watch The Titanic?

Then, drop a comment if you have anything to add!
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
OMG! Kim K posted another selfie with tons of cleavage! Rate this thread to express how quickly apps launch on the Vivo Nex 3. A higher rating indicates that even the most intensive apps launch quickly and without hesitation, even if they are no longer in RAM.

Then, drop a comment if you have anything to add!
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the Vivo Nex 3 performs when multitasking. A higher rating indicates that the Vivo Nex 3 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.

Then, drop a comment if you have anything to add!
[Vivo Nex 3 Real Life Review] XDA_RealLifeReview:
Some phones exhibit choppy scrolling, especially when navigating long web pages when multiple apps are running in the background. Rate this thread to express how you smooth scrolling feels on the Vivo Nex 3 under such conditions. A higher rating indicates that scrolling is always buttery smooth, even when you're reading a 10,000 word article on "how to kiss a girl".

Then, drop a comment if you have anything to add!