yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] DarkShadowMX:
Hi! I used your script but after it had success (no userdata format) the phone was still stuck at bootloader but the PC was no longer detecting it on fastboot... do you know why that would happen? :(

EDIT: For some reason it was only on my main PC, used another PC and fastboot was able to detect my phone. After multiple flash-all and deuce's script, I'm in now again :)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] jrbmed08:
Hoping someone can help me out here. I was trying to upgrade my bootloader unlocked and rooted Pixel 2 from 8.1 to 9.0 using a factory image and screwed something up along the way. Now I have a "slot unbootable" error and can not boot into anything except the bootloader. When I press volume down and power, it boots into bootloader mode instead of fastboot mode. When I try to enter download mode via the bootloader, the bootloader restarts and says "Error: Operation Denied." I really would like to use this script but it seems there's no way for me to get into fastboot mode. Any ideas?

Edit: The script seems to be running despite being stuck in bootloader mode, but my phone still won't boot. This time it's "LoadImageAndAuth Failed: Load Error"

Edit again: And it worked after updating to the latest version of platform tools. I had no idea that even had an effect until I started frantically googling how to fix it and found this: https://www.reddit.com/r/androidroo...oncerning_error_loadimageandauth_failed_load/

Thank you for this tool!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] nolimit78:
If you took a closer look as to what was failing, you'd see that it was having a hard time switching between the a and b partitions. I ran into this a few weeks back when I had to update my computer and did the 15second ADB installer. That uses an older version now and causes problems like you described.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Just FYI (nolimit78 gave you the answer), fastboot is a program you run on your PC. The bootloader is what you boot into when you want to run fastboot on the phone. (Some people call it bootloader mode, some people call it fastboot mode, but it's neither, it's just booting into the bootloader.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] jrbmed08:
Thanks! I'm used to a Sony phone in which fastboot mode was actually a separate mode with a different button combination to start it. There was bootloader, fastboot, and recovery...and if I remember correctly, all were different. (Edit: unless maybe I'm remembering wrong and it wasn't called fastboot mode, but maybe flash mode?

It was the mode you had to put the phone in to use Flashtool and Newflasher.)

---------- Post added at 10:27 PM ---------- Previous post was at 10:26 PM ----------

Ah yeah, good to know. It was a bit of a pain but I got things working with Deuce's script. And probably should have clean flashed either way.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] RomBetaTester:
Device might be completely bricked Please help!

So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date

Anything helps!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Supernoobsammyson:
so just want to say a huge THANK YOU. totally thought i fried my new pixel 3 xl. on android q beta. i couldnt take the ota to revert back to pie. after some research found this, opened this script up, modified it to work with the pixel 3 xl images. some are the same some are different. just folllowed your steps in linux, rewrote the script and blammo back on pie. again huge thanks, saved me some time on writing out a whole new script.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] nolimit78:
Ok, this is what happened to me with my device before I RMA'd it and I swear it was like, two days after I sent it in (even kept working on it up until the very last minute) I found someone who did some additional things that I didn't try and they had success.

https://xdaforums.com/showpost.php?p=78691702&postcount=12
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] loki993:
Ok I must got my phone back from RMaing it for another issue. Since I had it in a clean state I thought I root it and put a kernel on. I followed the step by step guide but it wouldn't flash the latest image with flash all. It would fail and say not enough space. I tried with the all in one tool and it also wouldn't flash, it sais flash-all is not a valid command???? WTF???. It was on January firmware so I figured I could deal with it later. Installed TWRP and ran Magisk with the all in one tool. I found a kernel I liked and it said it was on the latest april updates...so I thought I needed to flash the latest april google image for them. So I found this tool, ran it everything seemed ok and my phone bricked.

So now I get the standard your phone is unlocked message or whatever, orange, but I also now get a red message that says your phone is corrupted. It can't be trusted and may not work properly, and it will not boot. It will get to the g screen and just sit, or sometimes it goes back the the corrupted screen. I can get it into fastboot but its finicky about that too if I hold the buttons too long the screen just goes blank. I cant boot into TWRP either it just says the same thing. I rant deuces tool again because it seems to be the only want the phone would flash and it seems to flash the b partition but can't get back to the a partition and fails.

Im sure there is something stupid that I'm doing or have done but I need help. This phone for some reason had fought my in the process every step of the way to this point.

I DLed the latest platform tools from google, april factory image and checked the hash. Updated to the latest android usb drivers, so I think Im all up to date on all of that but maybe I missed something?

