Database Develop

HELP SD card not recognized

Ok this is extremely annoying. I got the g1 and rooted with 1 click rooting cyanogen 4.0.4 rom. It was so simple and worked BTW. Later I used the hardspl so that I could do apps to sd. I have had the phone for 7 months and have used custom roms since I’ve gotten it.
Following this tutorial http://forum.xda-developers.com/showthread.php?t=535232 I tried to partition my 8g sandisk micro sd card. Now I probably destroyed my sd card (Nothing to big). And I am stuck at the g1 screen (pretty big). When ever I try to flash a different rom with a different or even the same rom I get an error acout the sd card “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
With around 8 hours of digging around on forums I have decided that I might have to get a replacement unless someone could help me revert with access that I have to the recovery to allow my sd cards to be recognized.
Note: I didn’t install the Cyanogen ROM - Download v4.0.2 or Cyanogen Recovery 1.4 - Download as I had a better one. Hince my problem, and did use the apps2sd.apk. Things didn’t go wrong until I typed in “upgrade_fs” . After doing so my phone would not boot up after I restarted it.
Something tells me that I changed something in the phone to allow apps to sd partition 2 and I need to be changed back to the default, as I can’t even flash another rom to fix this problem. Any help would be greatly appreciated .

willl your phone boot when you remove the sdcard

My phone will not boot after removing the sd card.

One thing that I forgot to mention above is. While using the phone after my uncessful attemp to partition my sdcard, the top notification bar was displaying "The SD card is blank or using an unsupported file system." After messing with it a bit i decided to reboot but it froze. Being impatient I pulled the battery from the back of the phone.
Looks as if files are missing from the Cyanogen 4.0.4 rom. As when I type “mount sdcard” is displays “mount: mouting /dev/block/mmcblkop1 on /sdcard failed: No such file or directory” Sounds like I am missing mmcblkop1 from my phone now? Apps2sd.apk doesn’t change this file does it? I'm also wondering if you change a file to look somewhere else for the partition part of the sd card? And if so how would you tell it to look for the default?

Tried this "flash_image recovery /sdcard/update-cm-4.0.4-signed.zip" and it displayed this "usage: flash_image [-d] partition file.img" does this delete the partition of the sd card or what is this referring to?

I think you 'bricked' your sd card.
Try format it with SD Formatter.
Worked for me.
Because you did use App2SD, you have erased app data, so setting up your G1 from scratch is your best option.

Ok first of all using that guide to install apps2sd on cyanogen's rom is what messed up your phone. Cyanogen has clear warnings about this in his thread. Now that the damage is done lets fix it. Can you boot into recovery by holding home and pressing power? Is there an option to flash any zip file?

After rereading your post i see that you don't have recovery 1.4.
You need to do step 4 HERE when you're done do step 5 to install cm-recovery-1.4

After trying different things with the console as I posted above the phone allowed me to install the Cyanogen 4.0.4 from the 2gb sd card. For some reason the phone would not allow me to do this before. As it wouldn't recognize the sd card, or that it had 1 for that matter. What would cause this problem? Maybe a faulty sd card? But I swapped to the 2 gb sd card that came with the phone and tried this numerous times before. Glitch? Why work now? I'm so lost.
I'm so glad that this worked this time though..... another save for this g1. Its taken a licking and it keeps ticking. I have dropped it 14 feet from the top of a railcar. I have crippled it 3 times now as it wouldn't allow me to get past the g1 screen. A simple flash from the sd card allowed me fix that problem. I have also dropped it in water. It was submerged for around 6 seconds in a leather carrying case that clips on your belt. Fast thinking allowed me to remove it from the water, pull the back off, and pull out the battery. I allowed it to dry in the car for around 4 hours and then put it in a bag full of those "do not eat" packets that come in most shoes for 24 hrs. Thanks to Walmart for the donation. Probably the best phone that I have ever gotten.
Well looking over the history of the phone I understand now why it may have done this to me. However it shows that by being persistent you can figure out most things. I appreciate all who have made these guides that make my g1 ownership so much fun.
Now go to get that apps2sd working. Another method probably.

I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.

Jnewell05 said:
I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.
Click to expand...
Click to collapse
Unfortunately that guide is still a sticky and someone uses it at least once a week and we end up with your problem every week. ivanmmj added a warning to the guide a few mins ago. I'm glad you are working now. You are correct about apps2sd being included in cyanogen roms. In post 3 HERE I've made a script that will partition your sdcard for you.

