Develop Bugs

Froyo A2SD+ SD card corruption

Tons of new ROMs coming out now based on OTA and adding A2SD+. But one big issue. Quite a number of people have reported problems with corruption of their SD cards when setting the Desire into Disk mode and connecting it to a PC. I've read it the first time here
http://forum.xda-developers.com/showpost.php?p=7463184&postcount=348
and I can confirm it is reproducible.
Regardless if connecting to Windows or Linux, the card gets corrupted. It does not matter if you properly eject the drive. The Desire will respond saying the SD card is Read Only, and the only thing that one can do is to repartition it to fix the card.
I don't know what A2SD+ application everyone uses in their ROMs but I expect it's all based on some common version like the one put in from ieftm. As this is a serious issue it would be great if all you ROM cooks could look into it and try to fix it. Alternatively it may be a good idea to produce non-deodexed versions that save a significant amount of memory when installed normally without A2SD+.
Thanks for considering

I have this problem aswell its a bit of a nightmare there are a few files on my sd card that I can't even delete using andexplorer or my pc. I think the only way would be to remove my card and format it. I have never had this problem before only when I started using the 2.2 rom.

Noticed it before, i took the SD card out and put it into a cardreader, couldnt do anything in windows, said it was read only. Access via USB cable worked though.
Not that much of a issue for me, I mainly transfer files via Wi-Fi anyway, but I guess thats the explanation for the read-only behaviour.

Happened to me today, however I restarted the phone and everything seems okay now... :/
edit: nope, connected the phone again, chose "charge only" and then disconnected. The notification about my card being corrupted occured again, tapped on it and it went away... Dont know what to think..

I have the same problem .. And now it seems like the SD card is totally corrupted. Its not even possible to do a format

Okay thats it... Doing the titanium backup, nand backup and flashing some rom w/o A2SD+... :/

Out of curiosity guys, did the corruption of the SD card occur to the stock SD card that came with the Desire? I had the same problem with the stock card..
It seemed to unmount 3 or 3 times over a week and the next thing I knew it totally died and could not even be reformatted.. Happened on stock 2.1 that came with my Desire.. after I swapped to me own class 6 8gb Transcend I never had the proble again.. Just gonna upgrade to 2.2 now.. *fingers crossed*
Oh and yes.. I use A2SD+ on Modaco's 3.1. But that was after that card got corrupted..

I'm using card that came with the phone.
I'm going to try another Froyo Rom, just OTA rom rooted and we'll see.
Edit: I made my ext3 partition with ROM manager, if it makes any difference...

God dammit!
http://forum.xda-developers.com/showthread.php?t=747480

Yes its the card that came with the phone .. but it happen after i created the 512MB EXT3 Partition ... and I'm running this ROM : http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=741775&highlight=official it doesnt even use A2SD+

I dual boot my pc with windows 7 & ubuntu.... windows 7 scan and fix has repaired mine numerous times

I have class6 A-DATA 8GB and no problem. But with my last G1 i haved same card and with swapping goes to hell... I now correctly unmounting and disconnecting mobile from PC, after i save from PC to card. Flash have problems with writing.

This looks like a serious problem - it happened to me twice already. Devs, please have a look at this!

I have also had similar experience, SD card corrupt, yes it was the original card that came with the phone, EXT2 partitioned and using APSD+
Now why this happend is a mystery, but something I noticed when I tried the SD card in the PC - it was recognized, but said it must be formated, so I tried but it only saw it as a 32mb capacity!!! (it still would not format though - failed format..and since is no longer reconized at all..)
But, this made me think it "MAY" be something to do with the fact that when I did the Ext2 partition I seem to remember it also created a 32mb swap partition, or using Ext2 instead of Ext3. I have since learnt that it is advisable NOT to created a swap partition, so with my new SD card, after more reading about Ext partitions etc, I have only created only the Ext3 partion as I understand this is better than Ext2 and is less prone to corruption, and no swap partition and have had no problem since!
See this excellent post :- http://forum.xda-developers.com/showpost.php?p=7458565&postcount=8
It would be interesting to have some input from one or two of the developers with knowledge in this field to get an idea why this happens, and how it can be prevented.
It is also possible the the SD card was going to become corrupt anyway... with or without the help of Ext? / APSD+ - it does happen!

delta-101 said:
I have since learnt that it is advisable NOT to created a swap partition, so with my new SD card, after more reading about Ext partitions etc, I have only created only the Ext3 partion as I understand this is better than Ext2 and is less prone to corruption, and no swap partition and have had no problem since!
Click to expand...
Click to collapse
my sd was corrupt using a 512MB ext3 partition without swap partition in SD card :/

