Thanks for your reply, very helpful. Yes, that sounds unrealistic for my threat model, so not a real concern. Privacy is more important to me than security, although both are important. 
Just a quick comment. In iodéOS, the bootloader can be relocked on devices where it is technically possible: actually Fairphone FP3 and FP4, and the Pixel series.
2 Likes
Good to know, thanks!
Scenarios are also described that state that the hacker does not necessarily have to have physical access to the device.
Rather, malware that is infiltrated via an app can also gain access and the mobile phone can therefore be taken over remotely or automatically by the malware. When the bootloader is unlocked.
Yes, that may be the case, but I have never heard of a specific case. Only of the potentially possible scenarios.
But I’m happy to be taught otherwise if I get a concrete case with proof that an active attack was successful.
Unfortunately, or thank God, that hasn’t happened yet
2 Likes
The bit advantage of iodéOS is its compatibility with a number of phones other than the Pixle line
Thanks to the team especially for supporting the Samsung S10e
4 Likes
I have been using GraphineOS and i really like it , so far it has been a very reliable daily OS , their installer is a step bye step online web installer and everything installed with absolutely 0 Issues… Though , I recently came across iodéOS and i was super excited because in my opinion i felt , cosmetically it looks way better then Graphine OS …I had been watching videos on the way iodéOS looks to its functionality to installation and i was super impressed…so , I thought I would give it a shot…I installed the I iodé installer found here , ( Installation - iodé )…long story short , started the Installation , everything started fine … The installer downloaded the OS , it installed the iodé custom bootloader… then…auto reboot …Failed …it bricked my phone and will absolutely not become detected via usb anymore
Are you able to get the phone working again by using the relevant button combination to soft-reset the device?
yes , it was a struggle , but i was able to get it out …i booted back to Graphine , then tried again…for whatever reason , even after i tried both methods listed , it just would not take the IodeOS …the iodé installer will restart the phone about 2 times , then on the third boot to fastboot mode , then not detect device after it loads its own custom bootloader, every time i try… and i’ve tried both methods …same thing…it locks up the phone
If Graphene is still on the phone maybe the iodé installer was only installed in the other of A/B slots not used by Graphene. I don’t know for certain this is a problem, but having dual boot on the phone (both Graphene and iodé at the same time in different slots) would be problematic at best?
What Pixel model by the way, and were there any issues during the install that stood out (like getting “stuck” in the user fastbootd section? I had that issue very recently due to a usb-c to usb-c cable and only a usb-c to usb-a to my computer was successful).
Thank you so much for the response .
It was as you said…I hadn’t tried any other method , at least , not at first.
The method I used first…
USB -C to USB-C
Tried this twice : failed twice ,. This was using the standalone iodé application .
I started the application , everything started just fine , it would auto reboot twice and after auto 3rd boot , on the phone get stuck on fastboot showing the new iodé bootloader interface , on the computer app be showing , " Waiting for device " being stuck there eternally .
Next , I tried using iodé’s secondary method
Manually looking for the device and running the bat file as an administrator … Same result.
So , I thought it was the cable as well , your thought the same as mine.
So I tried a ,
USB-C to USB-A : same result .
…it could still be cable related , so even now , I’m not weeding that out …I have seen where there are certain cables not able to send and return certain information thus resulting in this kind of hickup …
I am however interested in hearing more about resolving a possible A/B slot issue , if of course you think that could be the case.
The phone I tried this on , thankfully wasn’t my daily…
I wanted to test the Loader first on a phone that I no longer use , Just in case I were to run into any issues.
The phone is a Pixel 7 pro .
This was exactly my experience with a Pixel 7 Pro, whereas with a USB-C to USB-C cable on a Pixel 6a there was no issue. And at least for me, with a “good quality” USB-C to USB-A cable, the Pixel 7 Pro also smoothly completed the install process, not getting stuck waiting for any device when booted into the fastbootd section where the actual install will take place.
I believe if you can get the device detected there, the stock installation method will correctly wipe the partitions as needed, so I am suspecting your cable. Keep us updated!
1 Like