yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Morgrain:
I wish you luck. It's high time that people managed to get some freedom - these locked bootloaders are a pest, and it's not even properly communicated. We had so many Verizon customers here on XDA over the years that were surprised by this situation and wouldn't have bought a Verizon phone, if they would have known of the locked bootloader.
[Google Pixel 6 Pro] HipKat:
Yeah, good luck. I have to tell you, I've seen people make these same type of posts on here for years, ever since the Nexus 6, which was the last great phone for Mod'g that I owned. Still haven't seen anyone make it happen though
[Google Pixel 6 Pro] HipKat:
I still always go back to the AZ Supreme Court decision that the end-user is ultimately responsible for a device that they own and voiding the warranty is their choice. Unfortunately, since Search Engines have become almost unusable anymore, I can't find the actual ruling
[Google Pixel 6 Pro] Lughnasadh:
However, under the Magnuson-Moss Act of 1975, manufacturers likely cannot void your hardware warranty for modifying the software (e.g. unlocking the bootloader) unless they can prove that the modifications led directly to the hardware malfunction.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Me too - I didn't realize about Verizon's practice until I was on my second Verizon Android phone, the VS985 LG G3, and VK810 LG 8.3 tablet. It certainly explained things about why I had to root my HTC Droid Eris (and LG devices) the ways I had to - of course with the Eris, that was still relatively early days of Android. Developers had so much success working around the limitations for several years, that I was an oblivious user.
[Google Pixel 6 Pro] V0latyle:
Yes...But also no.

You'll find that many manufacturers of many different products will not honor warranty if any modifications have been done. I've had to replace 3 water pumps and 2 engine speed sensors on my VW GTI, and I paid out of pocket every time. I have a cold air intake, a tune, and a turbo-back exhaust, but the engine is otherwise stock, and there is no possible way any of my modifications could possibly cause those failures.

Sure, you could potentially take them to court, but they have much more money, and attorneys on permanent retainer who will happily waste your time, so you'd most likely run out of money before your case got anywhere useful.

One guy I know had his warranty denied for a sunroof malfunction simply because he had a lowered suspension.

So in essence, even though the law may be on your side, and you would think the burden of proof would be on the manufacturer to prove that your modifications caused the failure, you'll often find that it's the other way around - you have to prove that your modifications didn't cause the failure. We are more or less at the OEM's mercy. Google has typically been pretty good about not voiding warranties on bootloader unlocked devices; I don't believe Samsung is quite as generous.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's the sad truth, but I believe you are fully correct. Thanks for reminding me! 😜😂 Now I can start my weekend angry and depressed. LOL!
[Google Pixel 6 Pro] Lughnasadh:
In the area of cell phones, the burden of proof lies with the manufacturer to prove that the software modification did indeed directly cause the hardware malfunction.

As another example, when using aftermarket car parts, the burden of proof is again on the manufacturer to prove that the aftermarket parts contributed to the failure.

It is illegal to not honor warranties in cases like this.

On what party the burden of proof lies depends on a number of factors, including the type of case, jurisdiction, the laws involved (including Federal Rules), if affirmative defenses are pleaded, the type of warranty, etc... But in the scenario I was specifically referring to, the burden of proof does indeed lie with the manufacturer.

And let's remember, just because a manufacturer will not honor a warranty or says that your warranty is void does not necessarily mean that it is. Companies say things all the time to try to dissuade people from suing. For example, you go into a valet parking lot and there is a sign that says "Not responsible for stolen items or damage to car.". Well, they can say this but that doesn't make it true. In a bailment situation such as this they have a duty to take reasonable steps to care for your car. And if they don't and items are stolen from your car or your car is damaged, they are indeed responsible, regardless of what they say or what signs they have up.

But you are correct in that the average person may not have the resources to actually go to court against a big company. But the point of my original comment was not whether it was feasible to take legal action, but rather that it is illegal to deny a warranty based on the scenario described (i.e. unlocking the bootloader).
[Google Pixel 6 Pro] V0latyle:
Way ahead of you, I started my Friday by getting my tax information together. Once again, maximum withholding resulted in somehow underpaying our taxes.

It doesn't matter what industry we are talking about - from a legal perspective, the burden of proof indeed lies with the manufacturer to prove that any modification caused the failure.

