My camera doesn't work anymore. Only a text box pops up which says "Camera" has been shut off (roughly translated form German).
Then I installed the google camera App from the PlayStore which at least opens and shows the live view through the camera on the display. So it's not (completely) a hardware problem. But there's an error message above the release button which says "insert SD Card" (again roughly translated). The SD Card Error message also appears of I want to start the Gallery App (it's the standard app where the pictures/Photos are stored).
Possible Complication:
I might have done some deep damage to the system beforehand, for which the not running camera is just a symptom:
A couple of days ago I installed CM11 (M9) and did more than the usual FullWipe. I went into CWM 6.0.5.0 and formatted anything I could find without knowing what I did, like /System, /sdcard0, etc (I know, it's stupid). I might even got some error messages (don't remember exactly). However, I could install M9 afterwards but the problems with the camera and gallery since then.
Then I repeated everything, formatted even more, like, sdcard0 in different formats as vfat (didn't work), then ext2/ext4...almost all of those. I tried different external SD cards, too, formatted them in ext4, later in Fat32. It seemed in one install that SDcard0 and SDcard1 got mixes up by the installer.
Then I also played a bit with the root rights. All those combination didn'T repair the cam. So here I am asking for your help.
Edit: godlessfather from the CyanogenMod-IRC solved it for me - I formatted my internal sd-card in ext4 which caused the issues. Now that I formatted it on vfat and made a clean install, it's all good. kudos to him!
Hi
I'm a newbie and installing a custom ROM first time. I have the same issue. Can you tell me the steps to format internal-sd card in vfat?
Thanks
SGE2010 said:
My camera doesn't work anymore. Only a text box pops up which says "Camera" has been shut off (roughly translated form German).
Then I installed the google camera App from the PlayStore which at least opens and shows the live view through the camera on the display. So it's not (completely) a hardware problem. But there's an error message above the release button which says "insert SD Card" (again roughly translated). The SD Card Error message also appears of I want to start the Gallery App (it's the standard app where the pictures/Photos are stored).
Possible Complication:
I might have done some deep damage to the system beforehand, for which the not running camera is just a symptom:
A couple of days ago I installed CM11 (M9) and did more than the usual FullWipe. I went into CWM 6.0.5.0 and formatted anything I could find without knowing what I did, like /System, /sdcard0, etc (I know, it's stupid). I might even got some error messages (don't remember exactly). However, I could install M9 afterwards but the problems with the camera and gallery since then.
Then I repeated everything, formatted even more, like, sdcard0 in different formats as vfat (didn't work), then ext2/ext4...almost all of those. I tried different external SD cards, too, formatted them in ext4, later in Fat32. It seemed in one install that SDcard0 and SDcard1 got mixes up by the installer.
Then I also played a bit with the root rights. All those combination didn'T repair the cam. So here I am asking for your help.
Edit: godlessfather from the CyanogenMod-IRC solved it for me - I formatted my internal sd-card in ext4 which caused the issues. Now that I formatted it on vfat and made a clean install, it's all good. kudos to him!
Click to expand...
Click to collapse
Related
Hello,
I'm trying to get A2SD working in my HTC Hero. I'm using MoDaCo Custom ROM 2.9. What I did was partition my SD card using a card reader and Ubuntu Linux (I used an application called GParted). I used the following partition table:
Patition 1: FAT32 (730MB)
Partition 2: Ext4 (512MB)
Partition 3: Linux Swap (32MB)
Then, I went to recovery mode and reinstalled MoDaCo. The installation went fine, and I have the impression A2SD is trying to use my Ext4 partition. However, the applications Google Maps and Google Sky Map (which I've just installed) crash almost every time, showing the following message:
"The application Google Maps has stopped unexpectedly."
I suspect the problem is either the Ext4 format (which I believe is new) or my SD card, which is a SanDisk 8GB microSD (class 2).
Do you guys think I should buy a better card? Or format it again? Is it OK to format the card in Ubuntu? Or is something else wrong?
Thanks a lot,
Tiago
I'm trying to reinstall the apps that are crashing, and that seems to be working. However, I couldn't figure out how to reinstall Google Maps. I uninstalled it, but I didn't find it in Android Market. Is there an easy way to install Google Maps?
I think what's causing the problem is turning the phone on without the SD card. The apps that were installed to the card disappear from the list, but if I restart the phone with the card in, the crashes start.
Does that make sense?
Check to see if you have swapper installed this is not needed in 2.9 and could be the cause of the crashing. For that matter nor is the Swap partition. Google Maps can be got here:
http://www.androlib.com/android.application.com-google-android-apps-maps-jw.aspx
and yes starting the phone without the SD Card in will cause any apps on the EXT4 partition to dissappear.
If you reformat the card you will have to re install the apps anyway.
Thanks for the answer! I don't have Swapper installed. I was going to install it, but I'll follow your advice.
I ended up formatting the card again and reinstalling MoDaCo. So far, I haven't taken the card out and everything's working fine. I'm pretty sure what caused the crashes was the fact that I started the phone without the SD card. The apps in the card disappeard, but when I restarted the phone with the card in, the apps that reappeared were not functional (they crashed every time). Is this a known issue or were the apps supposed to resume working?
I guess the final advice is to keep the card in at all times...
The thread says it all. I have a rooted EVO LTE running the CM 10. Everything was working fine until I accessed the SD Card from within TWRP to copy a file. Now I get errors when I look at the command line within TWRP "failed to mount /sdcard {Invalid argument)". Can anybody help me? Thanks so much to all of this community.
finman76 said:
The thread says it all. I have a rooted EVO LTE running the CM 10. Everything was working fine until I accessed the SD Card from within TWRP to copy a file. Now I get errors when I look at the command line within TWRP "failed to mount /sdcard {Invalid argument)". Can anybody help me? Thanks so much to all of this community.
Click to expand...
Click to collapse
I currently have the same problem and mannnn am I f'n pissed.... i did a factory reset from within the bootloader which is what caused mine to stop working right...anyways I am also looking for a solution so when i do I will give you the info.
zoned_out said:
I currently have the same problem and mannnn am I f'n pissed.... i did a factory reset from within the bootloader which is what caused mine to stop working right...anyways I am also looking for a solution so when i do I will give you the info.
Click to expand...
Click to collapse
The only way I was able to fix this was to mount the SDCard over USB in Recovery Mode and reformat it. I lost what was on there, but it's working now.
I formated my card through windows 7 and I still have the same problem. I never had this issue on any of my previous rooted phones I am really gettin pissed with the lte...
Sent from my EVO using xda app-developers app
Are you guys also having trouble accessing the Camera? Mine doesn't seem to pick up my SD card and only allows me to use the Camera using external storage...
Well when I pull my camera up my phone days " no external storage available" then at the bottom if my screen another pop up says "insert an SD card before using the camera" I have my SD in....idk what to do. I searched the threads already but nothing besides some guy saying format my SD...I did that but now I have the same problem along with my pictures and music being erased.
Sent from my EVO using xda app-developers app
Well you could have put the files on your comp first and then reformatted, but I am having the same problem. I guess we just gotta hang in there. It will be fixed soon I hope.
I'm having the same issue with the Aug. 31 CM10 nightly. I cannot access my SD card. If I look in system memory, it shows the card and the size, but I cannot access it, same as you guys. Trying with TWRP to wipe, it shows a bunch of e: failed to mount /sdcard (invalid argument). Still no solutions?
d1scopotato said:
I'm having the same issue with the Aug. 31 CM10 nightly. I cannot access my SD card. If I look in system memory, it shows the card and the size, but I cannot access it, same as you guys. Trying with TWRP to wipe, it shows a bunch of e: failed to mount /sdcard (invalid argument). Still no solutions?
Click to expand...
Click to collapse
I was able to mount the SDCard over USB in Recovery Mode and reformat it from my computer. Obviously I lost my data that was on the SDCard, but none of the apps I had running were affected. Once I did this and rebooted into CM10, everything was fine and I just made a fresh Titanium Backup of all of my apps. My previous TWRP Nandroids were on the SDCard, so they were lost, but I can always reinstall another ROM and restore my Titanium Backups and go from there. Hope that helps.
I had this same exact problem, but the external storage it is referring to is actually your internal sd card, and not the external.
What you need to do is go into TWRP and mount YOUR INTERNAL sd card (don't switch to external), and in windows 7 format it.
More detailed instructions: http://forum.xda-developers.com/showthread.php?t=1812774
midfieldmaestro said:
I had this same exact problem, but the external storage it is referring to is actually your internal sd card, and not the external.
What you need to do is go into TWRP and mount YOUR INTERNAL sd card (don't switch to external), and in windows 7 format it.
More detailed instructions: http://forum.xda-developers.com/showthread.php?t=1812774
Click to expand...
Click to collapse
This!
midfieldmaestro said:
I had this same exact problem, but the external storage it is referring to is actually your internal sd card, and not the external.
What you need to do is go into TWRP and mount YOUR INTERNAL sd card (don't switch to external), and in windows 7 format it.
More detailed instructions: http://forum.xda-developers.com/showthread.php?t=1812774
Click to expand...
Click to collapse
AWESOME! Thanks!
So I'm having a similar issue, except I didn't try to access the external sd card from TWRP. And yes I've verified its the actual physically removable card.
I can see it in the system storage menu. However when I try to access it in Estrongs, it's no longer mounted as ext_sd in the sdcard folder. I did some digging and found it's now mounted as external_sd in the root folder of the phone. Looking in the storage folder, it still shows up as sdcard1, and my internal storage is still sdcard0. This seems to have happened after I flashed one of the nightlies, like 9/1 or 9/2. Any ideas on how to resolve this?
I'd rather not revert to my last backup, which was a Sense rom. I think this is screwing with the media scanner, because none of my sounds for alarms calls or texts work anymore
BeerMit said:
So I'm having a similar issue, except I didn't try to access the external sd card from TWRP. And yes I've verified its the actual physically removable card.
I can see it in the system storage menu. However when I try to access it in Estrongs, it's no longer mounted as ext_sd in the sdcard folder. I did some digging and found it's now mounted as external_sd in the root folder of the phone. Looking in the storage folder, it still shows up as sdcard1, and my internal storage is still sdcard0. This seems to have happened after I flashed one of the nightlies, like 9/1 or 9/2. Any ideas on how to resolve this?
I'd rather not revert to my last backup, which was a Sense rom. I think this is screwing with the media scanner, because none of my sounds for alarms calls or texts work anymore
Click to expand...
Click to collapse
this is a work around for the HTC method of listing the sd cards, in my opinion HTC really screwed the pooch with the way they labeled the file system. The way sense accesses the external sd is through a shortcut to the physical address of the external sd. It really screwed with apps like power amp which had no problem reading both cards but if for example you went to power amp and marked what folders had your music by selecting the folders through the ext_sd folder shortcut it would read and list your music twice. another user who flashed cm10 noticed this (not the ext_sd file problem but the way CM10 was confused by the structure) and quickly wrote (then generously shared) a script that would rewrite the address correctly. I guess that a similar script (or that very same one) was introduced to the installer for the nightly builds
Wow thanks for the clear explanation. I too thought the ext_sd method was screwy, with all of my custom notification sounds showing up twice. Any idea on how to fix my alarm and call sounds not working? Can't afford to miss a day of class lol
This isn't definite as I haven't had to but going to fix permissions might help if some programs aren't recognizing the file tree
Welp, it was worth a shot, but no go. Ima keep tinkering. Thanks anyway tho
Well here's what I did after I flashed the original rewrite script, I had to factory reset (changes survived)and then wipe system, then reflash the nightly build (fastboot kernel for boot 1.15+)
Edit: I still have the shortcut folder on my internal however its not linked anymore so nothing shows up, everything else works fine
Ok, tried a full reset, wiped data, system, caches. Ringtones are working again, as are text tones. Alarms, still silent as ever... I'm so confused right meow
Sorry to hear that man
Hi,
Background story. It's long, and I am supposed to be brief, but maybe the stages I have been through trying to solve this matter (due to mishaps in upgrade process perhaps?) - so I'm giving it in full. Sorry in advance. I will note that I have done tens of Google searches on this problem, and the common denominator between all my findings were bugs in Custom ROMs such as CyanogenMod etc - where they have fixed it later. But I did not use any custom ROM, only original Samsung ROMs (at least as advertised). My device in Odin mode still claims to have an original Samsung FW, so I am guessing that assertion is correct?
So here goes.
I have been using 4.0.3 for quite some time. Then Samsung released an OTA upgrade, which failed to me during the reboot phase. I had a hunch (really a hunch, no proof), that this is somehow related to the fact that my device is encrypted, a feature that I have enabled after it was first supported, when I upgraded from 2.3 to 4.0.3 (OTA...).
Long story short, I tried to decrypt the device using the same menu I used to encrypt it. You would think that this would work, right? Well, it didn't. Just like the install, it got stuck at the very beginning, rebooted again, and the system was back as before (no data lost).
Last night, I felt lucky (oh, I was wrong), and tried the Decrypt again, probably the 10th time I'm doing it. This time it got stuck differently, eventually rebooting and giving me the 'swipe to unlock' screen (instead of 'enter decryption key'...). I though 'cool, it unencrypted the device...'. Wrong. After the swipe, got a blank screen. After some time, when I realized the thing is simply stuck, I rebooted through the power button.
Then I got Samsung's S changing colors... forever. Waited hours to no avail.
So I said, OK, let's try to just upgrade to 4.1.2, as this is what I wanted to do in the first place... at first I downloaded the "latest firmware" as advised by sammobile.com/firmwares/#firmware - which was from "Taiwan" and flashed it in download mode with Odin 3.0.7, by clicking on "PDA", selecting the MD5 file, seeing the verification was a success, and clicking "Start". . That seemed to work, and passed the "stuck S" stage, however I got a request for some password... in Chinese... couldn't really understand what it means, so:
I downloaded the I9100XWLSJ, which I understood is the latest for a European country (so I assumed it will be in English), which also succeeded the same way, and now I could understand the question - it was asking for my decryption password. I did actually guess this what the Chinese said, but alas, my decryption password did NOT work. And so it didn't on the English version as well.
I gave up my data. Went into bootloader, and wipe/factory default. Restart. Welcome to Android 4.1.2.
All seems to work well (OK, couldn't test the camera...), except for... the SD Card! It simply refuses to mount it as "USB Storage", as has always been. I tinkered with it for many hours (and even rooted my device for the first time...), and this is what I can say:
* The SD card is seen by the system, as external. Even though the SGS2 does not have an external SD port (unless I'm blind?). With a file browser, I can browse to it, play files from it, etc.
* Android seems to insist on using the internal card for everything. Opening the gallery. Opening the Camera. etc. Thus all those features currently do not work for me. I am merely guessing here that this is the reason, because apps say things like "Turn off USB storage before using camera" - as if the mountpoint is busy. And also - like I said - previously it was "USB Storage", for the best of my memory...
* The SD card seems to be mounted on /mnt/extSdCard or /storage/extSdCard
* The mount point /storage/sdcard0 seems to exist, and is symlinked from /mnt/sdcard, FWIW
* The SD Card is 8GB, from an old Nokia N85 phone
* Formatting the SD Card from the SGS2 didn't have any noticeable effect.
* A different SD Card [32GB] from an SGS3 running 4.1.2 shows the same symptoms
* I checked out /system/etc/vold.fstab, and in there I can see that:
Code:
# internal sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
secure_format = enable
discard = enable
supported_exfat = disable
}
dev_mount sdcard /storage/sdcard0 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard1 /storage/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
Questions:
* Is my assumption correct, that this should be mounted as /storage/sdcard0? If not, and extSdCard is correct behavior, any suggestion why any app that needs the SD card says it does not exist, even though it's accessible to file explorers?
* If it is correct, any idea WHY this is happening, or, a workaround?
Much obliged!
-- Shimi
System is usb. Don't mess with this.
Int sd or sd card 0. Is what you save to internally. Most apps camera save to this. Ext sd is the removable sd card. S2 has prob moving things to ext sd. Try Apps2sd to do that.
Gt i9100
Alliance v7.2
Dorimanx8.11.1
Xxls8
OK...
ansrewwrightt said:
System is usb. Don't mess with this.
Int sd or sd card 0. Is what you save to internally. Most apps camera save to this. Ext sd is the removable sd card. S2 has prob moving things to ext sd. Try Apps2sd to do that.
Click to expand...
Click to collapse
I'm not trying to move things to the external sd card, actually. If what you say is true, let's forget the SD card altogether. After all, the device has a few GB's of internal memory, right?
I basically started scratch with 4.1.2. I click on "Camera", I get an error about USB. Why?
Have you wiped delv/cache. Try that first. Or try settings, apps, camera, clear data.
Gt i9100
Alliance v7.2
Dorimanx8.11.1
Xxls8
ansrewwrightt said:
Have you wiped delv/cache. Try that first. Or try settings, apps, camera, clear data.
Click to expand...
Click to collapse
Not sure what delv/cache is. Google doesn't show any reasonable stuff.
If you mean Wiping the cache partition in bootloader mode. I believe I had, at the same time I did Wipe Data/Factory Reset. But to make sure, I did it again now. That, did not help.
Clearing data on the camera did not help either. I will re-iterate that the problem is not solely with Camera, rather than anything that tries to use storage. Camera, screenshot, gallery, Waze (navigation app).
Maybe there's something wrong with partition that causes it to not be able to be mounted?
I have no problem with re-doing the partition table with Odin, but the FW did not seem to come with a PIT file, which is required for that...
Do you have a custom recovery? If so go into it and wipe cache and then advanced settings the wipe delv cache. May help. Tryed flash how many times? Some take two or three to work prop I read. May help.
Gt i9100
Alliance v7.2
Dorimanx8.11.1
Xxls8
ansrewwrightt said:
Do you have a custom recovery? If so go into it and wipe cache and then advanced settings the wipe delv cache. May help. Tryed flash how many times? Some take two or three to work prop I read. May help.
Click to expand...
Click to collapse
Apparently the root I did to the device did change the recovery ROM
So I wiped that cache partition (for the 3rd time ) - saw the newly added Advanced option, found what you were talking about (it's actually 'Dalvik cache' - Dalvik is I think the VM Android uses to run apps?) - cleared that too. There was also an option to fix permissions there, so I did that, and also to partition the internal SD card, I went for that too.
All did not help. I guess I'll go to re-flash.
So, the re-flash didn't help
So I went and re-wiped the /data partition.
Went through all the first time wizard again, and then I had a notification that the internal SD card is not ready, and if I want to format it (maybe due to the 10 things we did since the first install? )
Anyways, I of course confirmed, and now Camera works (and detects the external SD, and suggested to move to it automatically. Funny that they don't do that automatically when internal is not available?)
So, thanks dude! (assuming you're a male)
Yes male lol. No problem you sorted it.
Gt i9100
Alliance v7.2
Dorimanx8.11.1
Xxls8
I am also having this problem after upgrading my stock T-Mobile SGSII T989 from ICS to the Factory build of 4.1.2 Jelly Bean.
Now my SD card will never auto mount. I must go to Settings>Storage>Mount SD Card anytime I reboot my phone.
I just wanted to clarify what you did in the end and did it completely fix the problem. Was it that you re-formatted your SD card? Or did you have to wipe and re-install the OS?
ocdavid said:
I am also having this problem after upgrading my stock T-Mobile SGSII T989 from ICS to the Factory build of 4.1.2 Jelly Bean.
Now my SD card will never auto mount. I must go to Settings>Storage>Mount SD Card anytime I reboot my phone.
I just wanted to clarify what you did in the end and did it completely fix the problem. Was it that you re-formatted your SD card? Or did you have to wipe and re-install the OS?
Click to expand...
Click to collapse
Hi,
I believe your problem is NOT like mine. I didn't have an auto-mount problem. I couldn't mount at all - the card was not even recognized.
The solution appears to be re-formatting the /data partition, like I said. Because numerous firmware re-flashes with Odin didn't fix it, and immediately after the wipe and a reboot, it asked me if I want to re-format it. This may be due to remainings from my encryption ordeal... so I can't tell for sure, but the circumstances suggest that was it.
So i have been having this problem for a few months now, and its driving me crazy.. I've read every thread on XDA about sdcards, but nothing seems to apply here
When I reboot, my phone launches External2Internal so my 32GB SD can be used as my internal drive, and I've used it fine for a very long time.. but recently the sd card just disappears after some period of time. it seems to happen whenever my phone goes to sleep or the screen goes off and is locked, i suppose
after I reboot the phone it works fine again..
I quite think its from a malicious program.. but I cant be sure
recently, I installed a bunch of sd card tools to rescan, remount, test etc.. and I also installed an External2Internal update... and after all that, the sdcard contents appear to have been deleted, even after multiple reboots, when viewed with ES File Explorer.. However all the contents appear in good condition when viewed with Total Commander.. .
and since all that tinkering, because the sd card seems on some level to be deleted, programs like avast are getting corrupted errors on their virus scans, such as "invalid context during scan".. an error it doesnt get when the sdcard is unmounted completely, but only now that it mounts as appearing mostly empty to es file explorer and probably most other programs.
so it seems like one of the USB tools or the External2Internal update has done something malicious to my card... or maybe it was a last ditch effort by some dorks malicious code from a program i deleted in trying to get this all sorted out
anyone else having this problem or know how it can be fixed?
and I prefer to try and find out what is causing the problem and fix that problem, rather than just reformatting the card or buying a new card, since i'm sure it will just happen again someday
thanks
-
This happens to me as well, the only difference is that I don't use External2Internal but the jellybean option "default write disk: SD card"
I own a Nokia 6, never rooted, 8.1.0 with the latest security patch installed (1 August 2018).
I have 32 GB internal shared storage and 64 GB microSD card installed. Be it a good or bad idea, I have formatted the card as internal storage, and migrated data to it using options available in Android settings, no third party shenanigans.
When I look at apps' details, those that have the option to choose storage signify that they are on sdcard.
Now, to the problem: I approached about half of used space on the sdcard, that's a bit over 32 GB, and I'm closing in on about half on the internal shared storage, that's about 13.4 GB used at the moment.
However, even though it would look like I have lots of unused space left, the phone started to act as if I don't have any. But... Not always. Let me elaborate.
I can't make a picture or record video, all I get is: "there was a problem with saving your photo or video."
I can't download files using a browser. It instantly fails.
I can't install apps from Google Play Store like "Google" and many others, however, I can install some other apps, seemingly at random (but if it fails, of keeps failing).
I can - because I just did - download security patches from settings/system updates....
From the above I speculate without any specific Android knowledge that:
- the internal shared storage isn't a single partition spanning the whole of built-in memory but rather is partitioned into multiple... Well, parts, therefore:
- there's probably a /system, /data and /user partition (forgive the layman guesswork on the names). There's probably also a /swap like in *nix? Then again, I guess not because that would probably slowly kill internal storage flash memory...
Anyway, from the above I gather that the simplistic reporting on how much internal storage I used doesn't let me know that I might have ran out of space on one of those discrete partitions.
That might explain why some apps I can install (they can be installed in external storage, so they do) and some I can't (they need to be on internal storage for whatever reason).
I have tried looking at the app info to maybe move apps to SD card but any and all I check either don't have the option or they already are on SD.
I tried deleting files and removing apps with various results:
- some files I just can't remove, even though they don't appear to be in use (still, maybe they have handles open, I don't know how to check for that apart of forcing suspected apps close)
- some apps (HERE Maps) left a considerable amount of junk in Android/data after themselves, and none of my file managers seem to be able to delete these files.
- some files and apps deleted just fine and the used space indicator did reflect that, however...
I still can't save a photo or video, or download a file, and apps still either install or not, just like before.
That got me thinking that there may be a problem with file/directory permissions for some bizarre reason.
I'm stumped. I'm on the go, visiting Milan tomorrow and I won't be able to take a single photo. Not that Nokia 6 has a great camera, but it's there and I can't use it when I need it.
Halp?
A little bump
So, am I truly sentenced to factory reset?
Hidden Android dialer codes don't work at all... I think I'm out of options here.
Update: So I did end up doing the factory reset. Afterward, my phone started to work fine, with the exception of the microSD card that always showed up in the notification area as needing of attention. I tried formatting it as portable, and it would supposedly work if you went by the final "success" message, but it wouldn't change anything, and it would still not show up in file manager. The notification about it needing to be set up would still be there, no matter how many times I tried.
So I took the card out and connected it to a PC - tried formatting it, deleting and recreating all partitions, wiping it out, all supposedly would work in partition managers, but after the things were all done, it wouldn't reflect on the actual card.
Seems like it was dying already.... Fortunately, I had a 32GB card to spare, got it into the phone. Worked on the first try.
So that's all folks, my 64GB microSD card died on me, and that's the reason of all the anguish above. Now you know.