I got my phone through my carrier. Unbeknownst to me at the time, carrier provided phones have locked bootloaders so you can’t install grapheneOS on them, or if you can, I haven’t found a guide to reliably do so. The phone was $800 off through the carrier so I can’t complain too much, but I would have got it straight from Google if I had known prior to buying that you can’t install grapheneOS on it.
All modern phones come with a locked bootloader. This is to protect the OS and the User data, preventing anyone with physical access to the devixe from reseting the device and installing their own software without permissikn. I had to unlock mine on my 1+ 7P before installing /e/OS. It might just be that carrier locked phones might need something extra to unlock them not sure.
There’s almost no risk, you can install it from the browser, the bootloader gets relocked so no issues with banking apps and rooted device, and you can still have play services on the phone but without it being able to access the whole storage and device info. You seem to literally just be spewing words without knowing anything about the subject.
If you don’t want it I’d be willing to take it and experiment myself with graphene OS.
I’m saying I don’t want to modify my device because I don’t want to risk damaging it. How is that spewing words without knowing anything about the subject? I don’t care how easy it is for other people to modify it or how functional the phone might be afterwards, I don’t want to risk modifying it myself, that’s all. Also I wouldn’t want Graphene for other reasons, but that’s besides the point. It’s on Google to fix their crappy software, not me.
Because there is practically no risk of damaging the device and bricking it. If you knew anything about the the distribution, it’s inhalation and android you’d know that the risk is almost nonexistent and reversible. I understand you don’t want to run any risk, sure, it’s a valid reason, but to damage the device is practically impossible just from installing another android variant.
Switch to graphene OS
I got my phone through my carrier. Unbeknownst to me at the time, carrier provided phones have locked bootloaders so you can’t install grapheneOS on them, or if you can, I haven’t found a guide to reliably do so. The phone was $800 off through the carrier so I can’t complain too much, but I would have got it straight from Google if I had known prior to buying that you can’t install grapheneOS on it.
All modern phones come with a locked bootloader. This is to protect the OS and the User data, preventing anyone with physical access to the devixe from reseting the device and installing their own software without permissikn. I had to unlock mine on my 1+ 7P before installing /e/OS. It might just be that carrier locked phones might need something extra to unlock them not sure.
I’m switching phones instead, but even if I wasn’t I don’t want to risk bricking my phone or playing the cat and mouse game with banking apps.
Either way I’m never touching a pixel again until they fix their buggy software.
There’s almost no risk, you can install it from the browser, the bootloader gets relocked so no issues with banking apps and rooted device, and you can still have play services on the phone but without it being able to access the whole storage and device info. You seem to literally just be spewing words without knowing anything about the subject.
If you don’t want it I’d be willing to take it and experiment myself with graphene OS.
I’m saying I don’t want to modify my device because I don’t want to risk damaging it. How is that spewing words without knowing anything about the subject? I don’t care how easy it is for other people to modify it or how functional the phone might be afterwards, I don’t want to risk modifying it myself, that’s all. Also I wouldn’t want Graphene for other reasons, but that’s besides the point. It’s on Google to fix their crappy software, not me.
Because there is practically no risk of damaging the device and bricking it. If you knew anything about the the distribution, it’s inhalation and android you’d know that the risk is almost nonexistent and reversible. I understand you don’t want to run any risk, sure, it’s a valid reason, but to damage the device is practically impossible just from installing another android variant.
@gvasco @IdleSheep recently it’s even slightly buggy too, but it’s still orders of magnitude lower than stock.