Try in windows: start > run > chkdsk x: /f
where x = desire drive letter.
I believe i did this in recovery mode > mount usb.

That's what happens when you don't want to use Froyos own A2SD implementetion because "widgetz doesnt workzz on dat."
Apps are not meant to be on an external EXT partition.
Wait until ROMs like CM have built in A2SD+, these hacky shell scripts can cause serious problems for the SD card.

LeeDroid said:
I dual boot my pc with windows 7 & ubuntu.... windows 7 scan and fix has repaired mine numerous times
Click to expand...
Click to collapse
Windows can not access EXTx partitions. As such is unfortunately not possible that it could possibly repair a broken SD-ext partition A2SD+ uses.

delta-101 said:
I have also had similar experience, SD card corrupt, yes it was the original card that came with the phone, EXT2 partitioned and using APSD+
Now why this happend is a mystery, but something I noticed when I tried the SD card in the PC - it was recognized, but said it must be formated, so I tried but it only saw it as a 32mb capacity!!! (it still would not format though - failed format..and since is no longer reconized at all..)
[...]
It is also possible the the SD card was going to become corrupt anyway... with or without the help of Ext? / APSD+ - it does happen!
Click to expand...
Click to collapse
I can confirm the corruption without any APSD+ ROM
I had a Stock Orange FR 2.1 ROM, and the 4Gb card that came with the phone get corrupted definitively (recognized as a 32mb capacity too, it has something to do with the Cylinder-head-sector combination).
Anyway, I'm going to try APSD+ with a class 2 PNY 16Gb, and tell you then if I get a corrupted card.
FYI, the Sandisk warranty is applicable for the original card: replaced in 5 days

I got some problems too with corruped files on my SDcard and had to format it. I'm thinking that from now i'll only mount my card to pc in recoverymode... maybe that is safe to do?

Not recognizing SD Card

I just flashed Business Gingersense 3.5 last night. Everything looks great on this ROM, but my phone doesn't think my SD card is present. I can't access pictures, audio, files, etc on the SD card. Is there something I need to do to get this ROM to see my SD card? I've reflashed a few times, removed and reinserted SD card, etc.
Thanks,
Alan

Is your SD card in FAT32 format? You could try copying everything from your SD card to your PC and reformat it. Then copy everything back on to it.

BTW, I'm not sure if it matters, but I'm coming from cyanogenmod 7.0 to Business GingerSense 3.5. The phone recognizes the card just fine when I reflash back to cyanogenmod 7.0...

I can give that a shot. Just curious - does cyanogenmod require a different format than gingersense? Perplexed as to why it is there w/ cyanogenmod.

I just checked the properties on my SD card and it IS in fact in FAT32 format. Any other suggestions?

Fad this prob before cm7 was ext4 ur new rom is most likely ext3 reformat or partition in recovery
Sent from my MB860 using XDA App

As long as it is in FAT32 it should work. I know that files on SD cards over time become corrupt from files being deleted and over written. Cyanogenmod is dependent on the SD card so reformatting it could possibly solve your issue.

Make sure you are on 1.5 of the ROM. You should not be having this problem unless you installed a mod that broke it or it was a bad install.

I'm thinking the latter... I flashed the ROM a few times with the same result. I also flashed McTwist Sense 2.1/3.0 and had the same results. Flashed back to cyanogenmod 7.0 and everything is fine again. Have any ideas of what to look for? Mind you, I'm a newb so you might have to spell things out for me.
Thanks again - really hoping to try out your ROM.
Alan

So many bugs... don't know what to do!

