Please check the section Reboot in second article, so that you know how to get out of recovery !
Edit, once you have got your bearings (and please be prepared to spend a little time doing this) – my method involved navigating to Advanced > File manager.
let’s try something easier first - as the stacktrace fails inside the account importer method and it relies usually on the official nextcloud client, install that one, associate with the murena server (disable file sync) and open the native Notes App (not yet the upstream fork) - let’s see if this let’s the migrations successfully run.
In any case you can still try the adb method if this doesn’t yield something positive.
the next /e/ update to v1.10 will avoid the error and open, but not restore notes that were local only and never synced. As I see it, adb methods are the only ones available. I can write more elaborate Howtos, but they will involve the commandline.
I mean I’d be glad if this (the recovery of local-only notes) works, but didn’t see it when I tested myself, maybe I missed something.
Nextcloud notes app uses the official Room library for its Db. There must be tooling around to offer a button in the settings to export db state - greatly simplifying any recovery if the user needs one. That is one of my takeaways from this. It would empower the user that can install a GUI Sqlitebrowser, but the whole adb stuff is too much for
Hi,
Thanks for the feedback. And sorry for the delay…
So there is nothig to do. Is that right?
Or would it be safer to save stuff before the next update
as you initially said you lost all your notes on both phone and in the Murena account I’m sceptic the v1.10 update once released will make a difference for you. But if it will, all the better and feedback that it does is appreciated
I noticed there was further work by Fahim I was missing before on introducing a migration for old note entries that never synced. That is the proper way, I’m impressed - https://gitlab.e.foundation/e/os/notes/-/merge_requests/39 … this will very likely recover notes that were thought to be lost with the App update
Hi,
Some time has passed since last time…After my initial disappointment and trying to get over this loss. I had decided to try the more involved recovery if someone can help. However, I hadn’t seen The last message of @tcecyk does it mean that I just need to update to v1.10? I haven’t done anything yet trying to avoid thinking about it .
Thanks for any advice!
Hi again
Looking at the solution by fahim it seems that the first step before updating the os is to:
setup [/e/OS Notee] app in <= 1.8 build.
I tried but this doesn’t work. I still get the message below.
Note that i’ve previously installed nextcloud app and this one synchronises. Is this enough?
Thanks
Vincent
App Version: 3.7.1
App Version Code: 3007001
App Flavor: ACCOUNT_MANAGER
Files App Version Code: 402060000
---
OS Version: 3.18.91-g35f12d2389e(eng.root.20230310.201313)
OS API Level: 29
Device: heroltexx
Manufacturer: samsung
Model (and Product): SM-G930F (heroltexx)
---
com.nextcloud.android.sso.exceptions.NextcloudHttpRequestFailedException: La requête HTTP a échoué avec le statut HTTP :301
at com.nextcloud.android.sso.api.AidlNetworkRequest.performNetworkRequestV2(AidlNetworkRequest.java:188)
at com.nextcloud.android.sso.api.NextcloudAPI.performNetworkRequestV2(NextcloudAPI.java:159)
at com.nextcloud.android.sso.api.NextcloudAPI.lambda$performRequestObservableV2$0$com-nextcloud-android-sso-api-NextcloudAPI(NextcloudAPI.java:113)
at com.nextcloud.android.sso.api.NextcloudAPI$$ExternalSyntheticLambda0.subscribe(Unknown Source:6)
at io.reactivex.internal.operators.observable.ObservableFromPublisher.subscribeActual(ObservableFromPublisher.java:31)
at io.reactivex.Observable.subscribe(Observable.java:12284)
at io.reactivex.internal.operators.observable.ObservableSingleMaybe.subscribeActual(ObservableSingleMaybe.java:31)
at io.reactivex.Maybe.subscribe(Maybe.java:4290)
at io.reactivex.Maybe.blockingGet(Maybe.java:2320)
at io.reactivex.Observable.blockingSingle(Observable.java:5381)
at it.niedermann.owncloud.notes.persistence.CapabilitiesClient.getCapabilities(CapabilitiesClient.java:32)
at it.niedermann.owncloud.notes.importaccount.ImportAccountActivity.lambda$onActivityResult$5$it-niedermann-owncloud-notes-importaccount-ImportAccountActivity(ImportAccountActivity.java:108)
at it.niedermann.owncloud.notes.importaccount.ImportAccountActivity$$ExternalSyntheticLambda2.run(Unknown Source:4)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.IllegalStateException: <html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
at com.nextcloud.android.sso.InputStreamBinder.processRequestV2(InputStreamBinder.java:246)
at com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestAndBodyStreamV2(InputStreamBinder.java:27)
at com.nextcloud.android.sso.InputStreamBinder.performNextcloudRequestV2(InputStreamBinder.java:2)
at com.nextcloud.android.sso.aidl.IInputStreamService$Stub.onTransact(IInputStreamService.java:43)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
the first item of that list that you quote is a test for reproducing errors or verifying the approach - not a solution itself. The line “update the os to the patched version.” is what you need to do, at best the latest v1.12.
The migrations should both recover unsynced notes and not introduce duplicates (that was a followup issue fixed in 1.11 I think). All that said, migrations are fragile, backups are great.
cool - at last ! the developer (Fahim) really did right by that issue and doubling down when the first restore migration had side effects. When /e/ dev team availability is criticized in other respects, I think back of this
Hello everyone, I’m reading this thread very hopefully. Had the same problem, notes in the notes app that weren’t synched and weren’t disyplayed anymore after an upgrade, but under settings the app info says there’s still a lot inside the notes storage.
inside the settings it says the app is currently on version 3.7.1
I’m a bit nervous about doing sth wrong right now, as I would be very desperate if I lost all the notes can anyone tell me what steps to take, would be incredibly grateful
just did the update, unfortunatelly when I open the notes app it only says “welcome to notes” and a button “select account”.
Is there anything I can still do to get the notes back?
Still says there’s 10MB inside the storage of the notes app, so I hope my notes are still there?
I am also able to use adb commands with instructions. Unfortunatelly my phone isn’t rooted, doesn’t simply have the options to do that in the developer settings, and also doesn’t have TWRP installed.
Any ideas what to do? Would still be very very grateful
Hi, thanks for your answer!
I’m a bit nervous that the internal storage data might get overwritten and I will loose it entirely if I synch with the cloud now. But if you know that won’t happen I’ll try that
I tried the 4 lines and am still working through error messages [if you want to know the current error:
x apps/foundation.e.notes/db/OWNCLOUD_NOTES
tar: --to-stdout: Not found in archive
tar: Error exit delayed from previous errors.
.
can anyone tell me what steps to take, would be incredibly grateful 