Related
I'm getting a SD card damaged error after going from 4.0.2 to 4.0.3.1. The laptop reads the card fine so I know the card is ok. What's going on here?
Nandroiding back to 4.0.2 makes the problem go away.
Thanks for the info I had the same exact thing happen to me.
Did not think it was the rom but I knew there was no way all my microsd cards where messed up.
Weird thing the first one got somehow wiped to ext3 without me requesting it.
Going back to 3.8.1 let u know if got mine fixed or not.
Still tough might switch to jf again or other roms from haykuro.
Be right back as soon as I get home in 3hrs
I was getting this on one of Cyans roms before especially when unplugged from PC then restart and it would be fine. Haven't had any problems since so I'm sorry to say I don't know what it is, but at least it's not permanent haha.
Just tried 4.04 and same thing happens.
Changing the SD card seems to work but why is just THAT card affected? I'm going to back up the data on the card and try a few things. I'll let you know what happens.
sucks I had to start from scratch had to use a regenerator to fix the sdcard.
Basically phone nor pc would pick up past partitions. Used a corporate software from Paragon and Norton to undelete or try to recover deleted partitions. And now I was able to recover some of the files there are some that have a I/O read error so no luck with those kinda like a data redundency check failure.
Then used a regenerator to wipe the whole drive and recreate it. Wierd thing is that the droid did not read it until I reverted back to old cyanogen 3.8.1
now I'm back debating if to update to the newest 4.0.4 but scared now.
well I already lost most of the data what else can I lose right? lol
Im telling you it is a great investment to have Paragon Hard Disk Manager for business. At least that is what saved me this time.
Well for me. the ext3 partition works fine. All my app2sd works good. But my fat32 parition doesn't work (but works on other builds)
Well, it works now.
See whenever I mounted the SD card to Windows Vista, it said there was problems with the SD card and Windows wanted to scan it and fix errors. Well knowing the card worked fine, I always said no to the scan.
Well since I was having problems with 4.0.3.1 and 4.0.4 I decided to let Window scan and fix it, and it seemed to actually fix it. So there.
yeah i had the same issue also i thought it was cause i was trying to add an old theme to 4.03.1 but it wasnt...i did a wipe repaired the extfiles then added 4.02 again went straight to 4.03.1 through cm updater and it was fine..so if anyone has the same issues try to wipe first and see if that helps
Wipe did not fix problem.
I have the same problem. I tried a wipe through the recovery and with the
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
command. It still says the SD card is damaged. Restore with Nandroid, and everything is fine. I think I will try a fresh partition (I currently only have two partitions). I will try to get back after I reformat to get the three partitions.
As i see, more and more people are asking, how to install Android. And since previous tutorial is outdated, i will create new one.
So, first some theory. There are two types of releases: ones with ext2 partition and ones without. Second ones are much easier to install (just copy files to SD card), but ones with ext2 partition are faster and works overall better. All newer releases are with partitions.
So, how to install Android?
1. First we must prepare our SD Card. You will need 1GB+ Card. Some users are reporting that there are problems with several cards, so i suggest you stick to card you got with your X1 (it works 100%).
Now it's time to hook SD card to your computer. You can transfer files via X1, but I recommend getting a card reader, since file transfers will be more reliable then.
Before you begin, backup all your files on SD card. When partitioning, all data on your card will be deleted.
So, let's begin. Partitioning is fairly easy, but instead of writing this in text, i will show you video guide of creating partitions (thanks to user e334 for making this tutorial):
(Program in the video is Minitool Partiton Wizard. Grab home version from their page.)
2. After we properly make partition, it's time to download android build. Beware, that root of your SD card will be messy. There is a method to run it in folder (Andboot), but i didn't manage to make it right.
In the time of writing, (my opinion) best release is neopeek's SuperFroyo + v2c kernel. But releases are changing rapidly, since Android is still under development. I will try to update that page, but i suggest you always check the forums for some new releases.
As you can see, this release is in two parts (main release + kernel). But most of the time, there are releases with kernel included, so you don't have to download it separately. So anyway, download and extract main release, kernel and modules into root of the SD card (leave modules in .tar.gz file!).
After copying, use safely remove hardware before disconnecting SD card.
Now it's time for big final. Open file explorer on your X1, navigate to StorageCard\npkinstall folder and click install. If you have done everything right, your phone should go into "text mode" (black screen with bunch of text) and after about a minute, it should start displaying long list of files. That means it's installing android to EXT2 partition. When installation finishes, it will automatically reboot.
Your X1 Android is ready to use now. To launch android, open file explorer, navigate to \StorageCard and tap HARET. Again, it should start displaying text and after that logo should appear. When android appears to be loaded (start wizard pops up), leave it for another several minutes, so Android can initialize all background stuff it needs to.
Happy Androiding!
Frequently Asked Questions
How to return to Windows Mobile?
Simply restart your device. Android won't alter Windows Mobile or on board storage at all, so your windows mobile stays intact.
So, now my Windows mobile is running in background?
No. HARET will shut down Windows Mobile, so Android can have all the memory for himself.
Battery life is very short
Yes, android power management is not very good. But it's getting better, especially last days there were some major improvements in that area.
Camera/FM Radio/Something don't work
Android is still under development, so not all features are working yet.
I can't see my new EXT2 partition in windows
That's OK. Only linux sistems like Android and Ubuntu can see EXT2 partition. Although, you can install 3rd party software, that can add ext2 support to windows (google for "ext2 windows").
How big should i make ext2 partition?
EXT2 partition is system partition for Android. It needs to be big enough to fit all android system files in, but there is no point to make it too big, since data is stored to SD card anyway. Somewhere between 300 and 500MB should be fine. Make it 512 if you have space to spare or 300 if you are really low on SD card space.
I can't enter my SIM PIN!
PIN is currently not working in Android. Turn off PIN in Windows Mobile.
matejdro.. you are one of the best "teachers" thanks a lot.. very kind if you could update this threat everytime if something is new, because there are a lot of new kernels and things coming in.. i try to get in to this matter but at the moment all i understand is.. chinese mixed with japanese.. hehehe
Hey, please, can you add "how install dual boot" in this guide? I really need it, sorry my bad english
Sent from my FRG83 by Neopeek using XDA App
How big the ex2 partion must be? 300 ,500mb?
EDit: i have made the ext2 and the fat32 partition but i can only see the FAT32 in windows. Am I missing something?
viper. said:
How big the ex2 partion must be? 300 ,500mb?
EDit: i have made the ext2 and the fat32 partition but i can only see the FAT32 in windows. Am I missing something?
Click to expand...
Click to collapse
Nothing is wrong.
Actually, Windows can't read an ext2 partition, because it's a linux-based partition.
About the size.. i don't know, but i followed the tut' and put the same size. It works well.
Oggy972 said:
Nothing is wrong.
Actually, Windows can't read an ext2 partition, because it's a linux-based partition.
About the size.. i don't know, but i followed the tut' and put the same size. It works well.
Click to expand...
Click to collapse
Yep, i have realised that windows7 is unable to read that partition because i did install the android on it and everything went fine. My partition is 450mb large and its working normally. This is so much better then other xdandroid version beacuse with this build you can connect x1 and the pc via usb .
Added both questions to FAQ.
thank you so much for this!
can someone please give the proper instructions on how to use the andboot floder does the folder have to start with capital?
and the v3c kernel needs to be run using someother programs and methords which are there in that thread can you help me with them?
Is it necessary to leave some unallocated space on SD card as shown on video ? And what size of swap partition should be ?
I'm not sure why he left unallocated space, but it's not necessary.
For swap partition, I'm not even sure if android uses it. You can live without it.
hello
I need help
If i start the exe it boot.
But when it is finished it restarts and then there is windows .
Whats wrong ?
Have you done everything correctly? Delete everything and try again.
Also, what is your battery level?
I have successfully install Android with ext2 partition on my X1. But, when I boot to Android, it always hang.
Sometime it hang at the first boot (when Android ask me to configure Google account to sync), sometime it hang when I try to change Android setting, sometime it hang when I play music, but often it hang when I put Android on standby (I press the power button).
I use 4GB SD card and partitioned it into two partition, FAT32 2,5GB and ext2 450MB.
I have try two Android build : CyanogenMod 6.1 and X1-frg83-06112010. Both have the same problem. I also try replace the kernel (zImage) with sp3dev, but the problem still there.
The other thing I try was extract androidinstall.tar.gz directly to my ext2 partition, but Android still hang.
Do you ever encounter this problem? How to fix this?
Hello
Now i have android all is ok and does go.
But one problem if i press the ok and the other buttons does go.
But a little time later no buton does go anymore.
Whats the problem ?
Signing in...
Hi,
All went well.
Now 1st boot it tries to get to me google.
Nothing happens.
It tells me 5 minutes, but that was 10 minutes ago
I am on 3G
Any help?
Edit: (Will boot again, and let you know if it works.)
Edit: Rebooted, and skipped the google account login. Will try with WiFi on loging into google again.
?
Sorry, i don't understand you. What is bugging you?
Hello,
With the issues I was having with the CM 10.1 nightlies, much as I would like to stay, I decided to install the Minimoto 1.7 ROM into the second ROM slot (created with Safestrap 3.05). First, let me say "wow!" I never thought I would see this much speed and available RAM on my Droid 3. Thank you very much, thingonaspring.
For the most part, everything is working great *except* access to both the sdcard (internal) and sdcard-ext (external) storage areas. I read many posts in the Minimoto thread and searched around but nobody else appears to have encountered this which I find rather odd.
After the initial install and after reboots, these areas were still not accessible. I finally ran the terminal emulator and found that, for some unknown reason, they were *not* mounted. I *did* find the internal storage (/dev/block/emstorage) mounted at /ss but not at /mnt/sdcard. I became root using "su" and did the following:
# mount /dev/block/emstorage /mnt/sdcard
# mount /dev/block/mmcblk0p1 /mnt/sdcard-ext
Now I can access them along with all of the files I previously had there. The included file manager, when started, presents buttons for "Internal Storage" and "SD", but it still complains that internal storage is not mounted. It will allow me to access the SD card, though.
Under Settings->Storage Settings, everything under "Internal storage" and "SD card" says "unavailable" and both the mount and format buttons are grayed out. Yet, under the "Windows Media Sync" heading, I *can* choose between internal and SD *and* it even shows the correct available/total space values.
Why were these not mounted to begin with? Is mounting them manually an acceptable solution? If it is, where do I put this information so that it occurs at boot like it should (there is no /etc/fstab on Android)? Did I perhaps do something wrong when installing this ROM, maybe because I used ROM slot 2 instead of 1 (which still contains the most current CM 10.1 nightly)?
I really want to get this resolved because, so far, everything else appears to work wonderfully. Even 3g access, which I still haven't gotten working with CM 10.1.
--John Gruenenfelder
I've been running Minimoto for months and both /sdcard and /sdcard-ext are mounted at bootup for me, always, just like stock.
So, I wish I could tell you why, but I cannot.
I guess what I would do is start over. Reboot into Safestrap, remove that second slot and recreate it. Flash the ROM and restart the phone. Do not wipe data/factory reset after flashing the ROM or you will be missing some files (basically, some files required by the customized initial setup application.)
It seems to be fixed! See below for (perhaps) how...
Okay, I gave this a try. Rather than wiping ROM-slot-2, I had enough free space to create slot-3 and I reinstalled Minimoto 1.7 there. Also, this time I downloaded the zip file on my PC and transferred it over rather than downloading it directly onto the phone. Using the UNIX "cmp" tool told me the two files were identical, but I still used the "new" one. It installed fine and I did *not* perform a data wipe.
Unfortunately, same issue. When the device starts I can see the "Preparing XXX storage" messages appear in the notification bar for both internal and SD storage. There are no error messages, but it also did not actually do anything. Then, using the terminal emulator, I gave a long read through the dmesg output. I am more familiar with the kernel messages one sees when booting Linux on a PC, but I still did not see anything unusual.
So, back into Safestrap recovery. This time I tried something different. First, I noticed that the Safestrap file manager *can* see both storage areas and in the locations where they ought to be. This is not new, actually, it has always been the case. Second, I uplugged the USB cable. I have been using it for charging (of course), but at present it was plugged into my laptop and not into the wall charger. Depending on how the mounting occurrs and the exact mount order, I thought this might interfere. Thirrd, and finally, I used the "Fix Permissions" button available in Safestrap on ROM-slot-2 where I had first intalled Minimoto.
After doing these two changes I rebooted the device back into ROM-slot-2. Surprise! I once again saw the "Preparing" messages in the status bar except this time it really worked. The two storage locations are available where they should be and I an access the data just fine. Even the "Storage properties" screen in Settings shows both as mounted with the correct available/total space values given.
Since a plain reboot did not work previously, I have to assume one of the two changes I made fixed the problem, though, since I did both at the same time, I cannot be sure which fixed it.
Now I can get back to enjoying the impressivee speed from Minimoto while I wait to see if (or perhaps when) either the 3g or HW keyboard ALT-key issues are fixed in CM 10.1. Of course, given how much slower CM 10.1 operates (by virtue of using *much* more RAM than Minimoto), I think I might find it very difficult to switch.
--John Gruenenfelder
If you've been trying to hoot while plugged into your laptop I can see it causing issues as when usb mass storage is active, the device can no longer see the sd cards. That is why we have a separate data partition for apps and app data. So if the computer is trying to mount them and denies the phone the ability to mount then I could see issues arising
Sent from my XT860 using xda premium
Hi.
I'm using Asylum Omni 4.4.3. Yesterday I tried to copu a big file (1,2 Gb) from external SD card (sdcard1) to internal SD card (sdcard0) but at 800Mb the copy stopped. I restarted the phone and tryied with small data and found that, if the data is more than 100Mb, it's easy that the copy stops and the phone have to be reboooted because it remains stuck.
If I try to use the internal SD for backup using TWRP, I'm able to save 1,5Gb of data without problems.
Instead the copy from sdcard0 to sdcard1 is working flawlessly.
I know that in KitKat there were many SD card issues.
But is it possible that 2 different sdcard on the same device have different behaviour ?
Zzgfont said:
Hi.
I'm using Asylum Omni 4.4.3. Yesterday I tried to copu a big file (1,2 Gb) from external SD card (sdcard1) to internal SD card (sdcard0) but at 800Mb the copy stopped. I restarted the phone and tryied with small data and found that, if the data is more than 100Mb, it's easy that the copy stops and the phone have to be reboooted because it remains stuck.
If I try to use the internal SD for backup using TWRP, I'm able to save 1,5Gb of data without problems.
Instead the copy from sdcard0 to sdcard1 is working flawlessly.
I know that in KitKat there were many SD card issues.
But is it possible that 2 different sdcard on the same device have different behaviour ?
Click to expand...
Click to collapse
This does not suprise me. Blame this bug.
Azeazezar said:
This does not suprise me. Blame this bug.
Click to expand...
Click to collapse
Thanks a lot for the hint.
I read the thread.
The weird thing is that I hadn't the problem with SlimBean 4.4.
Then I started to use SlimSaber, and release after release the device had some weird lock, that disappeard using an 4.4 kernel from Chasmodo.
So I tried Asylum Omni.
The external card seems ok even is VFAT and full of music. I listen music everyday with N7Player without issue.
The problem is during writing the internal sdcard, that is an ext4. And happens only with file bigger. Reading is not a problem too, as I simetimes watch films that are in the internal sd card without problems.
Today I tried to move a 2 Gb file with "adb shell" while in recovery and it worked. Slowly, but worked.
I have to try some old release of SlimBean to verify if the problem disappear. I got all my old nandroid somewhere in my notebook.
Zzgfont said:
Thanks a lot for the hint.
I read the thread.
The weird thing is that I hadn't the problem with SlimBean 4.4.
Then I started to use SlimSaber, and release after release the device had some weird lock, that disappeard using an 4.4 kernel from Chasmodo.
So I tried Asylum Omni.
The external card seems ok even is VFAT and full of music. I listen music everyday with N7Player without issue.
The problem is during writing the internal sdcard, that is an ext4. And happens only with file bigger. Reading is not a problem too, as I simetimes watch films that are in the internal sd card without problems.
Today I tried to move a 2 Gb file with "adb shell" while in recovery and it worked. Slowly, but worked.
I have to try some old release of SlimBean to verify if the problem disappear. I got all my old nandroid somewhere in my notebook.
Click to expand...
Click to collapse
After switching to exfat for both internal and external(Or sometimes ext4, if i swap out). I never had a problem, and good speeds. That is my recommendation.
I would not spent to much time looking for another way to make it work, because what seems to work for some does not work for others. But exfat seems to fix it for everyone.
Azeazezar said:
After switching to exfat for both internal and external(Or sometimes ext4, if i swap out). I never had a problem, and good speeds. That is my recommendation.
I would not spent to much time looking for another way to make it work, because what seems to work for some does not work for others. But exfat seems to fix it for everyone.
Click to expand...
Click to collapse
Just to notify that SlimKat 4.4 seems not to have such problem. I'ts not fast as SlimSaber or Asylum Omni, but file transfert seems ok.
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!