Hey everyone ! First I swear I don't post this because I'm too lazy to make a proper search, I've been trying to solve my problems for two days...
Ok, I'll try to sum it up. Sorry if my english goes wrong at some point, I'm french.
Having problems with my micro SD in my Desire, I bought a new one, a kingston 8go, class 10.
My desire was under CM7, was S-OFF with a modified HBOOT. And except from bugs due to my SD (sometimes it would not be recognized), everything was working.
After installing the new micro SD, i did some manipulations: wipe, reinstallation, change of radio/RIL/kernel, and unfortunately ended up with no recovery and others bugs. So I decided (at one point I did stupid stuff) to reinstall RUU aaaand as I was S-OFF with a modified HBOOT, I bricked my phone. BUt after some hours and thanks to the forum, I managed to put back a RUU.
Then I did everything properly: ROOT/S-OFF with revolutionary, wipe, micro SD partition, and CM7 installation.
THen it was hell: I tried everything from regular install to legacy2ext and SimplytoExt etc every time it's really unstable. First the all thing is slow, then I can't flash the google apps, no matter what I try. If I install an app from the market, sometimes it works, sometimes it makes the phone reboot from the boot animation, sometimes it can't install etc.. Google maps was especially unstable.
THen, 10 or 20 manipulations, formatting, reinstallations later, I decided to check other rome, like Oxygen or milwild.
On my last Milwild install, everything is fluid but I can't install a single app (it's just stay on "installation" forever) and I can't wake up the screen after the phone goes to sleep.
Last but not least, my usb charger seems to have transfer problems. It's way to slow and the speed is not constant. During large transfers, comes files go corrupted. Am I usb bricked or something? I tried with another micro SD and it's the same problem;
So here I am, I really don't know what to do more? Any help?
Thanks a lot for your eventual answers!

Seems that installing a RUU solve all the problems for now, I wonder what in the process of putting a custom ROM could have caused so many differents and random problems. I'am doing the all process again to see if I can do it properly.
And again, I installed a custom ROM with CM7 hbott: impossible to download any app and the camera crashed. Any idea?

1. Don't use any D2EXT scripts with Cm7, obviously that's what caused the issue. If you NEED more space (even with cm7 hboot) try using DarkTremor's A2SD.
2. Before you flash a new ROM, do a FULL wipe (either from fastboot or recovery) - erase boot, system, userdata, cache, sd-ext (make sure you have an EXT-n partition on your sd-card, best program to use is gparted)

Desire is designed for class 4 SD card. Although some class 10's will perform at class 10 levels, many do not because of this. Kingston Class 10 being one example (I have one).
My kingston class 10, in Android, performs at class 6 speeds. Which would be ideal, but my class 10 Kingston was slower with data2sd than my class 4 sandisk.

Thanks for your answers:
Desire is designed for class 4 SD card. Although some class 10's will perform at class 10 levels, many do not because of this. Kingston Class 10 being one example (I have one).
My kingston class 10, in Android, performs at class 6 speeds. Which would be ideal, but my class 10 Kingston was slower with data2sd than my class 4 sandisk.
Click to expand...
Click to collapse
Ok, I might send it back and change for another model then. But still it can't explain the problems I have
1. Don't use any D2EXT scripts with Cm7, obviously that's what caused the issue. If you NEED more space (even with cm7 hboot) try using DarkTremor's A2SD.
2. Before you flash a new ROM, do a FULL wipe (either from fastboot or recovery) - erase boot, system, userdata, cache, sd-ext (make sure you have an EXT-n partition on your sd-card, best program to use is gparted)
Click to expand...
Click to collapse
I only was using this script to put the apps on the ext partition and I removed it. It's obviously not the problem since they stayed after a clean install.
I always fo a full wipe, I even formated all the partitions and my EXT partition is there and well aligned.
Here I am: I managed to "stabilise" with a gingerbread RUU, rooted and S-OFF with revolutionary.
I used RM recovery (with USB brick fix) and it seemed to help. I don't have any USB transfer problem any more.
The RUU works like a charm.
Then I tried again to install two customs romq, without any script or modification:
-on Milwild, I have still this "deep sleep" problem. I can use the camera, but I can't install any app from the market. It's stays on "installation" forever.
-On CM7 (I put the CM7r2 HBOOT with it) it starts well: I can install google maps. But then I try to open it and it freezes. Then I try to mount the FAT32 partition on my computer and it doesn't work. The cellphone also freezes when I try to reboot (there is the wheel, turning and turning, but nothing happens). SO I forced reboot, and then, google maps had just ... disappeard. I think my phone is haunted...
Isn't it strange that my cellphone is perfectly normal under RUU but can't bear any custom ROM???
I think I'm gonna go back to the RUU and try to use another SD card but I'm sceptical. If someone has a miraculous idea to share, I'll take it!!!
Thanks again

Well, rootSU, it seemed that you found the answer. I put another class 2 sd card and it seems to work again! I just spent hours on this for nothing... The strangest is that the class 10 card work perfectly when out of my phone...
Any advice about a good class 6/8/10 that could improve the performances without crashing like this?
EDIT: last question, I used the app2sd script you introduced, but I can't install any app with it, it says that I've got unsuficiant stockage space Oo.

