Database Develop

Blank SD card/ Unsupported Filesystem

Using Cyan's tutorials on his wiki, I rooted successfully and am now running Cyan's latest, with his 1.4 recovery.
I finished running the apps2SD tutorial and now the print command reads 2 partitions
Number Start End Size File system Name flags
1 17.4kb 7587MB 7587MB fat32 msftres
2 7587MB 8099MB 512MB ext4
But I'm getting a notification as soon as it boots into android that says.
Blank SD card
SD card blank or has unsupported filesystem
All the amounts under SD card & phone storage settings menu reads: Unavailable. And my internal phone storage reads 46.82MB

Download the recovery image in my sig and use that parition manager.

Thanks alot evilkorn. Worked perfectly.
Cyan should implement something like that into his recovery

CaliLove310 said:
Thanks alot evilkorn. Worked perfectly.
Cyan should implement something like that into his recovery
Click to expand...
Click to collapse
Well its based of 1.4 and cyan said hes spending more time on his roms because Amon_RA made such a good recovery lol

CaliLove310 said:
Thanks alot evilkorn. Worked perfectly.
Cyan should implement something like that into his recovery
Click to expand...
Click to collapse
I think I spoke to soon though. Everything works on the phone, but it wont mount on WinXP.
It mounts on my mac, but when i try to transfer anything to it it gives me an erorr.
The Finder can’t complete the operation because some data in “data” can’t be read or written.
(Error code -36)
"data" (in parantheses) Is the name of the folder im trying to copy to the SD

Mount the file system as -rw, you should be able to find the commands on here some place. I use root explorer so I don't need to remember it =p.

Is it easier with root explorer? Mind telling me how to use root explorer to mount it as -rw like you said

It says remount as R/W.

to mount as r/w in terminal or adb shell:
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
to mount as r/o in terminal or adb shell:
Code:
mount -o ro,remount /dev/block/mtdblock3 /system

CaliLove310 said:
Is it easier with root explorer? Mind telling me how to use root explorer to mount it as -rw like you said
Click to expand...
Click to collapse
You can do this in ES FileExplorer too and its free.

having same issue
I didn't do anything fancy really.
I'm running a moto droid with the 2.01 update that I received over the air.
Today I launched twidroid and it completely ftoze the whole phone, non responsive even on the hardware buttons. I did a battery pull and upon restart the notification window says sd car blank or file system unsupported.
Tried browsing sd card with astro and it shows blank.
Any suggestions? I have a ton of photos and application settings I don't want to lose.
Thanks in advanced!

itsluy said:
I didn't do anything fancy really.
I'm running a moto droid with the 2.01 update that I received over the air.
Today I launched twidroid and it completely ftoze the whole phone, non responsive even on the hardware buttons. I did a battery pull and upon restart the notification window says sd car blank or file system unsupported.
Tried browsing sd card with astro and it shows blank.
Any suggestions? I have a ton of photos and application settings I don't want to lose.
Thanks in advanced!
Click to expand...
Click to collapse
I fail to properly understand the relevance with the Dream/G1 here..Your asking for help on a Droid in a Dream forum?..Maybe one of the other brotherns can fill in de blanks for me.. Thats like going into art class trying to get help for your driving test or putting cofee in ice cream ..Anywho try reformatting the sd something seems to be corrupted

having same issue
Except I didn't do anything fancy. My phone froze while using twidroid and upon reboot my sd card is blank or unsupported filesystem. How can I get my data back?

itsluy said:
Except I didn't do anything fancy. My phone froze while using twidroid and upon reboot my sd card is blank or unsupported filesystem. How can I get my data back?
Click to expand...
Click to collapse
I had this happen to me when using snes/twindroid/barcode/couple more and the weather widget to...Just format the sd in recovery and check for errors with your pc using a sd card reader.

this is the only
Ace42 said:
I fail to properly understand the relevance with the Dream/G1 here..Your asking for help on a Droid in a Dream forum?..Maybe one of the other brotherns can fill in de blanks for me.. Thats like going into art class trying to get help for your driving test or putting cofee in ice cream ..Anywho try reformatting the sd something seems to be corrupted
Click to expand...
Click to collapse
This thread came up on a google search for my issue. Although its a different phone the issue is the same so I figured it was worth a shot. I could start a new thread I guess but didn't want to overpost.

