Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
First off, I don't fully understand the first bit involving iPhoto. But if I understand correctly, you need to recover files deleted from internal memory.
I think recognizing a phone's internal memory is indeed a steep expectation for general Windows file recovery software. However, there may be some specialized programs out there designed just for that purpose. I know for a fact they exist for iOS for example. Not that I'm a fan. Anyway, googling "recover Android files Windows" showed some interesting results, but as I have no experience I can make no recommendations. I did see Easeus among the results, and I personally would start there based on experience with other software by them: http://www.easeus.com/android-data-recovery-software/free-android-data-recovery.html
This would be your safest bet. As you probably know, your photos are still there as long as they are not overwritten. Being able to recover from an external device (PC) is therefore preferable to making changes to your internal memory. It's also far less complex than rooting
Another thought before getting into rooting: I don't suppose you had an app like Google+ making automated backups of your pictures? If so, you might find them on your Google Drive. This also might be a good idea to avoid trouble like this in the future
Third and last resort: you could try a data recovery app on your phone, like GT Data Recovery. That does requires root. The good news: you don't need to unlock your bootloader to be able to root. Locked bootloader means you're limited to stock roms, but they too can be rooted.
Here's a useful thread describing in detail what you'd need to do:
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
In your case, I'd run data recovery ASAP, meaning
Downgrade your firmware, leaving data in Flashtool unchecked (!!) (See thread's FAQ for detailed explanation)
Root
Install GT Data Recovery or similar from Google Play and run it
After you've recovered all photos you can and backed up all your other data, follow the procedure in the recommended way, which includes wiping data. Do note however, that the firmware mentioned there is outdated (March 2015). You can find up to date firmware here: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
Good luck!
(Thanks to @bilboa1 and @istux for their useful posts!)
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
If you're rooted, you can use the app DiskDigger. Worked for me
Sent from my D5833 using XDA Free mobile app
kjoz said:
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
Click to expand...
Click to collapse
Generally speaking, wiping data is recommended when flashing a new ROM. Because Giefroot requires older firmware, you need to flash that firmware. Which means a data wipe comes recommended. Technically however, wiping data is optional. It is possible to downgrade without wiping data (by unchecking the respective option in Flashtool). So that is what I'd do in order to recover your pictures.
Once that has been accomplished, along with a backup of all other data you wish to keep, I would start the whole process again as described in the thread I linked to. Because this time, the objective would be not data recovery, but ending up with a stable phone. And that means wiping data. (Highly recommended.)
I don't want to complicate things further, but if you don't care about being rooted after data recovery, you could just upgrade to regular stock firmware instead of pre-rooted firmware. This would allow you to skip a few steps of the process, and also avoid being unable to apply Sony's OTA updates. (Significant updates can cause a loss of root.)
Personally, I would not want to give up root once I have put effort into getting it.
kjoz said:
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
Click to expand...
Click to collapse
If you have successfully imported from the phone into iPhoto, then you simply need to import your iPhoto Library into Photos in Mac.
Check if you can find the iPhoto library by going to Finder -> Home -> Pictures
There should be 2 libraries there - one for iPhoto, and one for the newer Photos app that came along in April. Double-click the iPhoto library and wait for Photos to launch, then follow the instructions to import the library into Photos.
Make sure you have enough disk space (on the Mac) to do this. You'll need at least as much free space as the size of the iPhotos library to import it into Photos and possibly more.
Hi All,
Day by day, another MIUI quirk/challenge... Things that were easy and possible under other phones and stock Android versions seem ever so more challenging under MIUI....
So, I purchased a nice 128GB SD Card to go with the built in storage. Mainly for moving data around, so don't loose it...
However due to Android 4.4 and beyond, Google make it difficult to write access this. However other File Managers and Android versions in past, I've managed to re-enable this. However with this phone, so far I have not found to a way to unlock it yet??
The usual app (FX Explorer) doesn't work, says I can't unlook the root of the SD Card, only individual folders... which it then complains, isn't the root.... (yeah, I know that... you wouldn't let me unlock the root of SD).
I try MIUI Storage settings, but that has nothing in there to unlock it....
I then install Google Files, as strangley a guide says that'll work... it doesn't....
There was then a guide with the stock Xiaomi File Manager to unlock write access to SD Card, yet the options in the guide don't exist in this version. And can't see how allowing access to my Contacts in File Manager and then clearing the settings would fix it anyway?
So now running out of idea's to allow access to SD Card... T'was so simple on other Android devices.....
Cheers, Lister
Update: Seems I am not alone, many have this bug and looks not to be fixed.... or consistently fixed. Very hit and miss....
https://www.reddit.com/r/miui/comments/joxuhi
The plot thickens.... or not, so it seems !!!
So under Developer Settings, there is an options to "Force Write Access to External SD for all Apps" so I have enabled this and it has done..... diddly squat !!!
What's the point of providing an SD Card slot, with no write access...??
Lister
Hi All,
Has anyone had any luck getting an Ext SD Card to be writable between apps....?? As all the usual methods that I know of, and apps (FX) that have worked in the past, don't work.
The OS built in settings don't work, and the hidden Developer Settings to force write access don't work....
So at this point, I am racking my brians why Xiaomi even bothered to include an SD Card slot, as currently its pointless and redundant !!!
I'm having to copy it from the Internal memory, onto PC, then from PC back onto Exteral.... and it's slow as hell and doesn't always work... It's a brand new SanDisk MicroSD purchased from large retail store... So not like its some iffy thing off eBay.
Cheers, Lister
Thats, lets say, weird. i never had that problem, try finding something in the developer options?
if nothing worked, then root your phone i guess
Yeah it's very weird, I've never faced this issue on any of my other phones in the past.... Which have mainly been Samsung's.... S2, S5 and Note 1.... All old and trusty models, had no issues with those phones over the years, they were like TANKS.... just kept on working.
However this phone, I am encountering issue, after issue.... things that worked like stock/standard under normal Android are not working on MIUI.... I can't even get Ringtones to work, just have the 3x ringtones it comes with with no option to add more....
SD Card won't allow me to write at the root of the card, it says create a folder from the root of the card and then make the folder writable. I do that, then the OS complains this isn't standard practice and that I should allow the whole card.... which was what I was trying to do, when it tells me "for my own privacy" not write at the root level... Argghhhhhhhhhhhhhhh !!!!! lol
I am trying not root the phone itself at the moment, as this is the most moddern and recent phone ever purchased and trying to run it as stock with banking apps.... But if pushed, I may try rooting and try masking root at a later date....
But for now, if there is any official non-root ways of making the SD Card work, would be grateful...
Cheers, Lister
Lister Of Smeg said:
Yeah it's very weird, I've never faced this issue on any of my other phones in the past.... Which have mainly been Samsung's.... S2, S5 and Note 1.... All old and trusty models, had no issues with those phones over the years, they were like TANKS.... just kept on working.
However this phone, I am encountering issue, after issue.... things that worked like stock/standard under normal Android are not working on MIUI.... I can't even get Ringtones to work, just have the 3x ringtones it comes with with no option to add more....
SD Card won't allow me to write at the root of the card, it says create a folder from the root of the card and then make the folder writable. I do that, then the OS complains this isn't standard practice and that I should allow the whole card.... which was what I was trying to do, when it tells me "for my own privacy" not write at the root level... Argghhhhhhhhhhhhhhh !!!!! lol
I am trying not root the phone itself at the moment, as this is the most moddern and recent phone ever purchased and trying to run it as stock with banking apps.... But if pushed, I may try rooting and try masking root at a later date....
But for now, if there is any official non-root ways of making the SD Card work, would be grateful...
Cheers, Lister
Click to expand...
Click to collapse
Yeah the root of the sd card is not allowed a lot of phones, i have a lumia 530 (windows phone) and don't have full access, but my huawei p smart 2019 has root of the sd
Hi All,
Just gets better and better..... NOT !!!
Xiaomi why the fook have you included an SD Card reader to your phones, and Google why do you allow the user to VIEW but NOT use additional storage? Might as well remove the SD Card slot and add a 3rd SIM slot.
Then rebrand Android OS to Google-iOS, and continue to lock this sh*t down !!! Utterly pointless....
Google Issue Tracker
issuetracker.google.com
So it seems this is a known issue since Android 11, getting worse in 12 and dread to think by time of 13. So many unhappy and angry users out there over Googles latest changes... So Google lock their DocsUI storage down to secure their devices, thus users are installing unknown apks to try and re-enable it or ROOT their phones to regain the feature back. Therefore reversing what Google are trying enforce... lol
Pity I purchased a 128GB SD for this phone, might as well slamed in a 2GB for all the use it'll get...
Lister
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
hmm
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
Btw, on 4), I didn't need a reboot on A10, just enabled write access, then updated. Your mileage may vary, though, with A11+.
Lister Of Smeg said:
Hi All,
Day by day, another MIUI quirk/challenge... Things that were easy and possible under other phones and stock Android versions seem ever so more challenging under MIUI....
So, I purchased a nice 128GB SD Card to go with the built in storage. Mainly for moving data around, so don't loose it...
However due to Android 4.4 and beyond, Google make it difficult to write access this. However other File Managers and Android versions in past, I've managed to re-enable this. However with this phone, so far I have not found to a way to unlock it yet??
The usual app (FX Explorer) doesn't work, says I can't unlook the root of the SD Card, only individual folders... which it then complains, isn't the root.... (yeah, I know that... you wouldn't let me unlock the root of SD).
I try MIUI Storage settings, but that has nothing in there to unlock it....
I then install Google Files, as strangley a guide says that'll work... it doesn't....
There was then a guide with the stock Xiaomi File Manager to unlock write access to SD Card, yet the options in the guide don't exist in this version. And can't see how allowing access to my Contacts in File Manager and then clearing the settings would fix it anyway?
So now running out of idea's to allow access to SD Card... T'was so simple on other Android devices.....
Cheers, Lister
Click to expand...
Click to collapse
I changed my SD card to another version and my problems were fixed... I don't know if it will help others bud I now associate the problem with my SanDisk as it is not working in my other Redmi
Be aware that when swapping cards, even if you had previously granted card write access, you'll get into the same problem again with the new card. Is it related it to FX not relying on system file transfer app to handle permission, but doing it on its own, instead?
Equally, bookmark links, which are linked to the card's individual path (/####-####/), once you swap card, won't work anymore, either.
Unfortunately, seems none of these and other reported issues seem will ever be fixed, so maybe it's time to move on...
Btw, wonder if this still works...?: NextApp SDFix
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
thank you also @xetc for reporting the fix first. I was experiencing this on my secondary phone with LineageOS 17.1/ Android 10.
@tliebeck can you revisit the v. 8.0.3.0 code and re-implement the way you enabled media card write access in that version back into the current version? Obviously something got twisted (and has been ever since v. 8.0.3.0 +)
Above all, thank you for your app !!
Not sure why to use FX Explorer. I use Total Commander and it works to the ext SD card fine. (NOTE: Be aware that if you update to the 3.33 version or higher, you will lose the ability to install apps manually from the SD card. Blame Google! You can solve this by signing it with your favorite app (like apk-signer) so Play won't keep telling you there is an update to the program.
Lister Of Smeg said:
Hi All,
<< Credit, where credit is due... as no other solution all over the web worked... other than below >>
Thanks to @xetc , with regards to this post... Ext SD Card write access has been resolved and can now make use of my 128gb Micro SD Card again... Yaaaaaaay....
Fault: If you're running Android 11, or higher. You will now find you cannot write/make use of your External MicroSD Card as Google have now blocked this. Android 10 is not as restricted, and Android 9 or below is not affected by this issue.
Solution: Download and use FX Explorer v8.0.3.0
To re-summarize steps...
1) If you already have FX Explorer installed, remove it.
2) Then download specifically FX Explorer v8.0.3.0 from your usual source.
3) Then click the top right corner, and select [Enable Write Access] at the bottom of the menu and follow prompts.
4) Once completed, reboot your phone.
5) Now test, to make sure you can write between internal to external, if all good, proceed to update.
6) Now grab the latest version of FX Explorer, once updated, re-check that you still have write access.
Happy days....
Lister
Click to expand...
Click to collapse
The old 8.0.3.0 from December 2020 is now a 7-day trial app, and step #3 does not produce any "enable write access" from the top right hamburger menu. I enabled root/developer access in its settings but no difference.
EDIT: though I see no "enable write access" anywhere the app, I can read and write to it, and send files from it to Drive, the last 2 things fail on my RN11. Both are on custom ROMs on A13. So, this has to be a developer's issue in the ROM, OR something with the card itself. I will keep testing to see what I can find.
i.e. this no longer works (NOTE: this might just be an SD card issue. I am able to write to and send files from an external SD on a different ROM on a different A13 phone - Redmi Note 10 Pro - without any permissions stalls at all using Total Commander 3.31, for example.)
xetc said:
Be aware that when swapping cards, even if you had previously granted card write access, you'll get into the same problem again with the new card. Is it related it to FX not relying on system file transfer app to handle permission, but doing it on its own, instead?
Equally, bookmark links, which are linked to the card's individual path (/####-####/), once you swap card, won't work anymore, either.
Unfortunately, seems none of these and other reported issues seem will ever be fixed, so maybe it's time to move on...
Btw, wonder if this still works...?: NextApp SDFix
Click to expand...
Click to collapse
Nope. It produces an error. "Platform permission file is invalid. no groups specified in WRITE_EXTERNAL_STORAGE"
Sheist! said:
The old 8.0.3.0 from December 2020 is now a 7-day trial app, and step #3 does not produce any "enable write access" from the top right hamburger menu. I enabled root/developer access in its settings but no difference.
i.e. this no longer works (NOTE: this might just be an SD card issue. I am able to write to and send files from an external SD on a different ROM on a different A13 phone - Redmi Note 10 Pro - without any permissions stalls at all using Total Commander 3.31, for example.)
Click to expand...
Click to collapse
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Lister Of Smeg said:
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Click to expand...
Click to collapse
The problem is I have other apps that need to write to the SD and at this point they started failing. I don't suspect A13, as CherishOS does not have this issue on RN10P, OR the SD card I am using on that RN10P phone is error-free. My card would not read in the crDroid recovery in my RN11 UNTIL I formatted it in Windows with NTFS. Even formatting in the phone in exFat gives an exFat error in the incorporated crDroid recovery! This is probably still some issue with my card or its formatting, as I don't see noise on this issue from other users. My external SD was working fine for my write/copy-to apps on A13 until I fixed the issue getting it to read in crDroid recovery, which oddly I don't even need anymore! (successfully installed TWRP to ramdisk now). I need to reformat back to exFat and see where I am. If good, then I will reply again.
Lister Of Smeg said:
Hi @Sheist! ,
All versions/editions of FX Explorer are considered a Trial edition when first installed... You can enable full features for a 7 - 14x day trial to which it reverts back to limited features. You only miss out on the bonus, networking/app management and few extra controls/filesystem features.... All the core Explorer features are still there...
This method was correct and accurate at the time of testing, which I believe I was on Android 11, as I don't think A12 was around at the time. Since upgraded to A12 afterwards it has still kept write access to the SD Card enabled after the hack.
I've not tried this method on A13 yet, as I am still on stock rom. However, each release of Android, from version 10 upwards keep tweaking SD Card usage, and restricts access to it more and more... So A13 could well have issues, don't know.
Personally, when I tried Total Commander back on A11, I couldn't get it to work at all (despite reading a guide somewhere) saying to use this. I tried all the various apps out there, one even suggested using the MiExplorer. No method worked at all, apart from that very specific release of FX Explorer, and when tried worked like a charm. As it always has done since Android 4.4x when Google first started messing around with SD Cards. I believe Android developers were asked to remove such features from their File Manager apps, hence why after 8.0.3.0 this feature disappeared.
There was a method briefly, using Googles own "Files" app, known as packagename "My Documents" or something like that... This feature only worked on Android 11, and had limited access when enabled. However as this is often a system app, and without root... Trying to disable, debloat, replace this app... this method also was fiddly and didn't work.... the only sucess that worked for me was what was mentioned above.
I tried practically everything, and was at the point of giving up and annoyed I wasted money on a 128GB SD card not to be used... until I stumbled on the above. Relieved it worked, and thought if it helps others in similar position, share the info... as I read pages and pages (forums/Googles own documentation) on how its disabled, how it no longer works, workarounds that didnt work... I believe it should still work for A11, and poss A12 roms (does via upgrade), however not personally tested on A13.
Cheers, Lister
Click to expand...
Click to collapse
I reformatted in the phone again (exFat) and all apps work fine again to/from the external SD card. I am on TWRP so I don't care about the installed crDroid recovery issue anymore. (A13, crDroid 9.3, TWRP 3.7.0_12-0)