this post was submitted on 02 Jul 2025
14 points (76.9% liked)
DeGoogle Yourself
12562 readers
124 users here now
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Rules
-
Be respectful even in disagreement
-
No advertising unless it is very relevent and justified. Do not do this excessively.
-
No low value posts / memes. We or you need to learn, or discuss something.
Related communities
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
GrapheneOS will only run on Pixel devices for now (including the Pixel tablet), see https://grapheneos.org/faq#supported-devices
LineageOS has two Lenovo devices listed, your (and my) tablet are not on that list, see https://wiki.lineageos.org/devices/#lenovo
Depending on the model you might find some custom built ROM on e.g. XDADevelopers, but be careful not to brick your device.
Thanks! Sadly my Lenovo P11 isn't supported for the moment.
If a device gets bricked, how do people unbrick them?
Without support from the vendor they don't. Mobile computing is so locked down right now that it might be possible that not even the vendor can repair a bricked phone tbh.
Compare it to a broken BIOS on a PC. You can basically throw out your motherboard if you fail while updating it. Some devices have hardware pins used only for provisioning and debugging (JTAG) but they would have to be reverse engineered first.
Can confirm, bricked a Latitude E6420 trying to put coreboot on it and completely missing an instruction in bright red bold text. Had a parts machine thankfully, and had to swap the boards.
And lastly you could self compile
well if they find the drivers, and make the necessary changes from another tablet or phone that's similar and suported, yeah
Are there guides or documentation for how to do this for me or future devs that are interested?
what I know though is that the device manufacturers are obligated by license to give you the kernel source code for the device on request, because linux is gpl.
but they are not obligated to provide you hardware drivers and device trees that are not included in the kernel. you may still ask in case they care, but it's probably rare they provide that. sometimes it's hard even to get their kernel source code.
in some cases they use (or at least base it from) a similar device's tree. usually a similar soc. i see such devs using a lot of the same drivers and even combining efforts on similar devices.
you'd probably have a better chance talking to people who maintains a similar platform.
I don't know. Haven't done this myself. I would look at the git history of devices currently supported. how they started out, what kind of changes they made, how did the maintainer obtain a file or figure out a config change, things like that. then maybe also contact the maintainer ofir that device, or the lineage mailing lists (or a more modern platform if they have one, but the more experienced folks are likely only reading the mailing lists)