Ive been using my gs3 for some time now, rooted and working great. i updated my clockwork and flashed a few new roms along with new kernels. My problem is now i can not get my phone to mount my 64 Lexmark micro sd. it was fatx then moved it to fat32 but when its fat32 my phone says its damaged and ask to format, so i format then after that it can not mount it. it works fine on my older android phones but they are not rooted. so i suspect Clockwork recovery. im at 6.0.2.3 tried both touch and non touch. no luck. tried many different roms along with stock and stock kernel. no luck. any help? or link to older clockwork recovery that work?
thank you also running 4.1.1 jedi outcast rom right now
Did you try formatting it back to exFAT? Mine is formatted FAT32 and reads fine. Does the card read when you put it in a computer?
Yes I tried to format it in my pc to both fat32 and fatx. Also reads fine on my pc.
Sent from my SAMSUNG-SGH-I747 using xda premium
I fixed my problem, i installed stock kernel, then stock recovery. did factory restore then re flashed Twrp and back to custom ROM and now it seems to be working. thanks for your help.
Related
I've flashed roms before on my phone and it was all fine and dandy. I recently though went back to stock, removed root. Then I downloaded Chainfire SU today out of boredom, rooted, installed TWRP and tried installing GE roms on my M919V. No matter which one I flash, I'm stuck on the Galaxy S4 screen which is annoying. Is there anyway to fix this?
Make sure you are flashing YOUR kernel made for your device.
Mateoftw said:
I've flashed roms before on my phone and it was all fine and dandy. I recently though went back to stock, removed root. Then I downloaded Chainfire SU today out of boredom, rooted, installed TWRP and tried installing GE roms on my M919V. No matter which one I flash, I'm stuck on the Galaxy S4 screen which is annoying. Is there anyway to fix this?
Click to expand...
Click to collapse
What version of TWRP are you using? I have heard of TWRP causing problems with v2.6. Try TWRP 2.5.0.2
Another thing could be a 64GB msdc. If you have one in that's format to exFat, a kernel that does not support exFat will cause you to bootloop or freeze on start screen. If that's the case flash a compatible kernel as suggested by TheAxMan or reformat to FAT32
baseballfanz said:
What version of TWRP are you using? I have heard of TWRP causing problems with v2.6. Try TWRP 2.5.0.2
Another thing could be a 64GB msdc. If you have one in that's format to exFat, a kernel that does not support exFat will cause you to bootloop or freeze on start screen. If that's the case flash a compatible kernel as suggested by TheAxMan or reformat to FAT32
Click to expand...
Click to collapse
TWRP 2.5.0.2 isn't without it's problems either. It worked alright for about 6 weeks and then it caused my phone to be unable to mount /data. I didn't have my phone useable for a whole day, and i finally found out how to fix it and now i stick with CWM which has never given me a scare like that.
Also, i used to have my 64GB SD card and it was exFat with a custom kernel that didn't support it, and my ROMS would still boot up, just my external SD would not be recognized until i reformatted to FAT32.
Those are by no means the one and only solutions. They're only a few things to look at as reported by others with similar problems.
☞Sent from here☜
Hello, i've been trying lots of different roms but basically every time i try to change my rom (running 4.3 google edition), i put the zip file in my internal sd card by usb cable, go on recovery, flash it, and it either says bad file- not compatible or it flashes but won't boot.
I tried all different recoveries. All of them suck as they don't have usb mounting working..
ATM I'm running Philz touch recovery that i downloaded a month ago.
Also, my phone has this weird problem with wifis disconnecting and not reconnecting sometimes, it started a few months ago..
Anybody know why is this happening? Should i try other recoveries? Bad USb connection? I tried downloading it on wifi too..
Right now i flashed a old version of wicked that i had saved in my internal sd because usb mounting wouldn't work in recovery..
Are you checking md5 sum of your files?
What are your procedure for flashing(steps you're taking)?
i have seen and heard problem with philz touch and twrp for a while now
philz touch doesnt like allot of roms
twrp works for some people, and doesnt for others
so try a different recovery. if you want the most stability install cwm or cwm touch. if problems still persist, try wiping internal storage. at one point i couldnt get anything to flash untill i wiped it
TheAtheistOtaku said:
i have seen and heard problem with philz touch and twrp for a while now
philz touch doesnt like allot of roms
twrp works for some people, and doesnt for others
so try a different recovery. if you want the most stability install cwm or cwm touch. if problems still persist, try wiping internal storage. at one point i couldnt get anything to flash untill i wiped it
Click to expand...
Click to collapse
Thanks for the help guys, after wasting 2 hrs of my hw time doing roms -.-! i flashed CWM recovery (latest) and it works perfectly.
TWRP didn't work for me either, latest version wouldn't go to recovery at all. PhilZ wouldn't flash most roms.
Husam2011 said:
Thanks for the help guys, after wasting 2 hrs of my hw time doing roms -.-! i flashed CWM recovery (latest) and it works perfectly.
TWRP didn't work for me either, latest version wouldn't go to recovery at all. PhilZ wouldn't flash most roms.
Click to expand...
Click to collapse
If you like TWRP and would prefer to use it, use the 2.5.2 version. There is a flashable zip for it in the TWRP thread somewhere. You will have to search for it...
That version is far more stable than the latest versions.
Sent from your phone. You should be careful where you leave that thing.
Husam2011 said:
Hello, i've been trying lots of different roms but basically every time i try to change my rom (running 4.3 google edition), i put the zip file in my internal sd card by usb cable, go on recovery, flash it, and it either says bad file- not compatible or it flashes but won't boot.
I tried all different recoveries. All of them suck as they don't have usb mounting working..
ATM I'm running Philz touch recovery that i downloaded a month ago.
Also, my phone has this weird problem with wifis disconnecting and not reconnecting sometimes, it started a few months ago..
Anybody know why is this happening? Should i try other recoveries? Bad USb connection? I tried downloading it on wifi too..
Right now i flashed a old version of wicked that i had saved in my internal sd because usb mounting wouldn't work in recovery..
Click to expand...
Click to collapse
Hi I couldn't use twrp it didn't work for me so I suggest you download cwm touch works great. Also when you download the rom from your computer make sure its going to the root of your EXTERNAL sd card. This is usually achieved as mounting as disk drive and your device will showup as external drive D or E. Then when you download your rom download to external drive D orE which ever name it gave your device when mounting as disk drive. This way the rom is placed on your external sd card. and when your in cwm you will press download rom from external sd card scroll down and find your rom then you should be good to go. Hope this helps .
realsis said:
Hi I couldn't use twrp it didn't work for me so I suggest you download cwm touch works great. Also when you download the rom from your computer make sure its going to the root of your EXTERNAL sd card. This is usually achieved as mounting as disk drive and your device will showup as external drive D or E. Then when you download your rom download to external drive D orE which ever name it gave your device when mounting as disk drive. This way the rom is placed on your external sd card. and when your in cwm you will press download rom from external sd card scroll down and find your rom then you should be good to go. Hope this helps .
Click to expand...
Click to collapse
Bad usb cables can cause problems so if you know for sure that the md5 was good and you followed all dev instructions related to wiping before install it wouldn't hurt to try a different cable.
Sent from my SGH-M919
Hi, I downloaded CM11 and had no issues with my internal sd but I tried a different rom, didn't like it, and restored back to the CM11 rom. Now, I'm having issues with the sdcard. It doesn't show. I have all my backups, pictures, music there. I know for a fact that it still exists because I can see it when I mount it on recovery. When I load into the os, it says I have no sdcard. So how do I fix this?
PaulBen112 said:
Hi, I downloaded CM11 and had no issues with my internal sd but I tried a different rom, didn't like it, and restored back to the CM11 rom. Now, I'm having issues with the sdcard. It doesn't show. I have all my backups, pictures, music there. I know for a fact that it still exists because I can see it when I mount it on recovery. When I load into the os, it says I have no sdcard. So how do I fix this?
Click to expand...
Click to collapse
I'm having them same issue. But can't mount in recovery or no apps can detect my SD card. I know all my data is on my SD card. Took data off formated SD still can't detect SD. Sooo stumped. Ran several 4.3 ROMs. Heard they weren't good because of SD issues. Issue did start after installing a 4.4 ROM though. If a solution if found I'll get back with you. But as it sits I've tried everything except reverting back to stock and rerooting. Last resort.
I just posted about a similar issue I'm having with custom ROMs reading my SD card for this phone. not sure but would be interested if anyone knows what's going on
Sent from my SGH-T989 using xda app-developers app
Good to I'm not only one. Been using twrp 2.6.1.0 with no issues. Been running 4.3s for while. Tried some TW.. No issue.. Tried some 4.2.2a again.. No issues. Tried latest Slim 4.3.1 and BLAMMO! had issues booting it but finally did.. Then restored back to a 4.2.2 ROM and now my ext SD is not visible. It is intact cuz twrp sees and restores from it.. WTF!
EDIT my previous. Slim is vindicated. Seems both of my 4.2.2 backups are corrupted for some reason. Restored a Slim 4.3 build and my SD card issues are gone. Weird.
OK so i bought a 64GB micro SD card for my phone. I moved everything from my old card onto it and all was working well.
Today i decided i wanted to flash a new ROM and i installed the ROM onto the external SD card. I went into CWM, formatted data/cache/dalvik and went to go look for the zip to flash. However CWM wouldnt recognize my SD card. I had to remove that SD card, install the ROM onto my old 16GB SD card and install it from there.
Just wondering if anyone else has had that issue. THe 64GB card worked perfectly fine up until that point...
You will have to format the new card to Fat32.
I read about that, but it was working before and now that I flashed a new rom, it's working fine again. It was just from I had done a factory reset until I flashed a new rom.
Sent from my SGH-T999 using xda app-developers app
So, is the recovery reading it now ?
Perseus71 said:
So, is the recovery reading it now ?
Click to expand...
Click to collapse
Yes. It was a CWM issue. Once i updated to the latest one it was able to read it.
Hello all,
I've searched d2tmo forums and couldn't find an answer for this so decided to start this thread. Ever since updating to Kitkat my d2tmo no longer recognizes my 32gb sd card. It reads fine on the latest 4.3 OTA firmware and my computer can also read it. I'm currently running CM11 nightlies. I have a smaller 8gb card in FAT32 that CM11 is able to read though, but somehow it doesn't recognize the 32gb card. Here's what I've tried so far,
- Formated to FAT32, to ext4 and ext2
- Tried to mount from CWR and TWR
- Used Remo recover and other file recovery software to format my 32gb card.
Please let me know if you have any fixes for this issues.
Thanks,
First format it back to FAT32 on PC. Then please flash another kernel and then try to format the card inside the phone.
Thanks Perseus
MicroSD is already in FAT32. Interesting that this could be a kernel issue. I'm currently running CM11's latest 3.4.74.
Will look for CM11 compatible kernels and let you know how it goes.
Thanks again
Sent from my SGH-T999 using XDA Premium 4 mobile app
Perseus71 said:
Then please flash another kernel and then try to format the card inside the phone.
Click to expand...
Click to collapse
Hi Perseus,
I've flashed KToosez's AOSP 4.4.x kernel found here and CM11 is still not recognizing my 32gb SD card. SD card is FAT32. I have also tried to mount it from recovery.
Any other insights?
Thanks,
André
This may seem strange. But try to flash a 4.3 AOSP Rom or better yet 4.2 AOSP Rom with built in Kernel. See what happens in that case ?
NOTE - Since you have got the latest Samsung's 4.3 OTA Bootloader, be careful and Weary when flashing Roms. You don't want to accidentally try to flash an older bootloader.
Perseus71 said:
This may seem strange. But try to flash a 4.3 AOSP Rom or better yet 4.2 AOSP Rom with built in Kernel. See what happens in that case ?
NOTE - Since you have got the latest Samsung's 4.3 OTA Bootloader, be careful and Weary when flashing Roms. You don't want to accidentally try to flash an older bootloader.
Click to expand...
Click to collapse
Thanks Perseus,
I'm going to try formatting it to extFAT and use dkp's kernel to see if it will recognize the card. I see dkp can recognize 64gb sd cards. Let's see how it goes. I just came from 4.3 AOSP and TW and want to enjoy using Kitkat for a bit longer.
Appreciate the insights.
I had remembered seeing somebody having the same problem in the aospa thread. Apparently they erased the card and remounted. http://forum.xda-developers.com/showthread.php?p=48901946. You could try messaging the post author for details
Sent from my SGH-T999 using xda app-developers app