[Q] Android can't find internal storage, TWRP can find it!

[Q] Android can't find internal storage, TWRP can find it! - Nexus 4 Q&A, Help & Troubleshooting

Hi all,
I have the weirdest problem. Ever since changing to another kernel, Android can't seem to access the internal storage (where all my files are stored) of my Nexus 4 (which is kind of a fake sdcard). The root system, with all the android files seems to be fine.
So, you might think, that's not that big of a deal. Just flash a new rom and all will be fine.
But the weirdest part is; TWRP actually has no problem loading up the internal storage. If I boot up TWRP everything is simply there, I can even acess the files from my PC.
But as soon as I boot up Android, it's gone.
So now I simply refuse to flash a clean rom, because I know for a fact all my files are still there and I don't see why Android can't mount, see or smell (or whatever it does) the internal "fake" sdcard.
What could possibly be going on here? I already tried multiple kernels, to no avail. I also tried to repair permissions from within TWRP, which led to no errors or anomalities whatsoever.
Thank you in advance,
Niels

Related

[HOWTO] WORKAROUND for BELL i9000m Internal SD Card Failure!!!!!

Hello Everyone,
I like most people upgraded my Bell i9000m from Kies to Froyo, only to have it bricked with the "can't mount /dev/block/mmcblk0" error at the recovery screen during boot-up. I upgraded it last week, where it took the firmware from JL8 to I believe JK3 or JL8 (not sure at this point).
Unfortunately I bought my phone from some guy on Kijiji using it on Rogers, so I doubt Bell is going to handle the return or give me any love
Anyways, I spent many days long days trying to get it back working, and I found a work-around that requires using an external SD card. and going back to Android 2.1 ECLAIR
Steps (This is what I did):
1. Install JK3 stock ROM via Odin (with re-partition at the pit on samfirmware.com, didn't update boot loader)
2. Install K13c speedmod kernel via Odin
3. Insert 16GB External SD card
3. Boot phone to Froyo
4. Reboot to recovery console and wipe data/everything
5. Install JL8 stock ROM via Odin (no re-partition, didn't update boot loader)
6. Phone will boot-up into recovery mode and automatically do wipe data
7. Phone will boot into ECLAIR
8. You will see internal storage of 1.85GB free.
9. Install Market apps - I installed twitter
10. If you remove external SD card, twitter will crash.
11. If you reboot phone without external SD card, you will get rebooting logo
12. If you put external SD card back it, phone boots!
This wasn't a fluke - I was able to reproduce if I flashed other ROMS (XXJPY or similar) instead of JK3.
Background:
Even though the phone can't boot with stock ROM, if I install JK3 ROM + speedmod K13b speedmod kernel, I can get the phone to boot to Froyo, but there is no internal storage (it shows up as 0 bytes available). So you can't install Market apps, and therefore is useless. I can't even mount the external SD card under the Settings app!
So I tried to log in the Froyo device using adb shell, and what I found is that internal SD card is no longer showing up under linux, and the OS thinks that the external SD card is the internal one. This is probably why the external SD card can no longer be mounted.
I figured out that the external SD card shows up as /dev/block/mmcblk0!!! WHich is the same block device as the internal SD card...so I'm thinking if I reboot into recovery and format SD card, how come it's not working? I even tried to partition the external SD card with android partitions, but still nothing!
I think Froyo is 'smarter' in that it knows the external SD card is not internal (whether it's grepping the device-info for manufacture data, don't know).
But if I go to JL8 Eclair, the Android 2.1 is 'dumb' enough that is doesn't see the difference between internal and external, so formats the external to look like internal.
Once I boot to ECLAIR, the external SD card is greyed out under Settings app, but I get 1.85GB internal storage!! OK I can't access the whole 16GB of the card, but at least my phone is not toast.
I can go ahead an install apps, which will install to the external SD card. But if you remove the external SD card, the phone will no longer boot. If I remove the card and apps are running, apps will crash (case in point: I tried twitter).
It will be nice if others can re-produce my findings. But for now my Samsung Galaxy S has been saved!
Kashif Shaikh

this sounds promising, can some more people confirm this solution to use External SD to imitate internal SD?

It worked for me as well! I have i9000M version, with internal SD failure. I'm also using 8GB external microSD card. I tried several 2.2 Android firmwares - specifically I9000XXJPY, I9000XXJPU. With update to speedmod-kernel I'm able to load device, but it doesn't see neither internal nor external SD card. So I couldn't install any applications, upload data or even shot with camera.
Based on this thread, on top of XXJPY with speedmod kernel I uploaded I9000XWJM8 firmware (Android 2.1) with Odin 1.7, no repartitioning. It worked right away - device loaded and I can see ~2GB of program storage (assume they storage is located on my external card). Both internal and external cards are shown as "Not available" in settings. I can install applications now, which made "brick" a bit better then it was before. Unfortunately, I still can't upload any data, i.e. a book for FB2Reader. And can't make a photo with my camera. And it's now Android 2.1, which looks slower.
First of all - thanks for the advice! It would be good to have this topic "sticked" and distributed - there might be other guys with no chance to repair phone under warranty.
Secondly - if someone can do a "hack" for Android 2.2 firmware so it can use external SD card for program storage specifically for I9000M device? And it would be terrific, if the remaining part of SD card (or at least some fixed size, like 4 GB) can be mounted as storage, so the data like music or photo or books can be uploaded.

I'm able to connect to the phone using adb tool, but I can't find a folder on the device where I can upload (push) a file to. I'd like to upload a book to the device so I can finally use it as a reader. I tried all "root" folders (adb shell -> ls) and all don't work. It says "No such file or directory" or "Permission denied".
Is there a folder on the device which I can push file to using adb tool? Maybe somewhere where applications are installed to, i.e. Program Storage location. Please help!

Anyone else following this thread with I9000M with internal card dead?

This isn't much of a fix. This will only work with phones with slightly corrupted (and not fully corrupt) sdcards; eventually your phone will probably stop booting with this "fix" as well. You're going to eventually loose some of the other partitions such as stl10 to corruption, and then you're screwed.
The OP's phone is corrupt in a specific way that allows this - and there are various procedures that will get your phone to a semi-bootable state if you only have a partially dead sdcard. Like the OP said - just installing speedmod kernel with an external SD in will allow your phone to boot, for example (I got my dead sd i9000m to boot froyo with the speedmod kernel, and others had reported the same as well). Then if you're technical enough you can switch around your mount configs and get it to work without the internal mmc device.
It doesn't matter if you bought your phone off kijiji or craigslist 2nd hand; send it back to samsung (or go thru futuretel or a similar provider). No receipt is going to be required (if they ask... just say you can't find it). Products like this will always be repaired under warranty based on manufacture date code.
Send your phone back; don't try to fix it - it's a hardware problem with the mmc connection.

Unfortunately, I'm 10 thousand miles away from Canada with no chance getting there. If I had option to send it back for repair I would do it right away. So I'm searhing an option to use this semi-brick as much as possible.
My i9000M phone has totally corrupted internal SD card - it failed two months ago and I tried all options for it reformatting / remounting / whatever. With speedmod kernel it loads even without external sd card. It just allows loading without internal storage - not use external card to mimic internal. Unfortunately, it doesn't see any storage then - no internal, no program, no external card. So it just loads.
With Android 2.1 and external card it loads _and_ see 2GB of program storage (on external card). It doesn't see any other storage - so I can't upload any file. But at least I can install applications.

I'll try this solution after buy a Microsd card. My i9000M internal sdcard dead in two days ago after fixlag use ext2 partitions.

hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.

SHINE.YANG said:
hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.
Click to expand...
Click to collapse
Samsung or bell can help you. Send your phone in for repair....

for same reason .i cannot send my phone to bell. so i very want to know find JL8 rom to let me phone canbe use . please help.

HI guys . thanks for your help.
actually ,every I9000 2.1 rom CAN use this solution. just need your external SD same as your phone internal SD size. if you are 8G internal SD , you must use 8G external SD card with 2.1 ROM . you can get 1.85G system space.

I've just tried XWJVB firmware - stock Android 2.3.3 - and it also works! Phone loads without flashing custom kernel.
I wonder, if there is a way to upload any file to the phone - so I can put there a book and read it.

does this mean this workaround still can't recover the files that were originally in my internal sd?

Nope. the internal sd is gone, probably forever.
workaround allows running the phone and having 2GB out of microsd card available for programs storage. it allows downloading and installing application from app market. still, you don't have other storage - can't upload a file or even make a photo with camera.
very wierd. if anyone would suggest a workaround to upload file to the device - even using any hacked way, like from abd or whatever

I flashed custom Kernel (CF-Root-XW_XEE_JVB-v3.1-CWM3RFS) over latest JVB. The device is now rooted.
Using adb tool I was able to push fb2 file to device - specifically to dev folder. (adb push file.fb2 /dev). Using Moon Reader I can open and read it! That's terrific after long time of finding a way of doing this.
Unfortunately, Moon reader is the only app that works. FBReader tries to open the book but fails with writing cache to sd card (which is broken).

This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...

raullugo said:
This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...
Click to expand...
Click to collapse
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder

stuck on step 6..
first of all, this is a great post for those who still stuck with a dead i9000m and no help from Sammy!
Steps (this is how i followed)
1. fine
2. fine
3. fine (i inserted a 16gb Sandisk class 2 in FAT32 format)
3a. i couldn't 'boot to froyo' i'm not sure if you mean fully boot into the OS or not, but it was in a bootloop
4. i was able to get to step 4 somehow to the recovery (3e) and wipe data (there was still the cant mount error when wiping data but no error when wiping cache partition - is that normal?)
5. i cant find JL8 but others here suggested any other 2.1 ROM works so i tried JM8 (no repart/no update bootloader)
6. the phone did do something other than boot loop! (first time wow!) it was trying to copy something but it didn't go all the way through.. there was an error saying 'efs format failed /dev/block/mmcblk0p2' after/during 'coping media files'.
- could it be the wrong format going in (should it be something other than FAT32?)
- could it be that class 2 was not the right class (no fast enough??)
- the copying process stopped after it finished copying media files.. (the micro sd card did have some media files
- there was 2 folders Samsung folder (with media files) and svox (i think that was the name of the folder)
can anyone shed some light on where i did wrong, thanks everyone, love this forum btw.

pavbul said:
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder
Click to expand...
Click to collapse
Thank you for the instructions, tha only reason to look for the jl8 rom is to follow the instructions to the letter. I trying your method right now, thank you for taking the time to give me another shot at my SGS, I will let you know how it goes

[Q] LG Optimus L5, recovery and app2sd don't see the external SD

Hello World,
I've got a question concerning the external 8gb sdcard on my phone,
the phone is rooted, has bootloader and cwm 6, the rom is stock btw
My phone can put/place some things to the sd but some don't,
for example,
- Camera saves some of the pics to it,
- My PC sees it when I connect the phone and I can put apps/music etc to it
but,
- I can't use the app2sd built into android assistant (or any other app2sd apps) to move the apps to the sd, they just won't see the sd,
- CWM wont backup to it,
No /sdcard/.android_secure found. Skipping backup of applications on external storage
Click to expand...
Click to collapse
I've searched the forum, but I can't actually find the right solution for this?
I'm new to all of this, and I want to learn. I've found some advices to similar problems and that the solution is to partition the sd, is that the catch or maybe something else?
Thank you in advance, newbie.
Edit
A new example of not seeing the sd in recovery,
I wanted to flash the "Sony Album" via the Pimp my Rom app, it downloaded the app successfully, it asked for clearing of the dalvik cache, I approved it,
phone rebooted and went into recovery, and then the recovery said that the file doesnt exist (something like that).
Edit
I've tried formatting the sd with fat32, no changes whatsoever :S

[HELP] Internal SD Card "Unsupported". Cannot access files.

Hi everyone,
I have a S5 klte with Samsung SD card formatted as Internal Storage.
Yesterday, I thought I will update my Slim rom 0.6 to the newest version 1.3. After flashing the rom, wiping cache and dalvik cache phone stuck on boot animation. Now, the stupid thing I've done was to push "Fix permissions" in TWRP recovery. After that, I was able to boot my phone, but it lacked most of the apps which were installed previously, none of the google services would work, I could see all the pictures/videos in my gallery, however. When I tried to backup those to my PC, I could see only a small part of it. Tried flashing previous rom, different gaps, wiping cache - nothing.
Then, I thought, I will do a regular wipe, since I didn't cared much about lost apps. From the experience I knew, that wiping does not touch media stored in internal storage. So I wiped my phone and restarted (with old slim 0.6 flashed before).
Now the phone works great, but there is HUGE problem. All internal storage is gone including pictures and videos and Samsung card, which was formatted as internal storage, now says "Unsupported card" and asks me to format it either to external or internal.
What could I do? Is there any way to "re-link" the internal card so that I could see its contents? Or I should use some file recovery software and see what I can get?
Thank you in advance for the help!

Did you try popping out your SD card out of your phone and using an SD card reader to get data off it onto a pc
Sent from my iPhone 4s using Tapatalk I also own a g900v

Well, I am using Mac for the moment, so when I try to connect sd card to it the notification pops up, that drive is not accessible, or something similar.
Tomorrow I will be able to try it on PC, but I believe nothing will change. The biggest problem is that sd card is formatted as internal storage and linked with phone's internal storage. I do not know these inner mechanics, but I believe that I need to somehow recreate that link.

Hmm your probably right good luck trying to fix it
Sent from my iPhone 4s using Tapatalk I also own a g900v

Sadly, there is not much of info due to complexity of this issue. Still waiting for at least some hints what should I do...
UPDATE: PC does not respond to the sd card at all, there is no sound, no drive, nothing.

[SOLVED] S7 Edge SM-G935S Soft-bricked: Unable to mount any partition

The problem is solved, the solution is as followed:
Problem
- The device is unable to mount every partition, this includes:
/efs
/persdata
/system
/data
/cache
Solution
Flash the stock firmware following this instruction to Repartition the device:
https://www.sammobile.com/forum/showthread.php?t=30800
The credit goes to member greenman of sammobile forum as the link above.
Thank you very much for everyone who took the time and effort to read the thread and answer my question. I appreciate it a lot.

HI there, i think you should try and grab an image for 935F from sammobile and restore with ODIN? This should restore the device into clean state. Not sure if you tried, ie to boot into download mode, and flash via odin?
**Edit, oops, i see you already tried Odin. Hope someone can assist you..

Edit. As far I have learned so far. Every root method etc will decrypt ur sd card. If you format it will be encrypted again. Because the files get reinstalled with the config. Wich can hurt allot. As I stated before try to get the first backup from efs and ur bootloader twrp makes. After make a new one and make sure they are on ur pc. I think u will need 2 freshly flash stock rom with repartition. Since it will relocate the sd card and reformats it. But im not truely sure. If I were you wait for some senior members to confirm.
I had this issue before kinda same as yours. No os etc. But I always make backups of efs and bootloader and everything else every change I make.
So I bassicly made a fresh flash. Downloaded latest stock firmware from sammobile and converted the 4 files into 1 huge file wich I putted in ap. And putted the normal once in bl and csc etc. Then Putted in hidden image for the repartion and checked reset efs.
The flash took 15 minuts and the bootup about 30 with 3 reboots.
But pls dont try this yourself. I Program whit icepicket multi flashdevice as daily job and write the coding for eepromx chips. Thats the heart of most prints with hidden coding. And controls all hardware. This method worked out for me. But like I said I rather should wait for someone to confirm this.

removed

removed

chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
chaopac said:
After some more reading, I think my last resort is to perform a "Full Firmware" flash, with options such as NAND erase, PIT file flash and EFS clear.
However, I am not entirely sure what they will do, and if in my device situation they will help fix the issue or make it worse. Information I've found so far on the net are quite vague.
So I guess I will wait until someone who is familiar with this so called "Flash Full Firmware" process to point me in the right direction to move forward. Until then, I will keep searching.
Thank you for your input. I appreciate your time.
Click to expand...
Click to collapse
Edit I have typed this and readed it back. There are allot of grammar corrections to make. But I had a shift of 9 hours and due a traffic jam I also had to drive 4 hours. Also im dutch and my keyboard trys to correct stuf to Dutch. Hope you will understand what I wrote. Im just to tired now to correct it haha.
Repartion is ussualy used when you change from a multi csc to a single csc with the open pit file from the csc file. It hold how your mobile provider app instaltion etc etc.
Efs clear will bassicly wipe the cache of that part. It hold the previous versions of your mobile provider allowed things and system apl version. Also the history of previous settings. When you set up the mobile first time with a sim and add your google account there is an option restore previous backup and seetings of accounts amd system app versions of last reset. Wich always be turned on after factory reset. If you tick clear efs in odin it will wipe that. The unique codes in the efs part are not wipeable easily. Only when you really start messing arround with fully system root acces.
When a print is flashed the mainbord it is done with a flash device. In this case the one I have is used by big corporations. Every print has an hardcode. With unique codes.
To acces these or flash a new one you need sich device. Then u also need the right method. From 5 pins to uart usb in this case. Them u need the right port nuber and flash time etc etc etc. Also corporations use those special devices since we can connect different cables mini usb rs245 and so on. Wich give use another layer of protection for people who try to steal our hard code.
To ecplain lets say I made a print and the flash will be on a mini usb. Lets say the cable has 3 wires to the mini usb amd the mino usb has 5 connectors we can connect to. This gives us the oppertunity to lets say we put wire 1 and 2 on connector 3 and wire 3 on connector 1. We have allot of options. Since we can also program eich wire will transfer the data. We even can put resistors on them as a safery check.
That is one of the reasons why its damn hard to read the coding and unlock a new bootloader or efs file to root stuf. It takes allot of time to get it done. And im not sure if great programmers like chainfire do it this way. But it takes them allot of effort and time to deliver us the great rooted software.

The issue is resolved. The solution is updated at the post #1.
Thank you for everyone who read the thread and participated in.

G4 Plus w/ LineageOS stuck at booting screen

So I installed LineageOS about 4 months ago or so and out of nowhere the phone just turned itself off and wouldn't boot, it goes past the motorola screen into the LineageOS booting screen, and it just keeps loading and loading, I can access TWRP, and I tried installing an older version of LineageOS and wiping the cache and dalvik, that seemed to have worked but the home button wouldn't work and some core system thing kept crashing and warning me on the screen and I decided to reboot, and now I'm stuck at the booting screen loading forever again, basically I'm trying to NOT wipe the phone data UNLESS I'm able to backup my apps with titanium backup or something like that; so since I managed to make it boot once maybe it ain't as bad as I see it, so yeah here hoping to get some options to fix it.

dante0397 said:
So I installed LineageOS about 4 months ago or so and out of nowhere the phone just turned itself off and wouldn't boot, it goes past the motorola screen into the LineageOS booting screen, and it just keeps loading and loading, I can access TWRP, and I tried installing an older version of LineageOS and wiping the cache and dalvik, that seemed to have worked but the home button wouldn't work and some core system thing kept crashing and warning me on the screen and I decided to reboot, and now I'm stuck at the booting screen loading forever again, basically I'm trying to NOT wipe the phone data UNLESS I'm able to backup my apps with titanium backup or something like that; so since I managed to make it boot once maybe it ain't as bad as I see it, so yeah here hoping to get some options to fix it.
Click to expand...
Click to collapse
With titanium backup its possible to restore data from a nandroid backup.
Did you installed exactly the same rom over the actual one again? Did you tried wipe cache and art?
Make a backup of system, data, boot and save it to your computer just in case.

strongst said:
With titanium backup its possible to restore data from a nandroid backup.
Did you installed exactly the same rom over the actual one again? Did you tried wipe cache and art?
Make a backup of system, data, boot and save it to your computer just in case.
Click to expand...
Click to collapse
When the phone got stuck at the loading screen I tried installing an old LineageOS rom, that initiated with the errors I mentioned, and when I did that I wiped the cache and dalvik/art cache as well, and now I've tried deleting them again many times and it doesn't seem to work, and quick question, the nandroid backup is basically doing a backup of what you told me, system, data and boot, right? Would that save all apps and their data, let's say, a progress in a game, or all settings exactly like I left them on an app.
Also I don't know if it's me, but I keep deleting some data from my SD card and it just keeps reappears again, even tho I'm seeing them getting deleted, same with pasting new stuff on my SD card, I'm doing all this thro my PC with ADB, tho pasting and deleting stuff on the internal storage works just fine.

Yes, a nandroid backup from your system/data partition saves all your additional apps with settings.

strongst said:
Yes, a nandroid backup from your system/data partition saves all your additional apps with settings.
Click to expand...
Click to collapse
Yeah it says my SD card is on "Read-only" and can't complete the backup, according to some thread it's a FAT error and I gotta mount the SD card on my PC and fix the error thro windows, but I have no SD card reader, meanwhile I'll wait for other answers until I find an SD card reader.

The issue was most likely caused by updating LineageOS many times over and over again eventually causing a corruption, that and my micro SD dying and just being read only made it worst, so yeah, I'd recommend erasing cache, dalvik and system every few months to update LineageOS, well I wouldn't take this that seriously, since I don't really know that much, but yeah, phone is working just fine now, just installed everything from scratch and google helped me restore my apps.

dante0397 said:
Yeah it says my SD card is on "Read-only" and can't complete the backup, according to some thread it's a FAT error and I gotta mount the SD card on my PC and fix the error thro windows, but I have no SD card reader, meanwhile I'll wait for other answers until I find an SD card reader.
Click to expand...
Click to collapse
The isssue you are talking about(sd read only mode). Im facing this problem and have done each and every method possible to give write access to sd card.
Well i can access the data(like can put anything i want in it) but can't modify it(copy, move, delete and even format). I looked for way arounds and tried my own method(even risked the data on sd) but no good comes out of it.
Im using rr and not lineage so we are on different boats in the same river.
If you get any solution pls inform me ans ill try it.

DgnrtnX said:
The isssue you are talking about(sd read only mode). Im facing this problem and have done each and every method possible to give write access to sd card.
Well i can access the data(like can put anything i want in it) but can't modify it(copy, move, delete and even format). I looked for way arounds and tried my own method(even risked the data on sd) but no good comes out of it.
Im using rr and not lineage so we are on different boats in the same river.
If you get any solution pls inform me ans ill try it.
Click to expand...
Click to collapse
Some sdcards become read only over time, had also 2 of them which had those issues. See reviews on Amazon. It's a known problem of the SD card itself. Try to format your card with pc and check if it's writable again, otherwise it's dead.

strongst said:
Some sdcards become read only over time, had also 2 of them which had those issues. See reviews on Amazon. It's a known problem of the SD card itself. Try to format your card with pc and check if it's writable again, otherwise it's dead.
Click to expand...
Click to collapse
Thanks for the concern and yeah i know that it is a problem with sd cards.
The thing i was saying that i literally tried each and every method formatting from pc to even twrp. I even used cmd for it and as a out come non of them work.
Well sd card is not dead. I can move, copy thing in it the problem comes after that. I cant delete or then move from sd card to other location. Its like read only compact disk(it will clear the idea what im talking about). My sd card is working as a read only cd does.

DgnrtnX said:
Thanks for the concern and yeah i know that it is a problem with sd cards.
The thing i was saying that i literally tried each and every method formatting from pc to even twrp. I even used cmd for it and as a out come non of them work.
Well sd card is not dead. I can move, copy thing in it the problem comes after that. I cant delete or then move from sd card to other location. Its like read only compact disk(it will clear the idea what im talking about). My sd card is working as a read only cd does.
Click to expand...
Click to collapse
That's what I mean: they become read only. Search on Google.

I had the same issue. I tried reinstalling Linage OS, clearing the cache, etc. But what finally resolved it was clearing the data. So the issue was corrupted data that was keeping the device from booting.

Database Users

welcome