yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] gupt07ash:
That's just a stupid blog. Samsung never gives more than 2 os upgrades
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Ruben Craveiro:
It is true.. it's wifi certification test on android pie.. it's going to be the first Samsung phone receiving 3 major OS updates
[Samsung Galaxy S7 Edge Guides, News, & Discussion] SkylineDriver:
Certificates were revoked. Likely somebody playing a prank or some other screwups. No Pie for S7/S7E- least of all for us in the US (we get screwed either way).
[Samsung Galaxy S7 Edge Guides, News, & Discussion] anaz2698:
Thats why i said FE ports are now live..
[Asus ZenFone Max Pro M1  Questions & Answers] Scanysdm:
Anyone using
[LG V20 Questions & Answers] tripaphonic:
Greetings community. This is my first post and I wish it were more positive but it's related to my LG V20 and the bootloop I cannot seem to pull it out of. It's my primary mobile so it's definitely a serious concern even though I'm using another device temporarily at the moment which thankfully was unlocked.

I cannot seem to find a thread showing how to pull the LG V20 out of a bootloop when safe mode is unreachable. I can and have brought the phone into a factory reset menu by holding the vol down & power until I saw the LG logo then quickly releasing then pressing and holding the power button again. I went through the factory reset process and still have the bootloop.

Any ideas? References or links anyone can point me to would be greatly appreciated. Thanks in advance.

tripaphonic
[LG V20 Questions & Answers] tripaphonic:
I can get into the Factory data reset screen but it does nothing when I try it.
[LG V20 Questions & Answers] paul999:
what has been done to the phone prior? is it rooted? what rom? what android ver?
[Xperia Z Q&A, Help & Troubleshooting] fetsk:
I have tried with cmd and flashtool to install twrp.img on my rooted Xperia Z, no luck.

My phone shows in fastboot devices but when I write fastboot flash recovery twrp.img in cmd, it says FAILED (remote: Command not allowed). The exact same error is showed in Flashtool.

please help.
[Xperia Z Q&A, Help & Troubleshooting] LitosVR:
Hi, I don't know if you solved it...

Any way you can check this wiki.lineageos.org/devices/yuga/install

I had the same error in cmd, just change <fastboot flash -recovery- twrp.img> for <fastboot flash -boot- twrp.img>
[Google Pixel 3 XL Questions & Answers] sal-paradise:
So while flashing an update, my Pixel 3XL turned off and now it only loads in fastboot (every other options goes to black screen). On the fastboot screen I get "Device state: error!" not locked or unlocked. When trying flash-all.bat, here's the read out. When I exit, nothing has changed. I can still only turn on the phone in fastboot and no other options. If anyone has any ideas, I would greatly appreciate it!

Sending 'bootloader_b' (8489 KB) OKAY [ 0.399s]

Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')

Finished. Total time: 9.746s

rebooting into bootloader OKAY [ 0.049s]

Finished. Total time: 0.052s

< waiting for any device >

Sending 'radio_b' (71148 KB) OKAY [ 2.501s]

Writing 'radio_b' FAILED (remote: 'error getting device locked state No Response')

Finished. Total time: 11.845s

rebooting into bootloader OKAY [ 0.047s]

Finished. Total time: 0.047s

< waiting for any device >

extracting android-info.txt (0 MB) to RAM...

Checking product OKAY [ 0.060s]

Checking version-bootloader OKAY [ 0.058s]

Checking version-baseband OKAY [ 0.062s]

extracting boot.img (64 MB) to disk... took 0.735s

archive does not contain 'boot.sig'

archive does not contain 'boot_other.img'

extracting dtbo.img (8 MB) to disk... took 0.075s

archive does not contain 'dtbo.sig'

archive does not contain 'dt.img'

archive does not contain 'odm.img'

extracting product.img (194 MB) to disk... took 3.284s

archive does not contain 'product.sig'

archive does not contain 'product-services.img'

archive does not contain 'recovery.img'

archive does not contain 'super.img'

