Related
I am running into SD card mounting problems on MIUI. After I load the rom, everything works fine for a while. Then the SD card will show up as having been ejected. I remove and replace the card, and if it is read at all, it's read as blank or damaged. It reads fine both on a computer and on this phone running other roms. What's even weirder is that, although the card reads fine on CWM at first, once I start having problems with it in the ROM, it won't mount in CWM either.
I have reloaded the rom three times now. First time was from DL09 stock, second time from EB01 stock, last time from CM7. Both times I went to stock I used the instructions from development (atlas.pit, repartition). All times I wiped cache, data, dalvik. I've flashed both from CWM4 and CWM3. I've used two different SD cards (both sandisk, a 2g and 32g) I've tried wiping and formatting the cards, both on the phone and on the computer. I've tried battery pulls and reboots. I've tried both cards. I've tried restoring apps from Titanium (just apps, no data) as well as fresh from the market.
From where I am now (card never mounts on ROM or on CWM, even if blank and freshly formatted), the only thing that has worked in the past is to go back to stock and reflash the ROM. But that doesn't seem to be a long term fix, because each of the three times I've done it, the problem just returns, and I can't identify anything I'm doing wrong. I haven't had problems with CM7 or comrom, but I really want to make MIUI work! Help!
I am curious as well about SD issues on AOSP in general. I was having the same issues on CM7 then shortly after it started I lost roughly 5 gig of data off my card, including all my pics. I was able to recover the pics with Recuva but I am still wondering why.
I remember reading a short blurb about this some weeks ago but haven't been able to find it again.
I've been having ongoing problems with my SD card in both MIUI and CM7. Basically, sometimes my card will mount and sometimes it won't. When I try to mount it, it sometimes says "damaged card" or "blank card" There's no consistent behavior. Sometimes it loads up fine on reboot, sometimes it works fine if I eject and reinsert it or unmount/mount it, but sometimes not. I've tried two different cards - one a sandisk 32gb class4, one a sandisk 2gb class4. I've tried reformatting the cards both on the phone and on the computer, using windows standard format and also the sdformatter program. I've loaded each ROM several times, ODINed back to stock, ext4 formatter, kernel cleaner; tried different kernels, different radios, different cards.
The cards I'm convinced are not the problem, because they work fine on the computer and also on my phone using different ROMs. I've seen people come up with this problem here and there, but not found a reliable fix. Every thing I've seen recommended I've tried, but nothing lasts. Sometimes things will work fine for a couple of days, then I'll start having problems again.
bump - anybody have any input on this problem?
+1
just flashed cm7. My sdcard works fine on cm6.
the other weird, app2sd is just fine, every app on that partition working, except accessing sdcard.
sdcard also can mount on recovery using, as well as mount mass storage via recovery (mass storage failed on OS)
The only problems I've ever seen with sd cards is on ec09 but not cm7 or miui.. based on what you describe...I would think its a hardware issue with your phone not the rom, not the kernel, nor the sd card itself, have you tried pulling the battery, removing the sd card and cleaning the contacts on your phone with some rubbing alcohol on a q-tip..do the same to the card or you can use a pencil eraser for the card...is it possible you could have tried to insert a card the wrong way or a little crooked? I'm just brain storming for ya cause I'm not sure on a definite fix.
If you can, I would back up everything on your card while its still usable just in case its crapping out on ya
Sent from my SCH-I500 using XDA App
Thanks. I haven't tried that, but not sure how it could be a hw issue since the card works just fine on other ROMs on the same phone. Never had any SD card issues of any kind until I started messing with these GB ROMs. I will try, though.
I'm really thinking of going back to a froyo rom for now because I need stability. But this is such an intermittent/rarely reported issue that I don't think anybody's really working on it. I don't know that it will ever get fixed, in other words. Oh, well.
Well, I've given up on cm7 for now. I've gone back to ed05, trying the powerwashed ROM for now. Got to get some stability out of my phone, and unfortunately, I'm coming up with nothing from cm7. Maybe if there's a big update or something I'll have time to play with it again.
solved on CM-7.1-Pre
tried installing other rom base on CM-7.1-Pre and it work like a charm.
still curious if i have bad sdcard, tried back to previous ROM, and.......... the problem persist there.
so I decide to try dualboot.....
All my sd card mount issues are usually solved with a battery pull
Sent from my SCH-I500 using XDA App
bstarr3 said:
I've been having ongoing problems with my SD card in both MIUI and CM7. Basically, sometimes my card will mount and sometimes it won't. When I try to mount it, it sometimes says "damaged card" or "blank card" There's no consistent behavior. Sometimes it loads up fine on reboot, sometimes it works fine if I eject and reinsert it or unmount/mount it, but sometimes not. I've tried two different cards - one a sandisk 32gb class4, one a sandisk 2gb class4. I've tried reformatting the cards both on the phone and on the computer, using windows standard format and also the sdformatter program. I've loaded each ROM several times, ODINed back to stock, ext4 formatter, kernel cleaner; tried different kernels, different radios, different cards.
The cards I'm convinced are not the problem, because they work fine on the computer and also on my phone using different ROMs. I've seen people come up with this problem here and there, but not found a reliable fix. Every thing I've seen recommended I've tried, but nothing lasts. Sometimes things will work fine for a couple of days, then I'll start having problems again.
Click to expand...
Click to collapse
I also have problems with my SD card. I can't partition mine. I more or less bricked mine about a month ago flashing a voodoo kernal, or not voodoo (I can't figure the whole thing out anyway) where it wasn't supposed to be (I think....), and followed Dale V's instructions on unbricking EXACTLY. I've now gone clear back to Eclair 4 times, ODIN'D AND HEIMDAL'D each and every time I've gone back to stock, AND I've used different links to different DL09, DL01, ED01, EB01, ED04, and on, and on, and on...and every time, my SD card partitions perfectly, I think (at least I don't get the E: can't format, file doesn't exist crap when I try to wipe dalvik cache, and only dalvik cache). As soon as I flash 7/17 CM7, the updates, gapps, glitch kernel, I have no partition. I can see the partition with file managers, but there's nothing there.
So, I totally feel your pain.
And while i'm here, why do I have a .apk called FOTAKILL in my files????
Peace!!
Mona
chaqiel said:
solved on CM-7.1-Pre
tried installing other rom base on CM-7.1-Pre and it work like a charm.
still curious if i have bad sdcard, tried back to previous ROM, and.......... the problem persist there.
so I decide to try dualboot.....
Click to expand...
Click to collapse
CM7.1 pre is an older build, correct? Where can I find it? Am I understanding that you install this one first and upgrade from there, or just leave it at this build? Anything else I should know if I want to try this out?
having the same problem mate my sd card is damage after i flashed miui
when i connected my phone to pc to test the connectivy it also cannot detect my phone btw my phone is sgs19000..and when i ejected the cable it says my sd cad is damaged..i know i safely remove it..but what is the proper way to safely remove it in miui because its a little different compare to stock/other ROms..
me too, but only on miui & 32gb c4 sundisk microsd on stock all normal. On all new kernel when my phone wake up I see this message.
I can't see problem on old kernel - try kernel neo09.
And maybe this help too - multimount app from market.
The problem: SD card is not recognized when flashing new roms that have been released the month of Feb 2013. Running the Venom Rom, or even the older NillsP roms, the SD card works fine
Here is my setup
- Rooted, HTC unlocked, S-ON, Gingerbread+patch Firmware
Here is what I have tried
- Running the new "wipe tool 5times wipe" , flashing the EclipticRez rom
- I log into the phone, go to settings, storage, click MOUNT SD card, and it says "preparing sd card" but never finishes
- Restarted the phone, back to settings, storage, mount sd card was still there.... clicked it .. no dice
- I then shut the power off, removed the SD card put in a spare 8 GB, settings, storage, mount, and even tried format.. that all failed
- I then... restored the old Venom Rom, and POOF SD card shows up and works....
- I even tried the new viral rom, and the sd card will not work there too...
- I have tried, wiping the rom again, reinstalling the EclipticRez with a different kernal, no dice...
You should get off gingerbread firmware. That sounds like its the problem.
Sent from my Nexus 7 using Tapatalk 2
where does one get the most current firmware
I thought that the firmware was the problem, but just wanted to ask everyone what they thought.... I have been digging around and can not seem to find where the firmware is posted. I am not sure which version to use for the new roms. Is it the ICS firmware? If so, do you have the link?
The latest (Global leak) version can be found here. http://www.androidfilehost.com/?fid=9390034591667978440. Since your s-on, you might have to relock then flash RUU. Unlock again. Install custom recovery. Then flash a rom. It is a lengthy process.
But since you are s-on. I would recommend flashing this one. http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Just a tip, delete the recovery.img from the RUU zip file and then run it. That way it won't overwrite your custom recovery
Sent from my ADR6425LVW using xda app-developers app
slash79 said:
The problem: SD card is not recognized when flashing new roms that have been released the month of Feb 2013. Running the Venom Rom, or even the older NillsP roms, the SD card works fine
Here is my setup
- Rooted, HTC unlocked, S-ON, Gingerbread+patch Firmware
Here is what I have tried
- Running the new "wipe tool 5times wipe" , flashing the EclipticRez rom
- I log into the phone, go to settings, storage, click MOUNT SD card, and it says "preparing sd card" but never finishes
- Restarted the phone, back to settings, storage, mount sd card was still there.... clicked it .. no dice
- I then shut the power off, removed the SD card put in a spare 8 GB, settings, storage, mount, and even tried format.. that all failed
- I then... restored the old Venom Rom, and POOF SD card shows up and works....
- I even tried the new viral rom, and the sd card will not work there too...
- I have tried, wiping the rom again, reinstalling the EclipticRez with a different kernal, no dice...
Click to expand...
Click to collapse
did you ever try RUU'ing back to stock and starting over again? Did that fix the problem?
My phone just stopped mounting my sdcard on any rom.
I've wiped, tried scott's 5x wipe tool, and both roms I tried will not work. it says "insert SD card" but it's already in. I can get it to say "Damaged sdcard" too, and tried formatting, but that didn't work.
So I'm now downloading the latest RUU [ http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ] it says 10 minutes left on the download..This will be my first time ever going back to stock on my rez. But I surely hope this will fix it. But does anyone have any other suggestion before I go back to stock?
edit: ok. I had the RUU downloaded, and was about to flash it, when I realized my sdcard in an external reader seemed to be acting funny. When I was searching for a file with "find" [lists all the files in subdirs] it would always error out and I would have to pull it out and put it back in the reader again.
So I tried formatting My sdcard again [I just did it a few days ago because I kept losing files to LOST.DIR, thought a reformat was in order]. So I did that again, used gparted in Ubuntu to format my sdcard fat32 again. I put it in the phone and booted it up, and I got no errors! yay. I'm glad I didn't restore it to stock. all is well.
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy
As the title says implies, I am having trouble writing data to my external SD card - both through the phone and while connected to a PC.
Background: Got the S4 about a week ago. It was on NK1. I rooted, de-bloated, and made back-up in SafeStrap. Discovered I had to run the KK SD Card fix, but was able to write to the SD card afterwards. Yesterday, while trying to copy a file to the SD card while connected to a PC resulted in a failure (Device stopped responding or was disconnected error). After that, the whole phone went wonky - Titanium, Root Explorer, File Manager, etc... wouldn't open and/or run properly after wards. Several reboots and the problem persisted.
Figured I would just restore my back-up. Well I screwed something up and got stuck in a boot-loop - I odined back to NC5 (figured I didn't need to be on NK1), and re-rooted. Setting my phone back up I realize I can't write to the SD card again. I run the SD Fix but to no avail. Opened Root Explorer and looked at platform.xml, which has all the correct permissions (as in this post).
What's going on and how do I fix this? The SD card is a pretty important feature for me. I can write to and copy to the internal storage either through the phone and while connected to a PC, but not the SD card. FWIW, the SD card works flawlessly in my old phone, so I know it;s not the card.
Going nuts here.
Thanks,
Edit - So playing around with another (lower capacity) SD card I find that everything works perfectly. When I get time this weekend I will have to reformat and/or get a new card. Strangely, the problem card still works good in my old phone. Very weird.
Turns out the sd card was/is bad. Found a great deal on a 64gb card and it's working great.
So now for more noob questions: What is the correct procedure for restoring and or flashing roms with safestrap? On my other phones I'm used to entering recovery (TWRP) and wiping data/cache/dalvik, formatting, doing a factory reset, etc, then flashing and or restoring.
When I attempted to restore my backup on my S4 (as described above), I wiped data, dalvik, & cache. After that I either did a factory reset or format (can't remember which), the phone automatically rebooted, and that is when I got stuck in the bootloop and couldn't enter safestrap recovery. I am interested in flashing Eclipse but would like to know the exact procedures to avoid losing the ability to enter safestrap.
Thanks for the advice.