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
Related
I am on stock 16GB sd card class2 and HD2 stock battteryI tried 2GB class 2 and 8Gb class 6. I am on Radio 2.10 and even upgraded to 2.12.Lot of SODS and phone restarts automatically.
After SOD windows won't load up and hangs at Stick together logo and will never go forward. Need to take off the battery and need to wait for couple of minutes and after wards it loads.
After getting into Android, gets again SOD and will reboot and when I get back into android, will try to check email or make call and then again phone restarts itself.
Any ideas.
I am on Darkstone latest release froyo2.2 with today's update i.e 18th August and tried all kinds of ROMS.
Any help is appreciated.
do you hspl3 your hd2
Yes it says 2.08SPL when I enter in tri-color mode.
Any help on this?
this has happened to me as well, using mattc 1.5b with Cloudy 1.6 winmo ROM
Radio 2.10.50.26. I am unable to provide the cause of this, just seems to be
random.
Could be corrupt files on you sd card. A bit time consuming, but doesn't hurt..
- Copy your sd card onto your pc.
- Format sd card (fat32)
- Copy everything back
I read somewhere that this problem can be caused with mounting your sd card from your phone via usb. I know I had a lot of problems with Android seeing the new files I copied over so I stopped doing it (connecting via usb).
polstein said:
Could be corrupt files on you sd card. A bit time consuming, but doesn't hurt..
- Copy your sd card onto your pc.
- Format sd card (fat32)
- Copy everything back
I read somewhere that this problem can be caused with mounting your sd card from your phone via usb. I know I had a lot of problems with Android seeing the new files I copied over so I stopped doing it (connecting via usb).
Click to expand...
Click to collapse
Friend,
I did copying N number of times, formatting SD card..
Do you want to me to try still?
Any other suggestions?
Just dittoing. Having the same problem with chuckyrom + mattc 1.5. Seems to happen when i'm not using the phone for a while.
Can I load the stock firmware , and install HSP3 and start running android?
Do I need to have a different ROM to run this? All I understood was earlier there was a sound issue but not now..Can I do the above step?
same
yea i get this very random, I'm not to sure if its bluetooth related for me, anyone's guess i think at the moment
kingfisher1111 said:
Friend,
I did copying N number of times, formatting SD card..
Do you want to me to try still?
Any other suggestions?
Click to expand...
Click to collapse
I had this same self-reboot issues, regardless of android build, even after deleting and re-creating the android folder in the sd card.
Following is how I managed to solve it:
Take out sd card and use card reader, mount it on a winxp machine.
Copy ALL files to a backup folder in pc. Use 'xcopy /e /c *.* c:\sdbak\.' for example, as normal copy/paste wouldn't work if it found errors due to corrupted files.
Use sd formatter. Refer to this thread. Do a Full format; a class 2, 8GB will take around 10 minutes to complete.
Copy back each backup folder into the formatted sd card, one by one. Recreate and copy your favorite android build onto the sd card.
Reinsert sd card, boot up and start android from fresh.
Let us know if this works for you.
i did do full format in xp before and have random reboot problems. Maybe something happened since then, ill try this tool.
Did it and no dice, still reboots. Im gonna try another suggestion about uninstalling setcpu.
setcpu
this restart happens to me everytime i use setcpu im on shubcraft 1.4b with the r4 overclocked zimage labeled NewKernels_LatestGIT_r4_BTalternative it just started happening with this zimage. are you using setcpu try uninstalling it it worked for me! i never had this prob with the original zimage! hope this helps!
b3ltazar said:
this restart happens to me everytime i use setcpu im on shubcraft 1.4b with the r4 overclocked zimage labeled NewKernels_LatestGIT_r4_BTalternative it just started happening with this zimage. are you using setcpu try uninstalling it it worked for me! i never had this prob with the original zimage! hope this helps!
Click to expand...
Click to collapse
I havent changed the zimage, but i am using shubcraft and setcpu, ill uninstall and see if it makes a difference. Thanks.
ferdaus said:
I had this same self-reboot issues, regardless of android build, even after deleting and re-creating the android folder in the sd card.
Following is how I managed to solve it:
Take out sd card and use card reader, mount it on a winxp machine.
Copy ALL files to a backup folder in pc. Use 'xcopy /e /c *.* c:\sdbak\.' for example, as normal copy/paste wouldn't work if it found errors due to corrupted files.
Use sd formatter. Refer to this thread. Do a Full format; a class 2, 8GB will take around 10 minutes to complete.
Copy back each backup folder into the formatted sd card, one by one. Recreate and copy your favorite android build onto the sd card.
Reinsert sd card, boot up and start android from fresh.
Let us know if this works for you.
Click to expand...
Click to collapse
It doesn't work. It still reboots inspite of doing all the above steps.
I have the same issue with crashing back to windows mobile when inactive, this is only recent for me, previously Android was solid as a rock. Guess I will try a build without adding apps or settings and see if it crashes, then add apps one at a time.
Does anyone know of a way of catching the error/crash reason?
b1ackhawk said:
I havent changed the zimage, but i am using shubcraft and setcpu, ill uninstall and see if it makes a difference. Thanks.
Click to expand...
Click to collapse
Just a note, shub and darkstone's builds gave me random reboots. Ive moved to mattc's nexus based build and it has been super solid.
I have installed mattc 1.7 and zimage r11 with all .ko files and no longer experience reboots in android, I use task manager and setcpu also, its worth trying a this if you have probs
Sent From My HD2 using xda Android app
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 have recently upgrade to android 2.3.3 and am using EWJET as a rom.
I cannot access the SD once Android OS has booted. All apps and the system/settings says SD Card isn't mounted. Tried multiple installs, nothing works.
All 2.1/2.2 Roms are fine.
If i tap back during start-up and access xrecovery I have normal access to the SDcard and can flash packages etc. So the phone is able to access the card ok.
My SD card is the 8gb that came with the phone and isnt partitioned in anyway.
However in the past I did have it partitioned, but not now. Incase I am installing 2.3.3 and the rom wrong, ill tell you my steps.
Factory Firmware 2.1 flashed
rooted, busybox and recovery installed
Flashed X10i_3.0.1.G.0.75_only_kernel_baseband
then install the EWJET rom as per his instructions..
I pray I am only doing the above steps wrong as I desperately want the SD working on 2.3.3.
Any help would be appreciated.
Brent
having something similar:
http://forum.xda-developers.com/showthread.php?t=1201915
brent0r said:
I have recently upgrade to android 2.3.3 and am using EWJET as a rom.
I cannot access the SD once Android OS has booted. All apps and the system/settings says SD Card isn't mounted. Tried multiple installs, nothing works.
All 2.1/2.2 Roms are fine.
If i tap back during start-up and access xrecovery I have normal access to the SDcard and can flash packages etc. So the phone is able to access the card ok.
My SD card is the 8gb that came with the phone and isnt partitioned in anyway.
However in the past I did have it partitioned, but not now. Incase I am installing 2.3.3 and the rom wrong, ill tell you my steps.
Factory Firmware 2.1 flashed
rooted, busybox and recovery installed
Flashed X10i_3.0.1.G.0.75_only_kernel_baseband
then install the EWJET rom as per his instructions..
I pray I am only doing the above steps wrong as I desperately want the SD working on 2.3.3.
Any help would be appreciated.
Brent
Click to expand...
Click to collapse
you try pulling it out and blowing on it like an old nes game...
jk smiles but have you tried perhaps throwing the sd into a computer and just formatting with different cluster sizes or in general formatting the card. Might need to use an adapter.
Happen the same thing to me but with wolfbreaks rom... some people told me to re-flash the rom but it didnt work. The funny thing is the the sd card will work on any other device, and any other sd card will work on the phone... havent try re-formatting the card cauze i dont have the adapter but it should work
Sent from my X10i using XDA App
J!K said:
Happen the same thing to me but with wolfbreaks rom... some people told me to re-flash the rom but it didnt work. The funny thing is the the sd card will work on any other device, and any other sd card will work on the phone... havent try re-formatting the card cauze i dont have the adapter but it should work
Sent from my X10i using XDA App
Click to expand...
Click to collapse
you might want to get an adapter. A while back i tried setting up a sd-ext partition on a 4gig card and long story short the only way i was able to run a format that gave me back the 4gigs was throwing it into an adapter
Had the same thing when I updated with stock-2.3.3.... At the time I had it partitioned in 2 partitions...
I connected the phone then with my pc, and there it was, alive and well.... So I backed up the entire card, that is, the first partition, where all my data were; I powered off the phone, took it out, found a adapter, deleted the 2nd partition with Partition Wizard Home Edition Minitool, made the sd-card 1 partition only, formatted that partition, and then I copied all my backed-up data back to the card
Then I put the card back in the phone, booted and voila: the card was recognized again by 2.3.3....! and now it functions ok!
Hope this helps, greetz, good luck,
kwarkje
J!K said:
Happen the same thing to me but with wolfbreaks rom... some people told me to re-flash the rom but it didnt work. The funny thing is the the sd card will work on any other device, and any other sd card will work on the phone... havent try re-formatting the card cauze i dont have the adapter but it should work
Sent from my X10i using XDA App
Click to expand...
Click to collapse
formatting did not help
Anything new on this?
for me it is a little different. The card that came with the phone works fine with the GB update, the thing is that I got another phone, this one came with a 4 Gb card so I took the one in the x10 with all my pics and put it in my new phone and put the other new card in the x10 but it doesn't recognize it...
I've tried with 2 different cards, in xRec i can read it, back up, etc, but once in android its like there's nothing there. Tried formatting it with no results....
What could it be that it reads the original x10 card and no other?
Ive got no idea, but its annoying. Im gonna have to go back to 2.1 which sucks.
We need to some how figure out whats causing this. Ive tried everything.
2.3 seems to be the problem.
brent0r said:
Ive got no idea, but its annoying. Im gonna have to go back to 2.1 which sucks.
We need to some how figure out whats causing this. Ive tried everything.
2.3 seems to be the problem.
Click to expand...
Click to collapse
I have 2.3 and the card that originally came with the phone (16Gb SDHT) works fine, the thing is that it doesn't read any other card.
brent0r said:
Ive got no idea, but its annoying. Im gonna have to go back to 2.1 which sucks.
We need to some how figure out whats causing this. Ive tried everything.
2.3 seems to be the problem.
Click to expand...
Click to collapse
Same issue no clue what to do
Today i found a workarround using DISKPART (6 years later hehe)
Note that this will wipe your storage card so BACKUP !!
Hold [Win + R] and type in : diskpart (or launch cmd as admin and types: diskpart )
Every lines should be followed by enter key.
list disk
select disk *
(" * " is the number of your drive. be carefull do not choice your hard drive number which is commonly 0)
clean
create partition primary
assign
format fs fat quick
exit
Tested and work fine on windows 8 (but should work on 7, 8.1, 10)
Thanks Hope i help even 6 years later !! cheers
Hi all,
I've been rooting Android phones (mostly Samsung) and installing CWM etc for as long as one has been able to. This is the first time I've had any major issues.
Issue being, no matter which CWM I install that states it supports external SD on i9300, I still can't install from zip on ext sd, or backup too it, or mount it!!!
Everyone else seems to be able to fine, but for some reason for me, following the same instructions step by step (tripple checked just to be sure) I cannot.
Now I did initially root the device relatively early on in the development stages for it, and installed a criskello rom (v6) about a month ago. Other than that, I've not played around with anything at all. Today I decided I'd try to install a new rom which I'd saved on the device to the external SD. But no, the CWM I had (6.0.1.0 I think) couldn't read ext sd.
Thus, I installed CWM 6.0.1.2 via Odin (following instructions found here: http://forum.xda-developers.com/showthread.php?t=1719744 )
But apparently for some crappy reason I have to be the odd one out, for whom it refuses to work!
Now, just to be sure, i've tried multiple SD cards, all just basic fat format, even reformated them all on the device itself. But nope, it just refuses to work for me!!!
Anyone got any suggestions or am I just doomed to internal memory only?
I'd REALLY like to be able to backup my device before trying new roms
This problem nevf happened to me. I can restore any backup ive saved.
Maybe its a crisckeloRom related problem.
Sent from my GT-I9300 using xda premium
fr0dzy said:
Hi all,
I've been rooting Android phones (mostly Samsung) and installing CWM etc for as long as one has been able to. This is the first time I've had any major issues.
Issue being, no matter which CWM I install that states it supports external SD on i9300, I still can't install from zip on ext sd, or backup too it, or mount it!!!
Everyone else seems to be able to fine, but for some reason for me, following the same instructions step by step (tripple checked just to be sure) I cannot.
Now I did initially root the device relatively early on in the development stages for it, and installed a criskello rom (v6) about a month ago. Other than that, I've not played around with anything at all. Today I decided I'd try to install a new rom which I'd saved on the device to the external SD. But no, the CWM I had (6.0.1.0 I think) couldn't read ext sd.
Thus, I installed CWM 6.0.1.2 via Odin (following instructions found here: http://forum.xda-developers.com/showthread.php?t=1719744 )
But apparently for some crappy reason I have to be the odd one out, for whom it refuses to work!
Now, just to be sure, i've tried multiple SD cards, all just basic fat format, even reformated them all on the device itself. But nope, it just refuses to work for me!!!
Anyone got any suggestions or am I just doomed to internal memory only?
I'd REALLY like to be able to backup my device before trying new roms
Click to expand...
Click to collapse
CWM 6 and onwards is known to not play well with external SD's, despite what they say, since the layout is a little bit different in Samsung phones. Try flashing Chainfire's CF-root package, which will provide you with root (of course) and CWM 5, which works well with external SD's. You have my guarantee.
BUT! If your SD card is somehow damaged, nothing will read it properly. Make sure it actually works, and that is has a format your phone understands:
32 GB and up, and running stock Samsung = exFAT
32 GB and up, and running an AOSP ROM = FAT32
Anything less than 32GB = FAT32
Theshawty said:
CWM 6 and onwards is known to not play well with external SD's, despite what they say, since the layout is a little bit different in Samsung phones. Try flashing Chainfire's CF-root package, which will provide you with root (of course) and CWM 5, which works well with external SD's. You have my guarantee.
BUT! If your SD card is somehow damaged, nothing will read it properly. Make sure it actually works, and that is has a format your phone understands:
32 GB and up, and running stock Samsung = exFAT
32 GB and up, and running an AOSP ROM = FAT32
Anything less than 32GB = FAT32
Click to expand...
Click to collapse
Hey,
I have the same issue as fr0dzy. I'm ran Chainfire's CF-root package with CWM 5.5.0.4 and i can't use my ext-sdcard in recovery (to install zips + nandroid backup/restore). My ext is a 64gb card formatted to FAT32 but i can use it when i boot my rom.
Any suggestions would be really appreciated. Thanks.
fr0dzy said:
Hi all,
I've been rooting Android phones (mostly Samsung) and installing CWM etc for as long as one has been able to. This is the first time I've had any major issues.
Issue being, no matter which CWM I install that states it supports external SD on i9300, I still can't install from zip on ext sd, or backup too it, or mount it!!!
Everyone else seems to be able to fine, but for some reason for me, following the same instructions step by step (tripple checked just to be sure) I cannot.
Now I did initially root the device relatively early on in the development stages for it, and installed a criskello rom (v6) about a month ago. Other than that, I've not played around with anything at all. Today I decided I'd try to install a new rom which I'd saved on the device to the external SD. But no, the CWM I had (6.0.1.0 I think) couldn't read ext sd.
Thus, I installed CWM 6.0.1.2 via Odin (following instructions found here: http://forum.xda-developers.com/showthread.php?t=1719744 )
But apparently for some crappy reason I have to be the odd one out, for whom it refuses to work!
Now, just to be sure, i've tried multiple SD cards, all just basic fat format, even reformated them all on the device itself. But nope, it just refuses to work for me!!!
Anyone got any suggestions or am I just doomed to internal memory only?
I'd REALLY like to be able to backup my device before trying new roms
Click to expand...
Click to collapse
I'm on a SGS2 Epic4g Touch- same issue. Rooting it everything runs fine, after installing CWM Agat Recovery through mobile Odin I lose access to all apps on Ext SD, something is definitely not playing right with the card. Have you found a work around?
---------- Post added at 10:07 PM ---------- Previous post was at 09:55 PM ----------
This is my first time rooting and running CWM--- is this issue with phones that have both an Ext SD and a internal MMC partition labeled SD? Thanks for any help, guys!
Solved for me!
Theshawty said:
CWM 6 and onwards is known to not play well with external SD's, despite what they say, since the layout is a little bit different in Samsung phones. Try flashing Chainfire's CF-root package, which will provide you with root (of course) and CWM 5, which works well with external SD's. You have my guarantee.
BUT! If your SD card is somehow damaged, nothing will read it properly. Make sure it actually works, and that is has a format your phone understands:
32 GB and up, and running stock Samsung = exFAT
32 GB and up, and running an AOSP ROM = FAT32
Anything less than 32GB = FAT32
Click to expand...
Click to collapse
This last piece of text solved my problem, thank you! I formatted my 2 GB card as FAT32 and installed a custom ROM (4.1.2 Stock) to recover from a broken Ubuntu Touch ROM.
It was a relief!
bruno.drugowick said:
thank you!
Click to expand...
Click to collapse
there's a button for that
Hi there,
I have the following issue and hope to find somebody with a solution here in the XDA-world...would be great.
Of course I did some searching before I post here, but the results are not sufficient for me...
I am using a 64 GB external SD card in my Samsung Galaxy S III since a few days. Before I put data to the card, I performed a format via the phone itself. The access works great - I can use all my files when I use the phone in normal operation. (with Ultima Rom).
Today I downloaded the latest ROM release and wanted to flash it via CWM 6.0.2.7 and I encountered a problem - I cannot access the external SD card in CWM recovery. It simply say´s "Can´t mount external SD".
Why is it? Any solution proposals? I used to have a 2GB card and the installations worked fine with CWM here....
Is it a wrong formatting probably? Or the size?
Thanks for any suggestions!!!
You should do some search before post, but since you are here, I give you some briefly information, but you have to search more details yourself.
1. 64 GB sdcard is formated in exFAT file system which CWM recovery doesn't support it, that's why you have problem with 64 , but OK with 2GB sdcard. (Some latest recovery has now support exFAT I think )
2. Solution, format your sdcard into FAT32 file system, or change to 32 GB sdcard because unless you have countless files or blue ray movies otherwise you won't need 64GB at all, that's what I did, I had 64 and change to 32 to avoid any kinda potential problem
Sent from my GT-I9300 using xda premium
Dotterdroid said:
Hi there,
I have the following issue and hope to find somebody with a solution here in the XDA-world...would be great.
Of course I did some searching before I post here, but the results are not sufficient for me...
I am using a 64 GB external SD card in my Samsung Galaxy S III since a few days. Before I put data to the card, I performed a format via the phone itself. The access works great - I can use all my files when I use the phone in normal operation. (with Ultima Rom).
Today I downloaded the latest ROM release and wanted to flash it via CWM 6.0.2.7 and I encountered a problem - I cannot access the external SD card in CWM recovery. It simply say´s "Can´t mount external SD".
Why is it? Any solution proposals? I used to have a 2GB card and the installations worked fine with CWM here....
Is it a wrong formatting probably? Or the size?
Thanks for any suggestions!!!
Click to expand...
Click to collapse
1. Use PhilZ Touch recovery (based on 6.0.2.8 - I think 6.0.2.7 was also very buggy - and with a new Samsung kernel supporting exFAT).
2. Format as FAT32.
I am currently using the 1st approach, but keep in mind that many ROMs (mostly based on CM10 stuff) still have a huge bug where the exFAT partition is not recognized but instead some stuff is written to the first sector - when that takes place just put the exFAT card in a SD-reader in Win7/8, reject any suggestion to format it and then from the command line run CHKDSK /F Letter:
Thank you!!!
Thanks a lot to both of you!!! It worked out! :highfive:
I also managed to search for "how to format an SDCard to FAT32", no problem.
To be honest I also had a look for a possible solution like you suggested prior to my post --> I just was not confident that these suggestions will solve the issue since I read many times "tried - but no success"...
I just wanted to be sure, coming back from work, not to spend hours to solve it, if you already have "the one working" solution available. Once again many thanks - I really appreciate this community, even if its my 2nd active post...