I use.my class 10 Kingston and it works perfectly as a class 6. Plus its pretty future proof. Just no.good for data2sd.
Should work fine for everything else though
Sent from my HTC Desire using Tapatalk

Well, mine didn't worked at all, except the RUUs...strange! I have fully configured my class 2 SD card with simple2ext (only app on the ext partition, not data) and it works.
As I'm tireless, I'll try to put all this via nandroid on my class 10. If it could work like a class 6...

What did you use to partition the Kingston?
Sent from my HTC Desire using Tapatalk

I partitioned it several time, with gparted and recoveries. I'm a bit worried about some part of the hardware managing the connection with the SD card that could be partly broken. I decided to change my first SD card when I first saw a "you need to put an SD card" when I try to take a picture. I had problems with files disappearing from the SD and reappearing. Also I lost some applications that I couldn't appear. I figured the card was dying.
Then I put a new SD card, faster and with larger capacity and everything goes wrong;
Then I put the old one back and... for now, everything works.

EXT-partition makes phone unstable.

Hi there!
I've got a problem with my HTC Desire sd card partition.
Every rom works fine, sd card also but it starts to force closing, freezing and randomly rebooting when I push apps to sd card using any of the A2SD scripts (except stock one). I mean, when I use roms which just need SD-EXT (such as MIUI or SpazeDog ICS) nothing seems to work uncorrectly but when I move apps all problems start. I tried many roms (MIUI, InsertCoin Sense, SpazeDog) and diffrent moving scripts (A2SD+ ; D2EXT ; and others which names i forgot) and it always caused reboots, FCs and frezzes when I pushed my apps. Can you guys tell me how to fix this problem, or is it just my SD card broken? I always partitioned card by 4EXT recovery, tried EXT3 and EXT4 file system, never made partition bigger than 1GB. My SD card is a Sandisk 16GB class 4.
Sorry for my bad english, Szotaa

An important thing is the method younused to partition your sd (a tool you used).
Also, it wouldn't be bad to buy faster sd card (class 6 or 10).

So, the solution for the problem would be using another partitioning tool? Is gpared a good choice?

Now I saw you used 4ext recovery, and it's the best tool. Gparted is the second best, but I think u need a new sd.
One more question, is your phone s-off? Some scripts need it to work properly.

Yes, my phone is s-off. So its a sd card issue. At the end could u tell me is supernova rom going to work properly, even on my sd card? Because i heard it is the stabliest d2ext ever made.

szotaa said:
Yes, my phone is s-off. So its a sd card issue. At the end could u tell me is supernova rom going to work properly, even on my sd card? Because i heard it is the stabliest d2ext ever made.
Click to expand...
Click to collapse
Supernova recommend a certain brand of sd card to work with the rom. I cant remember it off the bat but it's stated on Droidzone's website/forum.

stankyou said:
Supernova recommend a certain brand of sd card to work with the rom. I cant remember it off the bat but it's stated on Droidzone's website/forum.
Click to expand...
Click to collapse
Based on user feedback, we recommend a Transcend Class 6 for D2SD roms.

[Q] Cannot mount SD Card - Many methods tried

Hello!
I have been a long time lurker and have been tweaking my phone for years.
Usually when I stuff something up, I can fix it.
That is not the case this time ;_;
This phone has been working fine for over 2 years without a reflash or anything done to it.
The battery died one Friday and the phone was not charged for 3 days.
It did not boot. HBOOT and Recovery were fine, but could not mount /sdcard in recovery
I ended up installing an RUU (Telstra_WWE_2.26.841.2). Cannot install other RUUs as sd card (Goldcard) cannot be read.
Android runs without recognising the SD card.
Recovery still does not recognise the SD card
Have tried:
- fastboot oem enableqxdm 0 (success, but did not fix problem)
- fastboot oem clearconfig
- S-Off and flashed different recoveries via Fastboot.
- 4Ext Recovery - USB Unbrick is ineffectual
- 4Ext Recovery - Partition sdcard correctly tells me the size of the sdcard, but then returns "Cannot read partition table"
- Two different SD Cards tried to no avail
This really sucks. I didn't even get to break my phone by myself.
Phone current status:
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.11.05.14

No suggestions?

- Strange, you ran the RUU from sd card though, so it must have mounted and read it? Are the two sdcards same brand? Do they work ok in another phone?
4EXT recovery is the best solution for this, surprised it doesn't work.
- USB unbrick doens't work at all?
- Can't partition either card? Have you tried completely reformatting first?
- Can't install any ROM.zip from sdcard?
If it still doesn't work, I'd try reformat and repartition using gparted, then full wipe and resintall ROM from scratch.