Yes - but do you have the time and money to fight a multi-billion dollar corporation in court? The case would likely take years, and you'd run out of money LONG before they do. In the end it would have just been cheaper for them to repair your device, but when they simply say "no", they're counting on you not having the time, energy, and resources to actually take them to court over it.

Exactly. Like I said, they have an army of attorneys dedicated to this particular purpose, who will do everything in their legal power to make your life hell. They know that you'd probably win a judgement, so they'll do everything they can to prevent you from getting there. Death by a thousand cuts, as they say.
[Google Pixel 6 Pro] Lughnasadh:
Not necessarily. Depends on if it falls under the Magnuson-Moss Warranty Act. Or if it falls under any other federal law where Federal Rules would apply. Or if the FTC has granted the manufacturer or seller a waiver. And if state law applies, depends on the state.

And it depends on the type of warranty and for what purposes the product is sold. The Magnuson-Moss Warranty Act does not cover oral warranties or products sold for resale or commercial purposes.

There are almost always exceptions to the general rules. That's why in law school there is often as much emphasis put on the exceptions to the rules as there are to the rules themselves.

But again, my point was not whether it would be feasible, but only if it was legal to void the warranty when unlocking the bootloader. And if indeed the case falls under the Magnuson-Moss Warranty Act of 1975, there is a fee shifting provision in there that requires the manufacturer to pay for reasonable attorneys' fees if they lose.
[Google Pixel 6 Pro] V0latyle:
It's not that simple. If it was, unlocking Verizon variant bootloaders would be easy.
[Google Pixel 6 Pro] bobby janow:
Why are we doing this dance yet again? It's pointless and counterproductive.
[Google Pixel 6 Pro] andybones:
Thank you.

This same exact thread happened in the Pixel 5 forum.

He won't provide proof.

And he doesn't have to... It's that simple.

Just ignore, please.
[Google Pixel 6 Pro] FernBch:
What the actual...........????

data/local/tmp is locked (permission denied)?

How am I supposed to run stuff locally????
[Google Pixel 6 Pro] FernBch:
Ok, have tmp access. I'm sure things I created for the P3XL are useless, so I'll need to start fresh.

No promises, no ETA's, no updates unless I have progress or success.

Here I go.....
[Google Pixel 6 Pro] Fuse8499:
Well looks like im sending it back. I need Nethunter. My own fault
[Google Pixel 6 Pro] Doug8796:
Verizon Pixel 6 Pro Bootloader fix: Sell Verizon Pixel 6 Pro, buy any other version (possibly need to sim unlock) and boom. There is a reason the verizon versions of the phones on swappa are so much cheaper
[Google Pixel 6 Pro] bobby janow:
If you take a look they are not cheaper at all. They should be but they are not. Most people don't care about bootloader unlock outside of XDA.
[Google Pixel 6 Pro] FernBch:
Very True. I just try for the hell of it. Out of all The Big Red devices I've had over the years I have only been unable to unlock one. This might be number two, and it might not. Only time will tell.
[Google Pixel 6 Pro] Doug8796:
unfortunately with a lot of phones bootloader locked, it makes a lot of customization limited all around for android. Did a google trends on xda and it peaked around 2011.
[Google Pixel 6 Pro] BrainStormCEO:
Turn off your Google Pixel phone

Insert a sim card from a new carrier (different from the original carrier).

Turn on the phone.

Unlock the screen by sliding across the screen or by entering your screen PIN number.

The phone will prompt automatically for a SIM NETWORK UNLOCK PIN

Enter the Network unlock code (also called NCK)

Your phone is now fully unlocked!

8. Go to settings and unlock the bootloader.
[Google Pixel 6 Pro] Morgrain:
Pretty sure that your "guide" will only unlock the sim (working with other networks), not the bootloader. But since I don't have a Verizon issued Pixel 6 Pro, I can't check. I guess we'll find out once either someone here tells us of their success, or not.
[Google Pixel 6 Pro] andybones:
That simple, eh?

I don't own a P6 but I'm sure if this method works you just made a lot of people happy. And I don't forsee anyone coming to patch this work-around.. but what do I know?

Would love to see some pictures.

I'm certainly no developer, either. Just a tinkerer.

But developers don't hack bootloaders, so your first comment confuses me. Are you saying the developers on xda are good, or no good?