extracting system.img (2158 MB) to disk... took 27.091s

archive does not contain 'system.sig'

extracting system_other.img (418 MB) to disk... took 5.520s

archive does not contain 'system.sig'

extracting vbmeta.img (0 MB) to disk... took 0.002s

archive does not contain 'vbmeta.sig'

extracting vendor.img (445 MB) to disk... took 5.421s

archive does not contain 'vendor.sig'

archive does not contain 'vendor_other.img'

Erase successful, but not automatically formatting.

File system type raw not supported.

Erase successful, but not automatically formatting.

File system type raw not supported.

Sending 'boot_b' (65536 KB) OKAY [ 2.338s]

Writing 'boot_b' FAILED (remote: 'error getting device locked state No Response')

Finished. Total time: 76.748s

Press any key to exit...
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Do you have the current platform tools? Also, use a C>A USB cable and not a C>C.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
Yup, using a C to A cable. Downloaded the tools today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
[Google Pixel 3 XL Questions & Answers] Patch7:
The exact

same thing happened to me. I had to sideload and install the ota. zip and all is good again.
[Google Pixel 3 XL Questions & Answers] sliding_billy:
No answer about the platform tools, but had you updated the phone before this way? If not, different computer, cable, port, etc. The platform tools haven't changed since a few months before nd of last year, so if you had done this before that part should be safe...

Did you confirm the file download and make sure that it was not corrupted when you unzipped the D/L? Otherwise, the above post about using the OTA through recovery is a good option.

P.S. It helps if you quote the person trying to help so that they know there is an answer.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
[Google Pixel 3 XL Questions & Answers] Seamonkey79:
Every now and then I have to swap ports on my computer because I'll get weird errors, not sure if I've seen this one specifically though. Swap ports, swap cables, mix and match until it works or you go through every option you've got.

Speak gentle words of encouragement too.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
Unfortunately this is a bigger problem than just cables, ports, and gentle words :)
[Google Pixel 3 XL Questions & Answers] Homeboy76:
You can't.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
Right, but that's not an option because all options beyond fastboot lead to a black screen.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
Exactly.
[Google Pixel 3 XL Questions & Answers] Homeboy76:
Try this:

On your Computer:

- Open a Command Prompt in the Platform-tools folder

- Make sure these files are in the Platform-tools folder:

bootloader-crosshatch-b1c1-0.1-5191736.img

radio-crosshatch-g845-00009-181130-b-5157073.im

image-crosshatch-pq2a.190305.002.zip

- Boot the phone to fastboot mode

- Connect the phone to the computer with the A to C USB cable

The type these commands (one at a time) at the Command Prompt and press enter after each command:

fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5191736.img

fastboot reboot-bootloader

fastboot flash radio radio-crosshatch-g845-00009-181130-b-5157073.img

fastboot reboot-bootloader

fastboot update image-crosshatch-pq2a.190305.002.zip
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.

fastboot --set-active=a

---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------

If that doesn't work, you should be able to change slots with the fastboot boot [twrp].img version of TWRP (run from fastboot) and then reboot to system.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
When I try this, here's what I get:

PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot --set-active=a

Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')

Finished. Total time: 9.219s

PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002>

And yes, everytime I try flash-all I get the same at my original post with the same error:

FAILED (remote: 'error getting device locked state No Response')
[Google Pixel 3 XL Questions & Answers] sal-paradise:
I have an older bootloader version, so when I try this, it tells me:

PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot update image-crosshatch-pq2a.190305.002.zip

extracting android-info.txt (0 MB) to RAM...

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

Bootloader Version...: b1c1-0.1-5034669

Baseband Version.....: g845-00023-180917-B-5014671

Serial Number........: 85HY008F7

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

Checking product OKAY [ 0.062s]

Checking version-bootloader FAILED

Device version-bootloader is 'b1c1-0.1-5034669'.

Update requires 'b1c1-0.1-5191736'.