Help, partially bricked phone

I’m hoping someone can help me out with my phone. I have been searching the forums but it’s all getting a little much and i just need some advice please.
The background
I flashed my UK sgs (i9000 i think) with a darky modded ROM which has worked fine for about 6 months my phone has become more and more unstable. Seeing as i can work Odin i thought i would flash it again and fix my issues. Then my phone crashed and wouldn’t boot up, it was stuck on the Samsung Galaxy screen, before the flashing S. I then downloaded the official 2.3.3 ROM’s from the link of official Samsung ROM’s from the thread in the General forum and flashed it. This all went fine until i rebooted my phone, it went into recovery mode fine, although i got some error messages about being unable to mount the SD cards (i can add the proper error message tomorrow for you) i cleared user data and cache, rebooted and my phone came up with a new Gingerbread ROM. This was fine until i realised it had not mounted either my Internal or External SD cards. The operating system worked fine but i could not format or mount my SD cards. I then decided to reimage the phone using the same image i had downloaded in case something had gone wrong but i got the same error messages and now i couldn’t boot into the OS. Since this has happened i have downloaded a 2.2.x ROM and flashed that but i still have the same problem. I have also downloaded and flashed the Darky Resurrection ROM but that doesn’t seem to have helped. I have asked Odin to repartition, i have used PIT 512 and a couple of others, 1 and 3 file ROM’s and if i am honest, i have got nowhere apart from a headache.
I think i have some how corrupted the internal SD card and need to reimage all the right folders and stuff but with the huge amount of official ROM’s, custom ROM’s, recovery tools and tips and tricks, my head is just swimming. Can someone please just point me in the right directions and hopefully i can have a working phone in the morning.
Many thanks in advance,
Simon

do you have any lagfix before you flash to the official 2.3.3 ROM’s ?

I'm having a similar issue w/ mine. The external sd wouldn't mount and i had kind of already started the process to update the rom. It was a dumb mistake. i knew the sd wasn't mounting so i used a different phone to mount put the updates on. Nevertheless i can't use my phone, other than to get on clockwork.

I think i may have had a lag fix on it but as i was unable to get my phone to start there was no chance of removing it before i reflashed the phone. Now i just need to get the damn internal SD working again so i can have a working phone, can you help?
Also, sorry if my main post is a little rambling, i wrote it when i got home from the pub drowning my sorrorws and may have been a little drunk...

Ok, now i've had a coffee and my headache is dying down i can add a little more info which will hopefully help.
I just downloaded GT_I9000_XWJS7_XXJPY_XEEJS1 from Darky rom user guides page on restoring a SGS to a stock ROM and followed all of the instructions. the flash in Odin goes just fine, no errors or anything, my phone the reboots, gets to the Samsung Galaxy screen and i get into the recovery mode with the following messages :
Update media. please wait
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
Your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
This is where i then get stuck, my phone will just get stuck in a boot loop and there seems to be no way to get into the phone. This is starting to drive me to dispair now as everything i have tried has failed badly! Does anyone have any idea how i go about recovering from this?

ok so,
-flash froyo firmware (2.2.1 might be better) then flash speedmod kernel
-get into recovery mode and check your phone's file system in lagfix option
-if it is rfs change it to ext4
-if it is ext4 change it to rfs
im not sure about this method but i ever had this preblem after i converted system to rfs (ext4 before)
hope it helps you and tell me that it works or not,thanks.
edit:wrong word

FLash darky's resurrection Rom ...that error caused by you forget disable lagfix before...
or try Flashing a full rom (3files) with .pit to repartitioning your phone... thick repartition...and thats not "Brick" if you can go download mode...
Come on lets see

I once had the same problem. Same error.message. I searched a lot in xda n finally read something which says to flash Rom with 812 pit and eclair (2.1) with 3 files. After flashing the error message came again so I relished using only pda file. Next time it rebooted normally into home screen. Hope it helps
Sent from my GT-I9000 using XDA App