True hacking was done primarily on hTc (Verizon) devices.. and was done mainly by those involved in security research.

I tested for some of these groups..

It was a different time though. People complained about a $25 bootloader unlock. And it often involved the physical device needing to be sent to said unlocked. All in all about $50.

Either way, appreciate the share. Cant blame me for my post though. You've been teasing this unlock for awhile. But that's also your freedom to do.

I'm here to meditate though, after all.
[Google Pixel 6 Pro] Zach Alt:
He goes about in these threads implying that sim unlocks are bootloader unlocks. He is a very confused individual.
[Google Pixel 6 Pro] andybones:
Oh, trust you me.. I do agree.

I'll leave this and this.

He also questioned about a Pixel 5 bounty thread. Offering 100k for a Pixel 5 BOOTLOADER unlock.

It costs $$ testing true unlock methods. Bricking $1,000 Pixels isn't cheap.
[Google Pixel 6 Pro] FernBch:
That is the true definition of a troll. That method has been proven not to work so many times. It isn't funny.
[Google Pixel 6 Pro] LLStarks:
I haven't seen a phone that asks for a code in years. All carrier side now.
[Google Pixel 6 Pro] FernBch:
The devs here at XDA are good, IMHO.

As for the BL side of it, if I understand correctly, isn't directly through the SIM but close. For the P3XL anyway. I heard enough hints to get an idea but not enough to take it farther.

If I'm offering up a tease I apologize, that's not my intention. I dug and read through so many lines of code that I got a good idea on how the toggle was either allowed or denied. The hat trick I didn't figure out was how to be able to change it because of how it was set and where it is stored.

I'm just hardheaded like that. Maybe I can crash this one, too.....

Anywho, gives me something to mess with.....
[Google Pixel 6 Pro] FernBch:
Oddball Question. Where is a good source for MMI codes? Of course Google isn't. Some of the codes give me an invalid code or network error....
[Google Pixel 6 Pro] andybones:
XDA is still a wonderful community with amazing Devs. Times have changed, yes. but that's life. You change with it! Magisk for exampe..

and certainly not a tease, you aren't giving us false hopes and saying you can do it, and calling those who can't "amatuers". I respect the grind bro. keep at it!

I had one of these XTC clips that was the same as seen here.

It was one of the first gen clips and was sent to me for free 1 of 10 people IIRC, as part of a trial from the creater, before XTC clips blew up. it came with 10 S-OFF unlocks, and a friend from the Sunshine team made it unlimited for me.. i actually still have it lol.

It did everything from S-OFF, to IMEI changing to SIM unlocks and more.

It went into the SD-Card with the flex cable then to the PC using their software that was on an SD-Card (Java card) in the clip.

They went for around $100-$200 (still are), and a friend during my htc M9 and htc 10 days bought one and we were sending our devices to him to S-OFF. (Security Off).

HTC devices could be bootloader unloceked which allowed root, but S-OFF allowed full unlocking, and allowed things like flashing of other firmwares. So it was a way for htc to give root without risking bricks. Verizon of coarse blocked this, so S-OFF was our only hopes, and the Sunshine team unlocked basically every htc verizon device I owned (possibly all and I've owned 10)

When I remotely tested unlock methods, I had a 1gb CRAP sd-card, and we found out that once I put my 32gb sd-card in it, it immediately was successful S-OFF (using their method), we couldn't figure out why my device wasn't getting unlocked, It required short circuiting the device at a certain point in the boot prcoess, which allowed it to input their work. Goes to show the amount of time and the risks involved in finding these exploits.

Some devices that still have sd-card share it with the sim slot, so that is interesting to me.
[Google Pixel 6 Pro] FernBch:
I remember every one of those things. My first foray into Android was the Moto DroidX and I just took off from there. I wasn't real deep into code until lately. I was always good at bug finding and/or workarounds. When I had my SGS4 I became a little more interested in the dev side. #JDCDevelopmentTeam even asked me to join with them. I rocked that device for a while. I think it made it to Android 8 then it had a hardware failure. After that it was the P3XL on Big Red, bricked that one. Then a 1+ 8Pro, it was Ok. Now it's the P6Pro. Not sure about this one. So many bugs, it's like 12L needed to bake more before release....
[Google Pixel 6 Pro] andybones:
I'd love to learn code further. When I was deving (the sg3 and she were my only Samsung devices and I loved them! Esp the sg4) it was all just basically reverse engineering to see how things were done. It was fun for me.

I stayed on the hTc 10 far too long, from its release day until pixel 5 release day. Really wish I grabbed a Pixel 3 or 4. I went from Android 7.1.2 to 11. I am very happy on my P5 with A11 crDroid. I find 12 exactly the same, needs more time and I did my fair share of beta testing devices for hTc. I'm happy with the stability. A11 actually is really nice with all the apps getting updated and themed. My first Android was the Moto droid from Verizon that I returned for the Droid Eris. Verizon rep sold me on the Moto as the Eris was still on.. Android 2.1 iirc. That's when I found XDA and then it all began!
[Google Pixel 6 Pro] FernBch:
Verizon Moto DX + Loki = CyanogenMod!!
[Google Pixel 6 Pro] Az Biker:
Your insults directed at developers, and other members on Xda violate Forum Rules and are no longer welcome in the forums.

Please make sure you fully understand the following:

1) if you have a proven method to unlock the bootloader on VZW devices, open a thread, make yourself famous, and become the greatest Xda developer ever. If you can't or won't open your own thread and share your method, stop posting your self -righteous comments allover the forums.

