Database Info

[Q] SD only recognizes sd-ext partition!

My SD card may be nearing EOL. Yesterday my Shift all of a sudden stopped recognizing it, would tell me my SD was safe to unmount and wouldn't mount it. When put into the PC it gave me an error saying something about "being unable to mount dev super block" and wouldn't read or format it. Luckily CWM still worked to partition it.
Now again this morning I'm having the same problem. (Yay, Mondays right?) Anyone have any thoughts other than buy a new SD? Or course I'd like to but money's tight so I'd like to delay that. Plus, this one's only 6 months old.
Also, anyone know how to create an sd-ext partition bigger than 4gb without a PC? (I'll be away from mine while at work and am very impatient) If nothing else I may just partition the whole 16gb as sd-ext and deal with figuring out how to make apps save data to the internal partition (I think there're mods for that somewhere).
Any help or insight is greatly appreciated, thanks in advance!

jesusice said:
My SD card may be nearing EOL. Yesterday my Shift all of a sudden stopped recognizing it, would tell me my SD was safe to unmount and wouldn't mount it. When put into the PC it gave me an error saying something about "being unable to mount dev super block" and wouldn't read or format it. Luckily CWM still worked to partition it.
Now again this morning I'm having the same problem. (Yay, Mondays right?) Anyone have any thoughts other than buy a new SD? Or course I'd like to but money's tight so I'd like to delay that. Plus, this one's only 6 months old.
Also, anyone know how to create an sd-ext partition bigger than 4gb without a PC? (I'll be away from mine while at work and am very impatient) If nothing else I may just partition the whole 16gb as sd-ext and deal with figuring out how to make apps save data to the internal partition (I think there're mods for that somewhere).
Any help or insight is greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Sounds like your card might be done . But you can try SD Formatter , it's worked a couple of times for me on cards that were supposedly done. As for the sd-ext Partition, I think you might be able to do one that big with TWRP. I know when I was messing around trying to decide on mine I took the optional setting why past 2GB. I settled on just over a 1GB of partition .

prboy1969 said:
Sounds like your card might be done . But you can try SD Formatter , it's worked a couple of times for me on cards that were supposedly done. As for the sd-ext Partition, I think you might be able to do one that big with TWRP. I know when I was messing around trying to decide on mine I took the optional setting why past 2GB. I settled on just over a 1GB of partition .
Click to expand...
Click to collapse
Thanks for the tip! And I can now confirm that TWRP does allow the sd-ext partition to be as large as one wants. I'll probably try that program you linked.

Glad I could help

Titan backup doesn't see ext SD card.

I have titan backup pro and it doesn't see my 32gig ext SD card. Any suggestions?
Sent from my Paranoid Galaxy S3 using Tapatalk.

It does, but not how you'd think. What are you trying to do? Use your external as titaniums storage?
Sent from my SCH-I535 using xda premium

Yes so I don't have to move the backups it makes before wiping and flashing. Forgive me still learning the android system.
Sent from my Paranoid Galaxy S3 using Tapatalk.

You actually do not need to store them on the external sd. Titanium stores the backups by default on the root directory of the internal sd card (memory) and are safe from being wiped when wiping data/resetting to flash a rom. People do choose to change that location to the external for swapping backup to a different phone and for extra security in case of a brick or some other issue that could arise, but it is not required to do for general flashing of different roms.
If you do want to change the location, go into preferences and select storage location, the back button will navigate to different locations available. Choose external sd and make your batch backup..that's it. If you already made a backup on your internal before switching to external, you'll need to use a file explorer (I like ES, but others are just fine too) to move the entire Titanium folder to the external card. Then go back into preferences and be sure to select the titanium folder you just moved as the backup location.

