Database Develop

[Q] Problem with rooted Nook and ROM Manager

Hi all,
I hope this is the right place to put this - I'm not sure if it's a Nook Color, Cyanogenmod, ROM Manager, or Clockworkmod issue. I just rooted my NC to CM7 using Clockworkmod and it seems to work fine. I tried installing the GoogleApps .zip file at the same time. It said it was successful, but I don't see any of the Google apps in the apps drawer.
So, I went to ROM Manager to try and fix this. When I first opened ROM Manager it said I needed an SD Card installed to use it (I had removed it after the successful flash). So I inserted the card and mounted it in Settings->Storage and tried again. Now when I click on anything it says "You must have ClockworkMod Recovery installed before continuing! Install the recovery through ROM Manager first."
If I click the Install button, the dialog closes and nothing happens. If I click the menu option "Flash ClockworkMod Recovery" the title of the screen (ROM Manager v4.2.0.0) flashes for a split second. That's it. Nothing is installed.
If I reboot while holding the upside-down U button I eventually get an "Update failed!" screen that looks like it comes from the standard Nook UI. If I try to reboot into recovery using the Power button it just reboots as normal.
I've found a large amount of resources online regarding the "unable to reboot into recovery" issue, but I feel like I don't know enough about what I'm actually doing to implement them. I also don't know how the inability to flash ClockworkMod fits into this. It's especially strange how selecting the option to flash it actually does nothing.
Anyone have ideas?
[EDIT]
Since I'm a new user and apparently can't post links, I followed the instructions on the Cyanogenmod site's wiki.

SkittlesAreYum said:
Hi all,
I hope this is the right place to put this - I'm not sure if it's a Nook Color, Cyanogenmod, ROM Manager, or Clockworkmod issue. I just rooted my NC to CM7 using Clockworkmod and it seems to work fine. I tried installing the GoogleApps .zip file at the same time. It said it was successful, but I don't see any of the Google apps in the apps drawer.
So, I went to ROM Manager to try and fix this. When I first opened ROM Manager it said I needed an SD Card installed to use it (I had removed it after the successful flash). So I inserted the card and mounted it in Settings->Storage and tried again. Now when I click on anything it says "You must have ClockworkMod Recovery installed before continuing! Install the recovery through ROM Manager first."
If I click the Install button, the dialog closes and nothing happens. If I click the menu option "Flash ClockworkMod Recovery" the title of the screen (ROM Manager v4.2.0.0) flashes for a split second. That's it. Nothing is installed.
If I reboot while holding the upside-down U button I eventually get an "Update failed!" screen that looks like it comes from the standard Nook UI. If I try to reboot into recovery using the Power button it just reboots as normal.
I've found a large amount of resources online regarding the "unable to reboot into recovery" issue, but I feel like I don't know enough about what I'm actually doing to implement them. I also don't know how the inability to flash ClockworkMod fits into this. It's especially strange how selecting the option to flash it actually does nothing.
Anyone have ideas?
[EDIT]
Since I'm a new user and apparently can't post links, I followed the instructions on the Cyanogenmod site's wiki.
Click to expand...
Click to collapse
Question, did you have clockworkmod installed on your sd when you flashed cm7 or was it installed internally? Can you boot into recovery with rom manager? If clockwork is on sd, find the newest clockwork zip and flash it with your card internally. That should allow you to update to the newest version in Rom Manager. Try reflashing gapps.

bdcrim said:
Question, did you have clockworkmod installed on your sd when you flashed cm7 or was it installed internally? Can you boot into recovery with rom manager? If clockwork is on sd, find the newest clockwork zip and flash it with your card internally. That should allow you to update to the newest version in Rom Manager. Try reflashing gapps.
Click to expand...
Click to collapse
Clockworkmod was installed on the SD card.
I cannot boot into recovery using ROM Manager. It just restarts the device as normal.
I believe I have the latest CWM because I grabbed it from their website yesterday (4.2.0.0). How do I flash it internally? That's what I was attempting to do with ROM Manager. I followed the steps listed in thread #922870 on this forum (still can't post links) and I believe that results in CWM on internal memory, but ROM Manager still behaves the same way.
I did reflash gapps twice, but there is still no Maps, Market, Gmail, etc.

