Hi,
since i cant post on the development thread, i'll try it here.
im using the official cm13 for the d855 and have the following problem:
Until yesterday i've flashed every nightly with TWRP. What i've changed is, that im using my external sd card (64gb Sandisk) as internal storage (for music and app data). Since i set my sd card up as internal memory, twrp does not recognize my /sdcard directory.
When using the built in flash method, the phone reboots into recovery, then the console flashes for about 1/2 second red and then im at the main menu of twrp.
If i remove the sd card, i can update cm as usual.
Is this problem known, or am i doing anything wrong?
Greetings from Germany
Related
Hi...
This is my first post here.
I have a problem with my SD Card.
My SDCard: 32GB microSDHC, some application like music player and gallery sometimes can't read file on my ext sd card (but my file manager can do it flawlessly)
Furthermore, sometimes it shows PREPARING SD CARD on top of the screen, although I don't even do anything. I tried to re-mount it again. But the problem still sometime occurs.
This problem started happening when I changed my stock rom to Ressurection Remix, I thought this problem occurred because of the ROM. so I change it to AOSP. But still... the problem still existed. So then, I changed it back to my stock ROM (with restore option in CWM)
But yeah... Nothing happen.
Any idea?
P.S.: Sorry for my bad english.
extSdCard/sdcard 1 issues
I have a Note II N1907 (ATT) running Liquid Smooth with a SanDisk microSD ultra 32gb. I have been trying to figure this issue out since I bought this phone 2 months ago. I screwed up the original card that I transferred from my old phone some how by trying different things to make the phone recognize it. It worked fine in my HTC Vivid. I have root and am able to use root options to try to access this card of installation, but the best I have been able to do is use it for storage. And I have to manually move things to the card, because most apps do not acknowledge that it is there (can't see it). TWRP recovery can see it after I did my first ROM Flash, but I have to use internal memory for my first ROM Flash, because recovery mode was unable to mount extSdCard.
Is there a kernel I can flash to remedy this. I am no developer, but I think the problem is that the internal memory is also SD in type. I have noticed that internal memory shows up as SDcard0 (zero) and the after market sd card is sdcard1. Maybe the phone automatically defaults to the first sdcard and ignores the other (because it is only designed to have one sd card).
I am sure others have hard this problem with this phone. Thank you for any help you can offer..
floykoe said:
I have a Note II N1907 (ATT) running Liquid Smooth with a SanDisk microSD ultra 32gb. I have been trying to figure this issue out since I bought this phone 2 months ago. I screwed up the original card that I transferred from my old phone some how by trying different things to make the phone recognize it. It worked fine in my HTC Vivid. I have root and am able to use root options to try to access this card of installation, but the best I have been able to do is use it for storage. And I have to manually move things to the card, because most apps do not acknowledge that it is there (can't see it). TWRP recovery can see it after I did my first ROM Flash, but I have to use internal memory for my first ROM Flash, because recovery mode was unable to mount extSdCard.
Is there a kernel I can flash to remedy this. I am no developer, but I think the problem is that the internal memory is also SD in type. I have noticed that internal memory shows up as SDcard0 (zero) and the after market sd card is sdcard1. Maybe the phone automatically defaults to the first sdcard and ignores the other (because it is only designed to have one sd card).
I am sure others have hard this problem with this phone. Thank you for any help you can offer..
Click to expand...
Click to collapse
As soon as I saw your reply I scanned for the words "Sandisk Ultra" and then I knew this was your issue.
I had a lot of SD card corruption with this brand and searching a lot on the web I found many stories of people having the same issues as I did.
My 32Gb Sandisk Ultra was the cause of many of my problems. 2 months on with a Lexar 32Gb, no problems (touch wood)
Modded my first phone, no I am quite inexperienced:
I installed Cyanogenmod successfully. Unfortunately the camera terminates right after I start it. My guess is, it has something to do with the SD-card. A different Camera app from the PlayStore shows an image at least but prompts me to insert an external storage (sd card) before it can take a picture.
Actually there is a new sd-card with 16 GB inserted. I can access and browse it in the file manager and in Settings -> Storage the sd-cards size is recognized an I can mount/unmount and erase it.
Changing from Android 4.1.2 I did this way:
rootet like this, installed this custom recovery and then installed Cyanogenmod by Macclaw following this tutorial + GAppsMicro.
Due to my problems I wiped everything again and installed Cyanogenmod 11 by TeamCanjica. But same problems there.
Hello,
I have exactly the same issue.
I went to newest version of [ROM][4.4.4][TeamCanjica] CyanogenMod 11.0 (cm-11-20140807-UNOFFICIAL-codina.zip) + Micro package of GAPPs due to free Space on internal storage.
However after installation of the new system I realized the issue with Camera / Gallery what seems to be caused by a not correctly recognized external SD card: Error message: "No external storage available"
I red some Threads about this issue and have already tried following without any success:
Permission fix at platform.xml http://forum.xda-developers.com/showthread.php?t=2743840
IntSD-MountFix from AIO-Toolkit http://forum.xda-developers.com/showthread.php?t=2338577
Format SD card with boardtools of CM11 system
Format SD card at PC with FAT32
Does anybody have a different idea to fix this issue?
Any idea is more than welcome.
Thanks in advance,
Bastian
Now I tried CyanogenMod 10.2 by TeamCanjica. Camera asked for sdcard again... although inserted. But some moments later it suddenly worked... :/
Nekrok said:
Now I tried CyanogenMod 10.2 by TeamCanjica. Camera asked for sdcard again... although inserted. But some moments later it suddenly worked... :/
Click to expand...
Click to collapse
For me it works also with 10.2. Thanks.
Hello,
I just upgraded my gpe g pad to lollipop and am having SD card problems. My 64gb card worked perfectly with kk with the SD fix. In lollipop under settings, my card is listed correctly but when using solid Explorer or root explorer, the card is not listed when the doc viewer is displayed to give the program permission. I tried with an old 16mb card and that is listed. Was hoping lollipop fixed SD issues but doesn't seem like it. Does anyone have a solution or the same problem? I tried it with two 64gb cards both formatted exfat.
dcpyro1394 said:
Hello,
I just upgraded my gpe g pad to lollipop and am having SD card problems. My 64gb card worked perfectly with kk with the SD fix. In lollipop under settings, my card is listed correctly but when using solid Explorer or root explorer, the card is not listed when the doc viewer is displayed to give the program permission. I tried with an old 16mb card and that is listed. Was hoping lollipop fixed SD issues but doesn't seem like it. Does anyone have a solution or the same problem? I tried it with two 64gb cards both formatted exfat.
Click to expand...
Click to collapse
Try fat32, and the permissions trick.
sleekmason said:
Try fat32, and the permissions trick.
Click to expand...
Click to collapse
Thanks. It works with fat32. Shame exfat isn't supported on larger sized cards
Actually, I think the problem is because you upgraded the bootloader. Once you update the bootloader, the sdcard needs to be reformatted. Exfat might even actually still work too if the sdcard just reformatted again. I haven't tried to reformat using exfat after updating the bootloader.
Deltadroid said:
Actually, I think the problem is because you upgraded the bootloader. Once you update the bootloader, the sdcard needs to be reformatted. Exfat might even actually still work too if the sdcard just reformatted again. I haven't tried to reformat using exfat after updating the bootloader.
Click to expand...
Click to collapse
Why would you need to reformat with a different boot loader?
Anyway, I had no problems switching back and forth from KitKat to lollipop using fat32. Exfat is poorly supported. Like ntfs, there are constraints that make it more of an issue than its worth.
Why ext2 isn't supported out of the box is beyond me.
I think the bootloader affects how the files are written to the partitions, including the sdcard. If you think about when everyone said the problems started, it was when 4.4.2 was released.
I tried an experiment. I had cm11 with 20B bootloader installed. It was fine for a week. I then only updated my bootloader to 20D and within a day it started to randomly reboot.
I then kept the 20D firmware and reinstalled cm11 and reformatted my sdcard. After that, the device was fine again. But, the problem with rebooting still happened even after reinstalling cm11 until I reformatted the sdcard while using the new bootloader.
When we update the bootloader, we directly reboot into the recovery to reinstall the operating system. This formats everything except the sdcard. This is why the problems are happening with the sdcard, because it's the only thing not being formatted over.
Deltadroid said:
I think the bootloader affects how the files are written to the partitions, including the sdcard. If you think about when everyone said the problems started, it was when 4.4.2 was released.
I tried an experiment. I had cm11 with 20B bootloader installed. It was fine for a week. I then only updated my bootloader to 20D and within a day it started to randomly reboot.
I then kept the 20D firmware and reinstalled cm11 and reformatted my sdcard. After that, the device was fine again. But, the problem with rebooting still happened even after reinstalling cm11 until I reformatted the sdcard while using the new bootloader.
When we update the bootloader, we directly reboot into the recovery to reinstall the operating system. This formats everything except the sdcard. This is why the problems are happening with the sdcard, because it's the only thing not being formatted over.
Click to expand...
Click to collapse
Wild. You wouldn't think it would matter. You could test this by taking out the sdcard before upgrading if it is a read problem with the card. I'm more inclined to think it's a problem with the initial read by cyanogenmod on a card with used space. Does this happen on stock as well?
The OP has the 510 by the way. But this is very interesting.
Yes, this happens with all ROMs AFAIK. The ROM and kernel made no difference.
Edit: even updating the ROM to lollipop from KitKat did not fix the crashing. Only after reformatting the sdcard and copying the data back onto the sdcard stopped the crashing.
Deltadroid said:
Yes, this happens with all ROMs AFAIK. The ROM and kernel made no difference.
Edit: even updating the ROM to lollipop from KitKat did not fix the crashing. Only after reformatting the sdcard and copying the data back onto the sdcard stopped the crashing.
Click to expand...
Click to collapse
Does it happen when formatted fat32?
I could see only a few reasons that are even possible. One being that when you replace the boot loader it wipes the internal sdcard, and the ext sdcard but because our ext sdcard is separate from the device, and not just a separate partition, it can't remove the files and marks it as defective.
If you mount it manually using a terminal does it work?
Mount /storage/sdcard1 (as root)
And third, that it is a glitch in exfat, where something isn't getting passed correctly.
Sounds more like a bug than a security feature, but could also be that to keep something malicious from running.
Yes, the problem still happens when the sdcard is formatted as fat32. Simply changing the bootloader will still trigger the problem.
For testing purposes, I made separate installers for 20B and 20D bootloaders that don't touch any other partitions. After I install a new bootloader, I reboot into the recovery again to load the new firmware and then install my ROM (which formats the system partition during normal upgrade procedure).
I know this should be directed to the twrp forums but I wanted to get feedback from owners of the sprint lg g3 preferably using the CM12.1 android version 5.1.
I have always had this issue where I am unable to flash roms on my external sd card via twrp. Everytime I try (just tried again tonight), after over and hour of restoring, it was only at 10%. When I flash the same rom on the internal sd (memory) it only takes about 10 minutes to accomplish the entire restore, its the same way for backups too. I don't understand why I am unable to do backups and restores from my external sd. It is very inconvienant to keep moving the backups from external to internal and vice versa. Plus, I can never put more than 1 backup on my internal because they take up so much space (roughly 8gb). It doesn't matter what backup rom I flash it does the same thing. Has anyone else been able to flash roms from their external sd card and if so, what did you have to do to get it to work? I have sent my concerns to the twrp team with no replies back. I am just curious if others are having the same problem or if their has been a fix for this.
I am currently on version 2.8.5 of twrp.
Does anyone have any suggestions or feedback on this issue? Thanks
Hey mate,
You could try installing the TWRP version for the G3 from their app, rather than just the generic version for any phone. If that doesn't work, then it sounds like your SD Card could be corrupted. I backup my whole phone to my external SD Card before I flash any updates or anything else, and can install the ROM updates from my SD Card with no problems whatsoever.
All I can really think of is either a new SD Card, or the official TWRP for the G3 from their app.
iDefalt said:
Hey mate,
You could try installing the TWRP version for the G3 from their app, rather than just the generic version for any phone. If that doesn't work, then it sounds like your SD Card could be corrupted. I backup my whole phone to my external SD Card before I flash any updates or anything else, and can install the ROM updates from my SD Card with no problems whatsoever.
All I can really think of is either a new SD Card, or the official TWRP for the G3 from their app.
Click to expand...
Click to collapse
Thanks for the response. Do you have a G3 also? I have installed the official bumped version of twrp for my sprint phone and am still having issues. Just by curiousity, when you are in twrp, are you able to backup and restore directly to/from the sd card. I do not have any issues with my card other than this, I can transfer and move files, etc. I have noticed though on my 64 gb scandisk card that when it first boots up, it will say not able to retrieve location. I put a different card in the phone and that message stopped which makes me believe it has something to do with the card. That location message just started about a month or two ago.
iDefalt said:
Hey mate,
You could try installing the TWRP version for the G3 from their app, rather than just the generic version for any phone. If that doesn't work, then it sounds like your SD Card could be corrupted. I backup my whole phone to my external SD Card before I flash any updates or anything else, and can install the ROM updates from my SD Card with no problems whatsoever.
All I can really think of is either a new SD Card, or the official TWRP for the G3 from their app.
Click to expand...
Click to collapse
It turns out that it was something to do with the external SD card. I replaced it with a brand new card and i am able to backup and restore to/from the external card with twrp.
jreink01 said:
It turns out that it was something to do with the external SD card. I replaced it with a brand new card and i am able to backup and restore to/from the external card with twrp.
Click to expand...
Click to collapse
Nice, good to see it got worked out!
I just flashed the latest CM nightly for MM and when I put my SD card in the phone it says its corrupt. I do the reset with the phone to wipe it and after its done I only have 15MB instead of 64GB. Is there a manual fix for this or is it something I just have to wait for CM to do? I have the G3 D852 with latest TWRP.
OptimusOBrien said:
I just flashed the latest CM nightly for MM and when I put my SD card in the phone it says its corrupt. I do the reset with the phone to wipe it and after its done I only have 15MB instead of 64GB. Is there a manual fix for this or is it something I just have to wait for CM to do? I have the G3 D852 with latest TWRP.
Click to expand...
Click to collapse
It looks like you're going to have to wait for a long while to see exFAT get fixed, and yes, I am in the same boat as you are so I literally feel your pain, but that said, when the OS asks me to format the Samsung 64GB EVO microSD card, it gets formatted to FAT32, which is absolutely useless for large files that are more than 4GB, and I have a LOT of FAT32-UNFRIENDLY files that I need on my microSD card, so Android Marshmallow is officially off the cards for me until that problem is fixed.
I have the same problem.
When I format to swapable sd card, I end up in 16MB.
When I format it to internal storage, the formatting stucks at 20% and after a few minutes I get a toast message with "java.util.concurrent.timeoutexception blah blah" and I have to reformat the card on my computer.
Looks like moving on from 5.1 to 6 was one of my biggest mistakes since I have a smartphone.
//Edit
I see there is already a thread about this. Cheers!
http://forum.xda-developers.com/lg-g3/help/android-m-sd-card-formation-stuck-20-t3259186
Exact same boat as everyone here. 64gb card shows as 15mb. If I format it as internal storage, I get the timeout exception. Didn't even realize I was upgrading to cm13 when I hit the update through OTA. It's came in the same list as cm12.1 nightlies. Of course since I didn't realize I booted it up without flashing gapps for 6.0 and was stuck the entire day trying to wipe clean, flash and restore backups from titanium. Android wear doesn't function properly, BT pairings get deleted on every reboot, SD card is screwed, the list goes on. Such a silly way to include it through OTA update without any warning.
Good news folks!
For those users who have flashed finnq's CM13 nightlies (20151219 onwards), you can now use exFAT-formatted microSD cards - all you need to do is flash the Nebula Kernel:
http://forum.xda-developers.com/lg-g3/development/kernel-nebulakernel-rev6-5-build20150715-t3161768
All this because I wanted to free up space to install Grim Fandango...
I backed up my Samsung 64 gb card on my laptop and then reformatted my card as internal so I could use AppMgr III to move apps over. Now, I'm stuck with my SD card saying "checking...", and it doesn't recognize the card on my laptop.
Any ideas?
Fixes coming....
There are proposed changes currently sitting in code review at CyanogenMod. The changes have not yet been approved or merged. Here is a ROM image for LG G3 d850 that includes the proposed changes to fix the exFAT problem as well as the GPS problem. They work for me. YMMV. Use at your own risk!
cm-13.0-20160101-UNOFFICIAL-d850.zip