2) if you post any further insults directed at Xda members, your account will be restricted. Xda is about sharing and developing, not smoke & mirrors and insulting other members who have actually produced tons of legit development.

No more warnings on this, check your PM.

Thanks for your cooperation.
[Google Pixel 6 Pro] HipKat:
That's probably about right. It was crazy back then on here. It was the age of discovery when most of the stuff we take for granted now was being developed by users, Android and the kernels were open source and amateur development was encouraged, not stifled and locked out. Many things that good devs came up with were adopted by Android in future releases, like Swipe on our keyboards, for example
[Google Pixel 6 Pro] HipKat:
Yup!!

lol
[Google Pixel 6 Pro] Zach Alt:
{Mod edit: Quoted post has been deleted! - Oswald Boelcke}

Your verizon pixel 6/pro is not bootloader unlocked. It might be sim unlocked, but that's easy and doesn't mean anything.
[Google Pixel 6 Pro] FernBch:
Not trying to start drama, but I tried that exact method on more than one device. Current one included. I was not able to unlock.....
[Google Pixel 6 Pro] andybones:
{Mod edit: Quoted post has been deleted! - Oswald Boelcke}

Any proof?

Screenshot?

Screen record?

I find it funny how you're always quick to post as soon as your buddy can't anymore. Just like in the Pixel 5, here you are in the Pixel 6. With posts that prove literally nothing.

"I find it funny that they deleted the only way to do it and acted like he was a troll. #HeWasRight"

And what are you taking about? Deleted what?

The big "hack" is still right here for ALL to see..

https://xdaforums.com/t/verizon-pixel-6-pro-bootloader-unlock.4356373/post-86377061
[Google Pixel 6 Pro] Alekos:
you won't find it because they're stuck in 2017 when the Pixel 2 had a small glitch that allowed a * few VZW devices to be unlocked. Google actually was so mad that when you now get a refurbished Pixel 2 (fully unlocked) it can't be bootloader unlocked. (I'm speculating but it's such a weird issue I've helped 8 Pixel 2 (non xl) users on Reddit and xda since last May trying to unlock bootloader on unlocked models.

Anyway that's old news. People want to believe and will troll away like we see here. nothing new to see here except the same old 1%'ers that spew nonsense, just like we see in the *real world.

can we just ban these users like BrainStormCEO for once and for all. I'll be the first to have civil and meaningful conversations about this. those comments weren't that.
[Google Pixel 6 Pro] Alekos:
{Mod edit: Quoted post has been deleted! - Oswald Boelcke}

edit--

