Related
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Yeah this is very odd. A couple of us in ##incredibleroms have been working with AnthonyKash to figure this out. So far we have had no luck at all. No Sense UI ROMs do this to him, it seems like it's only vanilla ROMs. Very strange............
anthonykash said:
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Click to expand...
Click to collapse
I know you posted this months ago but was wondering if you figured out what is causing this? I too can't use ANY aosp Rome because they all end up being unusable after a couple of hours. It's almost like the CPU slows down to a dramatic crawl. Only way to fix is to do a battery pull to reset. I have cleared cache, dalvik, uninstalled setcpu, all with no luck. Anyone have any insights?
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
+1 to the above post. Seems like some sense files are bring left somewhere.
Sent from my ADR6300 using XDA App
smtom said:
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
Click to expand...
Click to collapse
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
One thing I do find very weird is that even after doing full wipes of user data, cache and dalvik, when I boot up on CM7 my wifi settings still work. I would have expected I needed to reenter all of those settings. Or does this stuff get saved to the SD or internal storage...normal? If it is not, then why are data wipes in Recovery not cleanning up my files?
I've not had this problem.
Sent from my ADR6300 using XDA App
greatchief1 said:
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
Click to expand...
Click to collapse
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are not wonky, maybe it is an app you have installed on the AOSP ROM?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Maybe try another different AOSP ROM?
I know the SD interacts quite a bit more with the SD compared to Sense ROMs - again, maybe copy SD card contents to PC, reformat SD to FAT32 either on the PC or in phone, maybe both - then d/l an AOSP ROM on a clean SD, see if it's still wonky.
smtom said:
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are wonky, maybe it is an app you have installed?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Click to expand...
Click to collapse
Sense ROMS work great, its AOSP roms that are giving my phone fits lol. Well last night I tried something new.
-I changed my radio from 2.15.00.09.01 to 2.15.00.07.28 Official Froyo radio.
-Installed CM7 #14 from the EMMC versus SD CARD.
-"Hit Wipe All" in recovery about 10 times in a row before I flashed CM7
I hope changing the radio to "official" is what does it. Anyone running AOSP roms using the leaked radio 2.15.00.09.01 ?
Radio?
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
smtom said:
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
Click to expand...
Click to collapse
Well it turns out that the radio version I was using was not the issue because the phone became unresponsive this morning when I tried to wake it up. To be specific, it does allow me to swipe to unlock but painfully in slow motion.
So that rules at the radio...which leaves me with its either the ROM/Kernel or some rogue app.
So this morning I wiped all user data in recovery and reinstalled CM7#14 but this time I did not log on to my google account during setup and have not installed any apps. So far no issues, but the true test is trying to wake the phone up tomorrow in the morning. If there are no issues, then that solves it (ITS A FREAKING APP).
If it is a rogue app that has been haunting me these past couple of weeks then who has the best way to identify which one is the offender? Why would a rogue app only affect me using AOSP roms and not Sense?
My suspicions are with..(Locale, Beautiful Widgets, ADW EX, Swype, CardioTrainer, Handcent) but I guess process of elimination is what its going to take.
Thanks to all for the help and recommendations.
cougar618 said:
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
Click to expand...
Click to collapse
Please tell me u meant 7gb not 7tb
If you have a SD card that huge I beg you to tell me where to get it
I've heard of a 2tb SD but they haven't released it
Sent from my Incredible using XDA App
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
greatchief1 said:
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
Click to expand...
Click to collapse
Good stuff. Glad to see it all finally worked out.
Hey all, so I've searched the "no app2sd partition found" topic and it seemed to be pretty popular. However, my situation is different than from what I have read thus far. Please read what I have to say instead of ignoring my post and assuming that my situation is the same as everyone else's and give me some stupid useless post like "google is your friend."
Here is my situation:
Normally running Baked Snack's ROM perfectly fine. I decided to try the miui ROM the other day and didn't like it too much so I went back to the ROM I've been using for the past few months, being Baked Snack's. That went perfectly fine. But then, today I tried the miui rom again just to show off to some friends. Day is over so I decide to go back to what I've been using. Now here's the problem, I wiped data, cache, dalvik the usual, but this time after I rebooted the phone, it went the the white HTC load screen and then it went back to the recovery. Now it keeps doing that. I've wiped data/cache/dalvik multiple times and I made sure of it. Upon wiping my data, I noticed that it said "No app2sd partition found. Skipping format of /sd-ext."
I've searched this topic but still unsure of what to do because my situation is different, I've already done this before multiple times and now it's not working. I would very much appreciate any help.
Seems you went from a non Darktremor A2sd rom to a darktremor a2sd compatible rom or vice versa.
Search on his a2sd thread and you'll learn all about it.
Thanks for the reply. I'm not too sure how that could have happened, though. I've done this before with the same exact ROM and had no problem getting my nand back up.
I don't exactly have all the time in the world to read through countless pages to try to figure what's wrong, especially when I have basically no idea what's going on. So if someone could help me out, it would be great
Try asking at wwwdotbakedsnackshackdotcom. If you went from an aps2sd rom to a non-aps2sd, then search trevor's post on how to use terminal emulator to empty the apps2sd partition back into the phone memory prior to loading the non-app2sd rom.
edit: I do think that is a standard recovery message, that it couldn't find an ext partition. You might try wiping twice then rolling back in the rom you want.
This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app
Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.
Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...
Hey guys, it's been a long time since I've been flashing roms and stuff and I barely came back since I was tired of this jellybean Rom I'm on. Right now I have an older Rom that from what I an seeing isn't being developed anymore, wicked v10, Android 4.1.1, and I went through all the backups, with using tb to back up my apps, and I went into my recovery, cleared data and system, flashed quantum 3.6.4, flashed pa gapps, the same old stuff, and after I set up, I noticed the emulated sd card as I expected as it did that to me when I used to run aokp, but I could not ever find for the life of me any of my titanium backup backups, screenshots, etc. Even when I checked my other sd card folders. I found that strange since when I restored my backup, I was easily able to find the rest of the things mentioned. So what am I doing wrong? Also, is there a way to port my sms to hangouts as the new Rom used, and will I be able to used the restore backups of my contacts through the xml or something file that I generate in my contacts app when I used the app that comes with the new Rom? Thx in advance
Adding on to the fact I cannot edit my old post from my buggin out xda app, I seem to have found out whats wrong, which is that my internal sd is either not mounted properly, or cannot be read properly, while flashing ANY kitkat rom. I tried to search forums and google for a solution to this but I couldn't turn up anything. So can anyone at least tell me if this is a recurring bug on cm11 or kitkat based roms or am I just screwing up on something along the way?
Sent from my GalaxyS III
Have you tried Odin flashing your firmware and factory resetting after?
Could also be the /0/0/0/ folder problem. Every time you flash a rom it adds another /0 and that becomes the default directory. Look in /storage (maybe wrong, going by memory). It's well documented though. Check the faq sticky, I think it may be covered there.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
Have you tried Odin flashing your firmware and factory resetting after?
Could also be the /0/0/0/ folder problem. Every time you flash a rom it adds another /0 and that becomes the default directory. Look in /storage (maybe wrong, going by memory). It's well documented though. Check the faq sticky, I think it may be covered there.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I have not tried odin flashing and all that stuff just yet but I checked every possible folder using es file explorer and it seems not to be mounted. I will check the faq though
EDIT: FAQ didn't come up with anything. The only thing I can do now is to Odin my phone but I'm not sure exactly if it would work and be worth my time. It seems as if other people with different devices using cm11 and cm11 based roms have had this issue
Sent from my GalaxyS III
Is theres a way to fix apps failing to connect to facebook. I installed S3rx Rom a few times and downloaded it a few times also and it keeps happening. Also thethering activates, im able to connect devices but when I go to connect to internet I get webpage cannot be displayed.
(First post, so please bear with me)
I've been running Android Revolution HD on my M8 for about a year with great success. A few days ago I did a dirty upgrade from 45.0 to 50.2, meaning I also upgraded from Lollipop to Marshmallow.
The new version is working fine, with one exception: I'm unable to mount the external SD, at all. Have tried several different cards, MicroSDXC and MicroSDHC, both empty and with content, same result. Have tried re-formatting a card with both FAT, ext4 and exFAT in TWRP and GParted.
Everything worked fine before the upgrade, no cards work now. Mounting external USB works.
The only thing I can think of is that I have not upgraded the firmware - I'm still on 4.16.401.10. I understand there is now a newer one, but I have not yet been able to find this for European GSM models (my exact CID is HTC__Y13). Could this be the reason, and if so, does anyone know where I might find the newer firmware, if it's available? If it's not, can I use the one from Google Play Edition, or something else, even if the CID doesn't match?
Exact symptoms: In Settings -> Storage & USB -> Removable storage, it reads:
SD Card
Ejected
If I click "Ejected", I get a dialog that reads "This SD card is safely ejected, but still available. To use this SD card, you have to mount it first.". If I then click the mount button, a pop-up displays reading "SD card is mounted", but nothing actually happens, and the card is not actually mounted anywhere. If I physically eject the card, the "Removable Storage" sub-menu disappears, but re-inserting it just brings back the same problem.
Any help or suggestions would be greatly appreciated. TIA
@mike1986. Just thought I'd tag you, since it appears I'm not allowed to post in the proper ARHD forum. Hope that's alright.
I recommend a clean install of the rom (full wipe) as it is a huge firmware upgrade. If the problem remains it might be a rom related issue but I don't think so at this time.
Mysterion1 said:
I recommend a clean install of the rom (full wipe) as it is a huge firmware upgrade. If the problem remains it might be a rom related issue but I don't think so at this time.
Click to expand...
Click to collapse
Thanks for your reply. I am quite willing to believe this is a firmware issue, rather than a rom issue, although on my part this is pure speculation. If you have anything beyond speculation to suggest it is indeed firmware related, I'd happily try an upgrade. But this still leaves the question of which firmware to upgrade to, and where to get it. Any idea?
If a firmware upgrade didn't solve it then perhaps a clean install/full wipe might be worth a shot, if there aren't other, more targeted suggestions. But I'd sooner like to rule out other possibilities, given the amount of extra work involved in a full wipe.
Still no go
With Marshmallow finally being released in WWE edition for European users, I have been able to successfully upgrade the firmware to 6.12.401.4. I have also upgraded ARHD to 51.0.
Unfortunately none of this has had any effect on my original problem, and with my initial hopes that this was a firmware issue now squashed, I am frankly quite stumped for ideas. I'd really rather avoid the pain of having to reinstall from scratch, especially when I have no other problems with the ROM, and several issues with sluggish UI I experienced before in Lollipop are now gone. Frankly everything else is working fine, apart from this.
Anyone have any ideas, any at all, besides the above? Have anyone else seen this problem, even?
Mysterion1 said:
I recommend a clean install of the rom (full wipe) as it is a huge firmware upgrade.
Click to expand...
Click to collapse
He doesn't actually mean "firmware" here. He just means you should do a full wipe since the ROM version is a significant upgrade (as you should always do for major ROM version changes). Dirty flash has a huge potential for random bugs, so you should eliminate that as the cause, first of all.
Same goes if you migrated the user data through the MM OTA.
Some ROM threads you will see around here, they tell you to not even think about posting a bug report, if you did a dirty flash.
Have the exact same problem after doing OTA upgrades from 4.4 to 5.0, and then from 5.0 to 6.0.
Wonder if the original poster did try a full wipe, and if that helped?
For anyone else finding this thread via google or similar, after wiping (I used the default wipe option in twrp) and rebooting, my sd card functions as normal.