i am trying to identify where furios comes from, like... where is the source code for it?
the furilabs github page has 182 repositories, and there is only 1 pinned repository: issue-tracker.
my impression is that the source code and how to compile/build is not online. it seems like a lot of source code may be in those 182 repositories, but it is a mystery to me how those repositories are supposed to be assembled in order to create the final file that is flashed onto the phone, and the process for flashing.
i am trying to fix the sd card mounting permissions problem. my sd card, which is in exfat format, is being mounted with root ownership and permissions instead of the user "furios" as it should be. kali nethunter for the pinephone pro mounts sd cards properly, making the sd card read/write by the user, and the sd card automatically shows up in the "portfolio" app under "devices" as it should.
i wonder what kali is doing differently as far as automatic mounting goes. but it's hard to compare furios to kali when i don't have access to the furios source code and build process.
Here is the Answerer from Barry from the Telegram Channel:
fatcho (from Matrix bridge) - 01:09
where is the source for furios?Xenon - 01:10
Also here are all the repos https://github.com/FuriLabsfatcho(from Matrix bridge) - 01:11
I saw those but didn't see anything that looked like theOS. Is there a build guide somewhere?Xenon- 01:20 (edited 01:21)
I dont think that there is a complete build instruction. If I remember correctly it is about 100gb of packages. You probably can build it with all repos.Or at least come close to it. (edited 01:21)
I am not sure if some packages are oem packages and that is why there is no complete build instruction (edited 01:21)
Barry (Bardia-san)- Staff - 01:22
every package used to build the image is publicly available in git and apt reposyou can definitely build a full rootfs with debootstrap (01:22)
Xenon- 01:23
The boss has spoken 😂Barry (Bardia-san)- Staff - 01:24 (edited)
we have internal tooling for building sp flashable images but at core they also use debootstrapXenon- 01:24
Is there a reason why they are not os?Barry (Bardia-san) - Staff - 01:25
it never seemed useful for the public and to release we have to remove all signing keys for images. factory images come with all firmware signed
cubetronic Topic starter
15/02/2026 6:28 pm
@xenon i dont understand all the tech involved, but it sounds like there is no way to build the exact image myself, as i would expect of a linux distro. it sounds like the reason given is for "signing" which has no value to me. the lack of transparency sounds like a security threat.
Xenon 16/02/2026 10:22 pm
Your concerns are super valid. I would like to also have a complete build guide. The Problem for them as a business right now is cleaning up the tooling's for public release would be a huge amount of work where they don't have much time for right now. The main goal for them right now is having a actually usable Linux phone. We had a similar discussion about open source hardware. They don't have the resources right now to make hardware and software 100% free and open source because they need to cooperate with manufacturers to make the phone a good bang for the buck. Also you do not need to trust them when it comes to the os you can use dual boot via SD Card and just use something else like Ubuntu touch. You don't need to use the onboard os.
Out of curiosity what do you think would be the best action to get it complete open source with the current tooling being full of secrets and signed keys ?
cubetronic Topic starter
17/02/2026 3:28 am
@xenon id like them to release their build process, and if there is a special key they wont share, then just redact that specific key code instead of withholding the whole build process.
i really dont understand this thing about keys and/or secrets. no linux distro ive ever heard of in my life has keys or secrets that they feel would compromise something if they shared. is it because of android integration? if it is, then that part should be an optional add-on, not part of the base os.
in my experience (since the early 90s) i find it necessary to reinstall the os regulary to keep a truly clean system. but i get tired of fixing the same bugs upon reinstall, so i write a script. but i dont like installing a bad system and then fixing it, when i can just fork the distro, fix it, and install it without it needing to be fixed.
by far the best distro ive ever seen is crunchbang linux, developed by 1 person. that distro opened to hood of the os and brought the user closer to the underlying os config files, instead of hiding configs behind poorly written gui interfaces that dont even show half the options.
i have list of about 30 bugs for furios, some of which ive resolved, but i am not welcome on github or matrix or telegram or mastodon, so my patches will not be pulled or merged, let alone even known to exist to the world. and my list of bugs is likewise unknown to the devs. if i could build the system, i could do more to fix it, and i can still release my solutions on here or something.
if the furios dev team is too busy, or too small, that means they should open source everything because they need all the help they can get.
for bugs and solutions, it would be more advanced to have an email address to report bugs to, because not everyone has access to github or other networks (believe it or not). email is not so exclusive, and sending email is way easier than receiving it, just like its easier to mail a letter to a bank vs opening an account.
you can build the rootfs using debootstrap just like you would any other debian system. signing keys and tooling are for firmware images such as the modem or dsp. you can find instructions about deboostrap in the manpage.
