I have a FF3 with /e/. Yesterday I did the update 1.9 that brings Android 12. In the process all my notes were deleted. The folder in the cloud was recreated and there are no deleted files to be found either. Can anyone help me further or are they gone?
Ich habe ein FF3 mit /e/. Gestern habe ich das Update 1.9 durchgeführt, dass Android 12 bringt. Dabei wurden alle meine Notizen gelöscht. Der Ordner in der Cloud wurde neu angelegt und es sind auch keine gelöschten Dateien zu finden. Kann mir jemand noch weiterhelfen oder sind die weg?
can’t reproduce this. I left a comment in the gitlab issue. The workaround is interesting - I’d think this only works if it’s a Folder mixup on the remote - because how should a different appid have access to the foundation.e.notes database? in any case, I think data is recoverable by direct access to the foundation.e.notes appid sqlite database. If everything fails I’ll writeup an howto.
Seems like the workaround involves syncing? But the notes were also lost to users who never synced to Murena or Nextcloud and didn’t want to, just keeping the notes locally on the phone.
So, to know how to get the notes data out of the now seemingly dormant database would be nice for them, I guess.
I guess it could be account misattribution, but without reproduction I can’t tell. For users who can do adb root and know how to use sqlite3 it is easy to recover, but that is not for everyone. On my device both tables are populated with the same notes.
adb shell 'echo "select content from NOTES union select content from Note;" | sqlite3 -csv /data/data/foundation.e.notes/databases/OWNCLOUD_NOTES' > notes.csv
My situation on install of e-1.9-q was that very soon after restart Notes threw up some sort of notification saying I had zero Notes. Shortly after, a “timer” icon appeared informing me that 254 notes were being “copied”. I lost no notes.
I was very keen to follow up the suggestions of @tcecyk if only to learn how to backup notes from the device.
Firstly I was able to find the databases with TWRP > File manager at the location /data/data/foundation.e.notes/databases/OWNCLOUD_NOTES
Thank you for the response. Unfortunately I am not technically inclined enough to know where to start trying that method to find out.
On another reply from another person they stated they could not find the/data/data/foundation.e.notes/databases/OWNCLOUD_NOTES folder. When I do a basic file search on my phone I see other files with /foundation.e.email,calender,drive etc. but no “notes”.
I see also some are trying to boot in recovery to get to this location, maybe it just hidden from normal file search on the phone. I have never booted in recovery, but could try in attempt to recover my notes.
Usually the user has no access to this folder if the phone isn’t rooted, so simply looking for it with the file manager wouldn’t show it.
You can use TWRP to see it as @aibd suggested.
You can use the adb root command to make it accessible via ADB, which the two command lines from @tcecyk make use of to get the notes.
To use ADB:
If not done already, make the Developer options visible by tapping on the Build number in Settings - About phone a few times until you are being declared a developer.
If not done already, enable Settings - System - Advanced - Developer options - Android debugging
Connect your phone to a computer via USB.
If not done already, download the current Android SDK platform tools to the computer and unzip the ZIP file to a folder you can navigate to easily.
Enter the adb devices command to display an ID of the phone to make sure that ADB works with the connected phone (upon first usage the phone should ask you to confirm this access from the computer, there you should also be able to select that the phone remembers that decision, if you want).
To use adb root you first need to enable Settings - System - Advanced - Developer options - Rooted Debugging … if your /e/OS build has this (prior to Android 12 = /e/OS S not every /e/OS build has this).
Basically affected users have a http instead of https endpoint configured still, and the schema redirect (from plain to transport encrypted) wasn’t handled. As this is a subset of users it didn’t trip for people testing the v1.9 release.
@omoney23 with the next update, the import activity will be able to avoid the failure mode (not handling the redirect), but if the Notes remote folder is already empty, I don’t think (and did some testing) it can recover in the current app logic, despite having them in its local db. It will prioritize the state of the remote Notes Folder.
If you had critical notes synced to murena.io prior and the method I outlined is too foreign - it’s straightforward to contact the murena.io email support and ask for a restore of the Folder.
(@aibd one can just subscribe to Gitlab issues with an account or vote on it, no comment/contribution necessary)
1.8.1 is on an earlier security patch level, which should trigger Android rollback protection, which should force a factory reset, which should delete the notes.
Theoretically reverting back should work for instance from 1.8.1 to 1.8 (same security patch level), although on devices with a locked bootloader I wouldn’t know whether this is allowed without unlocking the bootloader first, forcing a factory reset, etc.
notes App downgrade? haven’t tested. After “new Notes” migrations ran (before the 301 bailout?) then you’ll possibly end up with incompatible db schema for old App. Still, could work, but seems out of proportion, a vote for the availability of signed+versioned apks of /e/ Apps though. OS downgrade would be a bit heavyhanded.
I think remote backup if you had it enabled is best. If all the notes were local…
There’s also a non-root adb method to fetch the sqlite db, but as it involves doing aes decrypt on a tar file created by “adb backup” - not particularly simpler.