I purchased a Moto G power as a gift; it has Android 10 installed on it. One of the primary reasons to purchase it was the OOTB ability to take a 512GB SD card.
The difficulty is that the phone itself does not allow the card to be mounted such that it can be treated as 'internal' storage! There is no option to do this within the phone's menus. The SD card is treated as portable storage.
So: I turned on the developer options, connected via USB to Windows 7, and loaded up ADB to see what I could do, but no matter what I tried I would always get a result like this (showing here for the case where I tried to 'split' the SD card 50/50):
adb shell sm list-volumes all
private:179,67 unmountable
private mounted null
public:179,65 mounted 08CC-29A9
emulated mounted null
The red part would show up on the phone itself as a "corrupted" storage (albeit 'internal'), so I thought I was getting close, but 'reformatting' just that part set the entire card back to 'portable'. I want to note that I never saw private:179,67 unmountable null even when using adb shell sm partition disk:179,64 private to try to set the whole SD card as internal.
The full series of commands as executed (for the result shown):
adb shell sm list-disks
adb shell sm list-volumes all
adb shell sm set-force-adoptable true
adb shell sm partition disk:179,64 mixed 50
adb shell sm set-force-adoptable false
adb shell sm list-volumes all
I'm somewhat new to this game, but I was wondering if anyone could offer some insight as to what is happening?
leptonica said:
I purchased a Moto G power as a gift; it has Android 10 installed on it. One of the primary reasons to purchase it was the OOTB ability to take a 512GB SD card.
The difficulty is that the phone itself does not allow the card to be mounted such that it can be treated as 'internal' storage! There is no option to do this within the phone's menus. The SD card is treated as portable storage.
So: I turned on the developer options, connected via USB to Windows 7, and loaded up ADB to see what I could do, but no matter what I tried I would always get a result like this (showing here for the case where I tried to 'split' the SD card 50/50):
adb shell sm list-volumes all
private:179,67 unmountable
private mounted null
public:179,65 mounted 08CC-29A9
emulated mounted null
The red part would show up on the phone itself as a "corrupted" storage (albeit 'internal'), so I thought I was getting close, but 'reformatting' just that part set the entire card back to 'portable'. I want to note that I never saw private:179,67 unmountable null even when using adb shell sm partition disk:179,64 private to try to set the whole SD card as internal.
The full series of commands as executed (for the result shown):
adb shell sm list-disks
adb shell sm list-volumes all
adb shell sm set-force-adoptable true
adb shell sm partition disk:179,64 mixed 50
adb shell sm set-force-adoptable false
adb shell sm list-volumes all
I'm somewhat new to this game, but I was wondering if anyone could offer some insight as to what is happening?
Click to expand...
Click to collapse
Well I don't know how G Power behaves but are you sure the SD is formatted as internal storage?
It should show on Storage and the SD card should have a option to Format as Internal Storage.
If it doesn't it may be that the phone doesn't support it.
I'll try it myself and get back to you.
This generation of phone does not offer the ability to 'format as internal' as older generations have. I'm not developer-savy, but I did make the (bad, I suppose) assumption that even if the phone didn't offer the option that I could still work under-the-hood to enable it.
It shouldn't be the end of the world, but my intent was to gift a phone that would offer enough flexibility such that (barring damage) the lifetime would be limited by battery performance... and I was working from the perspective of being able to add some more 'internal' memory would provide an extra headroom. I personally don't use many apps that consume the internal memory of my current Moto g5plus, so in my own configuration the external storage is used exclusively for photo/video/audio, plus whatever apps will leverage an SD card for their own nefarious reasons. The last bit I'll write in defense of my (perhaps peculiar) attitude is that I had an earlier generation cell phone that was short enough on internal resources that it became a struggle to simply update applications, and I'll go to great lengths to avoid that misery.
Related
My Note II, running the latest CM 10.2 nightly, has had a ghost--or Electro--remove the SD card making SD card dependent programs stop working.
I have a 64gb SanDisk card that has been working like a champ since I bought the phone.
Earlier this week, I kept getting errors that my SD card was not available. These errors would come out of the blue, sometimes even when the phone was in its dock. This made Spotify and Camera apps useless.
However, the phone still recognizes that the card is still plugged in.
At no point in time had I touched the actual card physically.
The only way to fix it, is to either pop the batter door, pop out the SD card out and back in, and then force close the apps that depend on it.
Or, reboot the phone.
How do I go about fixing this?
Your card might have become mounted "read only" ....you can fix it in a computer. Do a google search for "sd card mounted read only". It has happened to me before. It happens sometimes when one or more files on the card become corrupted....the fix will not erase your card.
Sent from my SCH-I605 / Galaxy Note 2 using Tapatalk v 2.4.13
manbat said:
Your card might have become mounted "read only" ....you can fix it in a computer. Do a google search for "sd card mounted read only". It has happened to me before. It happens sometimes when one or more files on the card become corrupted....the fix will not erase your card.
Sent from my SCH-I605 / Galaxy Note 2 using Tapatalk v 2.4.13
Click to expand...
Click to collapse
I had feeling that it would be something related to the writability of the card.
Seems that this is a common problem, but none of the solution threads showed up in my searches.
From here, we have the following:
Fix the FAT
- connect device to your PC (USB connection) and make sure it’s set so that you can copy files to/from your computer (on my device in the notification panel there’s an option to do this under “USB connected”)
- on your pc, open windows explorer (or click on start->computer), then right click on the mapped drive to your sd card – you may have to wait a minute or two for the mapping to take effect
- select Properties
- select Tools
- select Check now… (for error checking) to automatically fix file system errors (no need to deal with bad sectors at this time)
- when completed (takes a minute or so), the FAT will be in working order once again. No files are deleted during the process, so no need to worry about that.
- safely disconnect the device from your pc, at which point the sd card will now be mounted read-write and you’re good to go
Click to expand...
Click to collapse
Once I get home I'll try this out.
I just put it in a SD Adapter and plug it into the computer. Use the same process listed. Worked for me.
Sent from my SCH-I605 / Galaxy Note 2 using Tapatalk v 2.4.13
I executed a check disk on my sd card and put it back in my phone. The same problem persists. This is rather annoying.
Mine was close to capacity a while ago and exhibited all signs of being toast.
I removed about 20 gigs of music from it, and it came back to life.
Good luck.
Hmm, I'll give it a try. The SD card is pretty full with all the TWRP and Titanium backups ...
I tried everything under google's radar, and I cannot get this to work. The car simply does not like to be written on, cannot be formatted, an check disk does nothing.
HTML:
[email protected]:~$ dmesg | tail
[439975.916884] sd 18:0:0:0: [sdb] Write Protect is off
[439975.916896] sd 18:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[439975.918251] sd 18:0:0:0: [sdb] No Caching mode page present
[439975.918259] sd 18:0:0:0: [sdb] Assuming drive cache: write through
[439975.923608] sd 18:0:0:0: [sdb] No Caching mode page present
[439975.923616] sd 18:0:0:0: [sdb] Assuming drive cache: write through
[439975.924857] sdb: sdb1
[439975.929020] sd 18:0:0:0: [sdb] No Caching mode page present
[439975.929033] sd 18:0:0:0: [sdb] Assuming drive cache: write through
[439975.929044] sd 18:0:0:0: [sdb] Attached SCSI removable disk
[email protected]:~$ fdisk -l
[email protected]:~$ sudo umount /dev/sdb1
[sudo] password for z:
[email protected]:~$ sudo mkfs.vfat -n 'SDCARD' -I /dev/sdb1
mkfs.vfat 3.0.14 (23 Jan 2023)
mkfs.vfat: failed whilst writing FAT
[email protected]:~$
I looked up my order on Amazon, and then at the product reviews for the card. I stumbled upon this thread: http://www.amazon.com/review/RUM36X...IN=B009QZH6JS&nodeID=172282&store=electronics
Seems like it is time to call Sandisk and get this card RMAed
I have fixed this by transferring my card to pc, running a full format via cardreader. and putting my files back. I believe a full format will mark bad sectors. It will take a while though.
If you are having trouble formatting in windows try using a software called gui format.
johnwaynegacy said:
I have fixed this by transferring my card to pc, running a full format via cardreader. and putting my files back. I believe a full format will mark bad sectors. It will take a while though.
If you are having trouble formatting in windows try using a software called gui format.
Click to expand...
Click to collapse
I tried formatting from both Ubuntu and Windows. There seems to. Something totally off with the card; I simply cannot write to it.
Sent from my Nexus 7 using Tapatalk 4
Here is what happens in windows:
Through CMD
Code:
C:\>format /fs:FAT32 Q:
Insert new disk for drive Q:
and press ENTER when ready...
Code:
C:\Users\Z>format /fs:exfat /x /q Q:
Insert new disk for drive Q:
and press ENTER when ready...
The type of the file system is FAT32.
The new file system is EXFAT.
QuickFormatting 60890M
Volume label (15 characters, ENTER for none)?
Invalid media or Track 0 bad - disk unusable.
Through Disk Manager
Code:
---------------------------Virtual Disk Manager---------------------------
The format did not complete successfully.
---------------------------OK ---------------------------
There is something definitely wrong with the card
Hello,
I know, there are dozens of threads, articles and recommendations over XDA and internet. But I am still not sure what best practice is. Erasing Hard Disks is quite easy. In this case one deletes the whole storage from an external device. One can also delete unused storage and so on...
However, I have not really any idea how to delete the storage of my phone, especially internal storage of my Nexus 5. If i plug in the phone to my PC it is recognized as an MTP device. A tool like Eraser http://eraser.heidi.ie/ is not able to choose this destination to erase. I am also not sure how the partitions are handled in Android. Is it enough to erase securely the complete internal storage after resetting, wiping, reflashing the phone or are there still areas of interesting data around other partitions?!
Would be glad to get some advice
This is my suggestion:
1. wipe your phone and storage, data...
2. flash new ROM
3. adb shell: dd if=/dev/urandom of=/sdcard/junkfile (http://zackeryfretty.com/posts/secure-erasing-android-devices-guide-for-the-super-paranoid-seller)
4. adb shell: dd if=/dev/urandom of=/data/junkfile (http://zackeryfretty.com/posts/secure-erasing-android-devices-guide-for-the-super-paranoid-seller)
Any other suggestions?
can "format as internal storage" be restored to sony's MM?
I know MM has just arrived. but I was hyped for MM because of this feature so you can understand my disappointment. I actually downgraded to LP since they even removed Stamina!
The main problem is that the 16gb internal are not enough. And if you have many photos and videos, the thumbnail data can be large in size, reached 5gb with me! And you can not change its directory. And it regenerates if deleted.
In my former Xperia p, I think I overcame this issue by making the thumbnail data file a dummy one then read-only it (i'm not sure whether I did that on Xperia p or another former phone) . I wasn't able to do this trick in LP
I use z2 d6502 rooted LP now.
My SD card is Kingston 64gb class 10
Well, that's something that disappointed me, too. So I tried it different ways f.e. here, but ended without result.
fireheart2008 said:
can "format as internal storage" be restored to sony's MM?
I know MM has just arrived. but I was hyped for MM because of this feature so you can understand my disappointment. I actually downgraded to LP since they even removed Stamina!
The main problem is that the 16gb internal are not enough. And if you have many photos and videos, the thumbnail data can be large in size, reached 5gb with me! And you can not change its directory. And it regenerates if deleted.
In my former Xperia p, I think I overcame this issue by making the thumbnail data file a dummy one then read-only it (i'm not sure whether I did that on Xperia p or another former phone) . I wasn't able to do this trick in LP
I use z2 d6502 rooted LP now.
My SD card is Kingston 64gb class 10
Click to expand...
Click to collapse
if you want to get your game obb files from your internal storage to your sd card for example i can reccomand the xposed module "OBB TO SD"
it`s simple to use, just inable it and then you can move your obb files from sdcard0\Android\obb to sdcard1\Android\obb!
if you want a rooted mm with xposed and a working twrp recovery check out this thread: id did it this way
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
in default , there is no setting to format as internal sdcard.
but you can enable it by usin adb command.
connect the phone to pc with usb debugging on..
open windows command prompt and type "adb shell sm list-disks" (ignore the quotes)
notice the output, it will be something like ---> disk:179,64 (179,64 is ID for sdcard)
now , parting the sd card.
* type .-->> adb shell sm partition disk:179,64 private (if you want to use the whole sdcard as internal storage)
* type --->> adb shell sm partition disk:179,64 mixed 70 (if you just want to use 30% of sdcard as internal storage)
** I found this way when i was googling, this is not a work of mine **
Thank you for your reply. I think I will try that
chax_84 said:
in default , there is no setting to format as internal sdcard.
but you can enable it by usin adb command.
connect the phone to pc with usb debugging on..
open windows command prompt and type "adb shell sm list-disks" (ignore the quotes)
notice the output, it will be something like ---> disk:179,64 (179,64 is ID for sdcard)
now , parting the sd card.
* type .-->> adb shell sm partition disk:179,64 private (if you want to use the whole sdcard as internal storage)
* type --->> adb shell sm partition disk:179,64 mixed 70 (if you just want to use 30% of sdcard as internal storage)
** I found this way when i was googling, this is not a work of mine **
Click to expand...
Click to collapse
This works for me. But I have camera issue. Cannot take picture, said "Memory unavailable." Don't know if it associated with adoptable storage. Am I the only one?
I have no problem in saving picture.
Or , just try to set sdcard ss default in camera.
Or , if you install xposed and use xinternal module, just remove it. It'll give so much trouble.
chax_84 said:
in default , there is no setting to format as internal sdcard.
but you can enable it by usin adb command.
connect the phone to pc with usb debugging on..
open windows command prompt and type "adb shell sm list-disks" (ignore the quotes)
notice the output, it will be something like ---> disk:179,64 (179,64 is ID for sdcard)
now , parting the sd card.
* type .-->> adb shell sm partition disk:179,64 private (if you want to use the whole sdcard as internal storage)
* type --->> adb shell sm partition disk:179,64 mixed 70 (if you just want to use 30% of sdcard as internal storage)
** I found this way when i was googling, this is not a work of mine **
Click to expand...
Click to collapse
i have turned on the usb debugging but when ever i type this in cmd it displays the message -
"adb " is not recognised as internal or external command
i have installed the adb drivers too! help low on storgae
arnavfoxtrot said:
i have turned on the usb debugging but when ever i type this in cmd it displays the message -
"adb " is not recognised as internal or external command
i have installed the adb drivers too! help low on storgae
Click to expand...
Click to collapse
Change folder to where adb.exe is and enter adb.exe instead of adb.
Or, add adb.exe to you path variable (see here http://stackoverflow.com/questions/...u-can-run-it-from-any-command-line-in-windows)
You get that error as adb is not into $PATH so you need to specify it or add it to $PATH.
Sent from my D6503 using Tapatalk
RCA Pro10 (Digiin) RCT6103W46 10" Tablet
RK3188 CPU
JellyBean 4.4.2
Problem: Unit hangs on RCA splash screen and therefore will not boot up even after factory resets. Unit was working fine until vold.fstab was edited to change the mount point of the external SD card.
USB Debugging enabled.
adb shell accessable.
busybox accessable.
When trying to obtain su privileges, via adb shell, the shell hangs.
Can not change read only status to r/w status for internal storage and therefore can not push edited vold.fstab back into internal storage.
Have tried several rooting programs (on both Windows 10, Ubuntu 18.04.2 and Mint 19.1 Cinnamon) to obtain root/su status on the tablet with no positive results.
No fastboot option available - only recovery is available via power/volume key combinations.
No viable firmware images availble either from manufacturer or available via internet searching.
Questions:
What software (or via adb shell) would pull a complete set of recovery images from
the unit so that I could install them to an external SD card with the purpose of attempting to boot/run Android from the external SD card?
Would this even be a possible option as I would imagine there would also have to be some method of overriding the original boot sequence so that it does boot from the external SD card?
I hate to think that this unit is totally bricked without exploring all options to try and revive it (including trying to install another OS which from doing net searches doesn't look to promising).
Any input on this topic would be much appreciated...thanks!
I have this device that suddenly becomes read only the entire internal storage.
I can boot and use it but the apps, including the launcher3 crash every time that they are launched. Only "setting" app and some other apps that not write to storage can work
tried to get an adb shell on pc but can not debug with usb because there is no debug app selected on phone, i think that is needed write access to do that. Tried flashing stock rom with the procedure indicated by the devs of the app, but not worked (it worked a time ago), this device is rooted.
I can connect through usb and mount internal storage on pc and read the contents, but can not write.
Connectbot does not work, but i think if there is an way to launch a terminal inside the device, maybe i can change mount options of partition or change some other things to recovery the phone.
so someone knows how to execute and not install a terminal shell from sd card?
CPU: 32bits - MediaTek MT6582
thanks!