You can have a carrier unlocked VZW device (is what we're seeing here). great. that won't help you with bootloader unlock on VZW models.

You can also have a T mobile or ATT device which can be bootloader unlocked, but before the bootloader can be unlocked, it has to be Carrier unlocked (and each Carrier has it's own terms, paid off, 60 days activation for example).
[Google Pixel 6 Pro] TheForceUnleashed:
I think the last VZ device I had that could be bootloader unlocked was the Droid Razr M back in 2013. And even that didn't have a complete bootloader unlock. It was a Bootstrap exploit that allowed custom ROMs to be run on top of the firmware.

This is such a weird thing to troll about. There's literally mountains of evidence and prior forever-locked devices before them on this, and the P6 is no different. If anything it's worse, there's next to 0 exploits to work with on these things now. Even iPhones have more exploits at this point.
[Google Pixel 6 Pro] Alekos:
Strictly speaking for the Pixel 3/4/5/6 series (latest devices), not having exploits shows that Google is taking security serious. Not sure if you meant worse as in it's worse for the trolls - the realization that vzw models can't be BL Unlocked, but better for 99% of users who want a secure phone. There are other phones that you can use if that's what you want (same model even!) - we have amazing amount of choice these days. I just think people want it so much because Verizon essentially gives a Pixel 6 or 6 Pro for free (with offers, trade-ins etc). Would I have loved to not have spent 1000$ on a phone that can be bootloader unlocked? Hell Yes.

I think the Nexus/Pixels are special and that's why I've always liked them and recommended them to family (prior to 6 series). They can be unlocked and modified, or not. What's better than choice? Talk about Freedom or whatever you want to call it.

Anyhow for someone here to refer to the "xda devs" as being "lower quality" or whatever, is truly ridiculous and shows how convoluted they are. I used to laugh at these people but now it's getting kind of sad - because you're right, the amount of evidence that supports this issue is truly mind boggling. Very bizarre. Kind of like the flat-earthers or q-anon type people. There will always be some fringe group that thinks they are right. It'll never change and with the internet, they have a "community" and a "voice".
[Google Pixel 6 Pro] andybones:
The htc m7 verizon was able to unlock the bootloader through htcs website. that was patches SO fast. I bought the phone on release day and ran home to try it. A few of us got in. but then verizon must have contacted htc because it was blocked on the site, not through a patch,, or every new in both M7 would have been able to unlock.
[Google Pixel 6 Pro] MrRob0t:
If you Google his username you'll find his website. (Put a . before ceo)
[Google Pixel 6 Pro] Zach Alt:
{Mod edit: Quoted post has been deleted! - Oswald Boelcke}

So show us a video of your Verizon phone rooted.
[Google Pixel 6 Pro] Alekos:
{Mod edit: Quoted post has been deleted! - Oswald Boelcke}

who said you were banned?

If it's true and you fellas can unlock a VZW pixel (3-6) then you just made yourselves an easy 50k (Google's bug bounty is usually between 25k-500k depending on the exploit) for charity.

The funniest thing I've seen is the steps to unlock the bootloader, are actually the steps to Carrier Unlock your device (SIM unlock isn't the correct term). Hilarious.
[Google Pixel 6 Pro] andybones:
That could be from any Pixel.. this proves noting man.

Is it A11, A12?

Pixel 1,2,3,4,5,6?

Hey look I'm using a Verizon!
[Google Pixel 6 Pro] TonikJDK:
Holy smokes! I'm unlocked on VZ also!
[Google Pixel 6 Pro] Az Biker:
Subtle, yet crafty :p
[Google Pixel 6 Pro] FernBch:
So, as quickly as I got back into it, I'm back out.

Google must have taken lessons from Bill Gates. Release problematic OS, then release updates. With each update fix this (or fix nothing), and in the process, break other things. Right now I'm not sure if February's update is worse than December's or not.

Reception is poor, can't have WiFi and BT on at the same time, voice typing doesn't work, and the list goes on......

I've had enough! Goodbye Pixel 6 Pro. It's going back. Should've waited for Sammy's reveal and ordered the S22 Ultra like I originally thought. New S22 Ultra with 512gb of storage will be here around the 27th.
[Google Pixel 6 Pro] HipKat:
Weird, I have none of those issues
[Google Pixel 6 Pro] bosox284:
Oh the Verizon HTC devices. Brings me back to the HTC Rezound and the wire trick to get S-OFF. Those were some fun times. I didn't fully understand what exactly I was doing back then, so it's fun to look back. Too bad removable backs are no longer a thing.
[Google Pixel 6 Pro] andybones:
This is the one I was testing for that had the wrong sd card that was worked with the better one. I rebooted that thing with that wire probably over 100 times with that paperclip, lol. That phone was a beast!