annoyingduck said:
You actually do not need to store them on the external sd. Titanium stores the backups by default on the root directory of the internal sd card (memory) and are safe from being wiped when wiping data/resetting to flash a rom. People do choose to change that location to the external for swapping backup to a different phone and for extra security in case of a brick or some other issue that could arise, but it is not required to do for general flashing of different roms.
If you do want to change the location, go into preferences and select storage location, the back button will navigate to different locations available. Choose external sd and make your batch backup..that's it. If you already made a backup on your internal before switching to external, you'll need to use a file explorer (I like ES, but others are just fine too) to move the entire Titanium folder to the external card. Then go back into preferences and be sure to select the titanium folder you just moved as the backup location.
Click to expand...
Click to collapse
NONONO DO NOT DO THIS!!!
Well you can if you don't then move your backups to your ext or a computer.
I believe TWRP wipes the WHOLE internal card when doing a factory reset as the Samsung Recovery does. ClockworkMod I believe is the only one that doesn't.
You probably need to format your 32gb ext to Fat32 instead of exFat that it comes with. See HERE It doesn't hurt to do this either way, unless you plan on putting files that are larger than 4gb each onto your card.

I don't use twrp, I use cwm with zero titanium issues on internal card. I find it unlikely that twrp would wipe the entire root directory bank of files because that would also wipe its own file including backups made. I'd like some verification on this, though I don't not use twrp, nor have seen any reference to not using the default location in any of titaniums guides.
Sent from my SCH-I535 using xda premium
---------- Post added at 12:53 AM ---------- Previous post was at 12:22 AM ----------
Quick note: I hate speculation. Please someone else chime in on some verification so that the op is getting accurate correct information.
My directions above ARE 100% correct if using cwm as your recovery. Titanium makes no mention or warning that you should change titaniums built in default storage location based on various recovery options. But again, I do not have any intimate knowledge of the workings of twrp, but certainly want to know so that my help is verifiable and accurate in the future.
Sent from my SCH-I535 using xda premium

annoyingduck said:
I don't use twrp, I use cwm with zero titanium issues on internal card. I find it unlikely that twrp would wipe the entire root directory bank of files because that would also wipe its own file including backups made. I'd like some verification on this, though I don't not use twrp, nor have seen any reference to not using the default location in any of titaniums guides.
Click to expand...
Click to collapse
Okay, if TWRP CANNOT wipe the internal card cuz of it's own files, then how the hell does the stock version do the same thing???
DUH!!! recovery is on a DIFFERENT partition! Know your phone!

Let's put this into basics. Do you know for a fact that twrp will erase a titanium backup stored in the default titanium storage location on the internal card, or do you need to change the storage location to external when using twrp recovery risk losing the backups?
All I got from you is telling the op to not use titaniums default location based on a speculation you had on twrps possibility to wipe it without any definitive info to back it.
My cwm based info is un-arguably accurate. So let's not confuse the original op's question here, and be sure your not rewriting the book on titanium.
Sent from my SCH-I535 using xda premium

First make sure your SD Card is formatted correctly (as FAT32, not NTFS)
Then make sure your TB is actually backing up to that drive. Meaning, go into a file explorer and make sure that the Titanium files are there.
If those don't work, try using a different Recovery.

Annoyingduck thank you for always answering my questions.
I would gladly read any info I could on the android system. I admit I don't "know" my phone. I haven't been able to find info to get intimate knowledge of my phone. I just assumed the entire phone was wiped when I told it to in recovery. I can see where the storage drive can get rather cluttered over time then. Is there a way to do a full wipe to kinda clean things up in the future?
I'm going to have to buy the book android for dummies.
My mem card is stock 32gigs sandisk class 10. Straight out the package. The phone reads it. File manager sees it. Idk if I would need files greater than 4gigs. Didn't realize there was issues with the 32. Thought it was just the 64. That's why I got the 32 and not the 64.
Sent from my Paranoid Galaxy S3 using Tapatalk.

