I'm running stock Android 2.2 and just rooted my phone yesterday. Since rooting my phone, I've had the following issues:
Cannot create a new folder on internal SD card ("The file '<%1 NULL:NameDest>' is too large for the destination file system") from computer while in mass storage mode (I can in media player mode)
Cannot copy/move files to internal SD card while in mass storage mode (I can in media player mode)
Cannot download from browser to phone using computer (I tried downloading an apk file from xda but it just kept trying to download.
Cannot download from mobile phone browser ("Cannot download. The content is not supported on the phone")
That's all I can think of for now, but you get the idea. I think it might have to do with the fact that I didn't unmount the internal SD card before rooting my phone (I don't think there's a way, but perhaps I rushed).
Is there any way I can fix this? Thanks in advance
Edit: It only affects the internal SD card. I put an external SD into it and it works fine.
I've been having pretty much the same issue since day one with this phone. While in Mass Storage, I cannot transfer files onto my phone. I can create/delete folders in the file tree though.
I would greatly appreciate any information you folks can come up with.
I have the same issues on a china-phone running 4.4.2 , is there any solution to this?
Also apart from these, but i think is due to the same bigger problem, i have some random issues with the gallery: it fails to load some images and it crashes.
Bluetooth transfer fails due to storage issues, yet i have some gbs free (internal or phone), and the files are just mbs.
I cannot copy some files from my phone to my pc, it keeps showing some errors (which appear to be due to FAT-FAT32 format, but in reallty i have no clue).
My phone is rooted, but it seems like i have no rights over the storage control... and that makes me real sad.
Any suggestions?
Sucore said:
I have the same issues on a china-phone running 4.4.2 , is there any solution to this?
Also apart from these, but i think is due to the same bigger problem, i have some random issues with the gallery: it fails to load some images and it crashes.
Bluetooth transfer fails due to storage issues, yet i have some gbs free (internal or phone), and the files are just mbs.
I cannot copy some files from my phone to my pc, it keeps showing some errors (which appear to be due to FAT-FAT32 format, but in reallty i have no clue).
My phone is rooted, but it seems like i have no rights over the storage control... and that makes me real sad.
Any suggestions?
Click to expand...
Click to collapse
It's hard to help/support a phone we don't know about. What device do you have exactly? Which root did you use? Also, FAT32 isn't supported by quite a few devices, I would suggest using a different format.
I have an Mpie t6s, which i believe is kinda new cause i haven't been able to find anything on the net.
I have failed to create a backup due to "task ended with error" from MTKDroidtools, and i was trying to find a rom that works. I couldn't.
So now, i have it with the rom of a similar model, mpie 909t, but the problems remain.
I have sort-of realized that the gallery issue was created because i didn't ejected the drive from My Computer (yea, it has Mass Storage, and MTP, and camera mode when i connect it to PC.
I read that 4.4.2 and mass storage are not compatible, and it came to me.
I rooted it with iRoot that was the only that worked.
I removed all the Chinese &(@$^ but i kept iRoot's Superuser because i thought that with SuperSU all the problems where returning (that was before i realized the issue with mass storage and safe remove).
BWolf56 said:
It's hard to help/support a phone we don't know about. What device do you have exactly? Which root did you use? Also, FAT32 isn't supported by quite a few devices, I would suggest using a different format.
Click to expand...
Click to collapse
So i came to realise that the internal sd is 69MB (after i repartitioned it and made 2.5gb the interal for apks), so i think this is the main problem!
Formating via windows showed me that size, at first i thought it was something wrong (everywhere else in win the size was 29 GB) but now i manage to deal with that.
Prefer that than an always crashing phone.
ExtSD to the rescue!
Related
Hi all
I rooted my phone today. I then installed clockworkmod and saved a stock backup. Following that, I successfully enabled 3 button recovery.
My problem appeared either after rooting or after clockworkmod. The problem was there prior to enabling 3 button recovery. I suspect it was clockworkmod that caused the problem.
Anyway, when I connect the phone to the computer the 16gb internal sd card & 2gb phone storage appear as removable drives in 'my computer'. However, double clicking on the drives gives the message 'no disk in the drive, please insert one'. Windows can't read the usable file space, browse or even format the drives.
However, I can browse the internal sd card fine using any android file manager.
Also, I can use adb to push/pull files.
What is going on?
I need to know quite quickly what to do. I initiated a phone repair with my carrier due to the mtp crash bug, so they are expecting it to be returned pronto. If the phone is stuffed, I'll send it back. If this can be fixed, I'll keep it since I managed to get the three button recovery working.
Also, I think there's a boot rom or something to do with clockworkmod still installed? How do I get rid of that if I'm sending the phone back. I know how to unroot.
Edit: I just found an external sd card to test. I formatted it in windows by using a sd card reader, then when I plugged it into the phone and tried it as a mass storage device windows didnt like it. Putting it back into the card reader one last time and windows recognised it. Makes no sense....
Edit2: In kies mode, kies can access it. And also it adds a 'galaxy s' to my computer where the internal sd card actually works... now I'm even more confused!
Have you tryed formatting your internal Sd or useing recovery 2e and factory resetting your phone?
I've tried formatting it and reset via settings->privacy->factory reset data.
Is 3 button recovery any different to the above type of reset? What will it roll the system back to?
(The recovery image I made in rom manager will have the same problem. I dont currently have an update.zip on my sd card due to formatting it, but I can get one on there using adb if I need to.)
quitestuck said:
I've tried formatting it and reset via settings->privacy->factory reset data.
Is 3 button recovery any different to the above type of reset? What will it roll the system back to?
(The recovery image I made in rom manager will have the same problem. I dont currently have an update.zip on my sd card due to formatting it, but I can get one on there using adb if I need to.)
Click to expand...
Click to collapse
Is your usb debugging on by chance? If so, turn it off ans reconnect the phone to the pc.
Mine does this when usb debugging is on and im on a stock eclair rom... Hope it helps...
Sent from my GT-I9000M using XDA App
That thought occurred to me too. Definately off. Ive checked it many many times now
When I first used adb, I simply pulled the plug out. I couldn't see any 'quit debug' command. There are start/kill server commands, they dont seem appropriate. Doesnt look like I should have had to do anything other than just pull the cable out.
Update:
I think that the update.zip's applied to my phone have changed some software to an earlier version that what my unit was shipped with.
When I first got the phone, I just plugged it into the pc and selected 'mass storage' on the phone. The drives then appeared (and worked) in windows.
Now, I have to click mass storage. That on its own isnt enough. But if I pull-down the tray menu at the top of the screen, there is another option to click (something along the lines of 'select this to transfer files between your phone and pc'). If I click that, it works.
There are some slight differences still:
1) I could swear that my phone originally allowed access to the 2gb phone internal memory (I never tried reading/writing to it, but I'm convinced windows displayed a 2gb drive).
2) I used to get the "xx/13.4gb free" under the drive letter in 'my computer', which I now only get in the status bar at the bottom of windows file explorer.
QUESTION
Does everybody else have to click "mass storage mode" AND pull down the task bar and click "transfer files" to get the internal sd to work as mass storage in windows?
Or do they just have to click "mass storage mode" and that's all?
Thanks
I always had to pull down the menu and manually mount the sd card when using mass storage.
Sent from my GT-I9000M using XDA App
Definately wasnt the case on my phone (bought mid october, so its quite new) because I got my music on there via mass storage twice before 'hacking' it. I couldn't have done that without knowing about the extra buttons to press. It's good to know that it's just a side effect of the update.zips I've applied, and that I get to keep the phone
Cheers
Im having issues with the internal SD card after the update. So is Dennishwc
http://forum.xda-developers.com/showpost.php?p=10484065&postcount=1057
Via Windows 7 64 "Error 0x80070057:The parameter is incorrect 'for file copy and 'The file is too large for the destination file system' when I try to make a folders.
When I try to format in Windows, it shows capacity only as 2.19GB rather than 13gb or whatever it should be. Same occurs on a Win XP laptop I tried, but explanation of the errors are more general but seem to be the same.
Seems it might be this issue that 2.2 caused for the SGS Vibrant ?
http://forum.xda-developers.com/showthread.php?t=860328
http://forum.xda-developers.com/showthread.php?t=846384
Could just be the SD card failing unrelated to the update, but I have no idea. Seems I can copy to an external SD, and then copy via the phone to the internal SD. Odd.
I have tried format via Windows, which resulted in 2.19gb size, but phone reboot reset it to 13gb. Format via phone did not resolve either.
Any fix that will work? or is it borked.
I'll repost my question here.
Did you try the "format internal-sd" from CWM recovery ?
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
rye&ginger said:
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
Click to expand...
Click to collapse
Download Rom Manager from the market and run it. Click on install clockworkmod recovery. Then you can reboot into recovery. Please see the clockworkmod thread for more info
Sent from my SGH-I897 using XDA App
Don't forget to root first. I had a pain rooting this JL1. I spent 20 minutes playing with JL1 and I couldn't stand the lagginess. I'm sure lagfix would've helped, but I just went to a custom ROM instead.
Tried superoneclick only once and I'm rooted even went as far as unlocking it. Also, my phone isn't affected by the sd card bug. I can transfer files bigger than 2.19 Gb and it's showing the full size in Windows. Froyo runs flawless so far even though it's still not clear whether it's official or not.
Hmm, that's an odd one indeed.
Curious - I took a look at the 2 threads that Rye pointed out and one seems to be about external sd issues and the other about the mounting issues with 2.2 vibrant kernels. Doesn't seem like the problem you are having is either one of those... Could be but didn't seem that way upon review.
Did you happen to try and restore any backup after upgrading to 2.2 or anything? Can't imagine what would cause it but seems like it's getting mounted strangely or something... Surprised that a format internal sd wouldn't fix it in recovery...
Second question - what Samsung drivers / driver pack are you using on your Windows 7 x64 install? Wondering if the driver is failing to recognize the file system type and is causing Windows to treat it as a file system that shouldn't accept a file larger than 2+GB...
I havent noticed any problems with the size of the file. What happened with mine is that i transfered a couple of movies (about 3 or so) and then transfered about 4 gigs of music. halfway through the music it started giving me the error. after that, even transferring individual mp3 or pictures would result in an error. The internal sd card showed up on my computer as having 8gig free. after that i ran the check disk (by right clicking, going to properties then tools). my computer found errors and corrected them. after that, the internal sd card showed up as only having like less than a hundred mb left
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19gb.
Im about to do the CWM recovery format and will post the results.
If you are using the Rogers 2.2 update with no kernel modifications then the CWM will not work for you.
The Froyo kernel from Samsung comes with Recovery 3e which RomManager can not replace for 2e as 3e requires digitally signed packages.
consider (i have not tried):
- root device
- adb shell
- su
- backup any files you need on /sdcard to /sdcard/external_sd
- use the format commands to re-format /sdcard
-- probably mkfs.vfat or the like.
rye&ginger said:
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19GB.
Im about to do the CWM recovery format and will post the results.
Click to expand...
Click to collapse
Yea, really not sure if the drivers are a problem or not. When I checked mine, running the Rogers 2.2, it shows the same as what yours does in the format utility - 2.19GB. That is odd because it seems to set the filesystem type as FAT32 which can easily handle the 13.0GB size of the volume. The properties in Windows show 13.0GB w/ about 11.0GB on my disk that is available...
Regardless, I would be hesitant to format or repair that disk within Windows. Who knows if there is something within Android that is put there as a translation layer that maybe Windows isn't seeing / reading correctly through the driver, etc. I'm sure someone does know but I'm not that guy so if anyone call fill in the details...
And, after just testing on my own system... bang, same issue trying to copy a 900MB file to it... Hmm, this just got interesting.
Going to check a couple of other things, will post result.
I had this exact same issue. The only fix for it that I could find was to do a complete restore of the stock rom. Oh well, nice to have a fresh phone.
Hmm, this is not a fun problem.
Just tested formatting the volume - from within the running phone only, mind you - and the result is strange. After copying everything from my SD card to my computer, with no issues, I unmounted the USB, formatted the card through the settings / sd card storage menu / format internal sd card. Took about 30 seconds after which point I reconnected the device, windows picked it up and I mounted it, recopied about 2GB worth of data to the card with no issues at all. Added an additional 500MB file to it with no issues. Disconnected the device from within windows using the safe removal tray tool, turned off usb connection on the device and then unplugged it. Remount the usb device and windows sees it no issues but I can't copy a single item or create a folder on it. Exact same errors as what Rye described and I encountered the first time.
So, seems like after a fresh format the sd card can be mounted in windows, ONCE, and then all hell breaks loose.
Why??? Will keep testing but looking like I need to move back to my previous di11igaf's ROM. Can't work like this...
Interested in what you find, Rye.
Oh btw, i am able to transfer files with no problems if i connect to the pc in media player mode. I have problems when i am in mass storage and kies connect modes
Riker2k, good stuff. I have no news, Im stuck where I am unless I swap the kernel it seems as I cant use CMW Recovery to format.
This is over my head, so I will for now probably just do a format, load up the card via Windows, and then use the external card to slowly add items when I want to and transfer over to the internal through the handheld. Ghetto. Either our Sd cards will get worse and die, or more people will have issues and it will get patched I guess?
Dennishwc, I will try media player mode but I think it did nothing when I connected that way the other day. I didnt mess with it much though. I need mass storage to use iSyncr app though, but there is a wi-fi add-on that may help me avoid that.
Well I just tried the format and dump a lot of stuff via Windows idea, and it only did about 2.2gb before the error stopped the fun. It did this twice, so this is is EXACTLY at the 2.19gb capacity that Windows is seeing in the format utility. So, I do have some news.
Again, this is over my head as to what to do next.
Has anyone tried moving files over via adb and see if you hit a 2.19GB limit?
I am having the same issue when copy files while connected in USB Mass Storage Mode (consistent).
On the plus side, I also tried connecting in USB Kies Mode, and I have yet to see this error. Copying is slower; but, it seems to work.
This could be a workaround for folks getting the error in Mass Storage Mode.
I am running Rogers 2.2 (all stock) and rooted with SuperOneClick.
i'm having the exact same problem. if i pick "mass storage" i can't copy anything over hte internal sd card, but if i use "media play" option, i can do it without any problem. i guess that's a temporary solution
i'm having the same problem, though the size and free space of the internal storage shows up correctly in my system.
i can also copy files no problem to the external SD when in mass storage mode.
Hi folks,
the Android Media Scanner is deleting files stored on my ext. SDCard.
First I thought the card is broken but then I found this:
h_t_t_p:_/_/code.google.com/p/android/issues/detail?id=3692
Is anyone else having this issue and/or got a solution for it?
Thanks!
Edit: I am on CM7 n82 currenty
Probably own fault. Might be cause by mounting ExternalSD wrong way.
See updated thread andr. Dev.
Sent from my Optimus 2X using XDA Premium App
Media files being deleted from SD card
gonzalesdlx said:
Probably own fault. Might be cause by mounting ExternalSD wrong way.
See updated thread andr. Dev.
Sent from my Optimus 2X using XDA Premium App
Click to expand...
Click to collapse
Gonzales,
I updated from Android 2.3.4 to 2.3.6 this weekend, and the problem started. I came across both threads at the Android Developers forum, and found no solution.
You do mention above that it was "probably your own fault... see updated thread". Well, I did read the updated threads, and found no solution.
You hint that it has to do with the way the card is mounted/unmounted. And this weekend I did in fact mount/unmount the card various times, connecting it to the PC.
But what exactly did you do? Did you find a solution?
Thanks,
[SOLVED] Media Scanner Deleting Files from SD Card
OK, I believe I found the solution. Apparently the problem can be caused by the SD card being mounted and/or unmounted properly. In my case, I was connecting/disconnecting to/from the desktop PC, having the SD card as Mass Storage. At one point, Android wasn't detecting it anymore so I removed and inserted it a few times.
I did what I describe on the same thread at Android Developers: http://code.google.com/p/android/issues/detail?id=3692#c117
Here's what I wrote there:
So I did the following, and it seemed to solve.
1. Connected phone via USB to desktop PC, and dismounted card from phone, allowing data transfer to PC (via Mass Storage Device)
2. In Windows, as a test I created various folders with subfolders, with image files in them. On some I placed a .nomedia file in root and sub-folder, other only in root, others I renamed the sub-folder to start with a ".", etc. (NOTICE: I copied existing .nomedia files from other folders, as Windows doesn't allow files/folders starting with "." to be created)
3. In Windows, I ejected the USB drive politely (i.e.: I didn't just pull the cable out)
4. On phone, opened Settings/Applications/All and found Media Storage
5. Deleted data from Media Storage
6. On phone, I disabled the external access (file storage)
7. Waited patiently until SD card was detected and mounted (previously, I tried forcing that to happen by opening applications that would query the SD card)
The phone performed the Media Scan a couple of times, and ALL MEDIA FILES REMAINED THERE, where they would originally have been deleted from.
In all test folders I created from within Windows, no files were deleted. And in folders that originally had media files (which I didn't touch through Windows), the files no longer were deleted.
Anyway, this seems to have fixed it for me.
My system:
Samsung Galaxy Ace, Android 2.3.6, rooted.
An extra hint: if you feel you card access is slow, get an app like SD Booster and increase the cache size. On my device, it was as low as < 100Kb but increasing it to 1024Kb made a huge difference.
And if you don't want the media scanner to run on boot (increase boot speed), use Rescan Media Root.
Both need root access, by the way.
Click to expand...
Click to collapse
And I've had no problems at all ever since, and even mounted/unmounted a couple of times.
Hello. This is my first post, but I have been a reader for a while. I recently bought Samsung Galaxy Note. Rooted it using the ZergRush exploit and installed CriskeloROM v0.6.
It worked perfect for a week, but then something wierd happened.
On my way to work I got out of the door and opened spotify as usual, but the screen just blinked and the app didn't start. When I looked into this it seems as if the phone won't recognize the SD card.
Saying that the phone won't recognize the SD card isn't entirely true. The phone know the card is there, but it appears as full.
USB storage: Total space 11.08GB - Available space - 0.00B, not even a single byte.
When I hook the phone to a pc, I can see that I in fact have about 8GB of free space. I can also without problem browse all the files as if nothing was wrong.
The things I know I have done that might interfere with it is that the other day I was going to copy some wallpapers into my phone. To do this I was required to encrypt the disk station using BitLocker. I have also by accident disconnected my phone without dismounting.
I have done alot of searches in google and on this site, but I have yet to find someone with the exact same problem as me.
I have tried to take out the battery and leaving it out for 15 minutes.
I excuse the wall of text and my poor english.
Thank you
Dagnit said:
Hello. This is my first post, but I have been a reader for a while. I recently bought Samsung Galaxy Note. Rooted it using the ZergRush exploit and installed CriskeloROM v0.6.
It worked perfect for a week, but then something wierd happened.
On my way to work I got out of the door and opened spotify as usual, but the screen just blinked and the app didn't start. When I looked into this it seems as if the phone won't recognize the SD card.
Saying that the phone won't recognize the SD card isn't entirely true. The phone know the card is there, but it appears as full.
USB storage: Total space 11.08GB - Available space - 0.00B, not even a single byte.
When I hook the phone to a pc, I can see that I in fact have about 8GB of free space. I can also without problem browse all the files as if nothing was wrong.
The things I know I have done that might interfere with it is that the other day I was going to copy some wallpapers into my phone. To do this I was required to encrypt the disk station using BitLocker. I have also by accident disconnected my phone without dismounting.
I have done alot of searches in google and on this site, but I have yet to find someone with the exact same problem as me.
I have tried to take out the battery and leaving it out for 15 minutes.
I excuse the wall of text and my poor english.
Thank you
Click to expand...
Click to collapse
When you boot into recovery and mount internal SD is the info correct there?
Thanks for the answer!
When I boot into recovery, witch I thought was CWM but witch turns out to be HyperDroid RedPill Recovery, probably changed when I installed the ROM (?), I can choose
- Mount internal SD
Witch leads me away from the menu and into a new little menu.
"USB Mass Storage device. Leaving this menu unmount your SD card from you PC.
-Unmount
-+++++Go Back+++++
And that's it.
However when I try to actually do a recovery (the recovery file is in the internal SD) I get the message:
"HyperDroid RedPill Recovery
E: Unable to write to usm lunfile (No such file or directory)Error mounting /sdcard!
E:Can't mount /sdcard"
do you have an external sd card in the phone? some kernels seem to swap the internal and external about
No I do not. Thanks for the answers guys!
Hello.
This is my first post.
I have seen the noob video, I know I am not special. And still:
I have searched the forums, but my problem is different. Most of the posters don't know what caused this error. I know what caused mine. I have actually unexpectedly removed the SD Card. Kind of. Funny story: transferring data (green bar on windows not loaded at all, window stuck on calculating time/finding files etc -technically no data has been transferred), windows explorer decides to go all "Not responding" on me (thank you microsoft). The genius in me tells me to unplug the phone, so I do. Yay! explorer.exe is ok now. Too bad my SD card isn't.
There are some files on it... but none of the folders that I created, so I lost everything except photos and stuff. I have backed them up on my PC. When I connect my phone (which I have to do manually by going into USB settings so that my PC recognizes anything -auto play doesn't appear anymore-), instead of showing up as my phone, it shows up as a media device with stuff on it (folders like Android, DCIM, but none of my manually created folders containing music etc.).
I repeat, I have actually unexpectedly removed my SD card.
I right clicked on the drive in the PC and clicked Format. It warned me. I didn't care, I was desperate. In just one second, it said formatting complete. No files missing, however (still those Android, DCIM etc. folders).
I have a Samsung Galaxy S Advance GT-I9070 (this forum section, I think). I have flashed the I9070XXLQ4 (android 4.1.2) from Russia on it (a few weeks ago). Not root, or any custom ROM's.
Recap. I have unexpectedly removed my SD card. I want my games back. Or at least formatting it, making it usable.
Formatting the SD card from the phone settings has done it. I am a noob.
try formatting the sdcard on your phone thru the settings>storage..
re-download all your games or transfer them on the sdcard after the format.. if you have back up on your pc or other storage..
as for your pc.. try a reboot.. to correct the drivers of your phone as storage device..
jaycm1130 said:
try formatting the sdcard on your phone thru the settings>storage..
re-download all your games or transfer them on the sdcard after the format.. if you have back up on your pc or other storage..
as for your pc.. try a reboot.. to correct the drivers of your phone as storage device..
Click to expand...
Click to collapse
Thanks, I've managed to do that before you posted (but I'm a noob and I can't edit posts so quickly). It did it. Although I was hoping not to lose everything.
vici30 said:
Thanks, I've managed to do that before you posted (but I'm a noob and I can't edit posts so quickly). It did it. Although I was hoping not to lose everything.
Click to expand...
Click to collapse
is your sdcard a genuine one?.. no offense.. but there are a lot of fake sdcards in the market today..
actually i have a fake one.. its 8gb.. now, half of it is corrupted already.. my tablet hung due to it..
Hi guys.
I hope it's not the wrong thing to revive this old thread.
I was recently installing an RUU onto my phone. After the install completed, the phone restarted and it began checking the SD card again for an RUU - and it found one, as I had not by then removed/renamed it. So, after waiting for it to verify the RUU, selecting "no" to installing it, it restarted again and again it started looking for an RUU. By this time, I was getting impatient, so I tried to remove the SD card quickly before any actual data access happened.
WRONG
My SD card became RAW, inaccessible to Android or Windows. Testdisk and various free versions of paid-for undelete tools (like EaseUS) found only files from waaaaay back, before I had ever used the card in Android. As a precaution, I took two RAW copies of the full card onto two harddisks and compared the MD5 of each (match).
A little wary of the risk of using various features of testdisk, I thought the best thing to do next was a format (not quick format) to exFAT in windows and run all the undelete tools again. No results. Then I found this thread and, as suggested, tried formatting using Android. All software returned no results again.
What else can I do? The contents of the card should still be as they were (unless the formatting twice effected that). Am I correct to assume that the card (128gb) would have been formatted exFAT by Android 5/6?
In testdisk, are "superblock" or "boot" forms of recovery any relevance to me?
Thank you!
(PS: Android is working fine, I'm only having problems with the SD card contents)