I just noticed something else. When I mount my SD card on the NC it shows up as empty: /mnt/sdcard has no contents. Does this indicate an error with the SD card and/or partitions? I am using the 8 GB image of CWM on my 16 GB card (because there is no 16 GB version).

SkittlesAreYum said:
I just noticed something else. When I mount my SD card on the NC it shows up as empty: /mnt/sdcard has no contents. Does this indicate an error with the SD card and/or partitions? I am using the 8 GB image of CWM on my 16 GB card (because there is no 16 GB version).
Click to expand...
Click to collapse
Your SD card has clockwork burned as an image which the nook cannot read. You can format the card later for use (go to nookdevs website). I am attaching a zip file for clockworkmod 3.0.1.0 (credit goes to Mistar Muffin). Put that on your SD card, insert it into the nook and boot it up. It should take you into recovery. You can then flash the zip file and get Clockworkmod on your emmc. You should be able to update to the new version 3.0.2.8 from Rom Manager at that point. I think the nook is confused with the absence of Clockwork internally. As far as your rom goes, I would boot into recovery when the Clockworkmod issue is resolved and reflash the CM7 build, reboot, go back into recovery and flash the gapps. You can repeat the process with an overclocked kernel if you choose. This zip is a file that floated around the forum for awhile. It was removed when Clockworkmod got an update. I have used it on my nook. It should be safe. Good luck

bdcrim said:
Your SD card has clockwork burned as an image which the nook cannot read. You can format the card later for use (go to nookdevs website). I am attaching a zip file for clockworkmod 3.0.1.0 (credit goes to Mistar Muffin). Put that on your SD card, insert it into the nook and boot it up. It should take you into recovery. You can then flash the zip file and get Clockworkmod on your emmc. You should be able to update to the new version 3.0.2.8 from Rom Manager at that point. I think the nook is confused with the absence of Clockwork internally. As far as your rom goes, I would boot into recovery when the Clockworkmod issue is resolved and reflash the CM7 build, reboot, go back into recovery and flash the gapps. You can repeat the process with an overclocked kernel if you choose. This zip is a file that floated around the forum for awhile. It was removed when Clockworkmod got an update. I have used it on my nook. It should be safe. Good luck
Click to expand...
Click to collapse
Thanks for your help; unfortunately this did not work. Nothing has changed. I placed the zip file in my SD card that already has CWM imaged. I went to "Install zip from SD card" and installed the zip. It completely successfully. Then I rebooted and entered ROM Manager, which told me I needed the SD card back in. I mounted the SD card and am encountering the same issues as before.
What could I have possibly done to mess this up? I followed all the steps listed on the Cyanogenmod website and they never mention anything about flashing CWM internally. Another question - why do I need the SD card for ROM Manager if that app is downloading things from the internet?
Thanks!

SkittlesAreYum said:
Thanks for your help; unfortunately this did not work. Nothing has changed. I placed the zip file in my SD card that already has CWM imaged. I went to "Install zip from SD card" and installed the zip. It completely successfully. Then I rebooted and entered ROM Manager, which told me I needed the SD card back in. I mounted the SD card and am encountering the same issues as before.
What could I have possibly done to mess this up? I followed all the steps listed on the Cyanogenmod website and they never mention anything about flashing CWM internally. Another question - why do I need the SD card for ROM Manager if that app is downloading things from the internet?
Thanks!
Click to expand...
Click to collapse
Try uninstalling and reinstalling Rom Manager. Dont know if that will help or not.

bdcrim said:
Try uninstalling and reinstalling Rom Manager. Dont know if that will help or not.
Click to expand...
Click to collapse
How would I reinstall ROM manager? I don't have any sort of Market on the device.