fastboot: error: requirements not met!
[Google Pixel 3 XL Questions & Answers] Homeboy76:
¯\_(ツ)_/¯
[Google Pixel 3 XL Questions & Answers] sliding_billy:
Sorry, but I just got back online (been one of those nights). Looking at all the back and forth, I feel like there is a communication gap between you and those of us helping. There are questions and suggestions unanswered. For one, I never saw a reply to if this is the first time you are attempting to update via a flash-all on the same computer/port/cable/etc. That will answer a bit about your knowledge and the hardware functionality. If all that is a go, the only thing that jumps out at me is the possibility of a bad download or something easy to remedy like a command problem or file location/path issue. Have you checked with Google? I know that getting a replacement sucks, but you may need to start over. The folks here have done this tons of times and got back from bricks probably more severe than yours. I have never seen a device that could get to fastboot not be recoverable if all of the things we are talking about are being executed properly, but there is always a first like a serious phone hardware failure that nothing is going to solve except for a replacement.

One thing I see is the PS location. I know there are some commands that don't play nice in PowerShell, so type 'cmd' from PS and get to a standard command prompt.
[Google Pixel 3 XL Questions & Answers] samteeee:
I had the exact thing happened to me on my Pixel 2 XL but nothing worked,

not even the "Duce Script". I decided to use the "Skip Soft" tool as my last resort

and to my surprise it worked and fixed it in less than 10 minutes!

Unfortunately the Dev hasn't added the Crosshatch yet. I suggest you download it

and ask him to add it in the "Device Support" section, he''ll add it once he sees more requests.

Good luck.
[Google Pixel 3 XL Questions & Answers] sal-paradise:
My apologies, I thought a previous comment mentioning computer/port/cables that I responded to clarified this. This is not the issue as I've done it with multiple desktops and multiple USB A to C cables. Even when attempting to change from slot B to A I get the device state error, which I've copied in another post on here. Isn't that the problem here? If I can't figure out a way to get around the fact that there's no response when trying to determine the lock state, I don't think we can fix the problem here. I don't see how this would have to do with being in powershell or not or being a bad download. Since most things fail in fastboot because of this error, this is what I was trying to get more info on to get corrected as it clearly seems to be the heart of the failure.

Unfortunately a lot of the back and forth is because of the repetition about cables and ports or asking me to recover which I appreciate, but I stated choosing recovery sends me to a black screen. When there's been actual commands to try in fastboot, I've posted the results they've given, but it still comes back to " FAILED (remote: 'error getting device locked state No Response') "
[Google Pixel 3 XL Questions & Answers] sliding_billy:
I appreciate the reply. Some of the things are just things that take no real effort (like downloading/extracting the factory image again to be safe), while the PS thing was just to make sure that if folks are sending commands to try that they are sending the right ones. The question about whether you were using a Mac or Linix (that I think has been deleted since I read it) got me thinking about that and not that running the flash-all batch would react differently.

Last thing, have you tried anything with the TWRP .img version like changing slots or even doing a factory reset?
[8125, K-JAM, P4300, MDA Vario ROM Development] lenaddison:
I want to expreiment updating my ROm in my Tmobile MDA vario G3

I want to be able to backup my current ROM so i dont have to reinstall the software I currently have if i want to revert back

Iam looking to try WM6 or even 6.1 are these available for this phone?

your advice please
[Google Pixel 2 XL Questions & Answers] jd1639:
Your IMEI starting with 35 looks like it might be a Verizon motherboard. I believe the Google board's IMEI starts with 99, mine does, and Verizon's starts with something in the 30's. I don't remember exactly what it is. But being able to enable oem unlock is confusing though.

Edit, I have a pixel 3 so maybe I'm all wet too[emoji4]
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
Go to the imeipro website and run the new IMEI through it. Odds are good you have a Verizon motherboard.
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Thanks for all the thoughts and advice!

I ran the IMEI on the website, and got peculiar results...