That's what these forums are for, and hopefully getting the RIGHT info!
Your correct, the 32 should have no issues, the problems come along with the 64's. My SanDisk 32 class ten has no problems with files over 4 gig. Appreciate the support!
Sent from my SCH-I535 using xda premium

annoyingduck said:
Let's put this into basics. Do you know for a fact that twrp will erase a titanium backup stored in the default titanium storage location on the internal card, or do you need to change the storage location to external when using twrp recovery risk losing the backups?
All I got from you is telling the op to not use titaniums default location based on a speculation you had on twrps possibility to wipe it without any definitive info to back it.
My cwm based info is un-arguably accurate. So let's not confuse the original op's question here, and be sure your not rewriting the book on titanium.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I don't know for a fact that TWRP will wipe everything or not... I was meaning that the OP should copy his backups to his ext manually or to a computer JUST IN CASE. I thought I had read that the TWRP Factory reset/wipe did the same thing as the Stock's Factory Reset/wipe(Which erases ALL app data from the internal SD including TB's backups!
JB_orchidguy said:
Annoyingduck thank you for always answering my questions.
I would gladly read any info I could on the android system. I admit I don't "know" my phone. I haven't been able to find info to get intimate knowledge of my phone. I just assumed the entire phone was wiped when I told it to in recovery. I can see where the storage drive can get rather cluttered over time then. Is there a way to do a full wipe to kinda clean things up in the future?
I'm going to have to buy the book android for dummies.
My mem card is stock 32gigs sandisk class 10. Straight out the package. The phone reads it. File manager sees it. Idk if I would need files greater than 4gigs. Didn't realize there was issues with the 32. Thought it was just the 64. That's why I got the 32 and not the 64.
Sent from my Paranoid Galaxy S3 using Tapatalk.
Click to expand...
Click to collapse
@OP: The problem with the 64gb cards that I was referring to is their format. I know for a fact that 64gb cards are exFAT. I "think" that 32gb cards are doing the same thing. I dunno for sure. The problem with these cards is that the phone will read them, any file explorer will read them, but Recovery's have an issue reading them. Along with AOSP ROM's from what I've been told(I dunno for sure because I've always fixed my cards before going to AOSP).
If you dont see yourself using any files over 4gb(which usually are just bluray rips) then you might as well just format your card to FAT32 just to be safe. Go to and follow the GUI option of this THREAD. This is how I did my card and it's caused me no problems. Like I said the only downfall to formatting it this way won't allow you to use files that are over 4gb in size.
Now, there has been other problems with 64gb cards as far as stability. This is all speculative since I have not experienced it first hand, but I guess a lot of people were having their cards fail period. Meaning they were un-readable in any format on any device. Like I said, I have not experienced this.

I definitely would like to know more, especially about whether twrp does a full format. And just so I know, for cwm to erase root files, you would have to choose the format system option as opposed to wipe data/factory reset (which does not erase those files)?
Thanks man for the clarification
Sent from my SCH-I535 using xda premium

TWRP does not wipe /data/media which is the default save location for titanium, this location is the main directory of your internal storage. I have used TWRP on my SGS3 and my transformer prime and it has never erased this directory when doing a factory reset.
Sent from my Unlocked Rooted SGS3

Wish that was posted many posts ago...... Would have saved some headaches!
Sent from my SCH-I535 using xda premium

[Q] Trying to root my Inspire 4g