Edit.....I went into driver for the phone and said update driver...it found something and updated it. The driver I was using I got from google today...so I don't know how it could have been different. I made a new folder and put everything in there..platform tools and I extracted the factory image. I flashed all and it actually worked. I also used the march update just to rule out something being wrong with the april one, though now that I think about it that's very unlikely. So I don't know if it was the driver or the fact that I out everything in one folder, though I tried the folder thing before I'm pretty sure.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Make sure you have a USB 2,1 in there somewhere (the port, the cable, something - 3.0 will not work with the Pixel 2.

Before you use the zip you downloaded, check the SHA256 (the number is right at the download location , next to the package number.

Unzip the package (I find 7zip easiest for this package) and extract everything but the image-walleye-pq2a.190405.003.zip file. Then open that and extract everything in it. Boot to recovery (with it still unlocked, of course) and run Deuces flashing script (from here). (There has to be enough space on the system partitions. even if you load 118GB of files, that's on the user partition, it has nothing to do with the system partition.)

If it still doesn't work, call them back and ask them to RMA the RMAed unit.

(The first thing you should check with an RMAed unit is the build date. If it's current, leave it. )
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Ameelo:
hi deuces,

Will this script work on LOckEd Pixel 3a?

See my issue here on Post#54 - https://xdaforums.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413/page6

Your response will be appreciated.

Thanks, Amrit
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Locked bootloader? No, you have to unlock the bootloaded in Debug, then again either in the script or using fastboot (either one after you've booted to the bootloader).

I don't know whether the script itself will work on the 3A, but you can look at it to see what it does (it's just text) - either the .bat file or the .sh file, whichever you're more comfortable with.

But in your case, the fix is even easier. If the computer doesn't see the phone (fastboot devices should return the phone's serial number), hold the power button down until the phone vibrates - it could take 30 seconds or more. Then the computer will see the phone.

Then download the factory ROM (from https://developers.google.com/android/images#sargo) and extract everything in the folder in that file to the same folder that the .zip file is in. Run the flash-all file for your PC (.bat for Windows, .sh for MacOS or Linux) and it should install the OS. (I ran into the same sort of thing when I went from Beta back to Pie on my Pixel 2 - locked in the bootloader, and the computer didn't even recognize that anything had been plugged in. Someone here on XDA figured out the "power button until it vibrates" trick, but I didn't save a link to the post to credit him for it - sorry, whoever it was. once it gets recognized by the phone, you can try fastboot boot.img [after you extract boot.img from the .zip file you'll be left with after extracting everything]. If everything is back, use fastboot flash boot boot.img to replace the boot file and you're back in business. If not, open the .bat or .sh file in a plain text editor, remove the -w from the last fastboot line, run the file and you'll get everything replaced except all your apps and files - they'll still be there. [Unless you really did trash the whole phone, in which case you'll just have a new Android installation.])

But if the bootloader is locked, you can't do any of that, so contact Google and explain that you joined the Beta program, left it, and after that the phone is locked into the bootloader - and would they please replace the phone. (It's still under warranty.) If you're nice, not demanding, they're great people to work with. I push my phone to the limit, and I've been on the phone with hem many times, asking for a replacement (like the time my phone was locked into the bootloader but the computer wouldn't recognize it - before I read the fix here on XDA). They run about the best customer service organization I've ever run across - including two that I'VE run in my career.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
Did you have the bootloader unlocked in the debug screen before you started having the problems? If not, you can't flash anything, and you'll have to contact Google and have the phone replaced.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] frawstme:
Can this repair the bootloop without wiping all system files? Thanks!
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
No, unlocking the bootloader wipes the phone. You should do this before even setting the phone up the first time. You could manually back up as much as you can get to, then unlock the bootloader. (Assuming the bootloader on your phone can be unlocked - some can ne, many can't be.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] ISSLEDOVATEL:
not work
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
How about some details? Port level (USB2 ? USB 3.0? USB 3.1?) Type of cable (USB 2? USB 3?)

Also, what's going wrong? What is or isn't it doing?

I've had it working on my 2 since 2018 with a USB 3.0 port but a USB 2 cable.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] drancill:
Used this script worked wonders, the second time

Little hint to those who may be failing, your fastboot.exe may be old.

Pixel 2 Android 11 October Update
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
The date on my fastboot.exe is 8/14/2018 and it still flashed the October update. The Pixel 2 isn't that much older. (I suppose if you're still running fastboot from the OP, there might be problems.)
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Meandi51:
hi guys, will it work on a pixel 3a (sargo) either ?
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] legaldexter:
This is a Pixel 2 thread search in your respective thread
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
It should work on a 3, 3a also. You just have to download the proper ROM from Google every month ( Google | Factory Images for Nexus and Pixel Devices). Just remember to choose to not format when it asks, or you'll lose all your data and all your installed apps.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] nxrazlly:
Can i have D.Tool script v4.5 link ? Because only that version work on my walleye
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Rukbat:
@nxrazlly:

I don't have 4.5, but if 4.4 worked for you, you can download it at https://mega.nz/file/FMIE0b7b#27_ozSHBki4rRtjU0__evqZ9rkdqCfM5bjO-zHxw0uA.
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] nxrazlly:
thanks v4.5 already in it
[Google Pixel 2 ROMs, Kernels, Recoveries, & Other ] Recon009:
Im Getting This Error Pls Help...
[Sony Xperia XZ Questions & Answers] ghafik:
Hello !

Firstly, i dont have a very good english so I hope you can be a little understanding, well, lets get started, i've bought an xperia xz from someone ( he still has 2 month guaranted) , the few first days everything went normal and all, I didnt really watch the battery drain because i stayed all day in house, now that I have began to work, i've noticed that my battery usually falls at 12pm or 1pm ( works begin at 8pm), I've been looking at the internet to do some research but I still don't really get it, does the xperia have a fast battery drain or my battery is somehow borken, I need a phone that can lasts an entire days with an average usage, theres a way to make him lasts longer or do i change him for a Samsung s7 ? (
[Sony Xperia XZ Questions & Answers] :
Check my thread in the guides section
[About XDA developers] BigBen:
Am I the only one who is bloody damn tired of opening a thread that appears on the first page of a forum, thinking it is new, only to find that it is six, eight, ten months old?

Wouldn't it be reasonable to have a column in the forum listings that indicates the original posting date of each thread, so that just because someone posted to a five-year old thread, which bumped it to the first bloody page of the forum, we don't have to waste time reading old news?

Ideally, old threads would just fade away to page two, then three, then four, etc. until they ride off into the sunset. What sense does it make for them to take center stage six months after their birth, just because some noob comes along and posts a "downloading now" to LVSW's WM 6 v. 0.1?

Ah, that felt good. Thanks for letting me vent. That means I won't have to stalk the dark, foggy streets around the port of Miami looking for another victim.

Ben
[About XDA developers] gavink:
I mostly agree with you Ben. I look at the number of replys and views to try to determine how old a thread is. Then comes the bouncing from page to page to find the posts I haven't seen yet.

I'll admit that I'm new to XDA, so maybe there's a way of only showing the unread threads and/or posts? Then again, sometimes the older posts jog my memory about what is being discussed.

Guess with such an active message board, these sorts of issues come up. Anyone have tips they'd like to share on dealing with it?

Gavin
[About XDA developers] BigBen:
Michael, it's an honor to have a reply from you. I always enjoy your posts.

And no, you will not become one of my victims around the foggy port of Miami. Aberdeen, perhaps ;) Actually, it is rarely foggy in Miami. Come on over and enjoy the nice weather, friend.

I take your point. However, what about the idea of a column showing the original posting date? Or, could that date somehow be made to show up in the balloon when one places the cursor over the thread's title?

I wasn't really suggesting closing out a thread, Michael. Just letting them drift to the back of the line, perhaps. But even that is not necessary. Let them come to the front page when someone posts to them, that's just dandy. But let us know that they are a week old, or a year old.

Cheers for your contributions to the fora, Michael.

By the by, PLEASE do not accuse me of proposing something that emulates the AT&T forum! Ugh. That will bring out the Mr. Hyde in me. I had a terrible experience there with the appropriately named Mod Moose over a year ago and have not been back sinece :eek:

@gavink, thank you for your reply, too. This issue is a pet peeve of mine. It doesn't seem to bother many members, though, so it looks like we will have to live with it. A very old thread can have many, many posts, or very few, by the way, so that's no help.

Regards,

Ben
[About XDA developers] gavink:
Thanks for the tips, Mike... Didn't know what that box was for!
[About XDA developers] BigBen:
Hello, again, Mike:

As always, your replies are cogent and witty. Large sums, indeed. Please, let it be in US $, not Euros, eh? Be kind.

Well, yes, Miami is pretty fabulous. If you ever get over here, please let me know ahead of time, and we will open our house to you.

OK, I am not requesting any threads be deleted, or even re-ordered. If it were possible, all I would like to see is the date of the original posting. This would help us to avoid wasting time reopening a thread we saw six months ago. For those of my generation, who cannot remember what we did ten minutes ago, this would be very helpful.

Making the original date of the first post available just seems to make sense to my time- and whisky-addled brain. Not to be able to see the date is like publishing an old news article and hiding the date.

From the traffic on this thread, or, more accurately, paucity thereof, I guess it doesn't amount to a hill of beans, so I am going to go pour myself a wee drap of the Glenlivet now and then forget about the whole damn thing. (You see, like you, Mike, I too like the Scots "mist") ;)

But before I sign off, forgive me the breach of forum rules. With the cup of Glenlivet, I shan't be needing any other mind-altering drugs, however.

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