this is the only
Ace42 said:
I fail to properly understand the relevance with the Dream/G1 here..Your asking for help on a Droid in a Dream forum?..Maybe one of the other brotherns can fill in de blanks for me.. Thats like going into art class trying to get help for your driving test or putting cofee in ice cream ..Anywho try reformatting the sd something seems to be corrupted
Click to expand...
Click to collapse
This thread came up on a google search for my issue. Although its a different phone the issue is the same so I figured it was worth a shot. I could start a new thread I guess but didn't want to overpost.
Reformatting will pretty much guarantee that I lose my data. Any other suggestions?

this happened on my g1
I know the poster was getting flack for having 2.01 on his droid but I have cyanogen 4.9...... whatever he's at as of 12/25/2009.
This happened to me I was sending an sms it froze I popped the batt like I've had to do in the past except this time I'm getting a blank sd card error on boot. B4 I repartition and format is there a recovery option? Preferably something I can do from console since I'm in transit from the holiday?
I imagine since we used similar procedures to fix our "smart" phones maybe our recover procedures will be similar.

evilkorn said:
Download the recovery image in my sig and use that parition manager.
Click to expand...
Click to collapse
Please can you tell me where can I get Download the recovery image app ?
I am new just came from iPhone recently got HTC EVO and I am facing this Issue "SD Card blank or has unsupported file system" I tried everything please help.
thanks
Faisal

I have the same message on my G1
My phone is not rooted, and i don't know what to do!
I tried to format my sd card, i have tried with another card, and nothing; the same message!
I don't know what to do in this case....maybe if you have any solution to my problem.
Here is some info about my phone :
Model number : T-mobile G1
Firmware version: 1.6
Baseband version : 62.50s.17U_2.22.19.26I
Kernel version : 2.6.29-00479-g3c7df37 [email protected]#19
Build no : DRC92

anyone ? !!!!!!!!
i really need some help!!!!!
any solution to root without sd card ?

I could really use some help, *UPDATE* Thanks XDA....

I don't know where to turn. I started a thread about my effed up nook but it got deleted (my fault) I'm completely at my wits end here. I had NookFroyo .68 working just fine on mine but like an IDIOT I thought it would be neat to try out CM7. Big mistake would not get past the animated N screen no matter what. I got the SD version of the Customized Nook Froyo to boot up but its very slow and stuff doesn't work. How do I get a ROM back on the eMMC? Some one suggested I get CWR and a ROM on the card and flash it via CWR off the card onto the eMMC. How exactly do I do this? I CANNOT get the winimage method to work no matter what I do and I don't know WHAT I'm doing wrong. Everytime I direct winimage to the place I've downloaded an image to, theres nothing there....
I thought I ALMOST had it a few minutes ago. I can get the CWR to come up and I flashed the flashable eMMC NF. I got my hopes up as it started to boot BUT OF COURSE NOT - went into a boot loop, constantly doing the N screen over and over. WTF.
I'm desperate here. I'm at the point where I'm willing to pay someone a small fee to help me get this sorted out. I'm going to keep on trying....

on win image, when you go to select the file. you must change the file types it see's to everything. that will let you see the .img file you downloaded.

We are talking about Win32disk imager right? It only gives the *img selection.

KDOG2020 said:
We are talking about Win32disk imager right? It only gives the *img selection.
Click to expand...
Click to collapse
click the arrow and hit ALL FILES

I AM clicking the arrow, there is ONLY *img....
I've heard of an 8 boot reset. How does that work?
I'm reading the "Recovery" thread. Should I do the "repartiion" zip file? I'm starting to think that maybe the problem...
EDIT: Tried the Repartion.zip. No change. Still continously reboots.

I just tried the Nook restore file and it still gets hung up on a different N screen (the Nook symbol). What in the HECK! It wont' go into CWR anymore, says there isn't any room on the card. AN 8GB CARD!!!! I put the card back in the computer and it says its only 115MB! WHAT THE HELL IS GOING ON HERE.
EDIT X2: LOOKS LIKE I GOT IT BACK TO STOCK. WHEW! Now I can start over! Tomorrow after I rest a bit. LOL