OK, we're getting somewhere now but not there yet. Flashing the speedmod kernel lets me boot the phone which is further than i have got for a day so thats good, but it still won't recognisse any internal or external SD cards, if you look in the settings section it just shows options to format the sd cards.
I tried changing the filesystem to ex4 as recommended but once it reboots when it says it will go to the recovery menu to debug it just presents me with the option to convert it again as it says the filesystem for /data is RFS still.
Any ideas why it would be doing this and why it won't recognise any of the memory cards? I have also noticed that when i connect the phone to my PC now and tell it to go into Mass storage mode, it shows the drives but says there is no media there! I'm very confused by the whole thing now but at least i do have a phone again of sorts!

So i flashed Darky's resurrection ROM and this is now booting up much as the phone was with the speedmod kernel flashed but i still have the same issue where it won't recognise either the external or internal SD cards so i have no storage space at all. Is it possible i have broken them? I assume at least a bit of the internal card is working or the OS wouldn't be there but why can it not see the other half of the card?

Right, after messing about for far too long i have bitten the bulit and sending it in for repairs, i've read through a couple of posts that seem to say it's the only way to fix it so will see how good the Samsung techicians are!
Thanks for all the help though, you've got me a working phone again, even if i can't save anything on it!

[Q] VZW i800 tab data partition hosed.

Alright, so I've got a rooted Verizon OG Galaxy tab (SCH-i800). For the last couple months I've been running this ICS ROM:
-------------------------------------------
http rootzwiki dot com slash topic slash 11697-rom-cdma-aosp-ics-cm9-build101-0418
-------------------------------------------
A couple weeks ago, I plugged in my tab to charge and went to bed. When I woke up in the morning, the tab was powered down. I powered it back on, and it took at least 15 minutes to boot and when it came up the system was giving a warning that it tried to convert the system to an encrypted system and failed. It then said to hit "ok" to format data and reboot factory-fresh. So I said "ok" and tried that. It booted up into the same error screen another 15 minutes and just kept repeating this every time I tried.
So I went into CWM Recovery and tried to do a manual wipe data/cache partition from there. It also appears to have failed.
Lastly, I tried using Heimdall to reflash the tab to 2.3.5 rooted (where I started before the ICS ROM). When I do this, the tab boot-loops at the Verizon Wireless animated screen. If I go into stock recovery I get this error message immediately upon boot:
http i dot imgur dot com slash DSuyt.jpg
If I ignore that and select "wipe data/factory reset", then I get these error messages:
http i dot imgur dot com slash Ofr8s.jpg
As best as I can tell, the /data partition is messed up in some way. I'm GUESSING that due to the encrypted conversion, it's probably no longer formatted as ANY kind of filesystem so linux can't mount it.
I'd love to be able to fix this, but when I plug the tab in to my machine (Win7 64bit), adb doesn't see it.
Could REALLY use some help here. Thanks guys.