Best best bet is going back to stock and trying from scratch

SkittlesAreYum said:
How would I reinstall ROM manager? I don't have any sort of Market on the device.
Click to expand...
Click to collapse
Sorry, my bad. I forget that Rom Manager is part of the CM7 package. You should not need the sd card for Rom Manager to work properly. I am not sure why it is calling for it. Can you reboot into recovery with the power+n method, not the SD card? If you can do that, it tells me clockwork installed correctly. If you can get there, I would do your formats (data, system) and reflash the rom. Another option, if Titanium Backup is part of the rom package try to wipe data in rom manager and give it another try. You may can do that in manage applications (I don't have my nook with me). The link below may or may not help. Look at option 3. The 3.0.1.0 zip it is calling for is the one I sent you prior. I am about out of options. Good luck.
http://forum.xda-developers.com/showpost.php?p=12674682&postcount=355

AHA! I solved it, and it wasn't directly an issue with anything except my stupidity. I was connecting to my company's guest wireless, which as it turns out requires a username/password before you get anything other than the login screen. That is why the ROM manager was failing to flash itself - it had a worthless wifi connection. When I switched to another wireless access point it works just fine.
Thanks for your assistance bdcrim! Sorry it wasn't a more satisfying conclusion.

SkittlesAreYum said:
AHA! I solved it, and it wasn't directly an issue with anything except my stupidity. I was connecting to my company's guest wireless, which as it turns out requires a username/password before you get anything other than the login screen. That is why the ROM manager was failing to flash itself - it had a worthless wifi connection. When I switched to another wireless access point it works just fine.
Thanks for your assistance bdcrim! Sorry it wasn't a more satisfying conclusion.
Click to expand...
Click to collapse
Thats okay, glad you got it going. Made me dig a bit, which probably helped both of us be a little more educated for future issues. Have a great day.

[SOLVED] Removing Root

So I have come to the decision that I am going to remove root from this phone. I think that no matter what I do, something always happens to the recovery partition, getting a little tired of having to put it back on as it also removes my memory card from use as well.
I am not sure where the problem lies that causes the memory card and the recovery partition to go missing, my first thought would have been the Xposed framework, but I ruled that out as I installed that, straight after the pre-rooted Rom. That would leave it at either the Xposed APK install, any xposed modules or another APK. I like messing around with the idea of a rooted phone, but with having to redo the recovery install, its annoying, I have done it for the 4th time in 2 days.
If anyone has any suggestions to why this is happening, I am happy to listen, as I don't want to go back to stock ROM, but find that its just to troublesome to keep root on.

demon148 said:
So I have come to the decision that I am going to remove root from this phone. I think that no matter what I do, something always happens to the recovery partition, getting a little tired of having to put it back on as it also removes my memory card from use as well.
I am not sure where the problem lies that causes the memory card and the recovery partition to go missing, my first thought would have been the Xposed framework, but I ruled that out as I installed that, straight after the pre-rooted Rom. That would leave it at either the Xposed APK install, any xposed modules or another APK. I like messing around with the idea of a rooted phone, but with having to redo the recovery install, its annoying, I have done it for the 4th time in 2 days.
If anyone has any suggestions to why this is happening, I am happy to listen, as I don't want to go back to stock ROM, but find that its just to troublesome to keep root on.
Click to expand...
Click to collapse
The easiest way I guess is to flash the FTF again and uncheck the Wipe Data option (to maintain you data).

I know how to remove it, just wondering if anyone has any idea why I keep having the problem.
Sent from my C6903 using XDA Free mobile app

Well, I've done some testing here and if I remove the SD Card I can't boot to recovery too. Maybe the SD Card is where something crucial to it lies. The fact that your SD Card keeps being removed is another question. Maybe a faulty unit? Did you try with another one? Or even maybe some water have reached the SD slot and there's rust there...?

Rhadamg said:
Well, I've done some testing here and if I remove the SD Card I can't boot to recovery too. Maybe the SD Card is where something crucial to it lies. The fact that your SD Card keeps being removed is another question. Maybe a faulty unit? Did you try with another one? Or even maybe some water have reached the SD slot and there's rust there...?
Click to expand...
Click to collapse
The first time I did the root for my handset I was using a 2GB San Disk SD card, it happened on that one too, that is one of the reasons I purchased a Class 10 Samsung SD Card. So therefore I am thinking that there is something that I am putting on whether it be Xposed or an APK, I am fairly certain that it has to do with one of those.

So I've worked out that it had to be either an apk or xposed or a module that's causing the recovery and sd card to go missing, as I put everything on first and then put the recovery back on and so far no problems and is been about 12 hours (touch wood)
Sent from my C6903 using XDA Free mobile app

SD Card 'Damaged' If I start phone whith it inserted. (chkdsk, format etc not helping

:crying: Yesterday I spent almost 24hrs battling problems while downgrading to kitkat and installing a pre-rooted zip of 5.1.1 lollipop.
Eventually, with the help of the good people here at xda, I got it done and working fine, or so I thought.
After installing the pre-rooted zip, everything seemed good but after waiting a while I restarted the phone, to make sure everything was OK before I started re-installing stuff.
I restart the phone and BAM "Damaged SD Card. SD Card is damaged, try re-formatting it".
So I let it Format - doesnt try to format it.
I Physically remove and re-insert the card, and THEN it lets me format it and it starts working. Then I restart the phone and BAM, same thing.
***After Lots of trial and error, I have narrowed it down to something which is happening at system startup.***
I know this because If I remove the card while the phone is off, then start up, then reinsert the card it works fine!
If I remove the card before the phone switches off, and insert it BEFORE I switch the phone on I get a 'damaged' sd card.
I have tried chkdsk, formatting, partitioning, formatting through windows(quick and normal format), nothing helps. IF MY CARD IS IN THE PHONE WHEN I START/RESTART THE PHONE, IT SAYS 'DAMAGED' - even though its not.
If I start the phone with it inserted it says'damaged'... but If I then remove the card, restart the phone and then re-insert IT WORKS FINE.
When It says 'damaged' I can remove and re-insert and it still says 'damaged' BUT If I remove, then reboot, then re-insert it works again.
IF I BOOT INTO SAFE MODE WITH THE CARD INSERTED I GET SAME ERROR/BEHAVIOUR
So something is happening on system startup which is causing this problem. Does anybody here know whats happening? After so many problems with the downgrade/root process, this is driving me crazy. And to top it all off, My XZ Dual recovery no longer works after that first reboot - WTF (I'm hoping a re-install will solve this but for now I need to fix the SD Problem )
Any help would be greatly appreciated, thanks for your time.
EDIT: KitKat install was clean, wiped everything. While on kitkat I installed 2 busybox installers, root checker basic and busybox itself. After flashing the pre-rooted 5.1.1 I DID NOT wipe cache/dalvik as I was afraid of losing root :embarassed: sureley this is not the problem?!? as booting into safe mode doesnt help!?

I think the two problems are probably not unrelated (SD card problems and XZDR not working). Obviously, XZDR runs on every boot and it does try to touch the external SD card. It could be breaking something.
What brand and model and size SD card? Android, and specific phones, can be very finicky. It's possible (but not likely) that 5.1.1 broke support for your SD card somehow.
Did you have to format it specially the very first time you used it with the phone? For example, I had to hack my 64GB SDXC card to be a bigger-than-actually-allowed FAT32 partition for the phone to play ball.
Can you reproduce any weirdness with the card in a PC? Maybe the card actually has a problem and you can RMA it.
What happens if you format the SD card after boot so that it works, then eject it, then reboot the phone without the card in, and insert the card after install? It should mount fine at that point if it really is something in the boot process. If it does work, without rebooting, reinstall XZDR and see how that goes.

xasbo said:
I think the two problems are probably not unrelated (SD card problems and XZDR not working). Obviously, XZDR runs on every boot and it does try to touch the external SD card. It could be breaking something.
What brand and model and size SD card? Android, and specific phones, can be very finicky. It's possible (but not likely) that 5.1.1 broke support for your SD card somehow.
Did you have to format it specially the very first time you used it with the phone? For example, I had to hack my 64GB SDXC card to be a bigger-than-actually-allowed FAT32 partition for the phone to play ball.
Can you reproduce any weirdness with the card in a PC? Maybe the card actually has a problem and you can RMA it.
What happens if you format the SD card after boot so that it works, then eject it, then reboot the phone without the card in, and insert the card after install? It should mount fine at that point if it really is something in the boot process. If it does work, without rebooting, reinstall XZDR and see how that goes.
Click to expand...
Click to collapse
First off... thanks again for the help.
Secondly, I just got a chance to re-install xzdr and....*drumroll please* ...IT WORKED
:highfive: :good: :good: :good:
I cant believe this whole process went so smoothly; usually I run into a few little problems
Anyways, I'm not sure what went wrong with XZDR... it installed and worked fine on kitkat and the pre-rooted 5.1.1 included XZDR flashable which also installed and worked fine but only on the first boot.
Regardless...recovery installed fine again and now my sd card mounts fine on startup. rebooted a dozen times, switched off and cold booted a few more times... no problems with SD Card on boot. well happy.
Thanks again for all the tips and advice mate, much appreciated.
As you suggested, I'll pay it forward as my knowledge improves/returns and if and when my money situation improves: I'll chuck a couple of beer tokens your way.
cheers fella

thesweeney80 said:
First off... thanks again for the help.
Secondly, I just got a chance to re-install xzdr and....*drumroll please* ...IT WORKED
:highfive: :good: :good: :good:
I cant believe this whole process went so smoothly; usually I run into a few little problems
Anyways, I'm not sure what went wrong with XZDR... it installed and worked fine on kitkat and the pre-rooted 5.1.1 included XZDR flashable which also installed and worked fine but only on the first boot.
Regardless...recovery installed fine again and now my sd card mounts fine on startup. rebooted a dozen times, switched off and cold booted a few more times... no problems with SD Card on boot. well happy.
Thanks again for all the tips and advice mate, much appreciated.
As you suggested, I'll pay it forward as my knowledge improves/returns and if and when my money situation improves: I'll chuck a couple of beer tokens your way.
cheers fella
Click to expand...
Click to collapse
:highfive: blame the blood moon, eh? glad it was so simple.

xasbo said:
:highfive: blame the blood moon, eh? glad it was so simple.
Click to expand...
Click to collapse
ha. didnt see that 'blood moon' thingy... too busy going nuts over a 'simple' problem.
Last night shall from this point forwad be known as... 'The night of a thousand formats'
:good:

Text editor apps crash when writing to the external sd card with root

I have a Moto E 2015 LTE (surnia) running the latest version of SuperSU (2.79) on CypherOS 3.6.1 (Nougat 7.1.1). I flashed SuperSU with TWRP, and there were not any errors. Root works fine for everything else I have tried. This problem started happening out of nowhere. There were not any updates to either SuperSU or the text editors when this started happening. I tried this with QuickEdit Pro and Turbo Editor. They both freeze the phone and make it reboot when I try to save to the external SD card with root. I have tried different SD cards, and both FAT and F2FS. The SuperSU logs are blank. I cannot take a logcat which has anything meaningful because it freezes before showing anything useful in the logs. After this happening twice, my phone went into a bootloop. I needed to reinstall everything. I did, and the problem still happens after the second time saving to the external sd.
Is this a known bug or does anyone have any ideas about the possible causes and fixes of this?
Thanks in advance.

Cannot Detect SD Card

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!