Related
Today it opened my phone and it shows my sd card as damaged and all the apps are crashing all over the place, so i reverted to a backup and same deal, i installed the stock htc hero rom and it worked fine, i did a wipe and installed modacos 3.1 again and it finished but all the apps started crashing again and it had all the apps that i had installed previously, how do i restore my phone to a clean stock version of modaco 3.1 without keeping all my apps installed!?
mike390 said:
Today it opened my phone and it shows my sd card as damaged and all the apps are crashing all over the place, so i reverted to a backup and same deal, i installed the stock htc hero rom and it worked fine, i did a wipe and installed modacos 3.1 again and it finished but all the apps started crashing again and it had all the apps that i had installed previously, how do i restore my phone to a clean stock version of modaco 3.1 without keeping all my apps installed!?
Click to expand...
Click to collapse
Sounded weird, can agree with that. Are you using apps2sd? Try do a backup of your sd-card, format it, wipe and install ROM. Dont restore a backup or something.
Now copy ur files back to the sd-card and see if it makes any difference
Yeah, it sounds like your ext2 (or ext3/ext4) partition for apps2sd is corrupt. It may even be an issue with your SD card. SD cards are not optimized for ext2/3/4 partitions, and as I learned through running android on my Vogue, it's rare, but your SD card can become permanently damaged by using this filesystem on it.
If formatting your SD card like sinnadyr suggested doesn't work, I would re-partition the entire card, making your FAT32 partition smaller by maybe 512MB and have everything else the same size. This will obviously result in 512MB less usable space on the card, but at that point I don't think you'd have another option anyway.
(I may be off about the size of 512MB... I'm tired and drunk and can't be bothered to look up the actual size of the swap/ext2 partitions.)
If all else fails, try a new SD card.
Your Hero can be saved
Ok... I've had this... and this is how I solved it:
-save what you have to from sd to pc
-format sd
-partition from scratch
-reboot
-put what you saved previously back on
-done
sounds easy, but it actually took me AGES in between finding out and doing it.
In my case it was due to a combination of using a program to move the cache to SD AND mounting the SD card WHILE some app was doing something (APP2SD was enabled). All I know is I never used the cache to SD program again and 3.1 is now running smooth on my hero.
Good luck
Ciao
p.s. If the steps above do not seem to work just do all the Wipes, load another rom, play with it for 2 mins, then re-do all the wipes and start off. I know I'm being a bit confusing but trust me, problem will be solved eventually. Just make sure u have plenty of time when u start the whole process
V.
There's a guide somewhere how to repartition your SD card through ADB, this is what I did when the same thing happened to me and the partitions were corrupted.
Ok, I have a Samsung Fascinate.
Rooted, CWM, ROM Manager, Root Explorer, Titanium Backup, SetCPU, ASTRO, JT 1000 voodoo kernel with animation.
Ok the problem is and I am almost certain that what caused it is flashing JT's 1000 kernel over top the original 0.2 JT voodoo kernel. However I had read in the forums that people have done this with no problem and I believe in the install thread it says you CAN do it with indeed no problems. However soon after doing the flash everything was working great and I took a couple pictures at dinner which is how I know it was working. Later last night I went to take another picture while out and it wouldn't let me because the SD card wasn't being detected.
I have a sd card reader but not with me and won't until I get home later tonight but I figured maybe until then I can get some help to how to fix it for when I do get home.
I have took a 8gb mini sd from my girlfriends HTC Eris and put it in just to see if it would read which it does perfectly fine. However you plug my 16gb back into the phone and it doesn't even recognize plugging it into the phone.
Any ideas?
all the views and no replies?
any ideas would help guys!
Sounds like your sd card is corrupted. Did you try the card in another phone? Try to reformat the card.
sent from my 1.2ghz voodoo fascinate
Copperhed said:
Sounds like your sd card is corrupted. Did you try the card in another phone? Try to reformat the card.
sent from my 1.2ghz voodoo fascinate
Click to expand...
Click to collapse
the back up that I made and all, wouldn't that be on the sd card though?
I would think trying to save the card would be a better choice at first eh?
anyone else?
vecchioni27 said:
anyone else?
Click to expand...
Click to collapse
If the card works in another device, then I would wonder if the problem could be voodoo specific, such as the 0 internal memory issue. As far as I know, the only fix for that is the complete voodoo removal process, and a wipe in both stock recovery and cwm.
Sent from my SCH-I500 using XDA App
Daswolven said:
If the card works in another device, then I would wonder if the problem could be voodoo specific, such as the 0 internal memory issue. As far as I know, the only fix for that is the complete voodoo removal process, and a wipe in both stock recovery and cwm.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I tried to put the card into my sd card reader on the computer and it wont read it...assuming its a bad card. When its in the phone the sd card reader slot heats up too a massive HOT temp really quick within second and doesn't do anything. I guess I am gonna unroot using another sd card and take the phone to verizon and be like wtf....
I un-rooted and am gonna take the phone to the verizon store.
I plugged a 1GB from my old phone into the sd card slot and re-flashed CWM to see if I just removed the kernel's if maybe that would fix the sd card but I am almost positive its the sd card that is fried somehow...But it put the phone back to stock except it was rooted...not sure how that happened but i guess everything was on the sd card that I had done???
So confused but basically I am just gonna goto the store get a new card when they realize mine is bad and then re-do everything...Just never flashing a kernel on top of another one again whether people say its safe or not!
vecchioni27 said:
I un-rooted and am gonna take the phone to the verizon store.
I plugged a 1GB from my old phone into the sd card slot and re-flashed CWM to see if I just removed the kernel's if maybe that would fix the sd card but I am almost positive its the sd card that is fried somehow...But it put the phone back to stock except it was rooted...not sure how that happened but i guess everything was on the sd card that I had done???
So confused but basically I am just gonna goto the store get a new card when they realize mine is bad and then re-do everything...Just never flashing a kernel on top of another one again whether people say its safe or not!
Click to expand...
Click to collapse
I can assure you that had nothing to do with your card. Sometimes you get a bad lot. I order about one a month for various things, and have had to RMA here and there. I swapped the one my phone adopted with for an 8gb class 10 anyway, because the stock are class 2.
Sent from my SCH-I500 using XDA App
Daswolven said:
I can assure you that had nothing to do with your card. Sometimes you get a bad lot. I order about one a month for various things, and have had to RMA here and there. I swapped the one my phone adopted with for an 8gb class 10 anyway, because the stock are class 2.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I am a bit confused...it sounds like you said it had nothing to do with the card but then went on to say how you RMAed a few here and there and such...lol
vecchioni27 said:
I am a bit confused...it sounds like you said it had nothing to do with the card but then went on to say how you RMAed a few here and there and such...lol
Click to expand...
Click to collapse
Lol. I mean to say the kernel flashing cannot cause the sd card to fail. The card was probably bad to begin with. A bogus card will simply fail, sometimes after functioning fine for awhile.
Sent from my SCH-I500 using XDA App
Daswolven said:
Lol. I mean to say the kernel flashing cannot cause the sd card to fail. The card was probably bad to begin with. A bogus card will simply fail, sometimes after functioning fine for awhile.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
oh ok, makes sense now...however a bad sd card pretty much screws me over because that is what held everything on it including the kernel and such along with all my apps?
vecchioni27 said:
oh ok, makes sense now...however a bad sd card pretty much screws me over because that is what held everything on it including the kernel and such along with all my apps?
Click to expand...
Click to collapse
No. the install file for the kernel, but that installs it on the phone. Apps are stored on the internal memory, not the sd card. Pretty much, it just holds your music, pictures, application data in some instances (not the app itself), and any files you need to flash.
Sent from my SCH-I500 using XDA App
Daswolven said:
No. the install file for the kernel, but that installs it on the phone. Apps are stored on the internal memory, not the sd card. Pretty much, it just holds your music, pictures, application data in some instances (not the app itself), and any files you need to flash.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So when I get my new sd card tomorrow and load launcher pro back onto the phone, my apps should still be on the phone??
what if I can't even download launcher pro due to this problem of it not letting me download an app because it says I don't have enough internal memory available...
Whoa.
Now that problem is the internal memory issue, not the external sd card. That is voodoo related, and the post about completely removing voodoo addresses it. I ran into that once, and it took about soften minutes to fix following those instructions.
Sent from my SCH-I500 using XDA App
vecchioni27 said:
So when I get my new sd card tomorrow and load launcher pro back onto the phone, my apps should still be on the phone??
what if I can't even download launcher pro due to this problem of it not letting me download an app because it says I don't have enough internal memory available...
Click to expand...
Click to collapse
If its internal and not your sdcard here is your solution.
http://forum.xda-developers.com/showthread.php?t=804784
nemesis2all said:
If its internal and not your sdcard here is your solution.
http://forum.xda-developers.com/showthread.php?t=804784
Click to expand...
Click to collapse
awesome, thanks!
Why do I still see stuff in /sdcard after wiping and ODIN-ing JFD and re-wiping? How do I really turn my phone back to factory?
I'm having some flakiness with some of the new ROMS, and I am pretty sure it has nothing to do with the ROMs. Specifically, I have a problem where my phone will wake up after receiving a text message and never go back to sleep. Also, several times my phone will boot into a situation where it cannot see any towers (almost like airplane mode). Just general flakiness. So, I want to put my phone back in its newborn, fresh out of the box state and start over. However, I still see all of the files and directories in /sdcard that were in there before I wiped (from recovery). Strange.
Skip
I actually did this earlier today because of a major problem with the music player. I transfered all my backups to my computer then went to Settings>SD Card and Phone Storage then scrolled down to Phone Storage and selected Format SD Card. After I formated the card, I installed JFD with Re-Partition checked. After Odin did its thing, I let the phone reboot and copied a rom to my internal card and the Clockwork update.zip. Installed the update zip through stock recovery and the rom through Clockwork.
Hmm, that didn't work for me. Sure, my external sd card is clean now, but /sdcard still has all the same files in it. Is it safe to just rm -rf * in the /sdcard directory?
For instance, I just odin-ed (with repartition checked) and I still have external_sd showing (a leftover from Obsidian 4.2). I also see busybox, TitaniumBackup and several other folders. I'd like it all to be gone so I can be sure of my re-installation process.
Don't format the SD card, format the phone storage.
Yeah, you formatted the wrong one. Were you on Axura 2.0.5? I had that issue also for some reason... might have something to do with BlackFroyo on top of it?
Just went to Axura Final and am not noticing it...
If you want to wipe the whole phone including the internal memory card. Go to the market and download SGStools. Once installed go to secret codes and find Hard Reset. Just make sure to a make back up of both internal and external cards, cuz one never knows.
@s15274n, no I was not using Axura.
I did see that I formatted the wrong one the first time. Np, I had backed everything up to my computer. Anyway, I formatted both internal and external storage, re-Odin-ed, and then flashed Obsidian 4.2. I have already seen when I miss a call, my phone display does not go back to sleep, even with the new ROM. I guess I will Odin again and this time just stay on stock, or maybe just stick with the Bionix ROMs. If my phone can't play nicely with these new ROMs when flashing on top of a fresh Odin JFD, then I guess it just wasn't meant to be.
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Did you ever run an older ULF kernel at some point? Are you running one now?
I had similar issues with both my SD card *and* the internal SD, which was causing all sorts of random system glitchiness. In my case, I suspected that this was due to the problems in early ULF kernels that caused filesystem corruption. I ended up using Heimdall (you'd use Odin if you're on Windows) to restore an official Samsung firmware, then I reformatted both SD cards, and from then on everything was fine.
There's probably a less drastic approach to be taken, but restoring to stock from Odin/Heimdall is a pretty surefire way to get rid of all the gremlins.
Incidentally, it was at that point that I decided to stop flashing anything except official or leaked Samsung ROMs until CM gets released. The price for being an early adopter is just too high
I am not sure what ULF kernels are, but all I have had is stock, then Eugene, then I did a restore to my stock backup (that screwed thigns up) so I reflashed eugene. I don't know how to use odin\can't figure out what files i should use.
julienrl said:
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Click to expand...
Click to collapse
Julie, I had this same problem with both this ROM, and my proceeding one, ASOPish; as have many, many others!
I too have been wanting a fix, but have not come across one. Because I am able install data onto my micro sd card via the adapter this is what I have resigned to doing. There was a mounting fix posted last month some time, but it didn't work for me, though others state that it did for them.
Sorry I couldn't give you a more workable solution, but at least, for me, this way does work.
FYI I had this problem until nero V3
Eat at Joe's
Having micro sd issues also. I tried moving some music and pics from the internal sd. It put the names but 0 data. I erase them and they come back. I reformatted the 8gb card it said 8gb free. I go back to the gallery or music player and they are all back. Check the sd with a file manager and thete they are.
t1n0m3n said:
FYI I had this problem until nero V3
Eat at Joe's
Click to expand...
Click to collapse
hum... anyone else with this problem fix it by using nero v3?
This is happening on all 2.2 roms.
One issue was fixed, where the internal and external cards were being read opposite to what there were ..., but the issue of reading external sd above 2gigs is still there ...
If I remember correctly, this was the issue when 2.2 was released for the N1 .... they forgot to re-add support for sdhc cards... that's why they pushed 2.2.1.......
My SD card access has gotten EXTREMELY slow. I'm running CM7 nightlies, with DT A2SD 2.7.5.2. For some reason lately, writing files to my SD has slowed to a crawl, and it seems to be getting slower and slower. Copying an ~80MB ROM to my SD can take 5-10 minutes.
Is there anything I can do short of re-formatting the card? That would be a big PITA.
There is an issue with .37 kernels that cause this.
Sure enough, I'm running redstar's kernal which is a .37 version.
I get around by just mounting from recovery.
That's fine for flashing, but it doesn't help with moving large media on and off the SD card.
Sure it does. You get full SD access in recovery, no different from mounting via the notification bar.
And recovery uses a different kernel i believe. (.35.7 ?)
Sent from my Nexus One using XDA App
Yeah, that's why it works.
Hi.
I've got the 37.2 kernel for cyanogenmod 7 RC2 and got the same problem. Is there any other kernel that is supported and will increase the speeds?
Got that same issue in recovery :S
Regards
Kevin.