Migrating from org.bromite.bromite.dev to org.cromite.cromite #91
Replies: 2 comments 4 replies
-
I have an additional method one can use for migrating all data from org.bromite.bromite to org.cromite.cromite. Note that login cookies will be invalidated by this procedure, so you'll need to login on Cromite. The reason for this is unknown. First, ensure that both Bromite and Cromite are installed. Force-stop them, then launch Termux and issue Then, execute the following: src="/data/data/org.bromite.bromite"
dest="/data/data/org.cromite.cromite"
cp -rpF "$src"/* "$dest"
mv ”$dest/shared_prefs/org.bromite.bromite_preferences.xml" "$dest/shared_prefs/org.cromite.cromite_preferences.xml"
cd "$dest"
owner="$(stat -c %U .)"
chown -R "$owner:$owner" * This will wipe all the Cromite data and replace it with a 1:1 copy of the Bromite data, including the cache. Then, it'll fix the filename of the Cromite preferences and finally set the right owner for the data. Once finished, launch and immediately close Cromite once, otherwise some gestures will not respond. |
Beta Was this translation helpful? Give feedback.
-
Hi, looking for a way to do so with CalyxOS' backup solution seedvault whch is used also by grapheOS, which usually has no root access unlocked. Can we trick the backup to apply to the backup to another app? |
Beta Was this translation helpful? Give feedback.
-
First off, you need root to do this.
I have been using bromite.dev as a daily driver for a while and it's great to see the direction with this new repo and launching of new cromite.
The idea is to trick a backup app to restore app data from old bromite.dev to the new cromite app and resume all data/settings/cookies/sessions as normal.
This process might take 30mins to an hour. Process requires your mind fresh and active as the steps need to be taken as prescribed and the paths/file locations have to be aligned or the restoration of the backups will not proceed.
Get started. The apps to use. 4 in total.
Open Migrate-GPE (first app) and create backups of both bromite.dev and cromite. Make sure to select only app data and permissions. App is not required. Name the resulting files bromite.zip and cromite.zip so as not to confuse them.
Extract both zips.
Go to bromite folder, you need to extract this file using termux in the background - org.bromite.bromite.dev.tar.gz. This is what holds all of our important data. It is loaded with a lot of files, took me 15 mins to extract.
Once you have the result of the extraction. i.e org.bromite.bromite.dev folder. You need to move this to the cromite backup. See below step on how.
Go to cromite backup folder we extracted, there should be no directory named - org.cromite.cromite. Create this new directory and then copy the org.bromite.bromite.dev folder that we had extracted before inside the new directory.
Now rename this copied folder from org.bromite.bromite.dev to org.cromite.cromite.
Finally zip all the contents of the cromite folder.
Your zip is the new backup of cromite containing all your data from bromite.dev.
Open migrate flasher and select the new zip. Follow instructions.
Then open migrate helper. Restore backup.
Open cromite with all of your data restored from bromite.dev.
Hopefully this helps someone. :)
Beta Was this translation helpful? Give feedback.
All reactions