Related
Hello out there!
I sure hope someone can help me with this! I have rendered my phone completely useless. I have been working on this thing for the past 7 straight hours.
I upgraded to the 5.08 radio and then the MIUI_Au_1.1.28_R4_N1_EN-signed.zip
Everything was working beautifully until I decided to do a Nandroid restore. I guess I did not truly understand the function of this. After a reboot, I was back at square one.
I rebooted again into the recovery mode and then wiped and reinstalled the new rom. Now the new rom is giving me an error. I cannot get any network connectivity from it. I wipe and reinstall several more times and get the same effect.
This is when I get the idea to format and partition the SDcard from within the recovery menu. This was clearly not the best choice.
I cannot get the phone to restore back to factory anymore. The SDcard is empty. I have even taken it out. When it boots up it still boots into some non-working version of the new MIUI rom. No network connectivity. Where is it storing this? I have wiped everything possible. Played with partitions. I have tried hard resetting in the limited interface and in the Recovery console.
At this point, I cannot work on this any longer. My next idea is to put the micro SD card in another device and put original stock image on it. Is it possible that the new rom installed a kernel and that is what I am seeing? I figure if I can install a different rom from the SD card I might just be ok.
Any input into this mess would be greatly appreciated. Because I still have access to the Recovery console I know this is not the end for my phone.
Someone please tell me they know what is going on!
I would be happy to elaborate any more points regarding this issue.
It seems to me that I am not able to delete something because the new rom keeps coming up. Where is it booting from if I wiped everything?
I am at my witts end!
Thank you so much for your thoughtful responses!
glizitch
If you can enter the recovery mode, you just have to enable the SDCard to browse it from your computer. From there you can push in the sdcard whatever zip you wish. Remember to wipe cache and data.
If you can't enter the recovery mode, go in fastboot and flash it again.
And of course, the ROM is booting from /system partition on internal Flash memory in the device, which you can't wipe without knowing fastboot/adb commands - which obviously isn't the case. Wiping SD card won't do anything, and wiping user data isn't going to help you either.
As already mentioned above, since your recovery is working - get into it, mount the USB-MS, connect to PC, copy a ROM of your choice to the SD card, unmount, flash it, enjoy. I suggest RTFM before doing things.
Gratitude!
Thank you for your replies!
I have been putting off doing this upgrade for some time and have been living with limited functionality on the phone due to the amount of time and research I would have to put in to make sure I cross all my t's and dot all my i's.
I was never able to get the MS-USB toggle to work. Windows XP would not show I had put a new drive in when I used it.
I remedied the situation by getting a microSD to SD adapter so that I could put the new rom on the SD card. I used the original microSD card at first and installed the MIUI again. This caused me the same results of rebooting a few times before it went into the rom. When it got in I had no network connectivity.
I decided I would try this brand new microSD card and put the EvIL rom 1.26 on it instead.
I wiped and installed the Evil rom on the new card and Walla!
I have Evil rom now working with network functionality. There must have been some kind of hidden garbage on the old microSD that was keeping me down.
8 hours into the project, I AM SO HAPPY TO HAVE MY PHONE UP AND RUNNING!!!!
I hope others may find this post useful!
Many Blessings & Thanks!
glizitch
I've got a Samsung Galaxy Note n7000. I've hopped around a bit, but recently I've tried to move (back) to JB based CM10 (nightly) and also AOKP (JB Milestone 1).
For both CyanogenMod and AOKP, I quickly came across the issue that most apps can't see any storage folders. This includes:
-Browser and Chrome can't save files as there's 'No storage'.
-Google Maps won't cache anything.
-The camera and gallery won't work because they can't see any storage.
-When I plug the phone in to a PC via USB, the phone is identified, but no storage folders come up, regardless as to whether I'm using MTP or MS.
-In the system settings under storage, it can see the 2GB for my app Data partition. It says there's a 32GB SD card available, but under the Internal Storage heading, clicking 'Mount SD card' flashes up something in the notification bar before looking like nothing happened. There's nothing about the internal ~10GB partition either.
However, if I go into a file browser, I can see both the internal storage mapped as /storage/sdcard0 and the SD card mapped as /storage/sdcard1. I believe this is how JB is now mapping storage now? Why is it confusing itself?
Note:
-I can see the storage in CWM without issues (although internal and SD might be reversed???).
-I can read the files fine from a file manager, so there's nothing wrong with the SD card as far as I can tell. It works fine in an SD card reader too.
-I tried AOKP first after a full wipe (factory, data, davlik), hit the issue. Tried CM10 which was the same. Tried AOKP again with a factory wipe before and after flash and it still didn't work.
I've been trying to find a solution for nearly 2 weeks now! Please help before I give up and flash back to a Samsung based ROM!
For history:
I've had the GNote unlocked for a while and I've played with a few ROMs including CM9, earlier releases on CM10 without any issues. For the past couple of months I went back to an ICS TouchWiz based ROM as I thought the only way to get an MS Exchange email email app with full device encryption was to use Samsung's.... anyway, found an app that'll do it for me without suffering the slow down of encrypting the whole phone AND putting TouchWiz on, so I thought I'd try to go back to a 'pure' ROM until I ran into the above problem... Is it because I previously had the phone fully encrypted? I can see the folders now though.... AAAARRRRGGH!
...
Just in case it was an issue that has been fixed recently.... I tried ParanoidAndroid for the Note (v2.54 10 Nov 2012)... same issue. I did a factory reset, cache wipe and davlik wipe before and after flashing. Still both internal and SD storage are mapped so the apps and System settings can't see them.
What is wrong?
Update 2...
I tried flashing the following ROMs:
-A TouchWiz based ICS ROM (Sweet v5)
-A stock based ICS ROM (CM9.1)
-A TouchWiz based Jelly Bean ROM (Rocket Bean V2)
-Re-flashing CM10 nightlies
In every case both the internal and SD storage can't be seen in System>Storage.
What have I done???? Have I somehow screwed up the formatting on both the internal and SD card, yet CWM can read it??? Any ideas?
im on a XXLS7 based rom and its in
/storage/extSdCard
/storage/sdcard0
may be you want flash a stock GB or ICS rom again using Odin and start fresh
I haven't tried Odin yet... but when I was about to, I discovered something. I installed Titanium Backup. Instead of complaining I didn't have any storage (like all other apps), it complained that my storage directory wasn't writeable...
How do I check what the permissions are? What should they be? How do I fix it?!!!
Thanks.
Hi!
I have the same issue.
I'm currently on RocketRom V3 but I had the issues with others roms before.
I have a temporally fix: using root explorer, set the permission from r/o to r/w for the folder /mnt/sdcard
But after a while (fews minutes), it turn back to r/o, I don't know who/why.
Same here. Thought it was me!
Started when I switched to jb leak.
Says storage us full when I try to open camera,etc, even though it's not true
Sent from the man hiding in your attic.....
Ok, I found an fix that works for me
It looks that I had a bad file/folder/whatever on my internal storage, so the system put /sdcard (internal memory) on read only as it notice the bad thing.
Formating sdcard or emmc from cwm didn't work, full wipe neither, formatting internal from android settings neither, but I manage to mount internal SD on my computer using mass strorage (UsB switcher is included on Rocket V3 to switch from MTP to Mass storage)
Once mounted in Windows, I did a full format (fat32) of the internal memory, and so far it works!
I re-formatted my SD card in a memory card reader. I've put it back in the phone and now when I plug my phone in to my PC and select USB mass storage, the SD card comes up in Windows and I can write to it! Woot!
At the moment I still can't write to my internal storage (which means most apps still complain). It appears as a drive in Windows via USB, but I can't open it. I'll try Feyris' RocketRom suggestion later.
Any guess as to why this has happened? Anything to do with the fact I had full-device encryption on the phone before????
Is there any way to sawp the card location as on im on jb its taking external card as internal default location..As i am having class 4 sdcard so itz slowing down the system
Feyris said:
Ok, I found an fix that works for me
It looks that I had a bad file/folder/whatever on my internal storage, so the system put /sdcard (internal memory) on read only as it notice the bad thing.
Formating sdcard or emmc from cwm didn't work, full wipe neither, formatting internal from android settings neither, but I manage to mount internal SD on my computer using mass strorage (UsB switcher is included on Rocket V3 to switch from MTP to Mass storage)
Once mounted in Windows, I did a full format (fat32) of the internal memory, and so far it works!
Click to expand...
Click to collapse
When I put my Rocket V3 into the mac with usb switcher it mounts two drives. Both, however, are part of the internal SD card. It does not mount the proper external sd card. One is titled sdcard of the drives just called sdcard, the other is called storage (which has folders sdcard0, extSdCard, and usbstorageA-F). Should I format them both? Do I need to recopy all the files back onto the sdcard before booting up again?
Thanks!
Edit: I was either totally confused (most likely) or somehow I managed to fix my issue (less likely)...so I am ok now.
Internal Storage Mount
So I am having a similar issue.
I have an Evo 4g LTE running CM10 (cm-cfX-20120904-OFFICIAL-jewel)
I tried upgrading to the 11-13 build from get.cm site. I factory reset, wiped delvik, installed .zip from external sd card, installed gapps (gapps-jb-20121011-signed) wiped delvik again, rebooted, everything came up like it should, but I had no mobile data connection. All of my settings said unknown. So I rolled back to the (cm-cfX-20120904-OFFICIAL-jewel) build. Everything was working fine again, except I went open CWM v 5.8.3.5 from my app drawer and noticed message "you need sd card to run clockworkmod" so I went to sys settings > storage > internal storage (not mounted > mount storage and it attempts to read the data, but then does nothing. No error message or anything. I can't get my computer (windows 7) to read my internal storage so I can't format (which I have already done before)
I'm getting really frustrated as I have searched everywhere for the fix and have found nothing. If anyone has any idea I would greatly appreciate it.
Finally got around to spending a few hours on this yesterday to try to fix my 'missing' internal storage...
As suggested by nokiamodeln91 (cheers mate), I used Odin to go back to a stock ROM. Steps:
-Did a CWM backup of my current my current favourite ROM (I also used Titanium and SMS backup, but didn't need it in the end).
-Found an appropriate Samsung factory ROM. I went back to 2.3.6 as it's supposed to be safer. (For the n7000, make sure you choose an early one and not 'L' series or it's harder to root.)
-Used Odin to write the factory ROM. Note I only wrote the ROM, I didn't flash the modem, PIT, etc.
-Confirmed that I could see both my internal storage and my SD card (and also confirmed that a factory fresh install from Samsung looks and feels as ugly as I remembered).
-Used an 'update' hack to give me root.
-Installed CWM again.
-Simply restored my CWM backup of my favourite ROM...
In reality I went down several dead-ends... but I eventually got it all working again.
Guigsy said:
Finally got around to spending a few hours on this yesterday to try to fix my 'missing' internal storage...
As suggested by nokiamodeln91 (cheers mate), I used Odin to go back to a stock ROM. Steps:
-Did a CWM backup of my current my current favourite ROM (I also used Titanium and SMS backup, but didn't need it in the end).
-Found an appropriate Samsung factory ROM. I went back to 2.3.6 as it's supposed to be safer. (For the n7000, make sure you choose an early one and not 'L' series or it's harder to root.)
-Used Odin to write the factory ROM. Note I only wrote the ROM, I didn't flash the modem, PIT, etc.
-Confirmed that I could see both my internal storage and my SD card (and also confirmed that a factory fresh install from Samsung looks and feels as ugly as I remembered).
-Used an 'update' hack to give me root.
-Installed CWM again.
-Simply restored my CWM backup of my favourite ROM...
In reality I went down several dead-ends... but I eventually got it all working again.
Click to expand...
Click to collapse
Dude! you are insane...Got my S2 4.1.2 working, thanks to you.. tried for 3 days back to back until i stumbled on your solution.
Thanks so much.
A BIG Thanks to Guigsy & nokiamodeln91
Long story short is I broke the screen to my GNote 2 which is on its way to Samsung for repair (A little under US$200 round trip). When I removed the battery to get the emie number there was "goo" oozing out the back from the screen I suspect.
Anyway, turned on my GNote 1, which hasn't seen the light of day since last October and booted to discover that it wasn't working right. I tinkered for quite an embarrassingly long time to where I found myself in the same situation as others here. No write access to the internal storage on my CWM rooted GNote.
Although I had a nand backup, I ended up using ODIN to flash LT4 Germany, lost root as a result. went back in to Download mode and used ODIN to install PhilZ-cwm6-XXLT4-OXA-5.00.5.tar the exact same way, booted into CWM recovery and flashed PhilZ-cwm6-XXLT4-OXA-5.00.5-sigend.zip and was good to go. Issue definitely resolved.
I did not have root after installing the PhilZ-cwm6-XXLT4-OXA-5.00.5.tar via ODIN but I was able to enter CWM recovery where I then installed the ZIP version. As I had fixed my issues I was able to copy over the ZIP version to my Ext SD card B4 going into recovery mode (Yup, one of the symptoms for me was not being able to copy to the external SD card when the phone was connected to my PC either).
Rebooted signed in and was quickly synching my apps, settings etc. I would have felt comfortable using the nand backup I had originally but since this solution brought me up a few versions of Android, I just did a fresh setup.
Had it not been for XDA and our friends here, I would have formatted, factory reset and who knows what else trying to fix this.
Thanks much,
Claude H.
This from a real noob, but I thought I would solict some additional input if there is some trick I have missed on my problem.
Since installing CM 10 on my Vivid, everything has worked well except the fact my internal SD has gone away. Based on stuff I have read here I have tried the following:
1. Factory Reset - no help
2. Mount drive using installed recovery, CWM - No Help
3. Install TWRP recover and try that, no help
4, Try various apps from Play Store, No Help
At this point it seems best to me to return the phone to factory state and see if the internal card is there, if it is, unlock the boat loader, install TWRP recover, then flash the rom, then boot imate (s on) and hope it works.
Any app that requires root and access to all the drives errors out.
A large group thanks to all of you who post so much info on the phone, and how to do things.
I assume you've tried mounting Internal SD in the Settings/Storage menu?
Sent from my Vivid 4G using Tapatalk
Internal Mounting
Thanks for reminding me about this, but yes, I have tried it numerous times but it doesn't work. A bit frustrating since it keeps me from storing certain stuff or using some rooted apps. Unless I find some other way, I will give the restore option a try in a few days when I get home.
Appreciate the reply.
pwebber09 said:
This from a real noob, but I thought I would solict some additional input if there is some trick I have missed on my problem.
Since installing CM 10 on my Vivid, everything has worked well except the fact my internal SD has gone away. Based on stuff I have read here I have tried the following:
1. Factory Reset - no help
2. Mount drive using installed recovery, CWM - No Help
3. Install TWRP recover and try that, no help
4, Try various apps from Play Store, No Help
At this point it seems best to me to return the phone to factory state and see if the internal card is there, if it is, unlock the boat loader, install TWRP recover, then flash the rom, then boot imate (s on) and hope it works.
Any app that requires root and access to all the drives errors out.
A large group thanks to all of you who post so much info on the phone, and how to do things.
Click to expand...
Click to collapse
My guess... Is you did a reset from fastboot...
If that is the case... I recommend getting twrp... Installing that... Mounting both storages in recovery... Then hook to your windows PC... And let windows format your internal SD...
After a reboot... Your phone will either mount your internal... Or offer to format it again... At which point it will work...
Unless we are talking about apps2sd in CM11...
Sent from my Vivid 4G using Tapatalk
More Info
rignfool said:
My guess... Is you did a reset from fastboot...
If that is the case... I recommend getting twrp... Installing that... Mounting both storages in recovery... Then hook to your windows PC... And let windows format your internal SD...
After a reboot... Your phone will either mount your internal... Or offer to format it again... At which point it will work...
Unless we are talking about apps2sd in CM11...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
____________________
As far as I know I did not reset from fastboot, but I have been in that mode a good number of times, so it is very possible.
I replaced CWM recover with TWRP and it would not allow me to mount the internal card, but the phone booted up OK, just no internal card. So I tried another factory reset and while in TWRP I noticed I was also getting a "can't mount /emmc/" message. Phone still boots up ok and works except for apps requiring access to the internal card.
I ran across some reference to a recovery called aroma something that is supposed to help with this problem, but am not sure it will work with my phone, still researching that.
So maybe this is pretty good evidence I did screw up and reset from fastboot?
I figure I am going to have to restore the phone to factory status, and start over, but I will wait to see if there any other suggestions.
Thanks again for the feedback.
pwebber09 said:
____________________
As far as I know I did not reset from fastboot, but I have been in that mode a good number of times, so it is very possible.
I replaced CWM recover with TWRP and it would not allow me to mount the internal card, but the phone booted up OK, just no internal card. So I tried another factory reset and while in TWRP I noticed I was also getting a "can't mount /emmc/" message. Phone still boots up ok and works except for apps requiring access to the internal card.
I ran across some reference to a recovery called aroma something that is supposed to help with this problem, but am not sure it will work with my phone, still researching that.
So maybe this is pretty good evidence I did screw up and reset from fastboot?
I figure I am going to have to restore the phone to factory status, and start over, but I will wait to see if there any other suggestions.
Thanks again for the feedback.
Click to expand...
Click to collapse
Ok...
You were close...
Don't mount internal for twrp...
Mount as USB mass storage in the same menu...
Then connect to windows...
Sent from my Vivid 4G using Tapatalk
I will give it a try
rignfool said:
Ok...
You were close...
Don't mount internal for twrp...
Mount as USB mass storage in the same menu...
Then connect to windows...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
Thanks very much, I will probably do this a bit later today and will let you know how it goes. Thanks for taking the time to help me out.
It Works!
Thanks againk, that solution did the trick.
So I have installed several versions of this ROM since it began, however when I upgraded to 1-12-14, all went well except my internal SDcard will not be recognized. This means I can't use the camera or Titanium Backup, etc. However, I can see and use the external sd card w/o any issue. Upon every boot I get the icon saying that I need to format SDcard0, but it never completes, only soft reboots and the icon is gone until the next full reboot. I flashbooted boot.img twice after doing a FULL wipe. I have tried reinstalling 3 times doing FULL wipes every time, still get the same. When I boot into recovery and try to wipe SDcard, I get an error saying
can't mount /dev/block/mmcb1k0p36 (Invalid argument)
Error mounting /internal_sdcard/!
Skipping format
I have also just tried the new 1-15-14 build and get the same results. I have fastbooted the boot.img each time. Please help. I have installed many ROMs on this device before w/o ever an issue. What did I do wrong and how do I fix it? TIA!
Reboot recovery
Mount USB storage...
Plug phone into computer...
Let windows format corrupt partition...
Profit
Sent from my Vivid 4G using Tapatalk
Just putting another method which worked for me (one time issue and fix, so it's a crap-shoot). I don't have the luxury of connecting to a computer via usb for anything except charging.
-properly flash a sufficiently different ROM (I had kitkat, so I flashed ICS)
-start ROM up, check if fixed (mine was not)
IF NOT FIXED, CONTINUE
-mount the SD card in your recovery (mine is WCX recovery)
-reboot your phone into the ROM
This method worked for me. I saw in a different forum that when this happens it's usually because a file that describes the partitions gets corrupted and that because ICS and GB partition the SD cards and internal storage in a different way than Jellybean or Kitkat, that flashing a different ROM (if problem is on ICS/GB, then flash KK/JB, and vice versa) will force an overwrite of the file in question.
This is not as easy as rignfool's method, and once my charge port arrives in the post, I will abandon this method and use Windows to repair the partition like a sane person
Also, it seems like all my media on the internal storage has been wiped, but wutevr :/
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Yuskow said:
Might want to try a newer build where that bug is fixed.
http://www.chronic-buildbox.com/nightly/holiday/
Click to expand...
Click to collapse
If this is directed at me, this happened after I installed the March 17th or 18th nightly (put a new one on every once and a while). And to be completely fair, I had accidentally selected factory reset in hboot (thought it was highlighting recovery, boy was I pissed).
The problem (or so I've read) with installing another kitkat/jellybean ROM is that the SD card is mounted the same (/storage/sdcard0, and external SD is only /storage/sdcard1) as opposed to ICS/GB (I only remember that you access external SD through /sdcard/ext_sdcard or something to that extent). Only when the SD cards will be mounted at differing locations will the system re-write the files specifying mount points.
I recently put an sd card in my phone, but for some reason the os is not picking it up. I checked in settings and file manager (even in root) but could not find anything. I get the same error in the stock rom. The card is formatted to fat32. This is weird since it is the same card I used before unlocking the bootloader and rooting, where it worked well.
Also, TWRP can read it but not the os, so I know that there is no hardware issue. TWRP says that the sd card is mounted. Any ideas? I could not find anything online.
I am using a sandisk 64 gb card.
Moto G(6)
TWRP 64 bit
Lineage OS
Thanks!
Try a low level format. Every time I've seen a new card do this its been problematic throughout its life. Might want to return it if other cards work in that slot... just not worth risking data loss over a buggy flash drive.
Always format a new card with that phone. Don't use it in other phones or devices as it can cause data corruption.
Once I install a SD card in a phone, I leave it there. All up/downloads to it are done with it in the phone. The more you handle it, the more likely it will be damaged. These cards are suspectable to ESD, it takes little to damage one. They have limited ESD input protection and are much safer when in circuit.
Never touch the contacts and be aware of static discharges. If you can see, hear or feel static electricity, there's already more than enough voltage potential to damage a flash drive.
blackhawk said:
Try a low level format. Every time I've seen a new card do this its been problematic throughout its life. Might want to return it if other cards work in that slot... just not worth risking data loss over a buggy flash drive.
Always format a new card with that phone. Don't use it in other phones or devices as it can cause data corruption.
Once I install a SD card in a phone, I leave it there. All up/downloads to it are done with it in the phone. The more you handle it, the more likely it will be damaged. These cards are suspectable to ESD, it takes little to damage one. They have limited ESD input protection and are much safer when in circuit.
Never touch the contacts and be aware of static discharges. If you can see, hear or feel static electricity, there's already more than enough voltage potential to damage a flash drive.
Click to expand...
Click to collapse
Thanks for the reply! It weird cause the card works perfectly fine with another moto g6. Also, I am unable to format on the phone, since it does not pick it up.
I can only view it on the custom recovery TWRP. This leads me to believe that it is an issue with the software, and not the card or reader in the phone.
The phone is also not picking up other cards. I have no idea what the issue is. Also, the custom rom seems to have no problem with sd cards as others have used it just fine. Do you have any ideas? I really appreciate the help as I have been trying for days now trying to get this to work.
HDXKohl said:
Thanks for the reply! It weird cause the card works perfectly fine with another moto g6. Also, I am unable to format on the phone, since it does not pick it up.
I can only view it on the custom recovery TWRP. This leads me to believe that it is an issue with the software, and not the card or reader in the phone.
The phone is also not picking up other cards. I have no idea what the issue is. Also, the custom rom seems to have no problem with sd cards as others have used it just fine. Do you have any ideas? I really appreciate the help as I have been trying for days now trying to get this to work.
Click to expand...
Click to collapse
It seems the issue is the phone. Carefully inspect the phones contacts for damage.
Try clearing the system cache.
Turn off Developer options temporary if on.
Try a hard reboot.
A system apk or it's data may be corrupted... there may be a bunch of dependencies here, so finding the culprit if any could be hard to find.
Have you installed or uninstalled any apps that may have effected it? Poorly written ones will sometimes alter hidden settings.
If you did a OS upgrade without doing a factory reset, now is the time. Otherwise it's always preferable to find the root cause rather than blindly fix issues with a reset.
It could be a mobo failure but this is probably the least likely cause.
Play with it... many times the answer is staring at you. Double check drop down settings and permissions.
blackhawk said:
It seems the issue is the phone. Carefully inspect the phones contacts for damage.
Try clearing the system cache.
Turn off Developer options temporary if on.
Try a hard reboot.
A system apk or it's data may be corrupted... there may be a bunch of dependencies here, so finding the culprit if any could be hard to find.
Have you installed or uninstalled any apps that may have effected it? Poorly written ones will sometimes alter hidden settings.
If you did a OS upgrade without doing a factory reset, now is the time. Otherwise it's always preferable to find the root cause rather than blindly fix issues with a reset.
It could be a mobo failure but this is probably the least likely cause.
Play with it... many times the answer is staring at you. Double check drop down settings and permissions.
Click to expand...
Click to collapse
I've tried reinstalling the rom with multiple resets (factory, advanced wipe, format data) but to no avail. TWRP can still read it, so I think the hardware should be ok. Do you have any other suggestions? Thanks for your help!
HDXKohl said:
I've tried reinstalling the rom with multiple resets (factory, advanced wipe, format data) but to no avail. TWRP can still read it, so I think the hardware should be ok. Do you have any other suggestions? Thanks for your help!
Click to expand...
Click to collapse
You're welcome.
Could TWRP's ability to access SD card to be a clue?
I don't root, my partition knowledge is limited, but could the issue be with data on one of the internal memory partitions?
Maybe a bad instruction set on the /misc partition? Be careful...
https://forum.xda-developers.com/t/info-android-device-partitions-and-filesystems.3586565/
This is interesting... I'm curious what's causing this.
Your hardware is ok.
I'm wondering why you use FAT32? SDs with 64GB+ normally uses exFAT. So, first I would try to format it manually to exFAT in TWRP's commandline. Maybe this could help.
First unmount the card (main screen > unmount) and then execute
Code:
mkexfatfs /dev/block/mmcblk1
WoKoschekk said:
Your hardware is ok.
I'm wondering why you use FAT32? SDs with 64GB+ normally uses exFAT. So, first I would try to format it manually to exFAT in TWRP's commandline. Maybe this could help.
First unmount the card (main screen > unmount) and then execute
Code:
mkexfatfs /dev/block/mmcblk1
Click to expand...
Click to collapse
I ran the code successfully, but it does not seem to change anything. However, I did get a decryption error and then wiped the data to solve it.
WoKoschekk said:
Your hardware is ok.
I'm wondering why you use FAT32? SDs with 64GB+ normally uses exFAT. So, first I would try to format it manually to exFAT in TWRP's commandline. Maybe this could help.
First unmount the card (main screen > unmount) and then execute
Code:
mkexfatfs /dev/block/mmcblk1
Click to expand...
Click to collapse
Any other suggestions? I'm stuck.
HDXKohl said:
I recently put an sd card in my phone, but for some reason the os is not picking it up. I checked in settings and file manager (even in root) but could not find anything. I get the same error in the stock rom. The card is formatted to fat32. This is weird since it is the same card I used before unlocking the bootloader and rooting, where it worked well.
Also, TWRP can read it but not the os, so I know that there is no hardware issue. TWRP says that the sd card is mounted. Any ideas? I could not find anything online.
I am using a sandisk 64 gb card.
Moto G(6)
TWRP 64 bit
Lineage OS
Thanks!
Click to expand...
Click to collapse
the error is your fat32 format... and no i dont make magic, and no, I dont have a magic method to you format it, so put on a pc and format on PC I has a 64gb sd card and works well in my two moto g6 ... and is exFat format.
Android formats SD cards
- up to 32GB > FAT32
- 64GB+ > exFAT
But SD cards with 64GB in FAT32 can be mounted by the system, too. (works fine for my Moto G6, no root)
brunogroa said:
and no, I dont have a magic method to you format it, so put on a pc and format on PC
Click to expand...
Click to collapse
It's already formatted in exFAT by using the terminal command mkexfatfs within TWRP:
HDXKohl said:
I ran the code successfully, but it does not seem to change anything
Click to expand...
Click to collapse
It's exactly the same binary as used by the stock ROM.
TWRP > mkexfatfs v1.2.2
Stock ROM > mkexfatfs v1.2.6
Try another card, make sure it's specs are compatible with the phone and it's fast enough.
Never encrypt SD cards or you will lose data, sooner or latter.
If it's not the phone when I see cards do this it indicates card hardware damage. They may function but they will have continuous issues throughout their life.
WoKoschekk said:
Android formats SD cards
- up to 32GB > FAT32
- 64GB+ > exFAT
But SD cards with 64GB in FAT32 can be mounted by the system, too. (works fine for my Moto G6, no root)
It's already formatted in exFAT by using the terminal command mkexfatfs within TWRP:
It's exactly the same binary as used by the stock ROM.
TWRP > mkexfatfs v1.2.2
Stock ROM > mkexfatfs v1.2.6
Click to expand...
Click to collapse
Oops my bad. Sorry for the confusion. I meant the sd card was formatted, but still not detected.
HDXKohl said:
Oops my bad. Sorry for the confusion. I meant the sd card was formatted, but still not detected.
Click to expand...
Click to collapse
Try a low level format of the card on the PC using a speciality formatting apk.
After multiple reinstalls and reformattings, I one day tried to reinstall the stock rom with Motorola's tool (Rescue and Smart Assistant). That seemed to do the trick!