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!
Related
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Same problem!
i do have the EXACT same Problem!!!! Any solution jet?
Got a similar problem with my Galaxy Tab... Anyone found a solution yet?
friend of mine has a htc and uses a program called superwipe
http://forum.xda-developers.com/showthread.php?t=834812
dont know if it will work on the galaxy s though, but coukd be worth a read through the notes and posts
Wow . I have a similar problem. Although EVEN more troublesome.
Inaddition to all this
I cannot even DELETE the alarms taht i set before having this problem. I cannot Install the apps as well.
Uninstalling the ones - and they reappear the next time I boot.
Need Serious HELP on this.
My phone is restricted to ONLY making calls and sms. Thats all.
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
jrhsu529 said:
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
Click to expand...
Click to collapse
I have a different problem. My internal sd seems slow. Anyway, I must feel lucky.
If you look at page 15 of the following datasheet, you will notice that the moviNAND can be set in a "write-protect" mode:
http://web3032.sh1.magic2008.cn.m1.magic2008.cn/uFile/3032/201144131545503.pdf
See if you can read the CSD register data on your phone, and mingle with it.
Good luck.
Any one fix this
Any one fix this I have the same problem
Yesterday I gave the soluction, but someone deleted my post.
EDIT!!
Sorry, I wrong topic!!!! Sorry!!!!
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
damgood said:
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
Click to expand...
Click to collapse
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
DerBusisVoll said:
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
Click to expand...
Click to collapse
Sorry - no - I had to start from scratch, my thougt was too many files on the ext card But I not sure and cannot recall - My phone is working good now. Only advice is to reinstall from scratch
I am also facing the same problem on my galaxy nexus after upgrading to KK using custom ROM. Any solution?
Does anybosy able to doanload the superwipe?
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Galaxy Tab 2 running on blisspop rom
I have to reboot every time this happens. The error message in mx player shows cannot write to internal sd..
Es xplorer cannot delete any item. Terminal emulator shows mount as read only
Any way to fix this?
Soooooooooooooo many problems..
1) When I try to delete stuff off my SD card (music, movies, pictures) they will delete but then when I plug my phone into my computer THEY ARE BACK THERE AGAIN!!!!!!!!!!!!!!!!!
2) When I try to partition my SD card to get a Ext4 partition, all I get is errors.
3) When I put a ROM Zip file on my SD (from my computer), it is there, when I boot into recovery and try to install the zip; i choose install zip from SD card and it isn't there.
Why is my Nexus One trying to piss me off? I've never had issues like these ever!
My Galaxy S, Galaxy S II, and Atrix never did this.
If anyone knows whats going on and can help fix this BS, that'b be awesome. If not, then I will just take this garbage to the shooting range next week.
Your SD card is most likely corrupted / unusable.
Jack_R1 said:
Your SD card is most likely corrupted / unusable.
Click to expand...
Click to collapse
Is there any way to fix it?
I tried the 4GB that came with my N1, and it doesn't have the same issue....
Do i have to buy a new one?
Try to format it in Windows.
Jack_R1 said:
Try to format it in Windows.
Click to expand...
Click to collapse
Would disk defrag help?
No, either completely wipe the card or just get a new one. That's simple...
Wow, taking anger out on the phone when its the sd card's problem..
Try formatting it, not just deleting the data. If another card works then it is definitely the card. Stuff happens, just get a new card if anything.
if you are going to format in windows as Jack suggested, use sdformatter--
http://dl.dropbox.com/u/28338566/SDFormatter 2.0.mht
format with full erase and size adjustment on
keep your swap at 0 when you repartition card when back in phone
if that doesn't work--need new card
also wiping system is important when flashing new rom. i like temasek's extreme wipe that is flashable thru recovery--
http://dl.dropbox.com/u/28338566/Extreme-wipe.zip
i still wipe data and caches after flashing the zip, usually wipe all 3x
ken
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
PMrjn83 said:
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
Click to expand...
Click to collapse
Have you looked over this guide ? or this ?
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
Thanks. I'll try when I get home to my desktop. For some reason, my laptop does not recognize the phone through adb. It shows "SGH-i897" in device manager with an exclamation mark. And yes, I have tried quite a few drivers, etc... :/
I might need to try this...
http://forum.xda-developers.com/showthread.php?t=1761968
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
PMrjn83 said:
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
Click to expand...
Click to collapse
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
gsstudios said:
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
Click to expand...
Click to collapse
Well, I tried. If it doesn't mount at all, how can you format?
Hi everyone,
I'm trying to fix a nexus one of a friend of mine, which has a major problem:it can't mount internal sd.
It was stuck in a bootloader, easily fixed by wiping data (except for sd, of course, as it can't be mounted and erased)
I tried flashing a different recovery (both can and twrp) , but it won't be able to format sd, i've tried to reflash stock recovery and formatting in bootloader menu, it looks OK but nothing changes, I can't sideload a new rom, wipe data skips sd formatting, and so on.
Is there anything I can still try, or is it likely a hardware issue?
Thanks for any help
Sent from my vivo X710L using XDA Free mobile app
Well, I "solved" the issue by simply purchasing a micro sd, which works now as internal storage...don't know why (proper internal storage looks gone).
Now for a quick tip: the phone belongs to a non-tech person, is it worth flashing something newer than CM7.2 which is on board now, or would the bugs be more than the enhancements?
In case it's worth trying something newer (and it must be something big , i need to look for and use old Pcs to make connection work, on my Win8 Pc it doesn't recognize device), which rom would you suggest?
Thank you
Hello, everyone!
It seems that there are many misinformation about using an external micro SD as internal memory when installing any of the (great) Marshmallow ROMs available to L90, so I decided to create this thread from my experiments and leave it open for discussion.
What is it?
With Marshmallow you can use an external uSD as internal memory, what is great for L90 because it has 8GB of internal storage, with only around 4GB available for users.
How does it work?
It's a Marshmallow feature so it's built-in, no need of extra apps. It will format a uSD inserted in the L90 micro SD slot and use it as internal storage.
The uSD card will work from now on only on your phone, but you still can unmount, remove and replace it with other cards as needed. All contents from /sdcard will be moved from internal storage to the uSD, and all apps that allow native "App2SD" will be moved too (you can choose to move or not, if you don't you can move apps manually later). Not all apps can be moved, but you can "force move" ones that don't support native App2SD, but be aware that it may break things, like widgets, etc.
How do I use it?
There are two ways to enable adopted storage:
1. it will offer you the option to use a newly detected uSD as internal or storage, so you'll probably see a notification when you insert a new uSD on your phone, or right after installing any Marshmallow ROM;
2. Go to "Storage and USB" in Settings app, select your external card, tap the three dot menu and choose Settings, it will then open a page where you can Eject, Format (erase) or Format as internal option.
Either way you will be guide through the process of formatting your uSD as internal memory and moving your data. Obviously, your micro SD will be formatted (erased) so backup any important data first.
Advantages
The main advantage is that it will improve your internal storage a lot. Even if you use a 8GB uSD, because it will move everything from /sdcard folder to the uSD. Also, if an app is moved, then all its contents (data, obb, cache) will be stored in the new adopted storage.
Problems
From what I've tested, the only problems are that even a Class 10 uSD is slower than internal memory and not as reliable. So make sure you use a fast uSD (I'd say Class10 is the minimum) and a reliable one. Of course, if you use the uSD to move data between your phone and other devices then you probably will want to keep using it as external (aka Portable) memory.
Observations (may be updated later)
1. If you don't choose the option to move your apps when formatting the uSD you can do it manually later: go to Settings, Apps, pick the app you want to move and then click on Storage, you should see a page with a button to move the app (and app data). If you see "Force Change" then the app doesn't support moving to external storage natively, and doing it may break something;
2. All internal storage will be used only for apps and apps data when using adopted storage, everything else will be on your external uSD, what means /sdcard is now on your uSD. Also every app and app data moved to adopted storage will be on your external uSD too, so removing the card will make those apps unavailable as well as any data stored on /sdcard;
3. You will still be able to access all data using MTP (it will show only Internal Storage, as /sdcard is on your external uSD now) or using TWRP 3.0.0 or later (/sdcard data will be available on the /emmc folder using the built-in File Manager, or separately using MTP). MTP on TWRP was very slow for me when I tried to use it, so slow it's useless for files > 1GB, but maybe it's because I have used Android File Transfer on a Mac, your mileage my vary;
4. Sometimes the format process may abort and Android will show your uSD as "corrupted" (maybe it's the wrong word for it). Don't panic. If you want to test your SD, use it on a computer and do a full format using FAT format, it will test the card. Simply restar the process if you've tested or you know your card is OK. If it still says your card is slow, don't worry, it may work fast enough for you (again, I am talking about Class 10 or higher);
5. When a uSD is formatted as internal storage it won't be "readable" anymore on any other phone or computer (OK, maybe you can on a computer that can read f2fs and its contents, but not the usual and normal way);
6. Going back is complicated: probably you will need to use a computer and MTP to copy the data from /sdcard to it, uninstall or move the apps you want to keep back to internal memory and then format your uSD card again as external memory.
7. It seems that you can use one uSD to both adopted and portable storage, see the link bellow (not tested, read the other page linked too):
Sam Liddicott: Android 6 semi-adopted storage
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html?m=1
Most things discussed here can be seen with pictures in this page from Motorola support website:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/109134/p/1449,9582
Cheers and thank you all for the great info I got from this forum! :good:
this is the reason my d415 is bricked ! :'(
DeathCrow17 said:
this is the reason my d415 is bricked ! :'(
Click to expand...
Click to collapse
Only formatting uSD as internal storage won't brick any phone. It's even listed on Motorola website for their phones. What else did you do?
lfom said:
Only formatting uSD as internal storage won't brick any phone. It's even listed on Motorola website for their phones. What else did you do?
Click to expand...
Click to collapse
While formatting the sd to make it internal storage, the screen just went black..so i search what's wrong, they said i need to wipe the partition and create a new one......before i did that, i can boot to the logo and booting screen still black on the home screen tho, but after i did that, my screen is totally black, wont boot
@DeathCrow17
Sorry, but I've done it more than twice and never had a problem. I don't know why it happened to your phone, maybe it was just a sad coincidence. Anyway, if you still can enter download mode you can flash stock firmware using LG Flash Tool. If not, there are fastboot and the hard unbrick tutorial, you may get more help in those threads. Good luck.
lfom said:
Only formatting uSD as internal storage won't brick any phone. It's even listed on Motorola website for their phones. What else did you do?
Click to expand...
Click to collapse
lfom said:
@DeathCrow17
Sorry, but I've done it more than twice and never had a problem. I don't know why it happened to your phone, maybe it was just a sad coincidence. Anyway, if you still can enter download mode you can flash stock firmware using LG Flash Tool. If not, there are fastboot and the hard unbrick tutorial, you may get more help in those threads. Good luck.
Click to expand...
Click to collapse
Tried everything but after wiping the partition because the tutorial said i should....my screen just went totally black, no LG logo booting screen nothing....there is 1 guy who 's been helping me, even him is having a hard time fixing my device, through teamviewer....but i still have my fingers crossed for this LG after all this is my only one LOL
Can anyone confirm that TWRP_3.0.0-0_060216_L90_Testbuild.img does indeed work with adoptive storage
Fábio Ferreira said:
Can anyone confirm that TWRP_3.0.0-0_060216_L90_Testbuild.img does indeed work with adoptive storage
Click to expand...
Click to collapse
As I reported in OP, Dark Blue version from the post bellow works just fine as described.
http://forum.xda-developers.com/lg-...rp2-7-1-0lgl90w7xxshoxx-t2826150/post65428096
lfom said:
As I reported in OP, Dark Blue version from the post bellow works just fine as described.
http://forum.xda-developers.com/lg-...rp2-7-1-0lgl90w7xxshoxx-t2826150/post65428096
Click to expand...
Click to collapse
Should i flash the .zip or the img inside?
And shoild i wipe anything?
Fábio Ferreira said:
Should i flash the .zip or the img inside?
Click to expand...
Click to collapse
Either way should work if you do it correctly. I flashed the zip using Rashr if I recall it correctly.
lfom said:
Either way should work if you do it correctly. I flashed the zip using Rashr if I recall it correctly.
Click to expand...
Click to collapse
And shoild i wipe anything?
Sorry for the begginers questions, but i've never updated any recovery .Thanks for your help
Fábio Ferreira said:
And shoild i wipe anything?
Sorry for the begginers questions, but i've never updated any recovery .Thanks for your help
Click to expand...
Click to collapse
No, simply flash it and next time you boot to recovery you should see the new version.