N3rdTek You can't use Google One backup service on GrapheneOS, as it's not supported as the OS backup service. Your only two options are to use Seedvault, or the internal backup mechanism of your apps, to back them up.

      treequell
      Unless I'm mistaken your first option does not work in any capacity whatsoever so the reality is I only have one backup option is that correct?
      What would necessarily be stopping me from trying to use something like Swift backup or super backup

          9 days later

          N3rdTek and devs wonder why anybody would want root and risk opening attack vectors 🙄

              • [deleted]

              • Post #5
              • Edited

              Device backup to Google probabaly requires a privileged system component called Google Backup Transport, Which is not avaliable on GrapheneOS

              N3rdTek What would necessarily be stopping me from trying to use something like Swift backup or super backup

              For rooting you'd have to Unlock the Bootloader, Which will wipe all your data. You won't get any help from this forum about Rooting.

                • [deleted]

                • Post #7

                One of the main requirements of apps that I use is an ability to back up manually. Aside from those where I don't mind losing data upon reinstall. This way I am not reliant on any solutions and my backups may require more user input but otherwise are pretty straightforward. This is just a suggestion.

                Sindaquil hmm, I just checked nowhere on the GoS main page does it mention Seedvault is more or less worthless

                  N3rdTek Unless I'm mistaken your first option does not work in any capacity whatsoever so the reality is I only have one backup option is that correct?

                  After a lot of trials I did successfully observe SeedVault restoring things! See: https://discuss.grapheneos.org/d/6686-seedvault-video/3

                  I think the key things I learned are: every SeedVault backup must immediately be followed by a test restore in a fresh profile; if you're trying to use SeedVault you need two separate devices so you can keep one known-restorable backup while trying to create another one; if a SeedVault backup is corrupt the only thing to do is to reformat the USB device.

                  At present it seems genuinely very unreliable. But I don't think it "does not work in any capacity whatsoever".

                      4 days later

                      de0u a backup is not a backup until it has/can be(en) restored.

                      I'll give you the notion if you have resources and time to test it in another profile immediately upon creation, and once verified it's guaranteed to always be restorable, fine. But that's a lot of involved work.

                      If it's a tossup each time you restore, it's the same or worse as "well it works maybe 25% of time maybe it do maybe it don't just try a couple times"
                      I got better things to do with my time & wonder if trading a little privacy for reliable Google backup known to be verifiably encrypted and secured via 3rd party audit isn't the worst thing ever

                          N3rdTek I got better things to do with my time & wonder if trading a little privacy for reliable Google backup known to be verifiably encrypted and secured via 3rd party audit isn't the worst thing ever

                          I doubt it would be "the worst thing ever" and it's not clear who might have claimed it would be. Perhaps a fork of GrapheneOS including Google's cloud backup would be very popular; I don't know.

                            2 months later

                            @GrapheneOS can you please advice on the backup replacement, are we likely to see it soon?

                            11 days later

                            Question: Can you restore a Google One backup (taken from stock Android) to Graphene?