Develop Bugs

[Q] App2SD Broke / Corrupt SD Card?

I've flashed back to standard FroYo with RUU -RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed - and all seemed well but I've noticed that when I now move an app over to the SD card using the standard FroYo APP2SD feature the app works fine until I reboot my phone and then it just has a standard android grey icon so it knows its on the SD - but it won't work again...
It's as if my SD card is mounted all the time...
Any thoughts on what I can do to fix this?

How frustrating...
I think this might be down to the new SD card I put in my phone...
Kingston 16GB class 6...
switched back to the SanDisk 8GB class 2 - and apps2sd seems to be working.
google sky maps is still on there after two reboots anyway which the 16gb wasn't.
Does anyway know of any tools to check the SD card for faults before I try and send it back?

someone suggested a chkdsk on it...
chkdsk from windows recovered a FOUND.000 folder with 1530 File(s) 2,805,137,408 bytes of file fragments!
any one have any suggestions of decent SD card checking tools or such or should I just try and send it back?
[edit: just noticed that the 1530 were all my photos and contacts on the SD card ]
[edit2: Anyone know if these tools are any good:
http://www.softwinter.com/storagetools.html ]
[edit3: just saw its for WM only]

done a full windows7 format on it (instead of a quick) and it might, might just be working...
got RAC Traffic on the SD and managed to do a reboot and its still there - which is further than I got before...
nope - still not working - second reboot and it has gone...
interestingly though if i unmount and re-mount the SD it does come back and work...
tried the above again - rebooting (not there) - unmount - re-mount - still not there - annoying...

Sd card test
h2testw: http://mympx.org/Downloads/p13_sectionid/2/p13_fileid/13
results for 1024mb:
Code:
Warning: Only 1024 of 15986 MByte tested.
The media is likely to be defective.
486 MByte OK (995328 sectors)
538 MByte DATA LOST (1101824 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
538 MByte corrupted (1101824 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x000000001d6b8000
Expected: 0x000000001d6b8000
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 1.79 MByte/s
Reading speed: 5.56 MByte/s
H2testw v1.4
I'm going to guess from that it's broke'd

A lot of guys on this site have had problems with Kingston cards (you can search for the other topics). Sandisk seems to make good cards, and on the advice of several people here, i purchased a 16gb class 6 A-DATA card and am quite happy with it so far.

Yeah, the more I had problems trying to get it sorted the more research I did into it - Patriot / A-Data / SanDisk seem like the best choices for MicroSD cards ...
I thought Kingston were a pretty decent manufacturer too!
I'm a bit frustrated as I wanted something bigger than the 8gb I had currently, and something that'll last a little while - 16gb/c6 seemed perfect for a decent price too - backed up and wiped my phone...
8 hours later I am flashing back to stock only to spend another few hours confused before going back to my 8gb/c2

LBA mode MicroSD problems - no LBA: +14MB/s on Patriot LX 16GB

Summary:
I bought a Patriot 16GB LX Series Class10 MicroSD and had huge problems with it. Freezes etc.
After partitioning with FAT32 without LBA the Patriot Class10 is superfast, 14MB/s write speed under Android Froyo. LBA mode was the culprit.
I have not tested this over several days, but so far things seem to be fine.
Problem description:
Phone: Motorola Defy on Froyo Orange. Problem also exists with LG P500
The Patriot 16GB LX Series Class10 MicroSD seemed to lock up, apps were freezing. Speed tests with SD Tools from the Market also locked up.
The Patriot worked however fine when put into a card reader with a PC. Write speeds are consistently over 12MB/sec. I tested also with Check Flash, google for "chkflsh misha"
I reformatted with the official SDFormatter Tool V.2.0. from the SD Association. No go, same problem.
How to solve:
1. Remove existing partition on MicroSD and make a new partition with FAT32 without LBA mode.
I used the Check Flash low level initialization function for partitioning, google for "chkflsh misha"
2. Format MicroSD under windows, command line with:
format X: /fs:fat32 /a:32K
Click to expand...
Click to collapse
(DO NOT use SDFormatter from the SD Association to format as the program repartitions the MicroSD in FAT32 LBA Mode!)
With FAT32 no LBA 32k allocation size the Motorola defy blazes away with the Patriot 16GB LX. Write speeds + 14MB/s are shown by SD Tools.
Thoughts:
My humble guess is that the Motorola Defy accesses the MicroSD in non-LBA mode and that leads to problems if the partition is LBA. This is either caused by the MicroSD controller or the Defy.
I also suspect that various MicroSD problems of other phone/card combinations are caused by LBA partitions.
As far as I can see LBA is anyway superfluous as Android can only access 32GB SD Cards currently.
Cheers
Geejay

Usually class 2 and 4 cards are better for use with phones and for running OS's or apps off of. Class 10 cards are designed to have fast sequential write speeds, but sacrifice their random read/write speeds and access times to achieve their fast sequential speeds. It's because they they initialize the section of the card that they are about to write to, which gives great speeds in sequential writes, but will cause delays and freezes when doing things that need quick access to different parts of the card or tasks that will read/write small bits of data from different parts of card.
Many people assume that higher class cards are better, but it really depends on what you're using the card for. For digital cameras, higher class is better, but for cell phones, where you will running apps or parts of the OS are store and accessed from the card, you want a lower class with better access times and random read/write speeds.
Different cards are better for different tasks.

Thanks for your comments. I bought the card because it was the cheaper than Kingston, the only other alternative in that shop.
Here is an interesting article, with detailed info of what you mentioned.
Google for "Working Groups Kernel Consolidation Projects FlashCardSurvey", I cannot post links.
It seems that these Patriot cards are indeed linear write. The author mentions a superior SanDisk algorithm for access.
Interesting benchmark which seem to confirm this: google for "MicroSD card performance test results"
Looking at the table Kingston seems to be slower than Patriot.
In any case there seems to be an LBA problem with the Froyo/Patriot combo.

Yeah, Kingstons are terrible for access speed and random read/write from the tests I've done. I'll never buy a kingston again. I usually stick with Sandisk... it's usually worth any extra money they cost to know you're getting a quality card. I have 8 different sandisk cards now... 2 32gb, 2 16gb, 2 8gb, 1 6gb and 1 4gb, and haven't had a problem with any of them and all except one has worked flawlessly with WP7 and all have worked great running android off of on my HD2.

I was interested in buying this patriot memroy card, is there anyone who can tell me whish access time ? ( you can use hd tune 2.55 to check it ! )

please delete

HD2 with cLK and clockworkmod recovery on Patriot 16gb class 10
geejay2 said:
Summary:
2. Format MicroSD under windows, command line with:
With FAT32 no LBA 32k allocation size the Motorola defy blazes away with the Patriot 16GB LX. Write speeds + 14MB/s are shown by SD Tools.
Click to expand...
Click to collapse
Thanks so much for the idea. Seems to have fixed the problems I was having with the card. My problem is that the ext3 partition is automatically formatted by the recovery program I'm running (clockworkmod 4.0.0.0), so I can't do the same for that partition.
I'm still not getting great write times, but read times are good for sequential:
-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 12.588 MB/s
Sequential Write : 3.915 MB/s
Random Read 512KB : 16.033 MB/s
Random Write 512KB : 1.103 MB/s
Random Read 4KB (QD=1) : 1.782 MB/s [ 435.1 IOPS]
Random Write 4KB (QD=1) : 0.129 MB/s [ 31.4 IOPS]
Random Read 4KB (QD=32) : 2.024 MB/s [ 494.2 IOPS]
Random Write 4KB (QD=32) : 0.111 MB/s [ 27.1 IOPS]
Test : 100 MB [H: 11.5% (1.6/13.9 GB)] (x9)
Date : 2011/09/20 14:23:51
OS : Windows XP Professional SP3 [5.1 Build 2600] (x86)

Thanks!
Just singned up to say thanks.
Just followed your instructions for an 8 GB Verbatim Class 10 card. Seems to work. It was laggy and buggy before that.
Thanks

Wow! This LBA thing seems complicated, is it really needed...? Heard that formatting in different cluster sizes can solve the problem already, maybe this LBA thing is not needed...?
BTW, Chkflsh doesn't seem to have a partition function at all...?
Cheers.

And how do we format in non LBA mode? I cannot find any instructions anywhere...
Please, help!

florin20032003 said:
And how do we format in non LBA mode? I cannot find any instructions anywhere...
Please, help!
Click to expand...
Click to collapse
My thoughts/problem as well...

Mac option for non-LBA formatting??
Hello everyone...
Was wondering if anyone knew of a Mac option to format in non-LBA mode. Does the internet formatting utility is the Mac OS ("Disk Utility") use LBA or no??
THANKS!!

issues

I am unable to partion my new 32GB class 10 sd card to ext3/4. I need to partion it for apps2sd but when I do it it will run the process but will format as other instead of ext3/4. any advise. Aslo I have flashed my phone over to the cricket wireless network and I keep getting a hands free actvation screen run every boot, I think it has something to do with sprint. Does anyone know what it is and how to delete so I don't receive that every boot.
Thanks is advance...

bump and over 100 views and no one has an idea ?

So no one has ever had a issue with there sd card not formatting to ext3

32 GB SD Cards done't play well with this phone. It's posted in a lot of places

HipKat said:
32 GB SD Cards done't play well with this phone. It's posted in a lot of places
Click to expand...
Click to collapse
Thanks for the reply, I would under stand that if I was using my phone to partition,but I'm using my computer and when its done it says other format instead of ext3. So I have not got to the phone issue yet lol

jmh033089 said:
Thanks for the reply, I would under stand that if I was using my phone to partition,but I'm using my computer and when its done it says other format instead of ext3. So I have not got to the phone issue yet lol
Click to expand...
Click to collapse
try formating it in recovery. i used the latest smelkus mod recovery to partition my 16gb class 4 about 2 days ago. see if it will work for your card. if it doesn't work there then its probably a card issue

PhxkinMassacre said:
try formating it in recovery. i used the latest smelkus mod recovery to partition my 16gb class 4 about 2 days ago. see if it will work for your card. if it doesn't work there then its probably a card issue
Click to expand...
Click to collapse
did that before I posted, thanks. I have contacted the seller and if I don't get a new one I will get my money back and buy a name brand this time lol
The media is likely to be defective.
1.8 GByte OK (3952533 sectors)
5.4 GByte DATA LOST (11341931 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
5.4 GByte corrupted (11341931 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000778f2a00
Expected: 0x00000000778f2a00
Found: 0x0000000000000000
H2testw version 1.3
Reading speed: 9.86 MByte/s
H2testw v1.4
might be the card ROFLMAO

HipKat said:
32 GB SD Cards done't play well with this phone. It's posted in a lot of places
Click to expand...
Click to collapse
I have a PNY 32GB class 10 card and had no issues with it.

with out a dought its the card, I'm having so many issues its not even funny...

What is the brand?
Sent from my NookColor using Tapatalk 2

[Q] FLAC files disappearing from SD Card?

Hi guys I just purchased the Samsung 64gb micro sd card and I'm having some issues.
I just copied over ~45 gb of FLAC music to the sd card using two different methods. 1) Taking the sd card out and using a sd to usb adapter and 2) plugging the phone into my computer via usb.
Both times all of the files copied over without any error or interruptions and after I put the sd card in my phone and booted it up I can't detect any of the files from Shuffle or ES File Explorer
So I plugged the sd card back into my computer and both times all of the folders are empty and none of the FLAC files are present. I ran diskcheck on the sd card and it said it fixed all of the errors but all of the FLAC files are still missing... Now I just have a folder called FOUND.000 on the root with a bunch of .chk files in it that are about the size of an album of FLAC music (~300mb)
What is going on...?

Jessooca said:
Did you by any chance get an error when copying the files over ? Such as a semaphore error? Were you using Windows to copy files or teracopy?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I used Windows Explorer to copy the files over. It looks like I have either a counterfeit or defective card. I ran SD Insight and H2testw on it and both returned obviously suspicious results.
sdinsight:
Manufacturer: Invalid (0x00)
OEM/Application ID: Unknown
Product Name:
Product Revision: 0.0
Serial #: 0xbd0c
Manufacture Date: Jan 2014
CRC7: OK
Size: 67GB
SD Card Specification: SD Physical Layer Version 2.00
CPRM Security Support: No Securit
Click to expand...
Click to collapse
H2testw:
Warning: Only 63907 of 63998 MByte tested.
The media is likely to be defective.
3.5 GByte OK (7486168 sectors)
58.8 GByte DATA LOST (123395368 sectors)
Details:41.5 MByte overwritten (85104 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
58.7 GByte corrupted (123310264 sectors)
60 KByte aliased memory (120 sectors)
First error at offset: 0x00000000c65db000
Expected: 0x00000000c65db000
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 3.80 MByte/s
Reading speed: 6.64 MByte/s
H2testw v1.4
Click to expand...
Click to collapse

Here is a copy of the email I sent the eBay user:
I have reason to believe the Samsung 64gb micro sd card that you sold me is counterfeit.
I first had a hunch this item was counterfeit when I copied 45gb of data to the card two separate times just to have it all erased/corrupted immediately after putting it in my phone.
After this happened, I decided to download an Android app called sd insight to see if the card was fake or not. These are the results I received from running the app: http://pastebin.com/RfG0JREq
As you can see in that log file, the manufacturer, product name, revision number, etc are all null. This led me to believe that the card you sold me was certainly counterfeit. If this was a legitimate card the entries would have reported things such as SAMSUNG and MB-MGCGB/AM. (The supposed make and model of this sd card) Additionally, there would be at least 1 revision to this card to counter the data corruption issues that was occurring to S3 and S4 smart phones in 2013 since it was manufactured (supposedly) in January of 2014.
In order to be sure for certain before I contacted you with this claim, I used a program called H2testw. H2testw is a program that writes data files to your sd card and reads them off until every sector has been tested. If corruption occurs you have an sd card error. Additionally, you can see the actual size of the sd card and many other cool things. Here is the log file that the program returned to me: http://pastebin.com/X8e0R6TM
As you can see, this card is actually only 3.5GB instead of 62.4 like reported by Windows Explorer. This leads me to believe this card has been hacked to report the incorrect capacity size. 58.8GB of data was lost because it was written to sectors which actually don't exist... This is proven by the hex address given by the location of the first error.
As you can see, it expects to encounter 0x00000000c65db000 but instead encounters 0x0000000000000000 when trying to copy data to that specific location. This is because that location doesn't exist....
Finally, you can see that the writing speed is only 3.8mb/s instead of 7mb/s and the reading speed is only 6.64mb/s instead of 24mb/s. This is another clear sign of a fraudulent item.
You sold me a class 4 3.5GB sd card in disguise of a class 10 64gb sd card. I would like for this item to be replaced with a legitimate Samsung 64gb class 10 micro sd card at no extra expense to me. This includes reimbursing my return shipping fees if you desire the item to be returned to you before continuing.
Click to expand...
Click to collapse

After the root sd card not identified "Samsung sd card corrupted"

I rooted my phone LG G3 D855 6.0 with kingroot&MM.
after the rooted I got error "Samsung sd card corrupted" also the sd card changes from FAT32 to EXFAT.
How can I slove this problem?

Connect your card to PC using card reader then open cmd (command prompt) then type chkdsk your_card_drive /f then press enter. Good Luck [emoji106]

not helped

Is your card opening in PC?

no
I just connect him with adapter

Now the only way i know is you have to recover your data using any good data recovery software then format your card.
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Or you also can try this method, download AutorunExterminator in your pc and run it while your card is connected then run cmd and type attrib -h -r -s /s /d your_card_letter\*.* press enter.
---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------
Make sure adapter is not locked it makes your card write protected.

Alexnoj said:
I rooted my phone LG G3 D855 6.0 with kingroot&MM.
after the rooted I got error "Samsung sd card corrupted" also the sd card changes from FAT32 to EXFAT.
How can I slove this problem?
Click to expand...
Click to collapse
Again format it to fat32 see what happen....

I got the very same error, Lg g3 d855 16 Gb . While booted android 6.0 can't see SD card anymore, and I get the same error samsung SD card corrupted. Strange thing is that I can see the card and all files from within TWRP recovery. I can even do back ups to the SD card from TWRP. So I put the SD card into pc and rund cmd.exe and hit the command chkdsk d: / f
As you can see from out put SD card looks good.
From my pc I can read and access all files and folders. No one is missing, and it appears the file paths are ok, as are the sectors.
Any idea how I can read the SD card from within android 6.0?
output:
Code:
C:\Users\joppy>chkdsk d: /f
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
So I did a deeper look and did chkdsk d: / r
Output:
Code:
C:\Users\joppy>chkdsk d: /r
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows is verifying free space...
80888 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
The only strange thing my eyes spots are the missing of Volume Serial Number. Could that along make card unreadable for android? Seems strange that I can read and access the content of the SD card on my pc, and even back up to the SD card from TWRP recovery.
Any ideas what to do make this SD card work?

joppy said:
I got the very same error, Lg g3 d855 16 Gb . While booted android 6.0 can't see SD card anymore, and I get the same error samsung SD card corrupted. Strange thing is that I can see the card and all files from within TWRP recovery. I can even do back ups to the SD card from TWRP. So I put the SD card into pc and rund cmd.exe and hit the command chkdsk d: / f
As you can see from out put SD card looks good.
From my pc I can read and access all files and folders. No one is missing, and it appears the file paths are ok, as are the sectors.
Any idea how I can read the SD card from within android 6.0?
output:
Code:
C:\Users\joppy>chkdsk d: /f
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
So I did a deeper look and did chkdsk d: / r
Output:
Code:
C:\Users\joppy>chkdsk d: /r
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows is verifying free space...
80888 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
The only strange thing my eyes spots are the missing of Volume Serial Number. Could that along make card unreadable for android? Seems strange that I can read and access the content of the SD card on my pc, and even back up to the SD card from TWRP recovery.
Any ideas what to do make this SD card work?
Click to expand...
Click to collapse
If you root on MM you must format your sd card as fat32

Anik49 said:
If you root on MM you must format your sd card as fat32
Click to expand...
Click to collapse
MM = marshmallows? don't know the lingo...
Could it be chkdsk / r changed the file system to exfat? SD card was read able in marshmallows until I soft bricked phone. But even after soft bricked was fixed I was able to see and read all files on SD card and back up to SD card from TWRP.
So from working in mm to not working in mm. Will try different solutions during the day and I will make sure to post later here so we either know whats works or don't.