Related
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.
So today i have had nothing but problems with flashing roms. I was on the PAC rom nightlies, but decided to go back to touchwiz roms due to the wifi calling. I tried flashing wicked v4, booted fine but once i reboot, got stuck at the samsung boot logo. tried reflashing/wiping/flashing other roms, including PAC again, all would result in getting stuck at the samsung boot logo. so i used odin to go completely back to stock. That wouldnt boot at first, so i tried wiping data in stock recovery, luckily that got it to boot. I then re-rooted and tried to flash infamous 2.5. same thing, got stuck at the samsung boot logo. finally, i was able to get infamous google edition to boot, but isnt what i want (since it doesnt have wifi calling), but is the only thing i could get to boot.
So does anyone have any idea why my phone is being so moody, or am i just having a bad day?
edit:i will attempt to try and flash infamous 2.5 when i get out of work to see if my phone is in a better mood, but right now i just need a working phone
edit 2: if its relavent, before i used odin, i was using twrp recovery, but after odin, i used clock work mod touched
I also having the same problem, by just rebooting on jedi it goes into bootloop. My guess is either the kernel or the recovery (no expert). On my friends ATT it bootlooped only because I didn't flash the required Ktoons kernel. As for Tmobile I'm not sure of the bootloops, but to fix it i just dirty flash a rom and it works but it happens usually after i flash some add ons.
Both of the problems here are kernels, change to another kernel, should fix these problems.
Good luck
If that does not work, come back here, we will figure something else out.
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
TheAtheistOtaku said:
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
Click to expand...
Click to collapse
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
mgbotoe said:
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
Click to expand...
Click to collapse
yes i have tried it with the kernel it comes with, same result.
still downloading wicked.
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
mgbotoe said:
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
Click to expand...
Click to collapse
ive used twrp before i odind back to stock. but now i have been using clockwork mod touch, still having the same problem
after flashing kernal wipe cache,dalvik and fix permissions that should work
LIL_ROOKIE said:
after flashing kernal wipe cache,dalvik and fix permissions that should work
Click to expand...
Click to collapse
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
TheAtheistOtaku said:
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
Click to expand...
Click to collapse
You're not "formatting data" correct? Should only "wipe data". Not format.
norml said:
You're not "formatting data" correct? Should only "wipe data". Not format.
Click to expand...
Click to collapse
no im not formatting data lol i know the difference
TheAtheistOtaku said:
no im not formatting data lol i know the difference
Click to expand...
Click to collapse
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
norml said:
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
Click to expand...
Click to collapse
its no problem
Check SD card
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Wow, SanDisk sd cards have been really sucKing lately. I'll try taking out my sd card if it ever happens again
Sent from my SGH-M919 using Tapatalk 4 Beta
31337_haxer said:
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Click to expand...
Click to collapse
I'm using a PNY SD card... just flashed the 7.2 version of infamous, and out of 20 boot attempts, 2 or 3 booted past the GS4 logo.
seems to work if I go back into recovery and factory reset, boot again, and that's the only way I've gotten past the GS4 screen.
Im using TWRP
I've since figured out the problem. For whatever reason when you wipe the cache & dalvic with twrp, sometimes something happens where your internal memory fills up completly, leaving you with no space. Formating the internal from twrp fixes that, but of course you loose everything not on your sd card. Can confirm this problem in twrp 2.6.0 also, since it happend a few times for me
I now just use clock work mod touch, and haven't had the problem since. Pity though,I prefer twrp
Sent from my SGH-M919 using Tapatalk 4
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium
I currently have a rooted E980 on stock ROM/Recovery.
My goal is:
1) Install CM 10.2 (and CM11 once stable)
2) Be able to back up ROMs (i.e. nandroid) - If I have a problem I would like to restore via a nandroid.
3) If all goes well, maybe try other ROMs (Carbon, Slim, etc) - Although I am not a flash addict.
I have experience with CWM and TWRP with other devices (Nexus, HTC), but it seems to be a bit different with the LG E980. I hear about Loki, Lokified, soft-bricks, boot loops, etc.
Should I use Freegee, TWRP 2.6.3 or PhilZ Touch? Any recommendations would be appreciated!
I have used the CWM 6.0.3.7 that came from Freegee to flash/backup/restore probably 20 ROMs with no issues. I know some people have had issues with it and prefer @madmack's hacked TWRP. I haven't had any though, so I have yet to jump ship. 2 cents.
Sent from my Optimus G Pro using Tapatalk
thathamiam said:
I have used the CWM 6.0.3.7 that came from Freegee to flash/backup/restore probably 20 ROMs with no issues. I know some people have had issues with it and prefer @madmack's hacked TWRP. I haven't had any though, so I have yet to jump ship. 2 cents.
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
same experience with freegee, no problems. the only issue I seem to have on some roms is that gps doesn't work and I have no idea why. and from what I hear you can't flash modems with cwm so I'm not sure if that's the problem or not.. everything else works perfect.
Thanks for the recommendations. Anyone used PhilZ Touch?
Ok, I used FreeGee to bypass security and installed TWRP 2.6.3.0. Boots into recovery fine, BUT it will not see my SD card and I tried two different ones. Normal boot shows the cards just fine. Trying to get CM 10.2 flashed.
Any ides???
madgalaxy said:
Ok, I used FreeGee to bypass security and installed TWRP 2.6.3.0. Boots into recovery fine, BUT it will not see my SD card and I tried two different ones. Normal boot shows the cards just fine. Trying to get CM 10.2 flashed.
Any ides???
Click to expand...
Click to collapse
Your cards are most likely in EX-Fat format. EX-Fat is a proprietary file system that is licensed my Microsoft. Since TWRP doesn't license it they can't (legally) include support in their recovery. You're going to have to copy everything over to your computer, reformat the card and transfer everything back. Otherwise you can look to see if there are any recoveries for the G Pro with EX-Fat support.
mrfeuss said:
Your cards are most likely in EX-Fat format. EX-Fat is a proprietary file system that is licensed my Microsoft. Since TWRP doesn't license it they can't (legally) include support in their recovery. You're going to have to copy everything over to your computer, reformat the card and transfer everything back. Otherwise you can look to see if there are any recoveries for the G Pro with EX-Fat support.
Click to expand...
Click to collapse
That is a negative, my cards in FAT format but for the heck of it I did a full format and still no dice. I even tried to use FreeGee and flash CWM, but TWRP still boots as the recovery.
Any other ideas?
madgalaxy said:
That is a negative, my cards in FAT format but for the heck of it I did a full format and still no dice. I even tried to use FreeGee and flash CWM, but TWRP still boots as the recovery.
Any other ideas?
Click to expand...
Click to collapse
Solved. I tried another install of CWM via FreeGee and it took. CWM is recognizing the sd card!
madgalaxy said:
Solved. I tried another install of CWM via FreeGee and it took. CWM is recognizing the sd card!
Click to expand...
Click to collapse
Just checkin....did you use the latest version of free gee from the play store?
Sent from my LG-E980 using XDA Premium HD app
I've searched for many hours and read many threads, but can't find anything on how to fix this.
I upgraded to MK3 following Cnexus instructions in this thread. http://forum.xda-developers.com/showthread.php?t=2538543
Everything appears to be working fine, but the S3 no longer recognizes the External SD card (64GB) after the upgraded,,. It can be read by my PC, and the S3 will mount/read smaller SD cards (I do not have a 32GB, but it mounts 16GB, 4GB and 32MB SD cards just fine).
My CWR recovery will not read external SD either.. and not sure if I should apply the img in the following thread http://forum.xda-developers.com/showthread.php?t=2391616
Internal SD is working fine.. just can't mount the 64GB microSD on my S3.
any help or directional pointers would be great...
thanks..
64GB SD Cards should be formatted to FAT32 for the S3.
Or flash DKP Kernel for ExFat and/or Fat32 64gb support.
prboy1969 said:
64GB SD Cards should be formatted to FAT32 for the S3.
Click to expand...
Click to collapse
Thanks for the reply... but this is not a new 64GB card.. it's been in my S3 and working just fine all of 2013 w thru the MA6, MB1 and MD4 updates.. it's only following Cnexus MK3 upgrade installs that it has stopped working. It won't mount the SD card.. it will hang the S3 when trying to, and eventually ends with a "safe to unmount SD card" notification.
I bought a new 64GB card and it gives the IDENTICAL behavior.. so I don't think it's the card format..
This is on Cnexus Sprint stock rooted MK3 4.3 ROM...
I've always stayed stock, but rooted.
Both cards are exFat format.. I can't format the new card in the S3 because it can't be mounted. So did we lose exFat support in Cnexus stock MK3 ROM or ?? 'cus I definitely had it in the other releases..
http://forum.xda-developers.com/showthread.php?t=2538543
I can't ask him directly.. not able to post in dev forums...
UPDATE: googling found this.. http://forums.androidcentral.com/sp...nt-now-after-installing-4-3-mk3-wifi-fix.html
It appears to be related to the wifi fix, but I'm not sure I want to install a custom kernel.. thoughts?
Ramer84015 said:
Or flash DKP Kernel for ExFat and/or Fat32 64gb support.
Click to expand...
Click to collapse
sorry.. bit of a noob on the phone side, but WHICH dkp kernel http://d-h.st/users/decimalman/?fld_id=19563#files should I be loading up and does one do that in the same manner as a normal flash (install on S3, boot to recovery, apply, etc) or is it Odin or ADB ?
I'm on cnexus stock MK3 ROM, so I assume that is touchwiz based?
http://d-h.st/users/decimalman/?fld_id=19563#files
s0c9 said:
sorry.. bit of a noob on the phone side, but WHICH dkp kernel http://d-h.st/users/decimalman/?fld_id=19563#files should I be loading up and does one do that in the same manner as a normal flash (install on HD, bott to reciovery, apply, etc) or is it Odin or ADB ?
I'm on cnexus stock MK3 ROM, so I assume that is touchwiz based?
http://d-h.st/users/decimalman/?fld_id=19563#files
Click to expand...
Click to collapse
Yes, you want to flash the TW 4.3 kernel. You flash in recovery. After rebooting your phone will see your extSD again.
Sent from my Nexus 7 using Tapatalk
s0c9 said:
sorry.. bit of a noob on the phone side, but WHICH dkp kernel http://d-h.st/users/decimalman/?fld_id=19563#files should I be loading up and does one do that in the same manner as a normal flash (install on S3, boot to recovery, apply, etc) or is it Odin or ADB ?
I'm on cnexus stock MK3 ROM, so I assume that is touchwiz based?
http://d-h.st/users/decimalman/?fld_id=19563#files
Click to expand...
Click to collapse
The one you want is in the link below. You can place the zip file on the root of your SD Card. Boot into Recovery, wipe caches, and flash.
EDIT :
Edited to avoid issues in the future for members. Instead go directly to decimalman's Kernel Thread. That way you will be assured to have the latest version .
TEAM MiK MikROMs Since 3/13/11
Ramer84015 said:
Yes, you want to flash the TW 4.3 kernel. You flash in recovery. After rebooting your phone will see your extSD again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
prboy1969 said:
The one you want is in the link below. You can place the zip file on the root of your SD Card. Boot into Recovery, wipe caches, and flash.
http://d-h.st/Dqe
TEAM MiK MikROMs Since 3/13/11
Click to expand...
Click to collapse
Will give it a try.. thanks for the help guys (very much appreciated).
if you read any of cnexus thread on that rom. you would have seem it was a issue with that stock kernel. flash the one above that will fix it. as for cwm recovery issues. check this out.
http://forum.xda-developers.com/showthread.php?t=2446393
kaos420 said:
if you read any of cnexus thread on that rom. you would have seem it was a issue with that stock kernel. flash the one above that will fix it. as for cwm recovery issues. check this out.
http://forum.xda-developers.com/showthread.php?t=2446393
Click to expand...
Click to collapse
Thanks... With all due respect.. I did read that thread (it's 95 pages long in Chrome) tho' not every last word of it as it went all over the place..and I did do searches within the thread.. I also googled VERY MUCH, but having the issue and knowing what to do to fix it are different (the info indicated a problem with exFat, but no fix in that thread with stock kernel, and I'm reluctant to install custom kernels due to my lack of knowledge in the xda arena), however, the suggested fix to install the new kernel DID work (Thanks decimalman)..
While I root, I don't mess with custom rom's much and stay as stock as possible.
I need a working phone, and can't afford to brick it.
UPDATE: For those relative noobs (like me) one needs to do the following to get your 64GB exFat SD card working....
Follow the steps in this thread - http://forum.xda-developers.com/showthread.php?t=2541900&highlight=mount+sd+card
Then install this version of Decimlman's kernel - http://d-h.st/Dqe