yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
[MENTION=4521871]kooocko[/MENTION]: The IMEI would be the most definitive method. However, according to an identical question on Reddit, the serial number label on the box itself should be slightly different. While the Reddit thread is in regards to the first generation Pixels, it's unlikely that Google would have done anything radically different with the labels. Thus, it's a fairly safe bet that all of the devices will have an IMEI and ESIM ID on the box. Verizon variants should also have a SIM ID on the box in addition to the IMEI and ESIM IDs.

EDIT: Confirmed. This image shows the Pixel 2 XL label for a Verizon device. Comparing it with the label for my unlocked P2XL reveals the following differences.

There are five barcodes on a Verizon label (including the UPC), all on the left side of the label. Presumably the fifth barcode is the aforementioned Verizon SIM ID. On an unlocked device, there are only four barcodes, and three of the four barcodes are at the bottom of the label, with the UPC being positioned above them.

To make room for the fifth barcode, the Verizon label removes the Canada import information found in the upper left of the unlocked device label.

I cannot determine this with any certainty since the box is positioned in such a fashion that the IMEI isn't visible, but it appears that French translations present on the unlocked device label have been removed from the Verizon label. If one of our members with a Verizon device could provide a good scan of the label with the IMEI and SIM numbers blacked out then that will help.

The OP merely need ask the vendor whether there is a SIM ID present on the box. If one is present, then the device is a Verizon model.
[Google Pixel 2 XL Questions & Answers] xunholyx:
[MENTION=2461175]mkhader[/MENTION]

The Verizon model will have 5 stickers instead of 4 is correct (SIM ID added).

The sticker on the phone's box for "SKU" (which is model#) should also be different.

Verizon will say GA00151-US.

My P2XL bought through Telus says GA00125-US, which I believe might be the same as the one bought unlocked through Google, though I'm not sure about that (I don't think I am after further research)

EDIT: The model # for Verizon listed above is for the black version. The black and white version is GA00152-US
[Google Pixel 2 XL Questions & Answers] mkhader:
Thank you so much for the very useful info that you all provided. :D

I will ask the seller directly about the box , and check if there is a SIM ID sticker or not. If it contains it, then it is a Verizon variant.
[Google Pixel 2 XL Questions & Answers] hatdrc:
My wife's 64gb black model from Google does say GA00125-US. My 128 gb black model from Google says GA00137-US
[Google Pixel 2 XL Questions & Answers] xunholyx:
So the model number is actually the same with the phone from Google and the phone from Telus after all.

Thanks for the information
[Google Pixel 2 XL Questions & Answers] Il_Spector:
Is your wife's phone an XL or standard size? I'm trying to compile a list of model numbers for Pixel 2 and 3 (both standard and XL). Info on the Verizon variants of Pixel 2 and 3 are complete, as is the Google variant of Pixel 3. There is a lot of conflicting information out there for the google variants of Pixel 2, especially GA-00125-US.
[Google Pixel 2 XL Questions & Answers] md303:
Having a list of SKUs/variants is a good idea!

I was just about to buy a GA00151-US, but despite being carrier-unlocked, that is a Verizon model with permalocked bootloader. This thread saved me $300+
[Google Pixel 2 XL Questions & Answers] Il_Spector:
"Permalocked"? Have you heard of DePixel8?
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
DePixel8 doesn't work on a P2XL. If it did, there would be no threads asking to unlock the Verizon model.
[Google Pixel 2 XL Questions & Answers] Il_Spector:
My bad. Guess I got lucky then.

Anyway here are the Verizon Variants and SKU information for Pixel 2 and Pixel 2 XL

GA00139-US Pixel 2 64GB Black

GA00140-US Pixel 2 64GB White

GA00141-US Pixel 2 64GB Blue

GA00142-US Pixel 2 128GB Black

GA00143-US Pixel 2 128GB White

GA00144-US Pixel 2 128GB Blue

GA00151-US Pixel 2 XL 64GB Black

GA00152-US Pixel 2 XL 64GB Panda