KDOG2020 said:
I just tried the Nook restore file and it still gets hung up on a different N screen (the Nook symbol). What in the HECK! It wont' go into CWR anymore, says there isn't any room on the card. AN 8GB CARD!!!! I put the card back in the computer and it says its only 115MB! WHAT THE HELL IS GOING ON HERE.
EDIT X2: LOOKS LIKE I GOT IT BACK TO STOCK. WHEW! Now I can start over! Tomorrow after I rest a bit. LOL
Click to expand...
Click to collapse
This will allow you to get the card back to showing 8gb:
http://www.sdcard.org/consumers/formatter_3/

Hi,
I found this post (in developers/cm7 users thread) very useful for installing
CM7:
http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
It is a little dated (weeks) but very detailed and should hopefully still all work fine.
Some more general information on:
http://nookdevs.com/Portal:NookColor
I find that I never have enough uSD cards to use - so make sure that
you have several spare. The emmc Androids are still in general expecting
an external SD card for storing data such as ebooks etc. and CWM will
backup to the external cards too.
CM7 and Froyo use different disk format types for various partitions, don't know,
but that may be part of your problem?
Your PC won't normally read some of the linux partitions on the SD card
either - hence only 115MB showing. This is the boot partition, formatted with
FAT32 (a PC related format) In general you don't need to reformat this partition,
just update or change some of the files. (Some of the names of formats used include:
FAT32, EXT3 and EXT4)
CM7/17 and CM7/19 Have both been very stable and easy to use for me. I switched
to CM7 from Froyo 6.8 a week or so ago.
Good luck, the Color Nook is a fun device!
Peter

Thanks all I appreciate the help. I used some HP utility to take care of the cards, worked great.

Ok I've got a NF .68 up and running. Titanium backup worked beautifully. SetCPU is running it at 1.1 interactive..... HOWEVER!....
I flashed it with a another version of the CWM flashable .68 NF that I had previously. I tried to reflash the other version and it went to install then stated "Installation aborted". I tried twice and got the same thing. I guess its no big deal since their the same version just this one thats on there had some more tweaks hence the title "Customized".
My question is why did it do that? My guess I was supposed to format or clear the data/system/caches' in CWR. Is that right? If so, which ones precisly do I clear or format before flashing a new ROM? I'm starting to think thats' what happened when I tried to load CM7 (Yes I had CWR 3010) and go me all borked to begin with....
And if someone would like to answer a quick question. What this EXT4 stuff and how does it pertain to flashing ROMs? Thanks guys... Your advice got me back up and running!

KDOG2020 said:
Ok I've got a NF .68 up and running. Titanium backup worked beautifully. SetCPU is running it at 1.1 interactive..... HOWEVER!....
I flashed it with a another version of the CWM flashable .68 NF that I had previously. I tried to reflash the other version and it went to install then stated "Installation aborted". I tried twice and got the same thing. I guess its no big deal since their the same version just this one thats on there had some more tweaks hence the title "Customized".
My question is why did it do that? My guess I was supposed to format or clear the data/system/caches' in CWR. Is that right? If so, which ones precisly do I clear or format before flashing a new ROM? I'm starting to think thats' what happened when I tried to load CM7 (Yes I had CWR 3010) and go me all borked to begin with....
And if someone would like to answer a quick question. What this EXT4 stuff and how does it pertain to flashing ROMs? Thanks guys... Your advice got me back up and running!
Click to expand...
Click to collapse
Always format /system, /data, and /cache. Whatever you do DO NOT format /boot.
As to why you may have had an issue on trying the other ROM. My guess is it has to do with what version of CWR you had been using and wha twas on the device prior to flashing it. I've found if you make say a nandroid backup using 3.0.0.6 or earlier, and are currently using CWR 3.0.1.0 they don't mix well. And I think it has to do with the fact the older CWR version only supported ext3, and the newer one has ext3 and ext4 support. So once you install a ROM using CWR 3.0.1.0 that uses ext4, and then you try to go back to a ROM that is ext3 it just doens't work out like planned.
That all said I not longer flash CWR to eMMC, and I have a bootable sdcard running 3.0.1.0 with all my current and old backup files. Make life much much easier IMO seeing as you can always boot to an sdcard, and all backups are in the correct format and will Restore just fine.

Thanks for the info! I'm sure that will make trying to upgrade to CM7 actually work! LOL!
But first can someone explain to me what this EXT3/4 stuff is?

