- Unlock bootloader (depending on vendor, you have to do an online verification),
- flash a recovery.img,
- load into recovery mode (which, depending on the phone, might need extra work)
- wipe some caches,
- select new os/rom image,
- pray it doesn’t brick your phone.
You’d think someone would’ve learned a thing or two from the easy graphical installations linux and even windows have been offering since the late 2000s.
purposefully. they dont want you messing with their device. its that simple.
“Their”?
ha, you werent under the impression you were buying a device, were ya?
youre buying a software license that happens to come with a piece of hardware.
I always tell people you’re not buying a phone ( software + hardware ), you’re just buying the hardware, what’s inside ( software ) it all belongs to the company, the manufacturer of your device
I’m glad to see that every person I said this to, seemed worried about their data, and asked me how they can truly own their phone
It used to be easy… When people were actually making custom ROMs for everything and you could literally just plug the device into your PC and run a program to do everything. I don’t think there is anything inherently in most phones stopping this; it’s the lack of people developing custom stuff for every piece of hardware out there. Some phones do actively try and thwart custom ROMs, such as Samsung with their Knox bullshit, but most don’t need to; nobody is hacking them in the first place.
There are a lot of reasons here which are correct, but one huge Factor when I was working with custom roms was the fact that the actual underlying hardware driver and firmware were a black box. Generally speaking you would need to harvest the binary files that made things like the camera, gps, and/or touchscreen work. Sometimes it wasnt too hard if you were going from one android skin to another that used the same underlining operating system, but if you wanted to make serious changes, and the phone manufacturer wasn’t great at sharing, it could take a very long time to figure out what data needed to be passed to the camera to make it turn on and be available to use. What got even worse is if you wanted to upgrade your android version (5 to 6 lets say), where android made serious changes under the hood, you ran the risk of having these blobs not even work with the system. They would expect something that android no longer passed or provided. Or they were using some deprecated API to make their function a accessable. It just became impossible to do without being able to recompile the binary only portions that weren’t subject to the gpl. As android has gotten more security conscious it has made things even more complicated.
GrapheneOS is insanely easy with the web installer just takes a little while
Xiaomi becomes a pain in the ass with HyperOS. It’s sad. The hardware was good and you could install custom roms.
For many reasonable vendor, the process is ver unlikely to brick your phone, and requires minimal effort to unlock the bootloader or load the recovery.
However, many phone vendors (Xiaomi was the one I know) subsidize phone price with data surveillance and ads; so they don’t want users to use other OS, as it hurts their revenue.
Look up the history of how Android was developed, particularly what happened when Google took control, and you will find your answer. Ofc if you want to help, feel free to be the change that you want to see in the world, I’m only talking here about the past, as you asked about.
TLDR version of that history: greedy corporations surprised everyone, somehow, by ultimately acting in a greedy manner. B-b-but their slogan was “Don’t be evil”! - once upon a time. And ofc Apple sure as hell wasn’t going to cooperate with that “nonsense” of allowing anyone to take even one step outside of their walled garden. So what then is left to us, besides what you see before you?
Less tinfoil in my take: a good reason there doesn’t exist other OSs is a lack of drivers and support for hardware. Good luck getting your screen to work if it’s proprietary to the manufacturer and device. Can’t communicate with the ASICs if they don’t use standard protocols, etc.
This was a big issue back when I was involved in the LG G Flex 2 community and I can assume it only got worse since then.
PCs are a bit different IMO since generic drivers might get you pretty far. Even then, support for modern graphics cards (for example) would be near impossible without the manufacturers playing nice or in-depth insider knowledge
I can’t answer your question, but is quite unfortunate. It really shortens the lifespan of many phones as they stop receiving OS and security updates after awhile (and in many cases, right away).
deleted by creator
GrapheneOS is a very easy install and can be done simply by plugging your phone in and clicking some buttons on the browser.
Only if your phone is a Pixel, which isn’t available in my country
deleted by creator
I honestly don’t think I’ve ever heard an average user say: ‘I like my phone’s hardware, I just wish it had a different OS.’
Phones by and large are seen as a locked system: you specifically choose to buy Android or iOS and stick with that.
There’s really no incentive for companies to make different OS installs easy. I’d say there’s plenty of reasons not to: do you really want to give the average user that much power to fuck up their phone? I assume there’s also some security implications if they made it too easy to fiddle with.
So yeah, it’s difficult because you’re fiddling with something that wasn’t meant to be an end-user thing in the first place.
Don’t get me wrong, I’d love it if they made phones much more open in terms of hardware and software, but the big guys aren’t going to do it.
That doesn’t really make sense. Every paragraph, except the 2nd, also applies to PCs, yet you can install a different OS.
The reason is quite simple: more money from users.
PCs aren’t phones -They have different expectations and histories.
Would you ever consider buying individual parts, and building your own gaming phone?
The end result is still the same: Less consumer power,.
The web-based installer for GrapheneOS is very easy to use. The catch is that it only works for Pixel phones (and only those that are still receiving updates).
I decided to install Graphene before looking up the installation and was blown away by how easy it is. I’d been on stock android for years and was expecting a similar experience as OP describes. My very old custom ROM folder is filled with files with names like ‘confirmedsafeblob’ and ‘bricksafe’ that I don’t even know what they are anymore but speak to some past misery. Then beep-boop done with the web installer.
Because vendors realized they’ve made a mistake. They’ve lost control they can’t regain. Same thing with game consoles.
So, it’s actually a feature for the companies selling you phones.
Unlock bootloader (depending on vendor, you have to do an online verification),
A few years ago, there were huge issues with reseller unlocking the bootloader to inject ads on the phones they sold, which forced many android phone manufacturers to add online verification with long wait time to prevent bulk unlock.
That may be an excuse they used, but I doubt that was really their motivation.
GrapheneOS’s guided installation is simple enough anyone should be able to install it IMO.
Provided you must use a google device
