Related
juts updated to tazz v28 and cannot move any apps to the sd card - any ideas?
Did you enable app moving in the CM settings? I don't have a CM ROM flashed currently (back to xtrSENSE) so I can't tell you exactly where but I think it's one of the first menus in the CM settings.
yes, i have that selected, and it doesn't matter which app i try to move, even w/ app2sd. when i touch the "move to sd card" button, i get the "failed to move application" error message. any help is greatly appreciated. thank you.
You can always do it again, wipe data+dalvik 3x, reflash. Make sure you do a nand backup before you do any flashing !!!!!
You can also go to this thread http://forum.xda-developers.com/showthread.php?t=733897 Scroll down to post #2 (FAQ)
-This is due to your sdcard being partitioned more than likely. You can either format the entire card on a pc to fat32 or use recovery to unpartition. FROYO won't recognize the ext partitions on your card. App2Sd on FROYO stores all the apps in the same partition as everything else, just in a separate folder that it creates on its own. ***CAUTION***
(YOU WILL LOOSE ANY DATA ON CARD AS IT WILL BE FORMATED SO BACK UP YOUR CARD FIRST!)
-Boot to recovery.
-partition sdcard.
-0 swap
-0 ext2 for apps2sd.
-this will make one whole fat32 partition.
Resolved or no ?????
i've done everything listed w/ no change. the only thing i haven't done is start over and i was hoping to avoid that. everything else is working well, just running out of space. any other suggestions or thoughts? thank you - it is appreciated.
swingdome said:
i've done everything listed w/ no change. the only thing i haven't done is start over and i was hoping to avoid that. everything else is working well, just running out of space. any other suggestions or thoughts? thank you - it is appreciated.
Click to expand...
Click to collapse
Sadly I think that starting over is about your only choice, if nothing else has fixed it. You could also always buy a new sd card and use that new one, then one by one start copying files onto the new card from your old one. Check the space available every time you copy a file over to see if it is 1 file causing this problem. Not really sure what else to do about it but what I posted should help. Try that out and let me know what happens.
does the platform make a difference? i'm running cyanogen mod tazz froyo 2.2.1 build, v28 on an htc eris phone w/ a 16gb sd card.
swingdome said:
does the platform make a difference? i'm running cyanogen mod tazz froyo 2.2.1 build, v28 on an htc eris phone w/ a 16gb sd card.
Click to expand...
Click to collapse
What exactly do you mean? Make a difference to what? Your Apps2SD problem or starting over?
No to either one, in this case.
i meant my app2sd card issue. didn't know if anyone else had this build on this phone and was experiencing a similar problem.
Hi,
I am having the same issue with this ROM, Apps move to SD is failing. I just posted a comment in tazz froyo 2.2.1 build, v28 forum. anyone else having this problem ???
I am having this same problem on my dInc after flashing Kingdom Gengersense 3.0, I have yet to try and reformat my sd card. Hoping that will work
Just formatted the card and did not work. Still won't let me move my apps to SD
verymadworld1988 said:
Just formatted the card and did not work. Still won't let me move my apps to SD
Click to expand...
Click to collapse
It won't let you move any? Some apps don't officially support being moved, but you can force move everything (except you'll not want to move keyboards and widgets because then they won't operate correctly) with Titanium Backup or some other apps out there.
Its Super user is bugged for gingerbread since the update im trying to find the fix
I recently encountered the issue with data dropping out on my phone, so I Odin'ed it back to stock and took it in to the local VZW store. They played with it for half an hour or so before giving up and shipping me a reconditioned unit.
I'd played with CM7 and OMGB/OMFGB before, but the show stopper bug for me was the phone not reading or even recognizing the SD card. (I have a PNY Class 10 32GB Micro SD card.) This was back in early August, and I remember reading a post somewhere stating that this issue had been laid to rest.
So this week, I gave both CM7 and OMFGB another spin, and damned if I didn't run into the EXACT same problem. I couldn't even get the phone to see my 32GB phone while doing the BML/MTS conversion. It would reboot, then I'd get the 20 second countdown for "Waiting for SD card to mount [20s]" So I had to run the installer from a freshly formatted 16GB card just to get it to see the card and finish the install.
My sequence went something like this:
1) Start from ED05 stock (either fresh from the factory, or via Odin)
2) Install cwm4_fixed_for_cm7-ODIN.tar via Odin
3) Boot into recovery, install cm_fascinatemtd_full-56.zip
4) Reboot, let phone boot once into Gingerbread, reboot again into recovery
5) After reboot, install Google Apps
Any suggestions? Am I going to have to reformat this 32GB card to get it working in Gingerbread? I've tried to avoid doing that, since there's about 20GB worth of music and videos that I don't want to re-transfer to it if I don't absolutely have to.
Rom manager does that to me sometimes. Do use it for awhile. Flash manually. But if you want to use Rom manager, go to Tom manager and press menu -> manually flash override -> select OK -> then Fascinate(MTD) -> Then clockwork 3.x.x will probably fix your issue. It fixed mine
Sent from my SCH-I500 using XDA App
Fascinate phones do not recognize 32 GB cards afaik. The card, as I understand, must be no more than 16 GB. If anyone knows differently, please feel free to correct me...
Another Fascinating post by my XDA app...
I've used 32GB cards in mine for the past six months. No problems out of it, until I tried to run Gingerbread.
The max capacity is 32GB, so it won't take anything larger, but anything larger would be hideously expensive anyway.
im sorry to tell you but your SD card may be fried. EC09 is very notorious for "eating" your card. i know GB is awesome and all for whatever reason the ec09 modem doesnt like your phone so try another rom. MIUI FascinateMTD ate 3 of my sd cards. i suggest finding a rom that doesnt use the ec09 modem. give this a shot:http://forum.xda-developers.com/showthread.php?t=1242747 nice rom and you have the option to not use the modem. also is eh09.
zander78 said:
im sorry to tell you but your SD card may be fried. EC09 is very notorious for "eating" your card. i know GB is awesome and all for whatever reason the ec09 modem doesnt like your phone so try another rom. MIUI FascinateMTD ate 3 of my sd cards. i suggest finding a rom that doesnt use the ec09 modem. give this a shot:http://forum.xda-developers.com/showthread.php?t=1242747 nice rom and you have the option to not use the modem. also is eh09.
Click to expand...
Click to collapse
the modem has nothing to do with fried sd cards... its a kernal issue that was supposed to be fixed. Fwiw I run the ec09 modem/radio on every rom I have tried with no fried sd card.
droidstyle said:
the modem has nothing to do with fried sd cards... its a kernal issue that was supposed to be fixed. Fwiw I run the ec09 modem/radio on every rom I have tried with no fried sd card.
Click to expand...
Click to collapse
This is correct. Eh 09 with the ec09 modem has given me the best and most stable kernel -radio combo
sent from my SCH-I500 PWGB 2. 0b3 voodoo
Can I ask a somewhat stupid and somewhat related question to this post?
I've never Formatted my SD before and I just recently installed a Gingerbread ROM. How safe is it to Format the SD from within the Phone options?
droidstyle said:
the modem has nothing to do with fried sd cards... its a kernal issue that was supposed to be fixed. Fwiw I run the ec09 modem/radio on every rom I have tried with no fried sd card.
Click to expand...
Click to collapse
Yeah, I avoided anything running EC09 for just this reason, remembering the warning in GIANT RED LETTERS about EC09 eating SD cards. I actually started out with a SanDisk 32GB card in my phone, and after running into repeated problems with builds of CM7 and OMFGB, I gave up, bought the PNY card for my phone, and moved the SanDisk card over to my Acer Iconia tablet, where (after being reformatted) it has worked without any problems.
The 9/22 glitch is giving me sd card issues.
See here for details.
http://forum.xda-developers.com/showthread.php?t=1252871&page=76
Sent from my SCH-I500 using XDA App
I'm back to Froyo for the moment because none of the GB ROMs play nicely with my SD card. The worst errors seem to have been fixed, but GB remains very finnicky about cards. It works great for some people but is unusable for others. This, of course, makes it nearly impossible to track down the background issues. I suspect things will remain largely the same until we get an official release. In the meantime, you can try different cards and see if one works for you.
droidstyle said:
the modem has nothing to do with fried sd cards... its a kernal issue that was supposed to be fixed. Fwiw I run the ec09 modem/radio on every rom I have tried with no fried sd card.
Click to expand...
Click to collapse
I also use ec09 modem with different roms along with glitch kernel and never had any sd card problem.
I updated my Captivate from Froyo to Gingerbread, via Kies. The SD 32GB card, which has worked without issue for almost a year, no longer mounts after the update.
A friend from work ran into the EXACT same problem with the same setup.
A 16GB card mounts fine. The 32GB card works in other devices, like a camera or on my computer.
A complete wipe and re-install of Gingerbread didn't help.
I've been searching for information on this, and there are complaints about this problem, but so far I haven't seen any solutions or suggestions.
Has anyone seen or run into this?
scifoso said:
I updated my Captivate from Froyo to Gingerbread, via Kies. The SD 32GB card, which has worked without issue for almost a year, no longer mounts after the update.
A friend from work ran into the EXACT same problem with the same setup.
A 16GB card mounts fine. The 32GB card works in other devices, like a camera or on my computer.
A complete wipe and re-install of Gingerbread didn't help.
I've been searching for information on this, and there are complaints about this problem, but so far I haven't seen any solutions or suggestions.
Has anyone seen or run into this?
Click to expand...
Click to collapse
Yes quite a few folks are having trouble with 32g sd cards...actually any card under a class 6 seems to be hit or miss, but almost all 32gb cards seem to be having trouble with mtd roms.
Damn cm7 ate my sd card. OH WELL, I upgraded from a class 4 to a class 10! And a stable release is the EH03 release, so try that. My sd card is good on that one. I heard somewhere that cm7 had some ec09 code in it, so maybe that's why this happened?
actinogen said:
Damn cm7 ate my sd card. OH WELL, I upgraded from a class 4 to a class 10! And a stable release is the EH03 release, so try that. My sd card is good on that one. I heard somewhere that cm7 had some ec09 code in it, so maybe that's why this happened?
Click to expand...
Click to collapse
dont think its cm7 solely, it can happen on all mtd roms...and it really has not been pinpointed why some cards bork and others dont. The only conclusive fact is; a class 6 or higher 2,4,6,8, or 16gb sd card seems to be stable on mtd based roms.
I have the exact same problem with my 32gig sd card...Wont work with CWM packaged with MTD roms...really angers me because I really wanted to try JT's ICS rom.
droidstyle said:
dont think its cm7 solely, it can happen on all mtd roms...and it really has not been pinpointed why some cards bork and others dont. The only conclusive fact is; a class 6 or higher 2,4,6,8, or 16gb sd card seems to be stable on mtd based roms.
Click to expand...
Click to collapse
what's MTD?
I just had my OGDroid eat a class 4 32gb brand new sdhc last night. My Christmas present
Project Elite 6.5
I'm afraid to go buy another one and have it happen again. What should I do? It doesn't even mount in Windows anymore.
Samsung Class 2 16GB works fine for CM7/MIUI/Touchwiz/ MTD ICS, SanDisk class 4 32GB only works well with touch wiz / MTD ICS and my Samsung class 10 32GB is the same as my 16 works well with any ROM that's from my experience.
Sent from my SCH-I500 using XDA App
Hi all,
I recently rooted my phone so I could install a custom ROM. I´m new with android and also with rooting. After reading a lot of articles about rooting and flashing a custom ROM, I decided to give it a chance. Because the CyanogenMod is very populair, I decided to flash this ROM. I rooted my phone with Odin adding the Siyah Kernel. This worked and I followed the manual on the CyanogenMod Wiki for I9100. I flashed CM10 with ClockworkMod Recovery. Everything went fine and I saw the great interface, which is a lot better than touchwiz.
But I could't use the camera app: No external storage available. A 16GB SD card is inside. It appears CM can't mount the SD. I also saw the internal storage: 1.97GB. But the internal storage has to be a lot more than that.
I might think that it has something to do with the encryption I did within Touchwiz. I haven't decrypted the file system before flashing the ROM...
Anything I can do?
Update: I went back to the stock ROM, and could acces the internal storage and SD card. Then flashed CM10 again, and everything was working well!!
cloneOne said:
Hi all,
I recently rooted my phone so I could install a custom ROM. I´m new with android and also with rooting. After reading a lot of articles about rooting and flashing a custom ROM, I decided to give it a chance. Because the CyanogenMod is very populair, I decided to flash this ROM. I rooted my phone with Odin adding the Siyah Kernel. This worked and I followed the manual on the CyanogenMod Wiki for I9100. I flashed CM10 with ClockworkMod Recovery. Everything went fine and I saw the great interface, which is a lot better than touchwiz.
But I could't use the camera app: No external storage available. A 16GB SD card is inside. It appears CM can't mount the SD. I also saw the internal storage: 1.97GB. But the internal storage has to be a lot more than that.
I might think that it has something to do with the encryption I did within Touchwiz. I haven't decrypted the file system before flashing the ROM...
Anything I can do?
Click to expand...
Click to collapse
Same Problem here, I update from CM 9 to CM 10 and I can't use Camera and It seemd than there is no internal SDCard
Frank
I am too having this issue ever since moving to custom ROMs. Its not the ROM as its happened on RR and RB ROMs.
I find it happens when the phone crashes and needs to be rebooted by holding the power button down.
Sometime after a few restarts I am then able to get the internal storage to mount, other times I need to turn the phone off and leave the battery out for a while but its just happened and nothing I am doing is working.
I really hope someone can help.
Try dori kernel. Should Mount OK custom is either 8.xx or 9.xx
I am using Dori (9.33). Having said that it never used to be as much of a problem when I used to run Siyah.
Sent from my GT-I9100 using Tapatalk 2
Try 9.32 I use 8.32 and have swapped ROM this week about 7-8 times and have no problems.
Hi,
i have no Problems with stock Rom, but in all 4.3 ROMs especially in PA 3.99 RC2, the Android system doesn't mount the sdcard0.
Does anyone know why?
PS: I am using the JBX Kernel
kattzenfleisch said:
Hi,
i have no Problems with stock Rom, but in all 4.3 ROMs especially in PA 3.99 RC2, the Android system doesn't mount the sdcard0.
Does anyone know why?
PS: I am using the JBX Kernel
Click to expand...
Click to collapse
try to clear cache from your recovery or else reset to factory defaults, this trick worked for my wi-fi issues
hi,
i already tried that
this also happens on every other 4.3 ROM to me with and without jbx kernel
Got The same problem. Gallery and camera wont let me in
Sent from my XT910 using xda app-developers app
I think this is an issue on all 4.3 ROMs, I have the same problem on Carbon 4.3.
thanks for the replies, then all 4.3 ROMs are just unusable
strange that noone complained about that in the DEV forums
kattzenfleisch said:
thanks for the replies, then all 4.3 ROMs are just unusable
strange that noone complained about that in the DEV forums
Click to expand...
Click to collapse
This is not true.. Every 4.3 rom i have flashed has had storage1/storage0. My micro sd card is where i keep my mp3 music i listen to via player pro. Sd is where my custom ringtones i created are stored along with pics, etc. Works great. Listen, sometimes going back to the beginning and starting over with stock firmware flash is needed as these memory slots can get corrupted. I use titanium back up for any/all apps/data with out these issues. Or simply go back to stock and copy what u dont want to lose to your micro sd (root explorer) is great or simply plug phone into computer and create a new folder on desk top for your keeps. After copy, format sd storage (pull micro sd card first) or simply copy nothing to micro sd only to computer and format both sd/micro sd. (Recomend) Would for sure do factory reset, if using ss uninstall and start fresh. This is not a guaranteed solution, only a suggestion.. Seems to have worked just fine for me more than once.. And others with similar issue.
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!
I have the same problem - only 1.28 GB of internal storage is seen by phone, even though it shows 13+ GB when connected to the PC.
is there anything that may help, (other then formatting everything) ?
I have already wiped cache/dalvic cache and mounted sdcard0 and sdcard1 in the CWM Recovery - didn't make any difference.
Hi!
I could not post this to the Development forum (new member so I'll try it here:
I've installed the DarkSense ROM 2.0.1 which is using a new kernel (extracted from AEROM v2). After fullwipe and install, the system cannot use the SD card anymore. At system start, it tells the SD card is damaged --> select "Portable Storage" and format SD card --> still shows as defect after format.
I've already tried to change filesystem to FAT, exFAT, EXT3, EXT4 using TWRP and reboot afterwards--> all show the same error.
I am using the following card: Kingston SDCA3/128 GB microSDXC (UHS-I U3)
I now flashed back Eragon ROM v2 and all is working well again with the SD card.
So question is: what is responsible for this behaviour? New kernel possibly? Anybody tried the new kernel (either AEROM v2 or DarkSense 2.0.1) with an SD card?
Cheerio!
hoehm72 said:
Hi!
I could not post this to the Development forum (new member so I'll try it here:
I've installed the DarkSense ROM 2.0.1 which is using a new kernel (extracted from AEROM v2). After fullwipe and install, the system cannot use the SD card anymore. At system start, it tells the SD card is damaged --> select "Portable Storage" and format SD card --> still shows as defect after format.
I've already tried to change filesystem to FAT, exFAT, EXT3, EXT4 using TWRP and reboot afterwards--> all show the same error.
I am using the following card: Kingston SDCA3/128 GB microSDXC (UHS-I U3)
I now flashed back Eragon ROM v2 and all is working well again with the SD card.
So question is: what is responsible for this behaviour? New kernel possibly? Anybody tried the new kernel (either AEROM v2 or DarkSense 2.0.1) with an SD card?
Cheerio!
Click to expand...
Click to collapse
Can you try the following for me please.
1. Flash my ROM, no need to reboot, just after you've flashed it go to TWRP backup settings and backup boot.img
2. Flash Eragon v2.0
3. Go to TWRP restore and restore boot.img
4. Reboot and test
If it is dodgy after that then its definitely the kernel, otherwise its the new system files from the 20160513 base that are causing the issues.
Cheers.
hoehm72 said:
Hi!
I could not post this to the Development forum (new member so I'll try it here:
I've installed the DarkSense ROM 2.0.1 which is using a new kernel (extracted from AEROM v2). After fullwipe and install, the system cannot use the SD card anymore. At system start, it tells the SD card is damaged --> select "Portable Storage" and format SD card --> still shows as defect after format.
I've already tried to change filesystem to FAT, exFAT, EXT3, EXT4 using TWRP and reboot afterwards--> all show the same error.
I am using the following card: Kingston SDCA3/128 GB microSDXC (UHS-I U3)
I now flashed back Eragon ROM v2 and all is working well again with the SD card.
So question is: what is responsible for this behaviour? New kernel possibly? Anybody tried the new kernel (either AEROM v2 or DarkSense 2.0.1) with an SD card?
Cheerio!
Click to expand...
Click to collapse
I have the latest darksense rom installed, SD card works fine (32gb)
Jonny said:
Can you try the following for me please.
1. Flash my ROM, no need to reboot, just after you've flashed it go to TWRP backup settings and backup boot.img
2. Flash Eragon v2.0
3. Go to TWRP restore and restore boot.img
4. Reboot and test
If it is dodgy after that then its definitely the kernel, otherwise its the new system files from the 20160513 base that are causing the issues.
Cheers.
Click to expand...
Click to collapse
I did the suggested procedure (with full wipe before installing first ROM DarkSense).
Result: SD card was recognized correctly and working.
So it seems it's the new system files...
hoehm72 said:
I did the suggested procedure (with full wipe before installing first ROM DarkSense).
Result: SD card was recognized correctly and working.
So it seems it's the new system files...
Click to expand...
Click to collapse
OK thanks a lot for testing it out for me, I'll have a look and see what I can do
I have same issue with Darksense 2.0.1 and 128 GB MicroSD-Card from SanDisk UHS-I. SD Card worked fine for a while, but then the described error occurred and it says SD-Card is damaged. It started after i put some new files onto SD-Card (never had that problem with Eragon-ROMs).
Thx for checking that issue...
Arangato said:
I have same issue with Darksense 2.0.1 and 128 GB MicroSD-Card from SanDisk UHS-I. SD Card worked fine for a while, but then the described error occurred and it says SD-Card is damaged. It started after i put some new files onto SD-Card (never had that problem with Eragon-ROMs).
Thx for checking that issue...
Click to expand...
Click to collapse
Different base used on the different ROM's, go back to 1.0.0 on my ROM if its a issue as a short fix for now whilst I look into it further.
@jonny: thx for fast reply and help with that great ROM. I currently do not use the phone as my 'default' phone so it's fine for playing around with the ROM. I will stay on the 2.0.1 and update to 2.1.0. Did you had time to update SD behaviour in 2.1.0 Version?
Arangato said:
@jonny: thx for fast reply and help with that great ROM. I currently do not use the phone as my 'default' phone so it's fine for playing around with the ROM. I will stay on the 2.0.1 and update to 2.1.0. Did you had time to update SD behaviour in 2.1.0 Version?
Click to expand...
Click to collapse
Not in 2.1.0 no - I think what I'm probably going to do is revert back to the older, but more stable 20160419 base in future versions.
Ok this seems to be a really intermittent issue, it just happened to me and I rebooted and it was fine again... this new base is causing both me and skeleton1911 no end of issues lol.
What I can do is continue the 1.x.x series of ROM's if you want until the base gets a bit more stable or until I hunt down which file(s) are causing the problems. For instance I can bring the new kernel and my fixed Xposed script over to the old base if its something you guys would be interested in, its not a lot of work so I don't mind.
Let me know what you think!
Cheers
Sounds good to me! Although I'm still waiting for my P9000 to arrive, probably tomorrow.
Seems like the better choice to continue with the older base for now, as the latest base isn't 100% reliable (yet).
Just my 2 cts though... ☺
I did a fresh install of your ROM, it didn't like the SD card, so I formatted it. I then copied some files across from the laptop. I then started getting the SD card corrupted messages. If I format, it just gives me the exact same message instantly.
I'm not sold on the new base, so would prefer the older base with the new kernel if that helps.
I'm hoping to get this phone up to standard (decent battery etc) and I can then sell my Sony Z5
I'm running Aerom V2 and don't have this issue. I have a Samsung SD card which was already formatted and it works fine. I've had Aerom on my phone for three days now without a problem?
ross232 said:
I'm running Aerom V2 and don't have this issue. I have a Samsung SD card which was already formatted and it works fine. I've had Aerom on my phone for three days now without a problem?
Click to expand...
Click to collapse
I've seen reports on the Elephone forum of people having this issue with that ROM, you must be one of the lucky ones.
ross232 said:
I'm running Aerom V2 and don't have this issue. I have a Samsung SD card which was already formatted and it works fine. I've had Aerom on my phone for five days now without a problem?[/QUOTE
I'm running Aerom V2 and don't have this issue. I have a ScandDisk 64 gb SD card which was already formatted and it works fine. I've had Aerom on my phone for five days now without a problem?
Click to expand...
Click to collapse
Yes please, Jonny.
I prefer v1.0, especially adaway!
Another bug I've noticed with the latest version is double texts being sent using messaging app. Not really a problem as I have unlimited plan...
Xposed is what I really want though.
Thanks for all your work
PS - getting SD card corrupt error too now
Hello Jonny
Can anything be done to the sd card problem that says every time she has a problem and need to format
Fabaure said:
Hello Jonny
Can anything be done to the sd card problem that says every time she has a problem and need to format
Click to expand...
Click to collapse
I've answered that a few posts further up/on the last page, can't remember exactly where.
I'm working on it but slowly at the moment, spent the last few days revising for a 2 hour Java exam today, now revising for a 2 hour Maths exam on Wednesday.
Thank you