• Off TopicSolved
  • Remove your phone is loading different os + remove google logo in startup

  • [deleted]

[deleted]

You could put on a privacy screen so no one nearby can see the display but you.

    Like the above user said a privacy screen would work, however I know where you're coming from and you want it removed when loading up, realistically though it won't do much good as there are other ways to identify that it is using GrapheneOS like the Moderator had said.

      • [deleted]

      • Edited

      [deleted] I have a privacy screen and idk what privacy screen you are using but saying "nobody besides u can see your screen" is false statement!!

      • [deleted]

      • Edited

      Famous A privacy screen makes it difficult to see your screen from a certain angle in certain light. Thats is far away from a proper solution.

      • [deleted]

      Famous Read my reply to the moderator...

      [deleted] I mean, you can control when it auto reboots. Do it in the early hours of the morning whilst you sleep. How much of a slim chance is it that you happen to take out your phone just whilst the GrapheneOS logo us showing, whilst having someone who is watching, and that same someone is someone who will do you some kind of harm for having Graphene in the first place?

      If this is all within the realms of reality for you and your threat model, and you have an extremely regular auto boot, then a more prudent option would be to mind when you take out your phone in the first place.

        [deleted] Explain your threat model and why you want to hide the fact that you're using GrapheneOS (it's not possible to hide it) autostart is set to 18h by default, it should never automatically restart in a normal situation where you use your phone at least 2 times a day for even 30 seconds. As written above, privacy should be normalized, not stigmatized.

          • [deleted]

          Xtreix My auto reboot time isn't anyones buisness. I can say it's not set 18h (default). Anyone telling me that i cannot hide the fact i am using GrapheneOS is right. But why give it away for spying eyes and cameras?

            • [deleted]

            mmmm Youre right, i should't take even more precautions. Its not a must have feature no.

            [deleted] But why give it away for spying eyes and cameras?

            Which eyes and which spy cameras? If you think that using GrapheneOS can harm you then there's a much more serious problem to consider here, the only advice I can give you is to use a VPN and then use Google's standard servers for connection checks so that your device appears as a regular Android device and blends in with the billions of other Android devices.

              • [deleted]

              • Edited

              Xtreix Using it won't harm me in that way, but it would open up directed targeted exploitation and cause suspection. Also that arey current settings youve mentioned.

                [deleted] but it would open up directed targeted exploitation and cause suspection.

                You're not basing your opinion on facts, and GrapheneOS protects itself very well against physical and remote exploitation.

                It seems that you should first study what a threat model is :

                https://www.privacyguides.org/en/basics/threat-modeling/
                https://ssd.eff.org/module/your-security-plan
                https://privsec.dev/posts/knowledge/threat-modeling/

                  • [deleted]

                  Xtreix If someone knows i am using GrapheneOS they can make attacks based on that knowledge. Using a secure operating system is causing suspection. What have u missed? Straight facts.

                  • yore replied to this.

                    Assumptions and suppositions are no facts.
                    I'd say that this discussion has run out of juice.

                      • [deleted]

                      Stephan-P

                      "run out of juice" you should have used that in op's thread about removing the usb port.

                      [deleted] If someone knows i am using GrapheneOS they can make attacks based on that knowledge.

                      Why? Are you being actively targeted by a government agency or organization that wants to exploit specifically your phone? To my knowledge, no GrapheneOS user or any custom phone OS user has ever been targeted simply for using a custom OS. Then again, maybe you really are as big of a target so as to have exploits made against you because someone saw a GrapheneOS boot splash screen that displays for a few seconds.

                      If you're not protecting yourself from an actual threat, you have no threat. I would suggest developing a threat model for your use case as you seem to be entering "privacy paranoia." There needs to be a credible and realistic threat to protect yourself from, and no toggle or switch will apply to any or all threat models.

                        Since neither the boot splash screen nor the google logo nor the yellow message is removed, this discussion is hypothetical and leads to nothing

                        It's not possible to hide this because the key fingerprint will still be shown at boot. There's no point in changing this. You're talking about a very sophisticated attacker with advanced exploits benefits from knowing the device uses GrapheneOS. You're talking about an attacker more sophisticated than Cellebrite. However, at the same time, you're saying they can't tell that the screen shown at boot with a key fingerprint indicates it uses GrapheneOS. They could also simply read the OS images from the SSD which show it's using GrapheneOS. The OS data partition has all blocks encrypted but the OS images are publicly available so there's no point hiding parts of them, and it's what implements the encryption so it can't be hidden that it's GrapheneOS installed on the SSD. There are multiple other ways to see that it's GrapheneOS including how it behaves in various ways including quick settings restrictions while locked, auto-reboot, USB-C being disabled at a hardware level, etc.

                          • [deleted]

                          yore I have seen People in China getting Problems for much more than that...

                          10 days later

                          Very interesting topic to read. Thanks for all of your insight ! From my understanding, there is no point to hide the graphene logo or the alert in the beginning. No threat model would really need that, and if there was then rewrite yourself grapheneOS and find a way to modify Google boot sequence to not show that warning. (Idk how technically but nothing is impossible assuming you have enough time and dedication.)
                          A dodgy solution would be to implement a physical switch in your Google phone to have your screen shutdown whenever it restart and also have any usb or peripheral off until it's fully operational. As you would have re-written grapheneOS you would have modified as much data that would lead people thinking it's the original grapheneOS. They might think it's a fork or just something unknown.
                          An other "dumb" solution if you care about people not watching you screen, is removing a layer of the screen managing the polarisation of the light. For normal people if would look like a blank screen, for you, if you have the same polarised screen on sunglasses it would just work fine. (Add a privacy filter for a specific angle for your screen to be seen and your officially paranoid, jk)
                          You will then have a kernel & os modified Google phone that have no alert showing up (idk how it could be technically done but it was on Samsung and other phone) that doesn't show anything up until finished boot sequence, with no ability to see the screen for other except if they have polarised sunglasses.

                          Very extreme. Totally overkilled, likely undoable. Entirely fictional. Yet fun to think of.

                          If this answer your threat model. Then wow. Hide.

                          (Remove any over the top solution and """just""" rewrite the os & learn/find a way to modify the boot sequence to just hide the alert & grapheneOS logo)