In ‘Files’ only ‘Downloads’ and ‘Recent’ is shown in the hamburger menu, normally I would expect to see ‘Images’, ‘Videos’, ‘Audio’, ‘Documents’, and then the phone ‘SM-G930F’.
Camera cannot take pictures, ‘Failed to Save Photo’.
Browser cannot save downloads ‘No available download locations’.
I have considered ‘Permissions’ might be something to do with this, Browser has ‘allow access to files and media’ allowed, and camera also allowed.
When I try to open ‘Storage’ in settings, the window flashes open quickly but then closes.
Have tried accessing the phones file structure over USB, but all you get is the phone icon when connected in WIN 10, but no file structure beneath.
Any help appreciated, as I am bit stuck … have tried googling, best I have seen is Permissions, which I have played a little with, but am wary to fiddle further.
Have you got an SD card in your phone? SD cards formatted as internal storage (“phone storage”) have caused similar issues in the past. For a while /e/ explicitly warned against this or even disabled this option, but I don’t know if they re-permitted it.
OK, thanks, is their a ‘Repair’ menu in e-Recovery (should I assume when you say TWRP you also mean e-Recovery ?), or should I simply download the same version e/OS updater and run it again via e-Recovery
There is no SD card in the phone, but thanks for the tip.
One would expect a specific warning for this, but is it conceivable that your storage was over 85%, and then perhaps one or more apps created a large backup?
Thanks I will look into TWRP, and try access the storage.
Thinking about things, a couple of weeks ago I upgraded the S7 to the latest e/OS v2.7, it had stopped updating about 12 months earlier, so the update jumped a few versions, and since going to v2.7 have had this problem with storage.
I followed your previous help with my S9 to force the upgrade on the S7:
On the S7 there was an unusual requirement to upgrade via 1.17.1-q-herolte in February 2024. Did the “jump” which you made perhaps exclude that step ?
1.17.1-q-herolte was a “special release” the purpose of which was to ensure users did not bring forward Adoptable storage. Here is the link to the Release Note v1.17.1-q · e / os / Releases · GitLab . As I understood it and loosely speaking, this requirement was part of the team’s workaround to dealing with the change of storage encryption method used beyond Android 10 (Q).
I would say that the risk of the downgrade going wrong is too high. (In addition you would have another problem to get hold of the 1.17.1-q-herolte build now.)
The pattern of errors you are experiencing does look (from here) a bit as if you are fighting some encryption issues … and back when devices were regularly upgrading from Android 10 (Q) the standard practice was that Format data was required.
I think I would concentrate on a backup strategy that would leave you feeling able to do a fresh install with Format data … to get a clean start away from this issue.
In CMD, with abd installed and running, I run:
adb reboot bootloader
After quite a delay the phone simply re-booted back into e/OS.
I then wanted to run
fastboot flash recovery twrp-x.x.x.x-xxx.img
But all I can see to install is this:
me.twrp.twrpapp-26.apk
Found on this page, which is the correct file for my device;
The TWRP install instructions show an ‘.img’ not an ‘.apk’ as the file type to install, what am I missing here ?
All I actually need to backup is AntennaPod settings, but none of the ‘export’ features are working, as the Location for the export is unavailable, I assume due to the phone storage issue I have imposed by skipping the 1.7 update.
Will TWRP back up AntennaPods setting for me ?
Moving onto the re-install, do I understand correctly that I need to install Heimdall to ‘sideload’ the e/OS 1.6 ?
I have been to:
I see the version I need: 1.6-q-20221129238948-stable-herolte.zip
So have that ready, I also see some TWRP 3.3 and 3.7 version files in the the same location … will i need these, and what are they.
The twrp.app is not usefull anymore, in the old time it was for updating an already installed TWRP
fastboot commands don’t works on Samsung devices,
you need to use Heimdall or Odin instead
No,
Heimdall (or Odin) is needed to flash the custom recovery.img (or .tar).
Then, you will need to boot in a custom recovery mode to install /e/, using adb sideload (or the TWRP install feature)
Ok, sorry stuck again, I have downloaded the latest build:
e-2.8-s-20250220470167-official-herolte.zip
Copied it to my PC’s ‘c:\platform-tools’ folder, run the ‘adb sideload’ command, but I receive a ‘device unauthorised’ error, please see below:
C:\platform-tools>adb sideload e-2.8-s-20250220470167-official-herolte.zip adb: sideload connection failed: device unauthorized. This adb server’s $ADB_VENDOR_KEYS is not set Try ‘adb kill-server’ if that seems wrong. Otherwise check for a confirmation dialog on your device. adb: trying pre-KitKat sideload method… adb: pre-KitKat sideload connection failed: device unauthorized. This adb server’s $ADB_VENDOR_KEYS is not set Try ‘adb kill-server’ if that seems wrong. Otherwise check for a confirmation dialog on your device. In e-recovery,
The phone simply displays ‘Now send the package’ … etc, no other message.
When I check … it again reports ‘unauthorised’:
C:\platform-tools>adb devices List of devices attached ce10160afd25b12301 unauthorized
Rebooting into e/OS and running the above I do not get Unauthorised
C:\platform-tools>adb devices List of devices attached ce10160afd25b12301 device
adb: sideload connection failed: device unauthorized.
No I did not get that on the phone when in e-recovery, this is in cmd, you mention if I saw it in Developer Options, please explain how I get to view that in Dev Options, is there some sort of console window ??
The phone is not reporting ‘unauthorised’ when booted into ‘e’, only when in e-recovery.
I tried deleteing adbkey and adbkey.pub * from the .android folder on my PC:
Reconnected the USB cable,
OK’d ‘Allow USB Debugging’,
adbkey and adbkey.pub were recreated in the android folder on my PC,
run ‘adb device’, and that returned ‘Authorised’.
Rebooted into e-recovery, selected Apply Update from ADB, ran adb sideload, but still got ‘unauthorised’ failure.
Releases · GitLab