Different filesystems for Linux/Android. Wikipedia has pages for each if you want google them and get too much info

Too much info? No thanks! As you can see I can barely handle the info I'm getting now!

[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)

[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1

Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (www.goo-inside.me/gapps/gapps-ics-20120317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get...e-cm-9-20120520-NIGHTLY-vibrantmtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/showthread.php?t=1447303

...and to think that I've "lost" a Vibrant about a year ago because such tecniques had not developed yet (back then we had no CM and the modding scene was all about samsung roms).
If that works, "thanks" on behalf of all those which are in the position that I was in. If only I still had the phone, I would had probably made it working one way or another

Yea luckily for me the phone's internal died about 3 days ago.

Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix

ferhanmm said:
Hmm... oddly enough the internal started working again.
Click to expand...
Click to collapse
Good news about this. You are back full and completely. Can you please go to this thread and read the OP and post your findings in it?

The error came up from a phone that was boot looping that was running stock kb5 with the "stock + voodoo kb5" kernel.
I tried flashing stock jfd then ics in attempts to fix the unmountable internal SD data. After that I did receive the encryption bug but only with the initial fix that I applied. But after the second fix I applied the internal was surprisingly brought back to life so I haven't had to deal with the encryption issues yet and I hope never again lol.
Regardless, I'll run those adb commands for you and post them when I see her again. Which should be soon.

ferhanmm said:
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
Click to expand...
Click to collapse
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.

McBang2023 said:
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
Click to expand...
Click to collapse
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat

ferhanmm said:
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
Click to expand...
Click to collapse
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.

McBang2023 said:
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
Click to expand...
Click to collapse
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.

ferhanmm said:
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
Click to expand...
Click to collapse
absolutely. and thanks again

Bump for interest of knowing if anyone else recovered internal memory after doing these steps

So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1

accordex said:
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
Click to expand...
Click to collapse
If you can access your internal sd after flashing stock jfd, then yes your phones storage is fine.
If you flashed eugenes jk2, check storage if it lists as unavailable then yes its messed up.

i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.

McBang2023 said:
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
Click to expand...
Click to collapse
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.

fishman0919 said:
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
Click to expand...
Click to collapse
i would be willing to try it....but the link is broken. so no valid download.
EDIT: i found a workaround. downloading and flashing now. i will post results later.
EDIT 2: after flashing, the phone does similar to if i flashed stock jfd. the only difference is it will restart after showing the vibrant splash scfeen back to the splash screen. on stock, it completely shuts down.

anybody ever try something like this with samsung tab sph-100..?
or think i could try this? what would i need to change?
I received this tab from someone over ebay and have never once been able to get past samsung boot screen.
I have the same errors in recovery mode, have tried a lot in odin but i came to believe from other xda members that there must be some internal memory / nand chip damage.
I just got an sd card in hopes i could try something with sd card.
Is this what i'm looking for?
mind, I've never worked with android before this.. noob status still.
sender said he never had any issues with it before sending, hoping to take his word for it, i think i can return it if nothing ends up working, but he's caught in hurricane at the moment, so i am willing to work on it a few more days.
wonder if somehow magnets thru shipping could have done something?

I doubt magnets messed anything up. My suggestion is go to the section here in xda for your device and ask your question there. I would also find out if the previous owner had a custom ROM?, if so which ROM. Is it rooted and does it have a custom recovery?
All will be important info to find a fix.
Sent from my SGH-T959 using xda premium

Basically what I need is to use this mod to boot my experimental builds on the external sd w/t wiping my main ROM (which would be installed to my phone). Is that possible?
So that whatever happens I could always boot back to stock (what I will have installed in my phone), with some minor tweaking through adb shell of course. It sounds doable, ain't it?

[Q] E: Can't mount /sdcard/ and no files found

Ive been having trouble and flashing roms for the past week trying to get my captivate to boot, but i constanly either get into a boot loop or i load into a black screen.
In CWM 5.1.0.7, when i choose "Install zip from sdcard > Choose zip from sdcard" i get a "E: Can't mount /sdcard/" error.
If i go to "Reformatting, tweaks and more > System Information > Browse directories and files", ill get "No files found." on a few of the directories and my /bin folder only has "init.goldfish.sh" in it. most of them have only bare minimal things in them. (im not sure if this is normal or not)
How should i go about fixing this?

Huhmeister said:
Ive been having trouble and flashing roms for the past week trying to get my captivate to boot, but i constanly either get into a boot loop or i load into a black screen.
In CWM 5.1.0.7, when i choose "Install zip from sdcard > Choose zip from sdcard" i get a "E: Can't mount /sdcard/" error.
If i go to "Reformatting, tweaks and more > System Information > Browse directories and files", ill get "No files found." on a few of the directories and my /bin folder only has "init.goldfish.sh" in it. most of them have only bare minimal things in them. (im not sure if this is normal or not)
How should i go about fixing this?
Click to expand...
Click to collapse
i think your internal storage has been corrupted..

n205des said:
i think your internal storage has been corrupted..
Click to expand...
Click to collapse
Could there be a fix?

Huhmeister said:
Could there be a fix?
Click to expand...
Click to collapse
check out this thread!
http://forum.xda-developers.com/showthread.php?t=2648547

n205des said:
check out this thread!
http://forum.xda-developers.com/showthread.php?t=2648547
Click to expand...
Click to collapse
Thanks a million! I atleast got my phone to start up now lol. Is there really no hope for the internal SD? No way to flash it back to normal? It is a software error afterall.

Huhmeister said:
Thanks a million! I atleast got my phone to start up now lol. Is there really no hope for the internal SD? No way to flash it back to normal? It is a software error afterall.
Click to expand...
Click to collapse
according to me , no there is no hope...
bt according to some users, their sd card came back to life after some time and then got bricked again...
and also no to the stock, it boots up bt cannot really do anything..
you can now use cm10,10.1,10.2, 11 roms using neat kernel..

n205des said:
according to me , no there is no hope...
bt according to some users, their sd card came back to life after some time and then got bricked again...
and also no to the stock, it boots up bt cannot really do anything..
you can now use cm10,10.1,10.2, 11 roms using neat kernel..
Click to expand...
Click to collapse
4 days later, I finally have the time to have one last follow up problem. I've flashed a CM11 nightly and my external sd shows up as my main storage in settings. I can download apps but i still can't access my camera or save pictures from the internet(it tells me "no SD card , and sd card is required to download). Also tested this with the voice recorder, it wouldnt start and told me the same thing.
Is this normal with the method you gave or have i done something wrong?

Huhmeister said:
4 days later, I finally have the time to have one last follow up problem. I've flashed a CM11 nightly and my external sd shows up as my main storage in settings. I can download apps but i still can't access my camera or save pictures from the internet(it tells me "no SD card , and sd card is required to download). Also tested this with the voice recorder, it wouldnt start and told me the same thing.
Is this normal with the method you gave or have i done something wrong?
Click to expand...
Click to collapse
you have done everything right, but you have forgotten to flash the neat kernel..
just flash it and everything wil be back to normal...

n205des said:
you have done everything right, but you have forgotten to flash the neat kernel..
just flash it and everything wil be back to normal...
Click to expand...
Click to collapse
I got it completely working with your advice but when i took the phone out of my pocket it was stuck on the neat kernal loading screen and rebooting it wouldnt help. I decided to flash back to stock and redo the process. I wiped all data etc. in recovery but when i went to partition the sd card again in cwm it finished instantly.
My pc wouldnt read it and even my another phone didnt detect it was there.
I'm assuming the SD card just died, its verbatim 8gig(Not sure if thats a reliable brand or not).
Could this be because i did something wrong is it just a coincidence with the sd card dying? Im buying a sandisk soon anyhow.

Huhmeister said:
I got it completely working with your advice but when i took the phone out of my pocket it was stuck on the neat kernal loading screen and rebooting it wouldnt help. I decided to flash back to stock and redo the process. I wiped all data etc. in recovery but when i went to partition the sd card again in cwm it finished instantly.
My pc wouldnt read it and even my another phone didnt detect it was there.
I'm assuming the SD card just died, its verbatim 8gig(Not sure if thats a reliable brand or not).
Could this be because i did something wrong is it just a coincidence with the sd card dying? Im buying a sandisk soon anyhow.
Click to expand...
Click to collapse
i think it died..
just to ensure longer life, buy a sandisk class 10 sd card..
i bought it!