Wow that's pretty hard core. Failure to mount cache could be a serious problem. Hopefully someone else can jump in and help as well... I'm afraid there could be a hardware failure. I.e. You may need to go to Samsung to have it repaired (replaced).
Some questions about how you flash to stock 2.3.5:
Did you repartition (flash pit file) when you restock your tab? -- and a just-in-case question -- You did choose a CDMA version of 2.3.5, right?
For the undetacted problem, you need to retry several (or many) times while odin (or heimdell) is started. Sometimes Odin (or Heimdell) will detect the tab before your computer can detect it as unrecognized device.
If you can go pass this detection issue, try to flash cache.rfs from a cdma ROM.
I hope this can solve the problem.
If not than it is almost 100% chance hardware failure, and SAMSUNG service center should know what to replace (I imagine it's the internal SDCard).
Good luck and I hope you are still under warranty.

yappoe said:
Some questions about how you flash to stock 2.3.5:
Did you repartition (flash pit file) when you restock your tab? -- and a just-in-case question -- You did choose a CDMA version of 2.3.5, right?
Click to expand...
Click to collapse
I did not re-partition. I've never been able to find a VZW PIT file, and the PIT's that I've found (Sprint CDMA) I could never get Heimdall to do anything with. I'm sure I've been doing something wrong.
As far as a CDMA version, yeah. I'm using the VZW 2.3.5 Stock Rooted to go back to stock with Heimdall.
You need to retry several (or many) times while odin (heimdell) is started. Sometimes it will detect the tab before your computer can detect as unrecognized device.
Click to expand...
Click to collapse
I've never actually had any real problems with Heimdall recognizing the device (as long as the drivers are installed right) and flashing the firmware. The problem is just trying to recover from this /data corruption.

bdsmchs said:
I did not re-partition. I've never been able to find a VZW PIT file, and the PIT's that I've found (Sprint CDMA) I could never get Heimdall to do anything with. I'm sure I've been doing something wrong.
As far as a CDMA version, yeah. I'm using the VZW 2.3.5 Stock Rooted to go back to stock with Heimdall.
I've never actually had any real problems with Heimdall recognizing the device (as long as the drivers are installed right) and flashing the firmware. The problem is just trying to recover from this /data corruption.
Click to expand...
Click to collapse
I just edited my earlier post.
Try to repartition with a pit file. Moving from ICS to Gingerbread requires different partition system (the EXT to RFS) -- This might be the problem. You can do it with ODIN easily. I'm sure you can use Sprint's PIT file without a problem.
Try that first, if you still have mounting problem, you need to find both dbdata.rfs and cache.rfs from a good CDMA rom.
If after you replace those three things, and you still can't boot it up.. you may have, as I said eariler, fried some hardware.
---------- Post added at 11:04 AM ---------- Previous post was at 10:56 AM ----------
Hey, read this guy's post. He downloaded pit file available with the heimdell and he has verizon tab.
http://forum.xda-developers.com/showpost.php?p=26067940&postcount=2

I'm having the same issue with a friends VZW Tab and I believe the Data partition is screwed up and is in some sort of read-only mode.
I am able to install different roms but can never wipe the data(or cache) partitions.
Once I installed ICS I got the same encryption msg as you.
I think there may be a way to create the data & cache partitions on an SD card.
The other option is replacing the internal flash chip.
bdsmchs said:
Alright, so I've got a rooted Verizon OG Galaxy tab (SCH-i800). For the last couple months I've been running this ICS ROM:
-------------------------------------------
http rootzwiki dot com slash topic slash 11697-rom-cdma-aosp-ics-cm9-build101-0418
-------------------------------------------
A couple weeks ago, I plugged in my tab to charge and went to bed. When I woke up in the morning, the tab was powered down. I powered it back on, and it took at least 15 minutes to boot and when it came up the system was giving a warning that it tried to convert the system to an encrypted system and failed. It then said to hit "ok" to format data and reboot factory-fresh. So I said "ok" and tried that. It booted up into the same error screen another 15 minutes and just kept repeating this every time I tried.
So I went into CWM Recovery and tried to do a manual wipe data/cache partition from there. It also appears to have failed.
Lastly, I tried using Heimdall to reflash the tab to 2.3.5 rooted (where I started before the ICS ROM). When I do this, the tab boot-loops at the Verizon Wireless animated screen. If I go into stock recovery I get this error message immediately upon boot:
http i dot imgur dot com slash DSuyt.jpg
If I ignore that and select "wipe data/factory reset", then I get these error messages:
http i dot imgur dot com slash Ofr8s.jpg
As best as I can tell, the /data partition is messed up in some way. I'm GUESSING that due to the encrypted conversion, it's probably no longer formatted as ANY kind of filesystem so linux can't mount it.
I'd love to be able to fix this, but when I plug the tab in to my machine (Win7 64bit), adb doesn't see it.
Could REALLY use some help here. Thanks guys.
Click to expand...
Click to collapse

bdsmchs said:
Alright, so I've got a rooted Verizon OG Galaxy tab (SCH-i800). For the last couple months I've been running this ICS ROM:
-------------------------------------------
http rootzwiki dot com slash topic slash 11697-rom-cdma-aosp-ics-cm9-build101-0418
-------------------------------------------
A couple weeks ago, I plugged in my tab to charge and went to bed. When I woke up in the morning, the tab was powered down. I powered it back on, and it took at least 15 minutes to boot and when it came up the system was giving a warning that it tried to convert the system to an encrypted system and failed. It then said to hit "ok" to format data and reboot factory-fresh. So I said "ok" and tried that. It booted up into the same error screen another 15 minutes and just kept repeating this every time I tried.
So I went into CWM Recovery and tried to do a manual wipe data/cache partition from there. It also appears to have failed.
Lastly, I tried using Heimdall to reflash the tab to 2.3.5 rooted (where I started before the ICS ROM). When I do this, the tab boot-loops at the Verizon Wireless animated screen. If I go into stock recovery I get this error message immediately upon boot:
http i dot imgur dot com slash DSuyt.jpg
If I ignore that and select "wipe data/factory reset", then I get these error messages:
http i dot imgur dot com slash Ofr8s.jpg
As best as I can tell, the /data partition is messed up in some way. I'm GUESSING that due to the encrypted conversion, it's probably no longer formatted as ANY kind of filesystem so linux can't mount it.
I'd love to be able to fix this, but when I plug the tab in to my machine (Win7 64bit), adb doesn't see it.
Could REALLY use some help here. Thanks guys.
Click to expand...
Click to collapse
Did you ever get this sorted out? I can't believe ICS roms can fry a device so badly. From what you wrote, it looks like I'm in the same boat, but all threads lead to nowhere.

This sounds like the ICS Encryption Unsuccessful bug. There are reports of Captivate owners (and probably others) who have seen this message at boot, and were left with broken phones. It seems the internal storage was permanently broken or at least locked. So far there's no real explanation what's causing it, or how to fix it. There's a workaround, switching the internal storage with the external storage. I don't think Tabs have been damaged permanently, However, these reports seem to occur more nowadays, so some may have been burned. I've seen this message a couple of times myself, but the Tab was working again after reboot, though it did a kind of factory reset every time. However I noticed it seemed to occur more frequently the longer I was running ICS. Restocking to GB with Kies even failed initially, and only succeeded with an emergency recovery. For the time being I've decided to stay with CM 7. I do hope JB will fix it, and it will be safe to run it on the Tab.

I can get into CWM recovery and put the Tab into Download mode, and the battery takes a charge. I refuse to accept that a spontaneous encryption could brick a device. I'm going to try this, though I've never used ADB, so I have a lot of learning to do (any help would be appreciated still):
http://0xfeedface.org/blog/lattera/2012-06-04/installing-cm9-encrypted-android-tablet

I find it very interesting that people that converted there tabs to mtd to run ics are experiencing this issue. Has anybody experienced this issue running a stock rom?
Sent from my SPH-D700 using Tapatalk 2

DaKillaWilla said:
I find it very interesting that people that converted there tabs to mtd to run ics are experiencing this issue. Has anybody experienced this issue running a stock rom?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Not that I've seen. I was leery about trying something like this, precisely because it requires a change from which you seemingly can't recover. Everybody says "restock with Overcome." Welllll...that doesn't work for the CDMA Tabs (wish I knew that before). I've had the Tab since it came out, so it's not a terribly painful loss, but I certainly would have preferred it not happen. Now, I'd be tickled pink just to get the Tab back to stock/unrooted
I still haven't tried the technique in the guide I linked to (have a lot to learn about adb).
Oh, and bdsmchs moved on. He got some help on rootzwiki which indicated his Tab was physically damaged after his ICS upgrade, and apparently had insurance to cover a new one. So...word to the wise.
I don't think my Tab is as bad as his was, but we'll see.

Try odining the sprint stock tar with its pit (repartition checked), and see if that brings it back. I notice alot of people running ics on the tab have said that it gets warm and the battery drains while its off. Mine was doing that on ics, so I figured something wasn't right. So I went back to a sprint stock ext4 rom. My guess is its either the ics kernel causing it, or maybe the chips in our tab just don't like the mtd partitions. For me its just not worth the risk. I could probably run a themed launcher to get that ics feel if I want. As long as everything just works I'm happy...
Sent from my SPH-D700 using Tapatalk 2

Just to clarify, the Encryption unsuccessful problem doesn't have to do with encryption. What happens is that during boot the Tab is unable to read the internal storage. It then assumes it must be encrypted but is naturally unable to decrypt it. It then gives up with the EU message and tells you to reboot. However, the internal storage failure may be caused because ICS uses a function that in combination with a bug in the controller firmware that is said to break the internal storage. If the internal storage is broken because of this, rebooting will not work. Unfortunately not even flashing will work. As far as I know this problem doesn't occur on Gingerbread, only on ICS. I've seen this problem a number of times on ICS, and it seemed to occur more and more the longer I ran ICS. For now I've gone to CM 7.2 to be safe, but I'm hoping JB doesn't have the problem.

Is the cm7 your running ext4 or mtd?
Sent from my SPH-D700 using Tapatalk 2

ableeker said:
Just to clarify, the Encryption unsuccessful problem doesn't have to do with encryption. What happens is that during boot the Tab is unable to read the internal storage. It then assumes it must be encrypted but is naturally unable to decrypt it. It then gives up with the EU message and tells you to reboot. However, the internal storage failure may be caused because ICS uses a function that in combination with a bug in the controller firmware that is said to break the internal storage. If the internal storage is broken because of this, rebooting will not work. Unfortunately not even flashing will work. As far as I know this problem doesn't occur on Gingerbread, only on ICS. I've seen this problem a number of times on ICS, and it seemed to occur more and more the longer I ran ICS. For now I've gone to CM 7.2 to be safe, but I'm hoping JB doesn't have the problem.
Click to expand...
Click to collapse
In your experience, did you ever know of anyone recovering? It looks like I won't be able to use adb to follow the steps I linked to, since I can't exactly select "USB Debugging."

well, like ableeker said,
the encryption unsuccessful message has nothing to do with encrypting your android to avoid people reading your /data (which is what your link points to).
It just can't read your /data and "think" it is encrypted because it reads gibberish.
In other words, toasted NAND chip.

priyana said:
well, like ableeker said,
the encryption unsuccessful message has nothing to do with encrypting your android to avoid people reading your /data (which is what your link points to).
It just can't read your /data and "think" it is encrypted because it reads gibberish.
In other words, toasted NAND chip.
Click to expand...
Click to collapse
Thanks for your insight. Some of the threads I've read pointed to either that, or the fact that the partition had been encrypted, but without knowing the key, you'd never get back into the partition:
"Here's the bad news:
Your partitions for /data and /sdcard are no longer accessible. They may be encrypted with a key you cannot know (completely lost) or just inaccessible (data restoration possible, but not at this time."
So I thought the procedure I linked to might be able to help recover the partition. I have no idea, though, so I'm grasping at straws. Just weird that most of what I've been reading is on custom ICS roms.

So did anyone find a solution to this? I also started running cyanogenmod 9 and after 2 days my tablet wouldnt boot beyond the startup screen. Found out through cw recovery that the /data partition is corrupted. I have tried multiple pit files but no luck yet.
One workaround I was thinking was to mount the /data partition on the external sd card and at least get the tablet working instead of throwng away. Im guessing that the internal nand flash is soldered.
So how does mount the /data to the external sd card? a softlink maybe?!

My friend bought the verizon sch-i800 tab. i was able to use Heimdall and flash over all the files (cache, recovery, ect.) but it tries to go in recovery to do a factory reset and says it cant find file or dir to anything and fails. im so confused.... i used the right everything and it flashed it all over to not read it??...
--wiping data...
formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache...
E:format_volume: rfs format failed on /dev/block/mmcblik0p1
data wipe complete.
E:failed to mount /preload (no such file or directory)
E:install_application_for_customer:cant mount /preload
your storage not prepared yet, please use ui menu for format and reboot actions.
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
E:failed to mount /cache (no such file or directory)

[Q] Internal SD Card Seems Shot!

Hi there. I've had my Galaxy S for nearly 2 years now, foolishly enough, I decided to play around with it. I managed to root it (not sure what firmware I was on, more than likely Froyo) and OC'd the phone, nothing more. After I bricked the phone (no download mode) the next day I managed to get the phone into DL mode and fixed it. However, I think that the SD card (or at least the partition tables or some other kind of information on it) is kaput. The errors I get are as follows:
- Bootlooping, whether it be a fresh flash or a rom i've left it with for a bit
- Turning off unexpectedly and then bootlooping
- Format errors: Can't mount /dev/block/mmcblk0p1 (no such file or directory), E:copy_dbdata_media:Can't mount sdcard your storage not prepared yet, please use ui menu for format and reboot actions.
I've flashed various roms, gingerbread, froyo, stock, custom ics/jellybean roms to see if it changes anything but nothing. I've tried factory resets, hard resets, formatting, and nothing seems to be able to remedy these formatting issues. If there's anything that might be able to fix my phone, I thank you in advance

[Q] Internal/ External Storage cannot be read

Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.

flapsy said:
Hi all
For days I've been flashing all different kinds of things in hope to get my phone fixed, but I just can't find the answer.
So for those of you most kind enough to help, here's what's going on with my captivate (at&t)
I took it out of my pocket last week and the phone was frozen. Sometimes it happens... a quick pull out of the battery and re-insert fixes it in most cases... but not this time.
After restarting the phone was hanging on boot screen (CyanFox bootscreen).
I restarted... 15 minutes on that bootscreen still. I had no idea what was going on.
So I decided to reflash. It was a big decision, seeing as this ROM has been working absolutely fine for weeks, but I needed to get it working.
Soon after getting it into recovery, CWM was saying that it couldn't mount /sdcard
I tried even flashing using Odin to go back to stock following the guide here: http://forum.xda-developers.com/showthread.php?t=1300843 still not working.
Most of them ended up showing that little android loading bar for a second or two, but then get stuck in a boot loop.
I tried flashing many different kernels, and different recoveries, but everything all pointed towards: Unable to mount /sdcard
But alas, finally I found something that more or less works. I flashed the Initial Kernal for Cognition: http://forum.xda-developers.com/showthread.php?t=1127578
And I finally got back into a working device... or so I thought.
The phone is still unable to access the internal SDCARD. Just says 'unavailable'. I tried putting in an external 2GB sdcard, but that reads as Total Space: 00, and Available Space: 00
The external sdcard I know works, because my wife's samsung mini2 reads it just fine.
Multiple formats and it still can't be read.
I tried plugging in the device into my pc and select mass storage, but although the computer detects that the phone is plugged in (in device manager) the 2 drives for internal and external both remain hidden, and cannot be accessed.
I have absolutely no idea what to do next. I've used Odin and Heimdall, Repartitioned, and followed every stickied guide here, but I still can't find what to do.
I really appreciate any help anyone can give me on this.
Just for the record, ADB works just fine from my PC. I can send the commands to the device, but mounting the sdcard still proves impossible at this stage (no file exists).
Thanks again, I look forward to any advice anyone can spare.
Click to expand...
Click to collapse
i had the same problem a couple of weeks ago...
you internal sd card is dead...
you can do nothing about it for now...
if you want to confirm open your camera app and see if you can take any pictures...
if no, then follow the things as i say..
this requires you to do a partition of your external SD card and to that it should be formatted, so take the neccessary backups..
1) download this http://www.mediafire.com/download/sbjd049x4m36pb6/I897UCKI2_noBL_BoogsKernel.rar
2) after flashing this stock firmare with cwm, open up the recovery.
3)follow this guide http://forum.xda-developers.com/showthread.php?t=1447303
4)i couldn't get ICS to work..
5)so you can now use kitkat roms only on the captivate as we have the kernel for 4.4 only with swap sd
6)so after you follow the guide and boot into ICS, copy the rom.zip which you want to flash and the neat kernel swap sd, which can be found here http://www.mediafire.com/download/s34o69u39u66x8n/NeatKernel_v1.03-[02-08]-cma-swap-captivate.zip, be sure to thank the developer here http://forum.xda-developers.com/showthread.php?t=2548081
7)so flash the kitkat om which you want to use,and then flash the neat kernel after flashing the rom after that you can flash the gapps and reboot..
if you do everything like i said, your cappy will be up and working again..

Sir, you are a gentleman and a scholar
Although it didn't go exactly as planned step by step, with your instructions I finally managed to get it working on my 2GB external card.
Here was the process I did
1) Downloaded CM11, Gapps, Stock Kernal and the SwapSD kernal you linked
2) Flashed the stock kernal, the phone just went on a rebooting spree.. but after a few attempts I got it into recovery using the 3 finger combo
2) Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1447303 to partition the external SD card. (Since I have only a 2GB card, I partitioned 1GB for data, and 0MB for swap)
3) Done the classic wipe sys/ cache/ data
4) (Here is where things changed a bit for me, as I couldn't boot into ICS either. And no other rom would work at this point) I installed the new SwapSD kernal to get a newer version of CWM by mounting USB storage via CWM and copying the files to there.
5) The device rebooted a couple of times during install, but it automatically went straight back into the newer CWM.
6) Installed CM11, let that finished and installed Gapps straight after.
7) Rebooted and the phone is now reading my external sd card as its internal storage, which is fantastic
Although with it's limited storage and broken internal storage, it still needs replacing, but at least I now have a device from which I can still run a few apps on regardless.
So thank you again dude
*edit* just need to figure out why the adb drivers decided to not work anymore.
Sometimes I hate having windows 8...