GA00153-US Pixel 2 XL 128GB Black

GA00154-US Pixel 2 XL 128GB Panda

There is another SKU, GA00155-US, which appears to have been used indiscriminately. I have seen it used on a number of variations (standard and XL, 64 and 128GB) and it is unclear to me at this point if it was used for verizon models or not. I can tell you that I have only seen it on labels with the barcodes on the bottom of the label, as opposed to the left side, without the SIM ID. (Earler in this thread someone noted that the verizon variants had the barcodes on the left side of the label with an added SIM ID barcode, and the google store variants had the barcodes on the bottom.) My guess at this point is that this SKU was used "incorrectly" early in production before eventually limiting its use to a single google variant, the Pixel 2 64GB Black. I say this because these labels appear to have non-universal text (XL, 5" or 6", 64GB or 128GB, A or C - the last character in the model #) printed on the box by the barcode label printer. The text is very dark and would have allowed them to use the same label blank for all variants. Eventually they created a different label blank for each variant as the text is as light as the rest of the universal text.

It should also be noted that the SKU number can also be found on the bottom of the box. Here it appears without any of the unique identifiers like IMEI or ESIM. This becomes useful when trying to elicit information from sellers. The number of sellers on ebay that are both ignorant AND paranoid is astounding. When you add in the liars and control freaks, getting reliable information is exasperating, to say the least. And I'm not just referring to the Tom, ****, and Harry's selling their personal devices, sellers specializing in new and used smartphones suck as well. You will have a better success rate if you ask for the SKU number from the bottom of the box, and avoid mentioning the SKU on the barcode label. And if you don't know already, never search on ebay using the SKU. Ebay's library of pre-populated item specifics is riddled with errors, and there is no way to exclude that from your search. Unless the seller is savvy enough to put the SKU in the title of their listing, you won't find it that way.

When I get more reliable google store variant SKU's, I will publish them here.
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
There was one month where the bootloader could be exploited to unlock the Verizon P2XL, and there are scattered reports of some people being able to unlock their devices outside of that time frame. The general consensus however is that those are exceptions and not the rule, as the multiple threads asking about bootloader unlocks for Verizon models indicate. This is all just a fancy way of saying that you did indeed get lucky.
[Google Pixel 2 XL Questions & Answers] Il_Spector:
Google Store Variant List

Pixel 2 64GB

GA00155-US Black**

GA00126-US White

GA00127-US Blue

Pixel 2 128GB

GA00128-US Black

GA00129-US White

GA00130-US Blue

Pixel 2 XL 64GB

GA00125-US Black

GA00136-US Panda

Pixel 2 XL 128GB

GA00137-US Black

GA00138-US Panda

As you can see there is a pattern to how these numbers are assigned with a couple exceptions: Pixel 2 64GB and Pixel 2 XL 64GB. The XL has the SKU you would expect its smaller sibling to have.

**As noted previously, the SKU GA00155-US can be found on other variants other than the Pixel 2 64GB. This most likely happened early in production. I cannot say whether or not it was used for both Verizon and Google Store variants during this period.

I saw some vastly different labels while studying this. The warranty replacement labels follow a different pattern altogether. I saw one "SKU" that was a hybrid of the Pixel 2 and Original Pixel model numbers. Definitely did not get a warm fuzzy with that one. Some of these are probably remanufactured by someone other than Google/HTC/LG, as the box always seems to be sealed.
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
Any model NOT sold by Verizon.
[Google Pixel 2 XL Questions & Answers] GROOVYJOSHCLARK:
This was very helpful, thank you! I am stuck with an incorrectly branded Pixel 3 XL thats NOT Google, but the piece of garbage Verizon branded (brand new mind you) so I am looking to just move on and buy a new Pixel 2 XL (there is so little differences between hardware - my currently owned Pixel 3 XL and the older Pixel 2 XL) that I dont care enough to worry about the differences with the little hardware changes. The locked BL on my Pixel 3 XL is worth it enough or me to downgrade to Pixel 2 XL. This post helped me NOT make the same bullspit mistake and land with another Verizon piece of of spit model!
[General Questions and Answers] Mpegger:
I've been searching for something that works like SyncToys (Windows PC) but for syncing Android directories to PC. I used to use Cheetah Sync, but it doesn't appear to be updated any longer and has a limited number of directories that it will support. I basically just want to keep the SDcard partition synced to my PC as a backup. Manually copying works of course, but I want to save time (lots) by having a sync software update with only the changes made on the device, instead of copying everything all the time. Any recommendations?
[LG G5 Questions & Answers] CbIP:
Hello!

On my LH G5 H850 I have unlocked the bootloader, installed TWRP (without dm-verity patch) and installed the Magisk interface. All this stuff caused no problems.

But when I try to install systemless Xposed framework, I get bootloop everytime. I have already tried to follow the manual in the Xposed module thread (https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268) and also tried just to install "Xposed Framework" which promises to do all the work automatically.

I would appreciate any advice how to fix the bootloops and install Xposed properly.

P.S. I currently use V20v stock firmware.
[Moto X4 Guides, News, & Discussion] munchy_cool:
How to Remove Unlocked Bootloader Warning on Moto X4
​

Shoutout/Credits to xda member [MENTION=7452143]AvenidaDelGato[/MENTION] for the modified logo bin file.

​

Text Guide.

Make sure adb and fastboot are setup and working.

Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.

Navigate to adb/fastboot folder

Windows

adb devices

adb reboot bootloader

fastboot devices

fastboot flash logo_a logo3.bin

fastboot flash logo_b logo3.bin

fastboot reboot

Mac/Linux

./adb devices

./adb reboot bootloader

./fastboot devices

./fastboot flash logo_a logo3.bin

./fastboot flash logo_b logo3.bin

./fastboot reboot

Downloads

Modified Logo.bin zip file - https://xdaforums.com/showpost.php?p=77013516&postcount=4

Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU

ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/

Motorola Drivers - https://support.motorola.com/us/en/drivers
[Moto X4 Guides, News, & Discussion] kofruge:
Thanks, that worked to remove the bootloader unlocked warning screen!

One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).