A wee drap o' whisky I tak' when I'm weary

My blood for to warm and my spirits to cheer

And when I sit doon I intend to be merry

So fill up a bumper and bring it round here.

(First verse of a traditional Scots song)

.........................................

One last observation that has absolutely nothing to do with nothing. Your country's flag, (displayed in your personal information at the top of your e-mails, is practically identical to the U.S. and British Navy signal flag "M." And "M" when spoken in those Navy's, and the international phonetic alphabet, is "Mike."

You have a right to be doubly proud when you see your flag, Mike.

Cheers, brother Michael!

Ben
[About XDA developers] BigBen:
Mike, I think we have lost the rest of the "crowd" that were already not looking at this thread. ;) Ah, well.

The history and pictures of the whisky mills were an absolute treat. It's amazing how rustic they seem (the sheds, that is)! Thanks for sending those. I will put them into my archive. I really would like to see them in person some day. Made it to London once, but that was a long time ago, and it's not Scotland, where some of my ancestors came from (along with some from Eire.)

I've not run across Macallan. Now I have a mission to find it.

That last picture is a gem. Give me the guy's contact information. From the looks of things, I don't suppose he has an e-mail, eh? I would buy a case of his brew without thinking twice, ha, ha!

As to the "Mike" flag, just Google "Navy Signal Flags." You are in for a treat when you see Scotland's proud flag identified as "Mike. Here is a table that shows both the flags and their phonetic names:

http://www.navsource.org/archives/sfpa.htm

Regards,

Ben
[About XDA developers] BigBen:
Thank you, Michael. Nothing should be done if there is a cost in money or time. Clearly, not many people are very worked up about about the issue.

Kind regards

Ben
[About XDA developers] BigBen:
You've a good sense of humor, Mike. Uh, is the photo typical of how the Scots bring up their wee ones? No wonder they are such a feisty bunch ;)

Cheers

Ben
[About XDA developers] BigBen:
Well, well, well. Methinks you have to much time on your hands, Mike. Of course, here's Ben answering you, so who am I to talk?

Check out my new avatar. I was going to use this when I joined the forum, but never got around to it. The website photo you sent me was too much to resist.

In spite of my age, as revealed now by my mugshot, I still have a bit of "bong" left. I have been feeling less "feisty" the past few months, however. Reading the article you sent, now I understand. Big Ben had lost its "bong."

Not sure those workers scurrying around the face of my, uh, inspiration are going to do much for me, though. Perhaps if one of them were "bonnie Jean" from "the streets of Aiberdeen...."

Ben

(There go my chances of getting my "original post date" request implemented by our dear Webmistress, eh?)
[Moto G4 Plus Questions & Answers] trsix:
Invalid zip file format

The only roms i can flash now are lineage 14 and 15. All others i get the error in twrp.

Any ideas why
[Moto G4 Plus Questions & Answers] ____Mdd:
Which TWRP you are using ?

For N builds, try shreps' 3.1.1 TWRP.

Have you modified any of those zips ?

Try md5 checksum and match with original download files, then download again.
[General Questions and Answers] Delgoth:
I've come to ask if anyone could give me some more insight on using PC application to emulate the Arm 64-Bit Arch in a way that would allow it to boot a full android firmware package? Namely a Samsung Device, it would entail the pieces of an ODIN firmware package or a normal system dump from the device.

Now I've seen this done. But that usually involves building AOSP from source or using a factory nexus image. I understand I could achieve my goal if I wanted to use a stock AOSP rom, but it should still be achievable using one of Samsung's roms right? Especially since a lot of their devices include init files for goldfish.

But I'd really like to ask for some pointers from some people knowledgeable in the commands of the emulators.
[YotaPhone] FataRana:
Dear Yotaphone developers Hello everyboy

worked for the first time) but the phone says it's wrong. What can I do to unlock my phone without losing the saved datas? Also I can't use my e-mail to confirm and unlock. I turned it off and on and it still doesn't work.

Thanks for your attention.

I’m looking forward to your reply.
[One (M8) Q&A, Help & Troubleshooting] jeeprcreepr:
I've read here of people converting their non GPE edition to GPE..and then being able to go back to Sense... I'd be interested in doing the opposite.. Go to sense and have the option to go back to GPE... Is this doable? Downloaded this "RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4" ... Is this what I need? and if so also should I update firmware? I helped my dad upgrade to Marshmallow on ATT&T branded phone but his would not work until we updated firmware. If firmware needs updating can a kind soul provide a link?
[One (M8) Q&A, Help & Troubleshooting] Roadrunner100:
+1
[One (M8) Q&A, Help & Troubleshooting] lucyr03:
You need S-OFF for converting it.