About a month ago, I already posted this question on askubuntu.com, but nobody was able to give me a proper answer to it. Maybe this was because of the fact that it is actually more of an Anroid question than a Ubuntu question. So, perhaps, you may know the answer to it. It could be that I don’t even need Ubuntu to fix this problem.
Last night, I was using the Jota Text Editor app on my LG G3 Anroid phone running Fulmics. The phone (which I am planning to replace very soon) crashed about two times whilst I was writing a text with the help of this editor. After the last crash, I wanted to open the TXT file I just edited, but it was displayed as empty by the editor. So, the index entry still seems to be there but the text cannot be found anymore. Thus, I would like to scan an interval of about [-1 MiB, +1 MiB] around that index entry in order to find the lost utf-8/LF (for Linux/Adroid) text.
I suppose that this could be done via the terminal, but I have troubles finding the right path in order to access my phone via the terminal itself. Also, I have not found out what file system the internal memory of my Android phone uses. Do you know where I can figure this out?
Edit: I have found a way to access my phone via the terminal. This answer has helped my a lot.
Furthermore, I was able to access the folder with Nautilus. There, I can see two versions of my TXT file. The first one is called
text.txt, has a size of
0 Bytesand has been edited at
00:55 hrs (12:55 a.m.). Below, there is an entry called
text.txt~which has a size of
78.0 kBand has been edited at
00:55 hrs (12:55 a.m.). But I cannot open
text.txt~with gedit, and opening
text.txtwill just show me an empty document, just as it is displayed on my phone.
Update: I have now used the Android Debug Bridge, running on Ubuntu 18.04. But this did not work either.
sudo adb pull /storage/emulated/0/text.txt~ /home/username/Documents/1-adb.txt delivered an empty document and
sudo adb pull /storage/emulated/0/text.txt /home/username/Documents/2-adb.txt did so as well.