I am asking this again here, as my previous thread seemed to be hijacked by someone elses question!
I recently decided to root my inspire as i am no longer using it as a phone, so i thought that it would be interesting to do and fun to play around with all of the options available (i recently did the same thing on my Nook Tablet, and that was the single best decision i have made a while!). I started out researching the manual techniques to do it, but i didn't really like the high risk factor there (i really dont want to brick my phone) so i tried Ace Hack Kit. Of course, it has to download the phone from 2.3.5 to be able to work. During this process, it has me hold volume up and power twice, and every time i do that, it flashes up really quick something about holding volume up and volume down and power, but then it skips past that. Anyway, here is where my problem comes in: It says that it should reboot in to hboot, which it does, but that hboot should run a test, then prompt me to continue by pressing volume up, and then should reboot, flashing twice, and that should be the end of it. THe problem is, it does boot in to hboot, but it is just a standard hboot screen asking to recover, load bootloader, etc. When i reboot from there it just boots in to the phone as normal. I have tried 3 different SD cards, all of which work and are recognized by my PC, my other phone and my Nook tablet. I have also inserted a working sim card, just to be sure that wasnt the issue, and i still cant make it work. Does anyone have any experience with his issue, or any idea what i might be doing wrong?

Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell

marsdta said:
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
Click to expand...
Click to collapse
OK, as i have stated, i have tried a new SD card (2, actually, with the same results.) as far as an output screen, there is none. Ace Hack Kit goes through the whole downgrade process, my phone gets in to hboot, but it is just a standard hboot screen, and it doesn't downgrade. When my phone restarts, it restarts like i just did a factory reset.

There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?

marsdta said:
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
Click to expand...
Click to collapse
by changing the of the boot img do you mean downgrading it? That is what i am trying to do. The kit is supposed to do it automatically. If that is not what you mean, please explain!
As to the output, copy thing, no, there is none of that. I have followed the instructions about 20 times. After starting the downgrade process, the phone restarts and comes up with a red triangle. At that point i am supposed to hold volume up and power, and it goes and reboots and i do the same thing again. At this point, i am told that the phone will boot into hboot and check the boot image. When it is done, i am supposed to hit volume up to confirm, and then the phone will reboot, this time in to the down graded image. That is where my problem comes in. Instead of checking the boot image, it just goes to a standard hboot screen. There are no error messages or warnings, and i have followed the instructions to the letter.
As far as the cards are concerned, the maker of the kit suggested a 2 or 4gb Sandisk series 4 or 6 SDHC card, so i bought 2 of the series 6 4gb, along with the 2 others that i already have. I also have 2 series 4 4gb and 2 series 4 2gb Sandisk cards, as well as an 8gb and 2 4gb PNY cards. All of the cards recognize in my phone and PC, and the older cards also recognize in my Nook (and were used to root and load custom roms on several other devices), i have not loaded the new cards in to any other devices besides my laptop and the phone for fear of corrupting it. So i find it difficult to believe that the cards could be the problem.

I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method

