Hi folks,
use the omnirom 4.4.4 on my A700.
Somehow it happens quite often, that the Os format's unwantedly my external SD-Card.
format/data / Media and reinstalling everything didn't help.
Any more tipps how to solve this problem ?
Really like the omnirom, wouldn't wanna change to another one.
Thanks
Related
Hi guys
I recently installed the latest omnirom (v4.4 / Kitkat), which can be found in the post below.
http://forum.xda-developers.com/showthread.php?t=2488986
After following all instructions and what seemed to be a successful installation, my phone seem to be unable to access it's internal storage. This leads to the camera, galary and other aps not working.
Note that I have tried the following:
1. Reformatted internal storage using gparted. I reformated it to fat32.
2. Installed supersu and tried using different aps to fix internal storage. I did not find any aps that actually helped.
3. Tried SlimKat rom instead of Omnirom. Same issue still prevails.
Can anyone give me some information on solving this problem?
Thanks
TJ
Recently, I flashed the CM11 ROM. After that, I couldn't access the Internal storage (sdcard0) from Inbuilt file manager or from ES File Explorer.
I was running CM10.1 Alpha 9 before this. I flahsed DDLF2, then CF-ROOT and then went to recovery, used wipe data/factory reset and wipe dalvik cache. Then, I flashed CM11.
Did I make a mistake while flashing?
I can still install apps and access both sdcard0 and sdcard1 from the recovery.
How can I access sdcard0 from the ROM? If I can't access it, the Camera, the Gallery and Bluetooth receiving don't work.....
Will re-flashing solve the problem?
Any help would be appreciated.
Ok. So since I'm not a Samsung expert forgive if I make a few mistakes lol. But assuming this is the CM11 you got right?
http://forum.xda-developers.com/showthread.php?t=2534312
drtweak said:
Ok. So since I'm not a Samsung expert forgive if I make a few mistakes lol. But assuming this is the CM11 you got right?
http://forum.xda-developers.com/showthread.php?t=2534312
Click to expand...
Click to collapse
This is weird......
An update was released just a day ago. I will download it, flash it and then see if the problem still persists.
Anyway, I am on this ROM, even though I am not on the latest build.
It seems there was a problem with the SD Card. Recently, it became unmountable. When I removed it, the storage was suddenly fine. No problems at all. Hence, I have found out that the problem was a faulty SD card.
Hi guys...
I'm getting mad about this... Tried everything... I'm getting random issues while copying/moving large amount of files from/to external 64GB SD Card with EVERY file manager I tried . The error is ENOMEM. I used CM11 with Grimlock compatibility pack kernel, OmniRom with original kernel, with or without GApps installed.
An hint seems to be that even the media scanner service has problem during the boot as I can see into the logcat. It gets stat() errors on a lot of media files. :crying::crying::crying: Another strange issue is that I get those out of memory errors in the terminal emulator If I run the followinf commands
su
find / -name something
/storage/sdcard1/folder/file1.jpg: Out of memory
/storage/sdcard1/folder/file2.jpg: Out of memory
/storage/sdcard1/folder/file3.jpg: Out of memory
/storage/sdcard1/folder/file4.jpg: Out of memory
......
The SD has no problems because it works well on PC.
And the BAD thing is that I tried to put it on an Asus HD7 ME173X with Android 4.2.1 and it works flawlessly without any error. But the WORST thing is that I got the same errors on my I9000 with CM 10.2.1 stable release.
Perhaps Android > 4.3.x is the problem?
Because both omni and CM11 are based on the same sources, something maybe is corrupted in both?
Please help!
Update ....
After a flashaholic hour I reverted back to CROMi-X 5.4 with GRIMLOCK 0.8 OC Kernel.
Surprise... IT WORKS....:laugh::good::highfive:
Really strange.... As CROMIi-x is based on 4.2.1 my supposition about Android version could be true...
Well Well Well.... I was getting mad about that, but...
At last I found the real issue....:victory::victory:
My external SD is formatted as exFAT FS and seems to be a it cannot be read correctly by CM11 ROMS.:silly:
Hints of this problem could be find just googling for 'CM11' and 'exFAT'.
I have the same issue on my Samsung Galaxy S3 with CM11 and a 64 GB exFAT SD-Card. You may format it with FAT32 and no problems occur but then you will not be able to store files larger than 4 GB anymore. If you often take HD videos this is inacceptable.
Hey guys,
I've tried so many things now, but somehow the internal sdcard is not working on Xperia L with CM11.
Problem:
After clean flashing, when I open the camera app is crashes instantly. Other camera apps say they need an external storage. The gallery says "no external storage"
In the file browser I see a lost+found folder but can't open it or do anything (write/read) even with root access .
I tried pac_taoshan-nightly-20141214, and FXP-cm-11-20150301-UNOFFICIAL-taoshan. (all KitKat based)
I'm using TWRP 2.8.7.0.
Before, I was using the latest official cm12.1 nightly for xperia l. Lollipop was getting a bit heavy my phone so I decided to switch back. When on cm12.1 I had formatted the cache and data partitions to f2fs, sdcard0 was ext4. There no major issues.
Before flashing to Kitkat I wiped everything and formatted everything to ext4.
-----------------------------------------------------------------------------------------
My external sd card is working fine.
After all this i flashed the original xperial L firmware 4.2.2, and on it everything worked fine. the camera worked, the pictures saved and opened in the album app.
Re-rooting and flashing kitkat brought the problem back.
-------------------------------------------------------------------------------------------
Any help would be appreciated.
A solution would be better.
hello,
My phone (HTC Desire S S510e) is frozen on boot screen, after trying to install a new ROM. For some reasons, my backup made with TWRP cannot be restored.
After different tries for resintalling/restoring, my status is the following:
- no OS installed / no OS booting : phone stuck at boot on HTC logo
- phone is S ON, HBOOT Unlocked, v2.00.0002
- TWRP 2.6.3.0 installed
- external sd card wiped many times using TWRP (I went many times between TWRP 2.6.3.0 <=> 2.6.3.1 trying, wiping options not being exactly the same).
I am now trying to get back to a working OS using CM 12.1 (from http://forum.xda-developers.com/htc-desire-s/development/rom-cyanogenmod-12-1-nightlies-t3071051). I have put the the zip file on the external microSD card (ext4, no journal, formatted from a linux box).
Installing the ROM zip from TWRP, I get the the following failure messages:
e:Unable to mound '/sdcard'
e:Unable to recreate and-sec folder
[...]
could not detect filesystem for /dev/block/platform/msm_[...]
[...]
Screenshot : https://dl.dropboxusercontent.com/u/102556377/20161105_155908.jpg
Is there a problem with my external microSD card ? any other suggestions ?
thanks
Tom
Maybe you haven't setup SagaOpt. I had similar problems on my Desire S "SAGA" when I flashed TWRP for SagaOpt.
I flashed TWRP for SAGA and now TWRP seems to be behaving itself.
lingowistico said:
Maybe you haven't setup SagaOpt. I had similar problems on my Desire S "SAGA" when I flashed TWRP for SagaOpt.
I flashed TWRP for SAGA and now TWRP seems to be behaving itself.
Click to expand...
Click to collapse
hi and thanks for answering,
from your post, my understanding is : there are two separate versions of TWRP , one is for "saga", one for "sagaopt" (I didn't know that, and will try both).
Since my initial post, I had the phone work "a little better": I managed to have a CM13 booting on the phone. I think the way I managed to install without the previous error messages was by formatting my external sdcard using fat32. I don't understand why it made things go better.
Now I'm stuck on "Encryption unsuccessful" message (like in this post: http://forum.xda-developers.com/showthread.php?t=1447303).
By reading a few others posts, seems like the problem is related to internal memory card and/or external microSD card partition type. Still very unclear to me about what to do next. Any suggestion welcome !
thanks
Tom
thomasveymont said:
hi and thanks for answering,
from your post, my understanding is : there are two separate versions of TWRP , one is for "saga", one for "sagaopt" (I didn't know that, and will try both).
Since my initial post, I had the phone work "a little better": I managed to have a CM13 booting on the phone. I think the way I managed to install without the previous error messages was by formatting my external sdcard using fat32. I don't understand why it made things go better.
Now I'm stuck on "Encryption unsuccessful" message (like in this post: http://forum.xda-developers.com/showthread.php?t=1447303).
By reading a few others posts, seems like the problem is related to internal memory card and/or external microSD card partition type. Still very unclear to me about what to do next. Any suggestion welcome !
thanks
Tom
Click to expand...
Click to collapse
Here's a short explanation that I got about Saga and SagaOpt.
Here's the latest TWRP for Saga 2.8.7.0 and here's TWRP for SagaOpt 2.8.7.1.
That's all I know at the moment, I'm new to HTC.
Mmm... this /data versus /system path may be relevant. in solving my problem.
I will dig more into this and come back with news in this thread.
thanks again
Just to let you now the problem is now solved :
- using TWRP 2.8.7.1 for "sagaopt" + CM 12.1 for "sagaopt".
- by changing my external microSD card. The first one got sort of corrupted (though working fine under Windows with fat32, maybe it's only a partitionning issue / partition table issue more than a real physical corruption)
- by launching wipe => format all in TWRP before installing CM
thanks for helping
Tom
thomasveymont said:
Just to let you now the problem is now solved :
- using TWRP 2.8.7.1 for "sagaopt" + CM 12.1 for "sagaopt".
- by changing my external microSD card. The first one got sort of corrupted (though working fine under Windows with fat32, maybe it's only a partitionning issue / partition table issue more than a real physical corruption)
- by launching wipe => format all in TWRP before installing CM
thanks for helping
Tom
Click to expand...
Click to collapse
Sure, you're welcome.
So, how's CM13 working for you? I tried CM12.1 and it was barely usable due to the slowness (not trying to offend devs, just making an observation).