While entering it in the "LG" section (where I've seen and had experience getting the most information out of an IMEI), it states "Unfortunately no results found for this IMEI number". But when entering it in the main page, it at least states that it's a Pixel 2, G011A, and it's "clean"! So, unfortunately, no conclusive results...

If anything, here is the last 4 numbers of the IME : 2512 (if anyone wishes to do further research, which I am absolutely grateful for, if so).

And I know it could simply be wishful thinking, but I would think since Ubreakifix stated that they had to get a motherboard sent (I assume from Google), that they most likely wouldn't be sent a specific Verizon variant but the "generic" or "default" produced board...I'm just thinking about the "likelihood"...

And, also, would the Verizon variants (whether it begins with 30's or not) also "spit out" the results from the log; get_unlock_ability comes out as 1 and the blue ticker? Although, in my research, I've seen some getvar all logs state "(bootloader) is_oem_unlocked:yes", but I'm not sure if that applies to certain bootloader versions, if that was Oreo or Pie, and if it even makes a difference being an XL model or not...

I'm absolutely confused...but please, again, any thoughts or ideas or suggestions is greatly appreciated!
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
....It does seem that this issue may be quite unique and I have my doubts many/any has experienced this issue and it doesn't seem that many people can offer much more...:crying::crying::crying:

So, I implore you to help in this regard...I am debating whether to bring this back/up to Ubreakifix or to try and run the new IMEI on Google Pixel Support -- but I am hesitant to to this as they've screwed me before with a device bought from Swappa, that was bootloader unlocked and rooted, but exchanged the device with a refurbished locked bootloader instead! -- and try an RMA...? What do you think or would you do?
[Google Pixel 2 XL Questions & Answers] jd1639:
I'm grasping at straws here but:

I did use verzions web site and your number and it came up. PIXEL 2 NON-VZW so that's encouraging. But it didn't show as XL which is interesting, or not, idk. I don't know if the motherboard is the same in the XL and non-xl?

You said you used different USB ports, but did you also try different cables?

Humor me and double check the fastboot version. When I got my pixel 3 I updated the sdk tools, or so i thought, and it took me awhile to realize that they didn't overwrite the old fastboot and adb. I doubt that's your case since you've been using them for awhile.

I wouldn't start with Google on the issue but it would be worth a discussion with Ubreak. I don't know how much they get involved with unlocking pixel devices but what they sold you should be able to be unlocked.

I'm feeling your pain and will continue to ponder this.
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
OMG I am extremely thankful! I can't thank you enough for even this much!

Yeah....this is a walleye and not a taimen (Pixel-2-XL), that's why it wouldn't show XL -- as previously mentioned, I see more experts around the XL parts as well as this forum is where I'm most familiar with & better chance at being known prior -- but I didn't think of checking the Verizon website so that was a great idea! I am hopeful at so many of the signs -- which makes it all the more frustrating that most of the signs point to it supposedly being able to work, but doesn't -- like the website confirmation, or fastboot confirmation, or having the freaking OEM unlocking not grey blue ticker! Why?!?!?!:silly::confused:

I will humor any and all; "fastboot version 28.0.1-4986621

I only have 2 USB-C to USB-A cords, and have tried/used both, as well as changing USB ports (two 3.0's and one 2.0) with no success. Before this whole thing, they've worked 100% and never had them not work before so...their track record is good but isn't working here... :-\

Thank you again so much [MENTION=4858937]jd1639[/MENTION]! I am also grasping at straws rather desperately, so I appreciate the continued pondering and am open to anything/everything... Just let me know what else to try or info to offer/give...

[MENTION=3730810]Badger50[/MENTION], [MENTION=4670411]Az Biker[/MENTION], I make a desperate plea for you!

I'd like to thank you all in advanced, if anything...
[Google Pixel 2 XL Questions & Answers] Az Biker:
I'm out in town right now, I'll read some back story on your situation when I get home.
[Google Pixel 2 XL Questions & Answers] jd1639:
I should have caught " walleye" in your fastboot print out. I just assumed it was an XL.
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Thank you...I appreciate just the reply...so no worries while you're out or anything...but I can guarantee you that it is a really peculiar unique case...

Yeah....sorry about that....
[Google Pixel 2 XL Questions & Answers] jd1639:
I found this which might be of interest

https://www.reddit.com/r/Android/comments/9xcdle/psa_rma_refurbished_pixel_2s_can_not_be/

https://xdaforums.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763

https://productforums.google.com/fo...searchin/phone-by-google/Bootloader|sort:date
[Google Pixel 2 XL Questions & Answers] Az Biker:
I didn't see anything mentioned about trying Deuce's Toolkit, thread here, it has auto bootloader unlock and a bunch of other useful tools (I have never used it, but can't recall anything bad being said about it, and do remember a lot of devices that were saved by using it)...

I can't say that after reading this thread, I have any idea that hasn't already been brought up except making sure you are intending to use either a OTA or a factory image, and the file names looks similar unless they're side by side and the pages look pretty much the same, and I once downloaded the OTA and almost flashed it thinking it was the latest factory image (not sure what that would've done if anything other than error out).

Sorry I can't be of more help. I am familiar with the routine stuff, but you're out inn deep water that needs someone with much more knowledge than I have.

Best of luck man!
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Thank you for this...and especially & particularly for you continuing on and searching to find all of these...it's not much but you have my utmost gratitude...

Those URLs do give some good speculation as to what may be going on, but unfortunately doesn't offer much in the way of what one might try or can be done....

Thanks for taking a look Az Biker...you truly are a great one! It's why you are legendary 'round these parts...

Basically, Deuce's is a greatly modified version of the flash-all.bat script and manually runs fastboot commands individually flashing each image file to each slot specifically. And, unfortunately, there's no running flash-alls, OTAs, factory images, or the images for Deuce's script because the bootloader is still locked. As I said, this seems to be a very unique and particular issue. But, for what it's worth, it is something to be considered and I am truly and very grateful.

Here's a bit of an update: I was able to talk to Ubreakifix, and they are willing to take a look and see what they can figure out, if anything. So, tomorrow, I'll bring it over to them and we'll see... They did double check the IMEI and even the motherboard part serial # (i assume) and made sure that it wasn't a specific one to a Verizon variant and/or that it wouldn't have a "bootloader lock" on it...**~shrug~**

So....I guess we'll see...but if things don't work out...i'm hoping to bring it up to Google support for an RMA...but I swear they better not screw me again and give me one with a locked bootloader -- I bought on Swappa, phone broke before I could get the IMEI, Google gave me wrong replacement, but since I didn't have the IMEI and couldn't prove what variant it was, had no choice/"leg to stand on". **~sigh~** ...So much uncertainty while I CAN see the blue ticker...!
[Google Pixel 2 XL Questions & Answers] Az Biker:
When I mentioned Deuces Script, I was thinking primarily of the bootloader unlock function, maybe worth a try depending on what ubrkifix ends up doing...

Fingers crossed!
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Thanks Az Biker!

So, a little update: after further reading the links jd1639 gave, I'm finding that this seems to be a rather prominent Pixel 2 walleye issue. It seems that any refurbished and replaced Pixel 2 walleye's comes with this issue.

Also, I've found some more interesting "flags" that point that it should be able to unlock; when running command "adb shell getprop ro.boot.cid", it results in 00000000 (which seems to be the case in all the refurbished replacements that are having this issue) as well as running the command "fastboot oem device-info" and it shows the very peculiar results of "Device unlocked: false" but "Device critical unlocked: true"?!?!

What seems most depressing and hopeless is that if nothing can be done in Ubreakifix, I can look forward to RMA'ing with Google (soooo much back and forth shipping) to up to 5 replacements and then begging for a factory new replacement...:crying::crying::crying:
[Google Pixel 2 XL Questions & Answers] crixley:
you'll keep getting ones that cannot be unlocked. I went through 4 before finally giving up.
[Google Pixel 2 XL Questions & Answers] jd1639:
That's very discouraging!