If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
[Moto X4 Guides, News, & Discussion] munchy_cool:
I think verity is set to logging is not part of the logo. It's a text message which is coming up for a reason i do not know.
[Moto X4 Guides, News, & Discussion] nykola5:
Be careful with this method, when you receive updates via OTA, you will not be able to update them since they will get an error ...
[Moto X4 Guides, News, & Discussion] kofruge:
Oh yeah, didn't think of that... Any way to fix OTA installation after flashing this?
[Moto X4 Guides, News, & Discussion] wanb1i:
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too? ;)
[Moto X4 Guides, News, & Discussion] MeowDotEXE:
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
[Moto X4 Guides, News, & Discussion] abrfilho:
https://xdaforums.com/moto-x4/themes/bootlogo-custom-bootlogos-dark-variant-t3832118
[Moto X4 Guides, News, & Discussion] vidra:
is there a way to restore the old logo?
[Moto X4 Guides, News, & Discussion] jhedfors:
Just fastboot flash the boot logo file part of the factory firmware.

https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
[Moto X4 Guides, News, & Discussion] HACK3DANDR0ID:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
[Moto X4 Guides, News, & Discussion] jhedfors:
No need to quote the OP.
[Moto X4 Guides, News, & Discussion] munchy_cool:
i dont make bootlogos

download android one firmware, and flash logo.bin from there
[Moto X4 Guides, News, & Discussion] HACK3DANDR0ID:
Found what i was looking for thanks
[Moto X4 Guides, News, & Discussion] gleenfield97:
Flash the attached modified bootloader (unzip first).

fastboot flash bootloader no-verity-warning-bootloader.img

Found it from a telegram channel. Tested it myself.

Credit [MENTION=8834019]abrfilho[/MENTION]