- Strange, you ran the RUU from sd card though, so it must have mounted and read it? Are the two sdcards same brand? Do they work ok in another phone?
I ran the RUU from my computer because the SD card was out of action.
The two SD cards are different brands. Would that affect it a lot? They both work in card readers, card adapters, other computers, and other Android devices.
4EXT recovery is the best solution for this, surprised it doesn't work.
- USB unbrick doens't work at all?
- Can't partition either card? Have you tried completely reformatting first?
- Can't install any ROM.zip from sdcard?
USB Unbrick does its little thing, then asks me to reboot recovery now. After reboot, I still get the "Error mounting your sdcard.." while 4ext is booting. 4ext then boots into safe mode.
I have completely reformatted and partitioned one of the cards in GParted running off a bootable USB stick, and that still didn't work.
Can't install anything from SD card ;_;
If it still doesn't work, I'd try reformat and repartition using gparted, then full wipe and resintall ROM from scratch.
Without an SD card, is installing a ROM possible?
Playing with all the settings in 4ext at the moment. I'll keep y'all posted.

When I click partition sdcard, it says "There is 9xxxxxxxx MB of space on your sd-card", which is why I don't think it is a hardware error.
I then clicked file system check, and then Repair Filesystem.
Partition sd-card now says there are 0MB of space on my sd-card. lol.
what is this i dont even
-------------------------------
Rebooted, partition sdcard reads the 9xxxx MB of space on the card, so no problems there.
Trying to repartition it gives this error "Error re reading partition table. Please reboot recovery and start over."

Last bump.

I can't figure this one out to be honest. I really thought a complete reformat in gparted would work. Are you trying this using a card reader i.e. partitioning while not in the phone?
I'm beginning to think that the phone has a hardware issue reading the actual sd card, because both cards work in other phones and are read by computers / card readers just fine.
Last resort, if you can't run the RUU from the computer.
- Reformat sdcard to FAT32 only
- Extract the 2.3.3 GB RUU from the ROM.zip, follow Step 7 of Bortak's troubleshooting guide stickied at the top of Q&A, to run the RUU from sd.

I can't figure this one out to be honest. I really thought a complete reformat in gparted would work. Are you trying this using a card reader i.e. partitioning while not in the phone?
The complete reformat and partition was done with the micro SD in an SD adapter in a USB card reader plugged into a computer. I couldn't do it from the phone as the phone cannot read the darn thing.
I'm beginning to think that the phone has a hardware issue reading the actual sd card, because both cards work in other phones and are read by computers / card readers just fine.
The only problem with the phone having a hardware issue is that 4ext recovery "sees" the card and tells me that I have 8 GB of space on it. However, 4ext cannot do anything to the card.
Last resort, if you can't run the RUU from the computer.
- Reformat sdcard to FAT32 only
- Extract the 2.3.3 GB RUU from the ROM.zip, follow Step 7 of Bortak's troubleshooting guide stickied at the top of Q&A, to run the RUU from sd.
I don't think this will work because the phone cannot see the SD card. Even converting a card to a goldcard and trying to install an RUU does not work.
This is quite saddening ;_;

thebestnoobcake said:
The only problem with the phone having a hardware issue is that 4ext recovery "sees" the card and tells me that I have 8 GB of space on it. However, 4ext cannot do anything to the card.
Click to expand...
Click to collapse
But if 2 different sdcards work in card readers and mount in other Android devices, then logic says it could be a hardware issue with the Desire.
Just because 4EXT sees it, the fact that it can't mount it or do anything with it further reinforces this theory.
Last resort, if you can't run the RUU from the computer
- Reformat sdcard to FAT32 only
- Extract the 2.3.3 GB RUU from the ROM.zip, follow Step 7 of Bortak's troubleshooting guide stickied at the top of Q&A, to run the RUU from sd.
I don't think this will work because the phone cannot see the SD card. Even converting a card to a goldcard and trying to install an RUU does not work.
Click to expand...
Click to collapse
You need to try it though
2.3.3 GB RUU does not require a goldcard as far as I know. If you made a goldcard, that process may have gone wrong somewhere not sure.
Which is why a complete reformat, a single clean FAT32 partition needs to be tried.
Try Step 7, see if the phone can read the PB99IMG.zip when started up in bootloader