Live data from Hacker News

Pixel phones are sold with bootloader unlocking disabled

fitzsim.org

191–200 of 359 posts

Re: Pixel phones are sold with bootloader unlocking disabled

#191

i was just considering switching to android after hitting “you’ve created too many apps in the last 7 days” and couldn’t build a project in xcode. glad to see that would be a waste of time and that everything sucks.

Everything sucks, but not in the same amount.

Re: Pixel phones are sold with bootloader unlocking disabled

#192

Basically this is done to ensure that the phone isn't locked by the carrier, meaning if you buy the device directly from google you can still unlock the device by connecting to the internet. Yeah, it sucks, yeah, you own your device less in a way, but im happy they still let you do it. I sent a support message a while back asking about it on the google store thing - and they said it was unlocked. I installed graphene…

So my choices are locked or locked? This is why I ordered my last phone from Hong Kong (and convinced the seller to take Bitcoin for it https://news.ycombinator.com/item?id=25598831 ).

No, buy it from Google or at retail and it will be unlocked. Buy it from Verizon and it won't be.

Re: Pixel phones are sold with bootloader unlocking disabled

#193

"Here is the rest of the network activity, all of which is TLS-encrypted by keys buried in the stock Google operating system, and thus not controlled by the device purchaser: Hostname Downloaded to phone Uploaded from phone storage.googleapis.com 383 MiB 8 MiB fonts.gstatic.com 137 MiB 3 MiB afwprovisioning-pa.googleapis.com 18 MiB 1 MiB www.gstatic.com 8 MiB 287 kiB googlehosted.l.googleusercontent.com 8 MiB 345 kiB…

Who gives a shit? If it's a new phone it has none of your data on it, and you're just about to wipe the OS and install one which respects you much more. No harm done.

Re: Pixel phones are sold with bootloader unlocking disabled

#194

If I wanted to buy a new phone that I could root, install a custom ROM on, and use without voiding the warranty, what's the current best bet? One Plus used to be pretty good, but they've gone down in freedoms and up in price. Samsung are an obvious no. The entire design of the iPhone is specifically aimed at keeping the user out of it. Linux phones aren't usable yet. The shop on the /e/ foundation website seems to be…

Pixel with GrapheneOS — you can reflash it back to PixelOS the same way, no harm done.

Re: Pixel phones are sold with bootloader unlocking disabled

#195
post #126

Earlier quoted context omitted.

When you buy a new car they have the VIN of the car and log any recall repairs done. So not sure how you think the same wouldn't be legal on a phone? Having a device in their database as NEVER_UNLOCKED takes away any onus from having to look for this in the first place for a large % of users. Additionally this is kind of important for a company that's had a history of selling devices with hardware defects. It'd be ve…

Maybe make a phone that cannot be bricked by any software? A phone that can always be reset to a clear state with a factory reset? I'd argue that it's possible in 2023.

The PinePhone can boot from an SD even if the eMMC install isn't working, so it kinda fits the description. You can either run an OS from the SD or boot an image to fix/reinstall on the eMMC.

Re: Pixel phones are sold with bootloader unlocking disabled

#196

> Request to Google: ungrey the “OEM unlocking” toggle in the factory, before shipping store.google.com devices to customers. Do not make your customers connect the device to the Internet before they are allowed to install the operating system they want. That won't happen. I can think of two big reasons off the top of my head: 1. Supply-chain attacks, someone gets a hold of the phone before it gets to you and unlocks…

> where user damaged the device through software

The fact this is even possible means the device is already broken straight out of the factory.

Re: Pixel phones are sold with bootloader unlocking disabled

#197
Shrugs I have a pixel 7, have never used this option, I put the phone in airplane mode and was able to flip the "enable OEM unlocking " switch without issue. Granted this phone has had intenet access for months so not sure if it already has decided it's "not a carrier-locked phone ".

Re: Pixel phones are sold with bootloader unlocking disabled

#198

Earlier quoted context omitted.

Not allowing a bootloader to be unlocked on a company-owned device does sound like a desirable feature, but only for company-owned devices. Applying that setup to all phones assumes that the default phone is a company-owned device and is subject to external control.

A different SKU for enterprise managed devices would cripple IT departments that don't pay the big bucks to e.g. verizon to manage their device provisioning & MDM enrollment.

Wut? I don’t follow? Anyway, once you are big enough to care about preventing bootloader unlocking on your company devices you are big enough to pay for that privilege.

Re: Pixel phones are sold with bootloader unlocking disabled

#199
post #121

Earlier quoted context omitted.

You are confusing Verizon's motives with Google's motives. Verizon disabling the bootloader on phones that users are still paying off, or bought at a discount together with special terms of condition, is something that might be defensible. Google however made it so that any Pixel phone bought anywhere , even by customers who pay 100% of the price themselves with no carrier involved are not actually owned by those use…

> is something that might be defensible. I would like to propose that it never is, and only seems so sometimes because our society is insane.

I don't think I'm insane for not wanting my cellphone to get stolen and then be sold as a working phone to somebody else. Anything to cut down resale value of stolen phones. With full root you can overwrite the IMEI, and the stolen phone is as good as new.

Re: Pixel phones are sold with bootloader unlocking disabled

#200

"Here is the rest of the network activity, all of which is TLS-encrypted by keys buried in the stock Google operating system, and thus not controlled by the device purchaser: Hostname Downloaded to phone Uploaded from phone storage.googleapis.com 383 MiB 8 MiB fonts.gstatic.com 137 MiB 3 MiB afwprovisioning-pa.googleapis.com 18 MiB 1 MiB www.gstatic.com 8 MiB 287 kiB googlehosted.l.googleusercontent.com 8 MiB 345 kiB…

Who gives a shit? If it's a new phone it has none of your data on it, and you're just about to wipe the OS and install one which respects you much more. No harm done.

"Who gives a shit?"

Google does. That's why the Google's code is forcing a computer owner to connect the internet using a Google OS before installing an OS that the owner chooses. The customer has paid, title has been transferred, the computer is no longer Google's or the carrier's property. If Google or a carrier does not get to collect some data after purchase, then no harm done.

Post reply on HN