SHA256SUMs:
b2efd37d2bef4e2de5bcbd7ca3e643a1e1e246d597e6ed4389679d321bebd2f0 no-verity-warning-bootloader.img
fcf3391a13f757d3f998c9b14c5ef40e6084d65b2d0162273d3842e75f972281 no-verity-warning-bootloader.zip
[Moto X4 Guides, News, & Discussion] infodude:
It worked for me, thank you heaps!
[Moto X4 Guides, News, & Discussion] jhedfors:
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
[Moto X4 Guides, News, & Discussion] gleenfield97:
Maybe it's not compatible with stock. I'm using Havoc.
[Moto X4 Guides, News, & Discussion] blueberry.sky:
The AndroidOne logo.bin if anyone else needs it.

Extracted from stock XT1900-1_PAYTON_FI_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.

Md5: e306b8ea948a10ec304ca62ebcd60495
[Moto X4 Guides, News, & Discussion] BigwaveMx:
Just a warning: after flash the bootlogo file, it seems this change prevent OTA updates. Some hours ago, i receive the 2019 july security patch update and it fails at 90-95 percent. I make a factory reset and it didn't help. Then I flashed the stock rom and the update install very well.
[Moto X4 Guides, News, & Discussion] chriswilliamdavis:
custom bootloader screen

I created the a custom bootloader image to replace the unlocked bootloader warning. Hope you like it. Just unzip the attached file and follow the directions but replace logo3.bin with logof.bin.
[Moto E4 Questions & Answers] OusaifShaka:
Give me firmware for flash with QFIL for XT1766
[Security Discussion] XAM999:
by sophisticated government attack i mean something with virtualization technologies, several masking and hiding capabilities like FinFishers solutions.

Does:

Updating to the newest version of ios

hard reset the phone

securely remove the spyware?

1) i see more as a bonus question that is not really needed, but might be interesting too.

I would thank you for a careful but practical answer, since this question relates to some "moving parts" like: "Is it possible to load a "real" update from an infected phone, or will a sophisticated attack redirect those requests" and if there is something you can do to prevent this etc. or the question whether a hard reset really deletes everything or if the spyware can somewhat hide in "blocked" or wrongly addressed areas of the storage and so on.

On the other hand i do know that there never is absolute certainty and would be more interested in a "probabilistic view".

Thanks to the Forum!
[Security Discussion] david68429:
I think your question is pointing to widespread security problems with most technology. Manufacturers often use closed source software and the same goes for most of the hardware devices. This makes security very difficult and of course these weaknesses are now being exploited by state sponsors.

Stuxnet was a good example and well worth reading about.

https://en.m.wikipedia.org/wiki/Stuxnet

http://itmanager.blogs.com/notes/20...e-protected-the-iranians-against-stuxnet.html

It infects microcontroller chips that do memory management. The introduced code returns modified data, maybe not even on each read.

So if the phone internal memory uses these microcontroller chips then even loading a new rom wouldn't help. You have to be able to have access to the microcontroller firmware and introduce your own access certification. It is very difficult to do this at present as most of the hardware information is not available, both for phone and internal chips.

Unfortunately this means that state sponsors can take the devices apart, inspect chips with an electron microscope, thus obtain a lot of secret information for their hacks.

Having had stuxnet on a laptop I became interested in these problems.

Contaminated updates again depend on the resources available. These rely on https and code signing.

https://arstechnica.com/information...ate-authorities-conspire-to-spy-on-ssl-users/

http://www.crypto-it.net/eng/theory/software-signing.html

A contaminated update requires access to the certificates and a delivery method such as intercepting a request from a known ip address.

Many states have access to the certificates and the means to target downloads. Using tor for updating might give some protection, as would a system to compare your download with that obtained by other people. We don't have this working automatically yet as far as I know.

https://www.torproject.org/docs/verifying-signatures.html.en

Phones have a second operating system where code may not be secure.

http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone

https://www.rsaconference.com/event...ile-apt-how-rogue-base-stations-can-root-your

