No Internal SD - Motorola Droid Bionic

After using FXZ to upgrade to JB, I have lost my internal storage, it is labeled in file explorer as unformatted and in the storage menu of settings I have no options whatsoever. I have tried manually flashing emstorage.img through moto-fastboot and it returns the error "cannot load emstorage." I have noticed that emstorage seems to be an empty file, but any ideas to fix this? I do not have root access.
[edit] Still not sure why I am not able to flash emstorage.img, but after about the 30th reboot, the status bar gave me an option to format the internal sd and that fixed the symptoms of the problem.
Sent from my DROID BIONIC using xda app-developers app

did you try the emstorage image from 246 fxz file?
<step operation="erase" partition="emstorage" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="4fa5e1dbdeff60f905b321abe267403e" />
I have the same problem, except I need to recover my data. So I just want to know if all recovery effort fails.

Related

[HOWTO] Make a Complete Backup Image of Your CM7/Froyo/Honeycomb SDCard without CWR

Ok I've seen many People asking about Backing up Their CM7/Froyo/Honeycomb Cards (Which I'll call "CM7/NF/NH" here) so here is a Simple way to Image your Entire Card for Backup Purposes. This Guide has Two Methods. One is for Windows Users, the other is for Linux users. Mac Users can lightly follow the Linux guide as Mac has DD as well.
Windows Users: Please make sure you have the latest Win32DiskImager!
Windows Users:
Download Win32DiskImager:HERE
(You Should already have this since you had to Burn NF/NH)
Next Unzip it Anywhere, and Run the EXE
Now Select where you want to save your IMG file and choose a Name
Next Select Your Card's Mount Letter(ie:'E:')
Now Select "Read" NOT "WRITE"
Wait a Little While (The Program isn't Frozen!) Your Card should be Imaged (Partition Format and all) to the IMG file
Simply follow the Same Process to Restore but Choose "Write" instead
Linux Users:
This is a bit more Complicated then Windows and uses Terminal but since you already got CM7/NF/NH (and I assume Market is installed) on your Nook I'll assume that that's fine since I've yet to find a Good GUI for Linux.
First Open Terminal
Next Find the Device Location for your Card (NOT the Mount Point) it should be in the "dev" directory (ie: Mine was "/dev/sdc") An easy way to find it (if you have Ubuntu) is to Open 'System-->Administration-->Disk Utility', Select your Device and then Look at the Top-Right Corner. It shouldn't have a number as numbers designate Partitions.
Now head back on over to Terminal and enter the following:
Note:Anything in Brackets'[]' is User Specific. Plus Remember to Remove the Brackets as well(ie: '/dev/[Location]'='/dev/sdc')
Code:
cd [The Location You want to save the Image]
sudo dd if=/dev/[Your Card Reader's Location] of=./[Your Desired Name].img
NOTE:It may seem like nothing is happening but just give it time. Eventually you should receive a Message similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's it you should now have an IMG file in whatever Directory you chose
To Restore Your Backup simply Follow the Same steps you used when first Creating your CM7/NF/NH card but use your Backed-Up Image instead of the Default CM7/NF/NH one
It may not be an Easily Browse-able File but it's a Good thing to do before you Upgrade in case something Bad happens as it creates an Exact Replica of the Disk so you can Restore like Nothing happened.
Hope you enjoy! If you have any problems post below
THANKS!
0) I wish I saw this before I trashed my nookie Froyo card
1) Could I use this to backup my autorooted stock 2.1 with OC kernel?
2) Moderator: could you put this in a sticky and/or FAQ?
THANKS!
Different SD Cards??
If I backup a 4GB card and then restore to a 16GB card, I assume that I will just get a 4GB image??
Could someone please point me to an post that explains how to backup the individual partitions on my SD card so that I can transfer them to a larger card??
You need to edit the Subject Line to add "CM7" to Froyo and Honeycomb.
macevanscb said:
If I backup a 4GB card and then restore to a 16GB card, I assume that I will just get a 4GB image??
Could someone please point me to an post that explains how to backup the individual partitions on my SD card so that I can transfer them to a larger card??
Click to expand...
Click to collapse
You can use GParted(Linux) or some other Partition Editor to resize the Partitions once Flashed over.
OR
You can copy individual Partitions in Linux. Just add the partition number to the end of the Device address.
(Ie: Partition 1 of /dev/sdc is '/dev/sdc1')
I don't reccomend doing this as it is time consuming and you'll have to use a Partition Editor to make the Partitions, so in a way it's redundant.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
ADude said:
You need to edit the Subject Line to add "CM7" to Froyo and Honeycomb.
Click to expand...
Click to collapse
You've got a point. I'll do it later as I have to edit the OP to add info for when moving to a new Bigger card.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
Is there any issue w/ using this to save (read) from one SD card and restore (write) to a different sd card?
For my case, both are 8GB cards.
When I try to write to the new card it immediately says "done". (With the same card if I write the originally downloaded froyo image it works fine)
Thanks
BigCask
bigcask said:
Is there any issue w/ using this to save (read) from one SD card and restore (write) to a different sd card?
For my case, both are 8GB cards.
When I try to write to the new card it immediately says "done". (With the same card if I write the originally downloaded froyo image it works fine)
Thanks
BigCask
Click to expand...
Click to collapse
Same here. I can read the the card fine & it takes its sweet time creating the img file, but when I try to write the file to another SD card, it says 'Done' immediately & nothing is on the card. :/
Sent from my NookColor using Tapatalk
bigcask said:
Is there any issue w/ using this to save (read) from one SD card and restore (write) to a different sd card?
For my case, both are 8GB cards.
When I try to write to the new card it immediately says "done". (With the same card if I write the originally downloaded froyo image it works fine)
Thanks
BigCask
Click to expand...
Click to collapse
Odd, I can't reproduce your problem. If you can tell me exactly what you did and maybe even attatch a dump of your terminal(should be an option in the file menu) I might be able to help.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
dzigns said:
Same here. I can read the the card fine & it takes its sweet time creating the img file, but when I try to write the file to another SD card, it says 'Done' immediately & nothing is on the card. :/
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me. I backed up two cards, thinking I might swap images around and use a bigger card with the Nook..and I was immediately suspicious because both images came out at exactly the same size. But I don't know much about this stuff, and thought there might be some compression involved. But then I had the same problems was you where the image would refuse to write. I downloaded another image program(WinImage) and it said they were invalid image files.
I also tried making a backup image with this program and it actually produced an image size comparable to the card, so while I haven't tried writing these images yet(don't have another 16Gb card to use)it seems to actually be working.
Anyone else having this problem with Win32DiskImager?
JRSly said:
Same thing happened to me. I backed up two cards, thinking I might swap images around and use a bigger card with the Nook..and I was immediately suspicious because both images came out at exactly the same size. But I don't know much about this stuff, and thought there might be some compression involved. But then I had the same problems was you where the image would refuse to write. I downloaded another image program(WinImage) and it said they were invalid image files.
I also tried making a backup image with this program and it actually produced an image size comparable to the card, so while I haven't tried writing these images yet(don't have another 16Gb card to use)it seems to actually be working.
Anyone else having this problem with Win32DiskImager?
Click to expand...
Click to collapse
I read somewhere that some people had issues with certain versions of Win32DiskImager. I'll see if I can find the recomended version.
Please keep in mind that the Image size is usually proportional to the card you Read from(ie: 4gb card= 4gb image). If you use dd there is away around this in that it'll only copy used space but generally if you have 4gb of data you'll get a 4gb image. So using this method is only useful if restoring to the same size card or moving to a bigger card; unless you manually delete files and shrink partitions before backup.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
I have a working copy of Nook Froyo Customized (0.6.8/v4) on an uSD card (Transcend 8GB/class 6). It is a dual boot enabled image so I can press 'n' to boot onto the card and not press 'n' to boot onto the emmc.
I use Win32DiskImager (v 0.2) to read an image of the card to my PC.
I use Win32DiskImager (v 0.2) to write that image to a new uSD card (SanDisk 8GB/class 4).
I verify the partition layout of the uSD card with EASEUS Partition Manager.
Now the problem...
When I boot without the card everything is fine.
When I try to boot with the card inserted, nothing happens.
I'm confused why the NC isn't booting.
Any recommendations?
UPDATE: I put the original card back into the machine and can boot/dualboot without issue.
I also noted that I cannot always 'see' the new card when the Nook is in stock mode.
byronczimmer said:
I have a working copy of Nook Froyo Customized (0.6.8/v4) on an uSD card (Transcend 8GB/class 6). It is a dual boot enabled image so I can press 'n' to boot onto the card and not press 'n' to boot onto the emmc.
I use Win32DiskImager (v 0.2) to read an image of the card to my PC.
I use Win32DiskImager (v 0.2) to write that image to a new uSD card (SanDisk 8GB/class 4).
I verify the partition layout of the uSD card with EASEUS Partition Manager.
Now the problem...
When I boot without the card everything is fine.
When I try to boot with the card inserted, nothing happens.
I'm confused why the NC isn't booting.
Any recommendations?
UPDATE: I put the original card back into the machine and can boot/dualboot without issue.
I also noted that I cannot always 'see' the new card when the Nook is in stock mode.
Click to expand...
Click to collapse
What are the specs of your new card?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
What are the specs of your new card?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
Old card: Transcend 8GB/Class 6
New card: SanDisk 8GB/Class 4 {purchased sealed from Radio Shack}
I am trying to 'downgrade' the card class based on another thread indicating that higher random Write numbers are preferrable. I've benchmarked both of these cards and the SanDisk (new) has a much better Random Write speed (~150 IOPS on the SanDisk vs ~3 IOPS on the Transcend).
The boot data is there - I can see it from the mountable 'boot' partition that Windows can actually see.
I've burned 4 workable cards with this rig and the software tools (two Nookie-Froyo-Custom cards v4 {the one I'm copying and one for my wife's nook}, a sample of HoneyComb and a test run of NFYCv6).
This is the first card I've not been able to boot from easily -- but also the first time I've not used a provided ROM image and am instead trying to backup/copy my own settings (because I'd prefer to just hop cards than re-download everything and redo all my settings).
My next steps are:
1) Try flashing one of the previously working provided ROMs to the new SanDisk card to see if it works. {This test would indicate that the problem is the image pulled from my current NFYCv4 card.}
2) Try using another SanDisk 8GB/4 card with my backed up image. {This test would indicate that the problem is the card, which seems unlikely}
3) Last Ditch: Try upgrading to Win32DiskImager v0.3 (just noticed that they had a new version out).
Any other suggestions? I'd prefer to be able to use this card if possible.
If #1 proves successful - any recommendations on why I'm not getting a clean image?
One other note: I'm on a 64 bit Vista Machine using an internal card reader, but that shouldn't matter.
byronczimmer said:
Old card: Transcend 8GB/Class 6
New card: SanDisk 8GB/Class 4 {purchased sealed from Radio Shack}
I am trying to 'downgrade' the card class based on another thread indicating that higher random Write numbers are preferrable. I've benchmarked both of these cards and the SanDisk (new) has a much better Random Write speed (~150 IOPS on the SanDisk vs ~3 IOPS on the Transcend).
The boot data is there - I can see it from the mountable 'boot' partition that Windows can actually see.
I've burned 4 workable cards with this rig and the software tools (two Nookie-Froyo-Custom cards v4 {the one I'm copying and one for my wife's nook}, a sample of HoneyComb and a test run of NFYCv6).
This is the first card I've not been able to boot from easily -- but also the first time I've not used a provided ROM image and am instead trying to backup/copy my own settings (because I'd prefer to just hop cards than re-download everything and redo all my settings).
My next steps are:
1) Try flashing one of the previously working provided ROMs to the new SanDisk card to see if it works. {This test would indicate that the problem is the image pulled from my current NFYCv4 card.}
2) Try using another SanDisk 8GB/4 card with my backed up image. {This test would indicate that the problem is the card, which seems unlikely}
3) Last Ditch: Try upgrading to Win32DiskImager v0.3 (just noticed that they had a new version out).
Any other suggestions? I'd prefer to be able to use this card if possible.
If #1 proves successful - any recommendations on why I'm not getting a clean image?
One other note: I'm on a 64 bit Vista Machine using an internal card reader, but that shouldn't matter.
Click to expand...
Click to collapse
Have you tried doing a complete Format before burning the Backup?
Try using this program to do a Format with the Following options:
http://www.sdcard.org/consumers/formatter_3/
Open Options and Select the Following:
-Format Type "Full(Erase)"
-Format Size Adjustment "OFF"
Many problems I've encountered with SD cards were solved when using this Program to format.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Have you tried doing a complete Format before burning the Backup?
Try using this program to do a Format with the Following options:
http://www.sdcard.org/consumers/formatter_3/
Open Options and Select the Following:
-Format Type "Full(Erase)"
-Format Size Adjustment "OFF"
Many problems I've encountered with SD cards were solved when using this Program to format.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
I'll give that a try when I'm with the machines again.
For the record, I tried to image to the card:
1) Without formatting it
2) After formatting it from the Windows Vista 64 PC
3) After formatting it from the Nook Color
I came very close to booting Ubuntu on the PC and checking the partitions with gparted to see if there was some hidden partition that was fouling me up, but I do that from a CD ROM and it's a very long process to get it loaded, so it is always a last resort.
I'll report in if this works - thank you for your replies so far, they have been very helpful.
Also you not getting a clean backup could be 2 things:
- Because of the Formatting problems had before using the above Formatter
or
- Win32DiskImager isn't making a Good Image which is very possible.
I have always gotten better results using DD in Linux.
(NOTE: You could always install Ubuntu using the Window Installer, this doesn't partition your disk, instead it Installs Ubuntu like a Program into a Virtual Disk Image. Pop the LiveCD while in Windows or Download from ubuntu.com. You just reboot your PC and Select Ubuntu from the Startup list. When you don't need it anymore Boot into Windows and Uninstall it from Add/Remove Programs in the Control Panel, just like a regular Program.)
Try going into Ubuntu and use the DD method in my OP to Backup the image and then use this command to burn the Image to the New Card:
Code:
REMOVE BRACKETS
cd [Location of Image]
sudo dd if=[Name of Backup Image].img of=/dev/[New Card's Mount ID] bs=1M
You could also try the Manual method.
-First use the above Formatter on the new Card
-Now Boot into Ubuntu and Open terminal and type these Commands:
Code:
sudo apt-get install gparted
gparted
Now in the Partition Manager that has appeared Partition your SD card similarly to your Old card.
NOTE: Make sure you Format with the same filesystems, as the 1st and 4th use FAT32 while the 2nd and 3rd use EXT3 or EXT4
-Now Manually copy all the files from the Old Card to their Respective Partitions on the New Card
This is a really advanced method and it's not for Everybody.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Also you not getting a clean backup could be 2 things:
- Because of the Formatting problems had before using the above Formatter
or
- Win32DiskImager isn't making a Good Image which is very possible.
I have always gotten better results using DD in Linux.
(NOTE: You could always install Ubuntu using the Window Installer, this doesn't partition your disk, instead it Installs Ubuntu like a Program into a Virtual Disk Image. Pop the LiveCD while in Windows or Download from ubuntu.com. You just reboot your PC and Select Ubuntu from the Startup list. When you don't need it anymore Boot into Windows and Uninstall it from Add/Remove Programs in the Control Panel, just like a regular Program.)
Try going into Ubuntu and use the DD method in my OP to Backup the image and then use this command to burn the Image to the New Card:
Code:
REMOVE BRACKETS
cd [Location of Image]
sudo dd if=[Name of Backup Image].img of=/dev/[New Card's Mount ID] bs=1M
You could also try the Manual method.
-First use the above Formatter on the new Card
-Now Boot into Ubuntu and Open terminal and type these Commands:
Code:
sudo apt-get install gparted
gparted
Now in the Partition Manager that has appeared Partition your SD card similarly to your Old card.
NOTE: Make sure you Format with the same filesystems, as the 1st and 4th use FAT32 while the 2nd and 3rd use EXT3 or EXT4
-Now Manually copy all the files from the Old Card to their Respective Partitions on the New Card
This is a really advanced method and it's not for Everybody.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
Interesting news with Windows Installer, I'll probably give that a try. Of course I'm planning on recapping this machine into a Windows 7 environment (and blowing away a lot of the slow clagginess it's developed lately) but that's another story.
In the meantime, if I do the repartitioning method (which I'm comfortable with), I have a query...
Originally this was a 2GB image and I simply increased the 4th partition (sdcard/FAT32). I don't have a lot of media - most of my utility comes from applications I've downloaded. Thehe SD card space is there when I need it, but I'd rather have more 'native' app room (Everything is running off of the card anyway) which means I'd want to boost the other partitions to reasonable levels, especially the apps portion.
If it comes to doing a full rebuild of a card, I might as well monkey with the partitions to give me more room, so are there any recommended sizing or maximum sizes I should be aware of?
Also you not getting a clean backup could be 2 things:<br />
- Because of the Formatting problems had before using the above Formatter<br />
or<br />
- Win32DiskImager isn't making a Good Image which is very possible.<br />
I have always gotten better results using DD in Linux.<br />
<br />
(NOTE: You could always install Ubuntu using the Window Installer, this doesn't partition your disk, instead it Installs Ubuntu like a Program into a Virtual Disk Image. Pop the LiveCD while in Windows or Download from ubuntu.com. You just reboot your PC and Select Ubuntu from the Startup list. When you don't need it anymore Boot into Windows and Uninstall it from Add/Remove Programs in the Control Panel, just like a regular Program.)<br />
<br />
Try going into Ubuntu and use the DD method in my OP to Backup the image and then use this command to burn the Image to the New Card:<br />
<br />
REMOVE BRACKETS<br />
cd [Location of Image]<br />
sudo dd if=[Name of Backup Image].img of=/dev/[New Card's Mount ID] bs=1M<br />
<br />
<br />
You could also try the Manual method.<br />
<br />
-First use the above Formatter on the new Card<br />
-Now Boot into Ubuntu and Open terminal and type these Commands:<br />
<br />
sudo apt-get install gparted<br />
gparted<br />
<br />
Now in the Partition Manager that has appeared Partition your SD card similarly to your Old card.<br />
NOTE: Make sure you Format with the same filesystems, as the 1st and 4th use FAT32 while the 2nd and 3rd use EXT3 or EXT4<br />
-Now Manually copy all the files from the Old Card to their Respective Partitions on the New Card<br />
<br />
This is a really advanced method and it's not for Everybody. <br />
<br />
____________________________________________________<br />
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
<br />
<br />
Interesting news with Windows Installer, I'll probably give that a try. Of course I'm planning on recapping this machine into a Windows 7 environment (and blowing away a lot of the slow clagginess it's developed lately) but that's another story.<br />
<br />
In the meantime, if I do the repartitioning method (which I'm comfortable with), I have a query...<br />
Originally this was a 2GB image and I simply increased the 4th partition (sdcard/FAT32). I don't have a lot of media - most of my utility comes from applications I've downloaded. Thehe SD card space is there when I need it, but I'd rather have more 'native' app room (Everything is running off of the card anyway) which means I'd want to boost the other partitions to reasonable levels, especially the apps portion.<br />
<br />
If it comes to doing a full rebuild of a card, I might as well monkey with the partitions to give me more room, so are there any recommended sizing or maximum sizes I should be aware of?
Click to expand...
Click to collapse
Not really. Just make sure you have enough space on each partition to fit the Old data.
Also just letting you know they'll have the sleep issue ironed out of CM7 soon. So you might want to consider switching ROMs instead of just imaging your old ROM. If you do deside to swith I reccomend using this thread to do it:
[ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
japzone said:
Not really. Just make sure you have enough space on each partition to fit the Old data.
Also just letting you know they'll have the sleep issue ironed out of CM7 soon. So you might want to consider switching ROMs instead of just imaging your old ROM. If you do deside to swith I reccomend using this thread to do it:
[ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
Click to expand...
Click to collapse
That thread is on my watchlist and when/if the CM7 sleep issue and battery life while resting issues are ironed out, I'll probably make the jump.
In the meantime, I have a short time to get a 'good enough' solution in place that I can rely on. Once I have such a card built, I can start experimenting on other avenues. It is my hope that a lower class SD card will repair most of the force-close issues I'm having with this current ROM, and that will give me a baseline for future endeavors.
I've got a list of things to try tonight. I hope the solution happens earlier and not later in the cycle.

Can't read/write even rooted!!!

Hi to all Devs,
Currently i have an issue with my evo5 rom installed and locked but "ROOTED" bootloader (Z1). The issue is that i cannot move any app to external sd card nor i am able to backup up with (GOBACKUP)!!! When i open gobackup it the pops up message window says
" READ/WRITE/SDCARD canot identify backups,
SD Card might damage!
1. Recommend to copy GOBackup folder to other SD Card to try again.
2: If it happened after flashing a new ROM, the ROM might deny to Read/Write SD Card, can try another ROM.
Please, i have uploaded already all my apps from my previous GB installed phone, and try to recover them so that i can get my contacts and all sms messages.
Appreciate for any help..
Apply the third party write to SD card fix from the general section.
gregbradley said:
Apply the third party write to SD card fix from the general section.
Click to expand...
Click to collapse
Firstly thanks for the answer mate. I've rooted my device by installing XZDualrecovery of "NUT". And afterwards flashed the JFXPERIAS's (EVO5) ROM for Z1 C6903.. I uploaded the screenpic of the popup window here. I've installed already third party apps like SDFIX and NextApp SDfix that supposed to to work, but they didn't, however it ought to be. Do you think the issue is because of that my device is bootloader locked or the ROM itself?
I don't think it's the ROM as no one else is reporting this issue. It could be your SD card?
If you still think it's the ROM, try a different one and see if the problem persists
Ahki767 said:
I don't think it's the ROM as no one else is reporting this issue. It could be your SD card?
If you still think it's the ROM, try a different one and see if the problem persists
Click to expand...
Click to collapse
I'am doing cloud backup and restore. So it doesnt suppose to be related to the sdcard though? What is the logic of it when i'am trying to restore from cloud to straight internal sdcard?
Tried different SDcard it failed again.
Hi , today i tried the 2 different External SDcards and it failed again, the issue is still there, and i dunno what to do!!! Is Aroma installer do the partitioning of the internal SDcard?
Jacker75 said:
Hi , today i tried the 2 different External SDcards and it failed again, the issue is still there, and i dunno what to do!!! Is Aroma installer do the partitioning of the internal SDcard?
Click to expand...
Click to collapse
I dont know if this helps, but if you really need your SD card, I suggest you make a nandroid backup, SD card backup, and flash back to Sony stock rom with root and the SD card fix. Format the SD card again through your phone Settings > Storage > Format SD card. Try again.
If that doesn't work, could be a faulty card or your SD card reader is bad (unlikely).
kentexcitebot said:
I dont know if this helps, but if you really need your SD card, I suggest you make a nandroid backup, SD card backup, and flash back to Sony stock rom with root and the SD card fix. Format the SD card again through your phone Settings > Storage > Format SD card. Try again.
If that doesn't work, could be a faulty card or your SD card reader is bad (unlikely).
Click to expand...
Click to collapse
I have tried a different SDcards too, but unfortunately it didn't do the trick too. But, i have installed the stock 534 firmware and dualrecovery then it worked fine. But, when i installed the EVO5 ROM the issue occured again and again... I think it's because of somehow the AROMA's partitioning or something related to it... I'am totally messed up...
Jacker75 said:
I have tried a different SDcards too, but unfortunately it didn't do the trick too. But, i have installed the stock 534 firmware and dualrecovery then it worked fine. But, when i installed the EVO5 ROM the issue occured again and again... I think it's because of somehow the AROMA's partitioning or something related to it... I'am totally messed up...
Click to expand...
Click to collapse
I will say it again, since android 4.3+ third party apps cannot write to SDcard.
gregbradley said:
Apply the third party write to SD card fix from the general section.
Click to expand...
Click to collapse
Try doing it manually as opposed to using apps.
gregbradley said:
I will say it again, since android 4.3+ third party apps cannot write to SDcard.
Try doing it manually as opposed to using apps.
Click to expand...
Click to collapse
Read the above posts please...
Jacker75 said:
Read the above posts please...
Click to expand...
Click to collapse
I have done, please read mine.
I say to try and do it manually by editing the file yourself instead of using apps.
If it works on a 534 FW (android 4.2) but not on later FW (Android 4.3+) then its not the phone, not the sdcard but the platform.xml file in system/etc/permissions
gregbradley said:
I have done, please read mine.
I say to try and do it manually by editing the file yourself instead of using apps.
If it works on a 534 FW (android 4.2) but not on later FW (Android 4.3+) then its not the phone, not the sdcard but the permissions file....
Click to expand...
Click to collapse
Now i got what you tried to mention. I've read about it, so i will have to edit the XML file? Well, that was the only way i didn't try. Would you paste the link of it to here please so i can easly go through it.
Thanks anyways mate.
http://bit.ly/1vvdkJG
It could also be that you have not disabled sony RIC so you are losing the ability to mount system after a reboot. The apps work by changing the file after each reboot, whereas if you do it manually it stocks because you are actually changing the file
gregbradley said:
http://bit.ly/1vvdkJG
It could also be that you have not disabled sony RIC so you are losing the ability to mount system after a reboot. The apps work by changing the file after each reboot, whereas if you do it manually it stocks because you are actually changing the file
Click to expand...
Click to collapse
Unfortunately mate, the permisson.xml settings didn't help either. You can check the permissions below. I edited in ROOT_explorer PRO.
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORA GE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
Jacker75 said:
Unfortunately mate, the permisson.xml settings didn't help either. You can check the permissions below. I edited in ROOT_explorer PRO.
Click to expand...
Click to collapse
Since I've been struggling with this for a bit, I thought I'd post on how I finally got around it. It turns out that nothing was disabling the RIC, which protects /system from being written. I don't exactly understand how/why, but this was also preventing my modified permissions.xml from taking effect. I have XZ Dual Recovery installed, so all I had to do was enable the init.d functionality, which by default will disable the RIC during boot.
After that, everything's humming along nicely.
EDIT: I was wrong about this (but that above is still totally valid) - in my case, I ended up getting things working with a different SD card. My normal SD card, somehow, stopped being writable. It *acted* like it was writable, but changes were never committed. I couldn't even format it. I RMA'd it to Sandisk.
Backup you files to your PC, format sdcard with any formatter with FAT32 option. Now in your phone with sdcard and with the ROM you want running, see if you need to format it through android on Status Bar then do it. This helped me out when I switched phones (WT19 to C6903).

[Q] SD Card Write Fix

SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
pressagny27 said:
SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
Click to expand...
Click to collapse
Does Root Explorer have root access? Also make sure you are using the editor to make changes.
pressagny27 said:
SD Card Write Fix
Just edit etc/permissions/platform.xml (using root explorer) as shown below...and reboot...
add line:
<group gid="media_rw" />
Now all apps will be able to write to external SD Card... This is a temporary manual fix until we have a working custom recovery).
I am rooted. I followed the direction and it keeps telling that it cannot save the file. I am puzzled.
Click to expand...
Click to collapse
Make sure you are doing it in the external storage section.
Glad I found this. I just brought my brand new baby home from the store this afternoon. As soon as I tried to delete some photos from folders on the SD card using Quickpic (photo app), I got the error. I understand the problem, but quite frankly, I don't understand why this issue exists only with the ext card, and not the internal storage. The skeptic/conspiracy-theorist part of me sees it as Google's way of making ext cards so uncomfortable and impractical to use (without root), that more people will start using internal storage exclusively - primping them for the Nexus (no ext SD) devices.
In any case, I didn't want to root on day 1. I'm frustrated enough about this that I'm really just about ready to return it and stick with my faithful Note 2.
Can these permission workarounds be performed without rooting?
ETA - Never mind - I'm able to manipulate the permissions file, but cannot save w/o root.
owlensteed said:
Does Root Explorer have root access? Also make sure you are using the editor to make changes.
Click to expand...
Click to collapse
Thanks I found the editor to make the change. Now all the apps I am downloading are saved to the SD. Is that normal? .

Somehow my phone doesn't see my internal SD card??

I flashed a ROM and it wouldn't boot so I restored my 5.1 ROM with twrp. Now somehow my phone doesn't open the files through file explorer, it sees all the file names, but when I click on them, it says that there empty. The phone recognizes that there is space used in settings and twrp also sees all the files and I even flashed the ROM that worked, but I still can not access files after a reset and new flash. Also when I try to download off chrome, it now says no SD card found as toast message. Is there anyway of making file explorer see the files without rest of sd card, or even a fix with a reset? What about rsd back to stock?
Sent from my XT1053 using XDA Free mobile app
I fixed the issue by going into recovery and selecting fix storage and it worked. It did reset my phone but at least I can use my storage again. My computer wouldn't even see the files. Glad I'm back had me wooried
Sent from my XT1053 using XDA Free mobile app

23.03 Gb of Storage on Marshmallow 6.0

Hi all,
Just bought into the 32Gb Nexus 6 (i know, im a year late!) and coming from a 64Gb Oneplus One i'm trying to find more space!!!
Anyhows......before i setup the phone i flashed the latest Android 6.0, and was looking at the total storage space for the phone and it's 23.03Gb and just wanted to know if that's the right amount of storage space on a 32Gb Nexus 6. I know system, recovery and boot partitions can take a lot, but just wanted to make sure.
Can someone who owns a 32Gb Nexus 6 please look at the total storage space under 6.0 and tell me if i have the right amount?
If it isn't the right amount, is there a tool available that helps recover lost space?
Thanks
Ive got the same space available on my N6 64gb after flashing marshmallow, I had to install twrp and perform a factory reset, and that fixed it. But idk how much space should be available on a 32gb..
Enviado desde mi Nexus 6 mediante Tapatalk
That sounds about right. After a clean flash of Marshmallow on my 64Gb Nexus 6 I only had ~54Gb free. The OS and everything else takes up around 10gigs.
wesleyrpg said:
Hi all,
Just bought into the 32Gb Nexus 6 (i know, im a year late!) and coming from a 64Gb Oneplus One i'm trying to find more space!!!
Anyhows......before i setup the phone i flashed the latest Android 6.0, and was looking at the total storage space for the phone and it's 23.03Gb and just wanted to know if that's the right amount of storage space on a 32Gb Nexus 6. I know system, recovery and boot partitions can take a lot, but just wanted to make sure.
Can someone who owns a 32Gb Nexus 6 please look at the total storage space under 6.0 and tell me if i have the right amount?
If it isn't the right amount, is there a tool available that helps recover lost space?
Thanks
Click to expand...
Click to collapse
you need to factory data reset. i did, and now have 25.98GB....
http://forum.xda-developers.com/nexus-6/help/64gb-stuck-23gb-t2970279
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
I have 25.98 GB available on my 32 GB Nexus 6 with TWRP installed.
just wanted to say thanks for the help guys.....i'm now sitting on 25.98 Gb free which is a VAST improvement over the 23.03 Gb i was getting before!!!
gotta say that's a horrible bug that google have somehow caused, all by flashing Android 6.0 in what i thought was the right way.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
To FIX the missing space, all i did was go to a CMD prompt and run the following commands
fastboot format userdata
fastboot format cache
fastboot reboot
Will have to start again installing apps and such, but getting an extra 3Gb of storage will help with the pain of a 32Gb Nexus 6!
You can use TWRP recovery and use wipe->advanced->data->repair or change filesystem->resize
And you will have back the original size.
Quetzalcoalt_Lp said:
You can use TWRP recovery and use wipe->advanced->data->repair or change filesystem->resize
And you will have back the original size.
Click to expand...
Click to collapse
Interesting, never noticed that before. Presumably that leaves all the file entries within the filesystem untouched?
danarama said:
Interesting, never noticed that before. Presumably that leaves all the file entries within the filesystem untouched?
Click to expand...
Click to collapse
I'm not sure what it does. I know that doing this I recovered my original storage capacity (from 23.03 to almost 26).
I didn't lost any data either.
factory reset from stock recovery also fixes the issue.
did not work for me, tried both methods, fastboot and twrp wipe, I still have 23.03 available. android version is 6.0 build MRA58K rooted
No need to wipe or install a custom recovery!!! All you have to do is boot the phone with another twrp, either with fastboot or using the NRT (this will keep your stock recovery) and do this:
You have an option that will preserve your data: use the new "resize partition" function within recovery.<br />
* Boot to TWRP (version 2.8.7.1 or higher)<br />
* Choose "Wipe" button (do not slide yet!!) then "Advanced Wipe" button.<br />
* Select the Data partition, then "Repair or Change File System" button.<br />
* Choose the Resize button.<br />
* Now you can slide to confirm, and it will expand the partition to it's full potential, without disturbing the data.
Sent from my Nexus 6 using Tapatalk

Categories

Resources