My understanding is that it’s a new project (first release on Github is from April 2026) and I haven’t seen any posts about it on PrivacyGuides. I am intrigued! Here are some relevant links:
2 Likes
Well said:
This would be a very bad idea. I’d rather have any StockOS from a major OEM over doing this because of:
… RestlessOS boots the vendor kernel
… RestlessOS uses whatever firmware the vendor partition provides
It’s using what it finds on the phone.
So you will never get firmware or kernel updates and so many features are disabled. This is a huge 1 to lose hardened_malloc.
It’s a security nightmare you can’t wake up from the next morning.
Should be called anti-GOS – never get security updates again.
4 Likes
GOS Forum Post
A phone without security requirements of the official Project shouldn’t be called GOS. It’d merely have some features inherited from GOS. It wouldn’t have the whole security model which is required for any device running GrapheneOS.
Basically just this and what @yes quoted, it’s a nice idea but part of what makes GOS what it is, is the hardware. Without meeting the hardware requirements and not getting updates to various things, it’s just counterproductive.
- hardened_malloc — causes boot loops on devices with 39-bit virtual address space. replaced with AOSP Scudo.
- Auditor — requires hardware attestation which doesn’t work on GSI
- mtectrl / misctrl — Pixel-specific memory tagging control; breaks vendor TEE drivers
- USB protection — the low-level USB port controls rely on Pixel-specific hardware and are non-functional on other devices
- native debugging protection — not ported; breaks compatibility with root solutions and vendor debugging tools
RestlessOS is an unofficial, unaffiliated fork of GrapheneOS packaged as a Generic System Image (GSI) for Project Treble devices.
And from the GOS FAQ
GrapheneOS does not support being used as a Generic System Image, which only exists for development/testing purposes and isn’t usable for GrapheneOS since we require kernel changes and the userspace part of the OS cannot run on top of a kernel without the required functionality. The generic targets simply run on top of the underlying device support code (firmware, kernel, device trees, vendor code) rather than shipping it and keeping it updated.
3 Likes
I don’t know much about GSI’s, would anyone know if it is literally true that you cannot update your firmware or kernel while using RestlessOS? Or did this user mean to say you cannot receive firmware and kernel updates once your device reaches end-of-life?
1 Like
Ive tried Restless OS out before but ended up scrapping because the lack of OTA updates and unlocked bootloader makes every other user facing security feature useless but being fair the only GSI based rom I’ve seen with ota updates is the official Infinity X GSI though i havent personally tested its stability
even with updates, my issue is it would be very difficult to trust any fork of GrapheneOS as of now and my default assumption would be to assume it’s federal. The main benefit for something like this is if you seriously want sandbox Google play and cannot get a pixel but for that there is also Voltage OS and Yet Another AOSP Project. I wish more lineageos based roms used Sandboxed Google Play
Or at least unprivileged micro G from DivestOS
This a nifty way to tryout GrapheneOS but I wouldnt daily drive it. If you already have a Pixel but are stuck on stock for whatever then this may be of utility
as you can test gsi’s without unlocking the bootloader (only on Pixels) so If you’re weary about GrapheneOS RestlessOS is a good test driver . So if you want to “dualboot” a GSi and stock you can use DSU sideloader and the adb gsi sticky mode command for it to persist as long as you like but I wouldn’t necessarily recommend this
2 Likes
The nature of GSI’s is that you cannot have updates of any kind you would need a computer or custom recovery to update the OS itself and there doesn’t seem to be any sort of mitigation from flashing a malicious image
3 Likes
Prepare for Daniel’s wrath
1 Like
Huh… Seems pointless to have a “hardened GIS” then.
1 Like
well, to be fair, GSI was never supposed to replace dedicated device ROMs it was meant for developers to test their apps in different environments and to streamline updating for OEM’s
it sucks because we basically don’t get dedicated builds of custom roms for niche devices anymore
Nothing felt better than buying a device for cheap waiting a few months for a port and enjoying the device that’s yours
3 Likes