You can minimize risk by keeping a device in airplane mode and using a separate mifi device.

If you consider yourself an innocent target or just want to minimise risk then perhaps regularly buy second hand or new devices from shops, keep them in airplane mode, keep the necessary software to send by bluetooth and check the md5 sums.

Web browsers could be another security problem if they can run exploits, but this is probably outside the scope of your question.

Secure communications apps will probably work fine as long as they don't require updates. Beyond that, keep it all locked up in a safe you built yourself. :)
[Android Software/Hacking General [Developers Only]] zh_eco:
FOR ALL CYANOGENMOD ROMS !​

Note : I didn't made this fix ,it belongs to developers who worked so hard to fix

a major ROM-killer bug . I'm sharing a fix that was made after long discussions between developers

it's a very popular problem so that's why I want to help everybody​

WHY Hotfix ?​

this fix resolve apps installing issue as when you want to install any app for example Temp Mail from the play store

after completing installation your Launcher will crash and the whole OS will get destroyed completely

what makes the phone stuck in a bootloop and probably you will not be able to do anythink because

every time you want to install an app the same problem remain and again everything will crash​

Hotfix info.​

it will replace the file which cause the problem (libandroidfw.so)

from /system/lib

it's just as simple as that ! magic ! can't be easier !​

Installation​

just download the zip file for your ROM (cm12.1 or cm13)

and flash it just after flashing gapps​

Downloads​

for CM12/12.1 users :​

OneDrive​

Google Drive​

for CM13 users :​

OneDrive​

Google Drive​

HUGE Thanks to​

[MENTION=241111]olaf[/MENTION] Titz
[MENTION=8690636]MariferC[/MENTION]
[MENTION=7744723]lescht[/MENTION]
[MENTION=6882175]Danilo-Sanchez[/MENTION]
[MENTION=243864]xda[/MENTION]​

Sources​

https://jira.lineageos.org/browse/BUGBASH-1052

https://issuetracker.google.com/issues/64434571

https://git.replicant.us/replicant/.../?id=953d2a3493aaceb3209afc7eef1ff1e7f7242908

Google

xda forums
​
[Android Software/Hacking General [Developers Only]] ayef999:
this backup file, atu install regular friend? this is directly the same Gappsnya
[Android Software/Hacking General [Developers Only]] zh_eco:
I can't understand your english

this is not a backup

it's a fix to a major issue

please read
[Android Software/Hacking General [Developers Only]] ayef999:
I mean this can be directly installed by using twrp, this is a backup file or a zip file
[Android Software/Hacking General [Developers Only]] zh_eco:
oh dear

of course you can flash it through any recovery

it's not a ROM or anything like it ! it's a system file (lib) and flashing the zip will replace the existing one on the ROM to resolve a problem .
[Android Software/Hacking General [Developers Only]] MattEffinTurner:
Looking for this patch

The download links don't seem to be working, wondering if you still have the files (or know where I can find them)?

I've found a kind of tutorial, but I'm not well equipped to decompile and recompile the libandroidfw.so to fix this on my own (and the rest of the fixes I've found were ROM specific)

Thanks!
[Android Software/Hacking General [Developers Only]] zh_eco:
download links are working perfectly

its just OneDrive that is a bit slow so you have to wait a bit . you can try different browsers . I added Google Drive links

if you want the original files checkout the sources (at the bottom).

HOWEVER , maybe on the files (Zip's) won't work ! you might get an error in twrp ! if that happened then you can just copy the file libandroidfw.so from the zip file and copy it to /system/lib

cheers :svetius:
[Android Software/Hacking General [Developers Only]] ssurell:
Bad flash

Won't get past bootloader on CM12.1 after flashing. So switched to the original backup copy I made, and boots normally. So this is not a universal patch. You have to modify the libandroidfw.so file built for the ROM as described in this post:

https://xdaforums.com/showpost.php?p=77526220&postcount=13
[Android Software/Hacking General [Developers Only]] Shashank Bhanu:
Will this file can be flashed in any device???