marsdta said:
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
Click to expand...
Click to collapse
I appreciate the attempt to help (the reason why i didn't post a direct copy paste was simply as i was in no position at the time to take one, not any reluctance to ultimately do so...) In my recent attempt to provide you with a full copy paste of the process, i was able to figure out what i was doing wrong. For anyone who may have the same or similar issue: format the SD card while it is in the phone from your PC right before starting the process. Thats all it took. Even for a card that was brand new and untouched, or formatted before putting it in the phone, i couldn't get it to work, but it worked doing it that way, and i am now happily rooted and ready to install CM9!

Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.

pazzo02 said:
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
Click to expand...
Click to collapse
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.

glevitan said:
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
Click to expand...
Click to collapse
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?

pazzo02 said:
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
Click to expand...
Click to collapse
As far as I am concerned the boot partition can not be restored by formatting. SDCARD should always be dismounted properly.

[Q] S3 Locked in Boot Following CRT Down zip

This is one heck of a way to introduce myself. I am embarrassed and frantic about what has happened. I've been using the guidance in these forums for years, never had any problems, but I usually made a backup. Because of the size of the S3 backups, I didn't have one this time.
I have a Verizon S3 on stock ROM, rooted, CWM Touch Recovery installed, bootloader locked. I flashed the CRT Down - ODEX.zip (attached) from the thread below. Everything seemed to go well, but on reboot the phone gets stuck in the boot animation. I have also contacted Scott over Scott's ROMS since this was where the file came from, but have not heard back. My first preference is to undo the changes to the modded files. Second choice is to flash the latest stock ROM (Stock Root - VRALHE - ODEX.zip) that I have downloaded, BUT I cannot get it on the phone since the phone won't boot, and for some reason CWM does not see any files on the external SD card. My last choice is to do a wipe/restore from stock, and I think I know how to do this, but it will be very painful.
Anyone in a helping mood? I don't know where to go from here. This is just terrible.
http://forum.xda-developers.com/showthread.php?t=1841802&highlight=crt

CWM won't read your SD card because it's not formatted to the correct file system. You could take your card and backup the data, format it to Fat32 then transfer the ROM over to your phone that way. I've long since lost the link to the simple format tool that I used to format my card but if you search for it you should find it in I think the General Forum...

SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.

undrgnd1 said:
SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.
Click to expand...
Click to collapse
If you reformated in phone you formatted it back to extFAT.

You are absolutely correct sir. Your assessment was dead on. Thank you very much. I can now make a backup to the external card. Unfortunately, I had to restore the phone (-#*@"*). I found that two other 64GB cards I was having problems with had the same issue. Wow! Twenty five years around computers and I just figured out how to format volumes larger than 32GB in FAT32. Thanks again. This thread is done.

sd card corrupted

I just wanted to post this here in case it might help someone.
If you have ever had the SD card corrupted issue after installing a ROM or an update the first thing you should check is the kernel. I have found that every time I've had this issue I could still see the SD card in TWRP you couldn't figure out what was going on. I have since learned that the issue usually stems from the kernel. So take and reflash your current kernel or try a new kernel. Hope this helps someone good day

I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.

AngryManMLS said:
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
Click to expand...
Click to collapse
Why format the SD card if just flashing another kernel will fix the issue lol

shadavis08 said:
Why format the SD card if just flashing another kernel will fix the issue lol
Click to expand...
Click to collapse
I could think of a reason, that being (and this is an Android-wide rule) the kernel dictates support for file formats.
If you're using a kernel that has better features than a stock one on a ROM (let's say Gamma vs the stock LineageOS kernel in this case) the better kernel might not support the file-system format the stock one does. It comes down to support for what file-systems a kernel dev chooses to implement.
At least personally, I'd rather move 64GB off my microSD card, format it and move it all back on if it means I get to keep using a better kernel.

Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh

Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.

shadavis08 said:
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Click to expand...
Click to collapse
shadavis08 said:
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
Click to expand...
Click to collapse
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows 10-formatted SSD into my Windows 7-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
At least personally
Click to expand...
Click to collapse
which, again, doesn't make my process flawed.

Redline said:
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows-formatted SSD into my Linux-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
which, again, doesn't make my process flawed.
Click to expand...
Click to collapse
Wow really dude? I was giving some advice for people that could potentially keep them from losing all their data on the SD card. By simply flashing a different kernel before just wiping a card when the android system throws up an error saying sd card corrupted. You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.

shadavis08 said:
You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
Click to expand...
Click to collapse
That's precisely the opposite of the reason why I'm here.
I was here to point out the benefits and potential downsides to doing it either way, but okay.

I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
You could simulate this just by pulling the card without un-mounting it and then reinserting and android thinks the card is corrupt

I don't know. I don't have a computer to test with lol

One Twelve said:
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
Click to expand...
Click to collapse
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.

Redline said:
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Click to expand...
Click to collapse
My mistake not Android folder but lost.dir folder needs to be deleted

Back on nougat this happened to me twice on the same card. Formatted once and it happened again and this was back before I tried any custom ROMs or Kernels. Was purely stock rooted with SuperSU so it was definitely something screwy with LGs kernels
Kinda fuzzy but I think it happened first on 10J for TMobile and then again on 10K for my H918

I've not had any problems with my sandisk extreme 128GB for over a year now. On N.
I don't take the card out and swap it about, its been in all this time.