When I boot up the phone, I get a message in my notification bar saying:
Damaged Internal SD Card.
Not an external memory card. My internal SD card. The one built into the phone. Anyone know if there's a way to fix this? Is there a way to reformat the built in SD card? My computer can't recognize it anymore. Am I pretty much screwed?
I posted this in androidforums as well.
EDIT: I found the "Format Card" option in settings. It's working fine, although the fact that this came up in the first place is very troublesome. Some further information: I did the GPS thing where you dial *#*# and some number, then rebooted my phone. My internal card was fine until I rebooted. That was the first time I got that message of a damaged internal sd card.
dude same thing happened to me today - any way to fix this ?
Format it, and hope you never see those dreadful words again.
norcal einstein said:
Format it, and hope you never see those dreadful words again.
Click to expand...
Click to collapse
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
Click to expand...
Click to collapse
what about when you flash a ROM that comes with LAg fix by default ? and you Disable it all the time can that happen to you? cuz ive flashed but most roms r being gay now with Lag fix ... i disable always might i get that msg? :/
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones
Click to expand...
Click to collapse
This affects the bell vibrants only, the captivates never had this issue.
peachpuff said:
This affects the bell vibrants only, the captivates never had this issue.
Click to expand...
Click to collapse
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
dpmurphy81 said:
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
Click to expand...
Click to collapse
That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.
And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...
The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
fatttire said:
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What was the fix you applied exactly? I'm interested to it. Thanks
I would like to know what else i can try. I am currently.experiencing the same damaged internal sd card issue and have tried reformatting to no avail. It just seems to skip the actual formating. My pc also cannot see the phone as a drive. Any help would be appreciated.
Bump. Having the same issue. Cant see any files in 'my files' (samsung galaxy s i9000), internal sd wont mount or format in clockworkmod recovery
Hi guys, Did you solve the problem somehow?
I just wanted to state that this may be correctable with JTAG. If you guys are interested in letting me try to correct this with JTAG please let me know. I have been able to fix, what I refer to as partition bricking on the i9000 and T959 Vibrant and this sounds similar.
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
AdamOutler said:
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
Click to expand...
Click to collapse
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
connexion2005 said:
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
Click to expand...
Click to collapse
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
AdamOutler said:
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
Click to expand...
Click to collapse
RIFF DOES SUPPORT THIS NATIVELY. Also, the phones I obtained were not fixable with CWM repartitioning. I spent hours on the first few to still have mount issue with DBDATA and /dev/block/mmcblk0p1 and /dev/block/mmcblk0p0 errors. I have found a few that were fixable with re-partitioning via ODIN but several that required JTAG to fix. I didn't spend days trying to find the perfect combo before turning to JTAG but I spent a lot of time on many of these phones.
Hi Connexion, I would be interested in trying this, can we do this to Korean Variant of Galaxy SHW M110 (anucall) let me know
Hi,
Unfortunately, that is not a supported model on the RIFF box right now. I sent you a PM I believe with some advice though to hopefully get through it.
Related
Setting the scene (without being too dramatic) Been on XDA since i jumped on the Captivate when it was first released, I respect all the work & knowledge that is shared here and rely on it more than the overpaid excuses-for-tech support @ att.
When i Grabbed the Infuse, i handed my cappy down to my kid, still no issues with it and even upgraded to GB.
I got my Infuse as a referb (as i did with my cappy) back in Sept of 11.
Im rooted, no ROMs loaded.
I cant pinpoint when things began (that im about to explain) but I thought after 2 replacement units (one through warranty [another referb], the other at the Device Support Center [a non-referb] it just might be me???
Here is what's happening:
1.when downloading apps, some freeze and never complete (reboot resolves, and restarts when phone boots up) I know this was once an issue with market app... but several "uninstall updates" of the market app later did not change this.
2. (most importantly) when rebooting phone, Apps located on SD Card do not (always) load, its a crap-shoot, it takes anywhere from 3 to 9 reboots for the apps to be recognized and accessible. Then, and only then, does #1 happen.
what is strange to me is that even when the apps do not load, all my music & video on my SD card are visible and playable from the basic audio/video apps (that are installed on internal sd) when the apps are not loaded, the External-SD can not be unmounted, even though i can browse to it, its as it it was never mounted
I played with several microSD cards and went to Samsung to find the optimal speed/class for the Infuse (class 4) and have tried several different manufactures of microSD (currently using a SanDisk 32GB class 4) none have resolved this issue..
what do you think?
any feedback would be GREATLY APPRECIATED. THANK YOU in advance.
Refurb is the keyword here...
I sent in my M11x laptop a couple months ago and it received a refurb motherboard and it hasn't been the same since...However, I've had refurb devices before with no issues, it's a hit and miss thing.
You could try starting from scratch:
Gtg's Unbrick or THIS one (which gives you root back and recovery if you ever need it)
Just make sure you read up on how to do it.
xIC-MACIx said:
Refurb is the keyword here...
I've had refurb devices before with no issues, it's a hit and miss thing.
Click to expand...
Click to collapse
Agreed, but the one im holding now is not a referb, i watched them crack open a new box in front of me at the Device Support Center. which is why I'm suspect that it's something I have done (or am doing) wrong,
I have taken this one Back to stock several times with GTG's Ultimate Unbrick, so when i go back to Device Support Center, they cant give me that "well your rooted" crap. but nothing changes.
i dont know, honestly, it's the only thing keeping me from trying any ROMs, but I wonder if some of them might just fix it.
I have a refurb and it has not given me any problems. It runs better than when i bought a brand new captivate. As far as the apps on the sd card goes I had problems on start ups when i had more than ten apps moved to my sd card. With the last two leaks that problem has gone away. For some reason these phones don't like apps on sd cards.
Sent from my MB865 using xda premium
quasimotto said:
Agreed, but the one im holding now is not a referb, i watched them crack open a new box in front of me at the Device Support Center. which is why I'm suspect that it's something I have done (or am doing) wrong,
I have taken this one Back to stock several times with GTG's Ultimate Unbrick, so when i go back to Device Support Center, they cant give me that "well your rooted" crap. but nothing changes.
i dont know, honestly, it's the only thing keeping me from trying any ROMs, but I wonder if some of them might just fix it.
Click to expand...
Click to collapse
Oh well that changes things lol I wouldn't let the issue stop you from installing Roms. Try out ZEUS, it is based off of one the newer leaks. (L2) Who knows, it might fix your problem, if not, you obviously know how to return to stock.
Thanks!
xIC-MACIx said:
Oh well that changes things lol I wouldn't let the issue stop you from installing Roms. Try out ZEUS, it is based off of one the newer leaks. (L2) Who knows, it might fix your problem, if not, you obviously know how to return to stock.
Click to expand...
Click to collapse
Thank you. I will try.
Thanks!
tmease1 said:
I have a refurb and it has not given me any problems. It runs better than when i bought a brand new captivate. As far as the apps on the sd card goes I had problems on start ups when i had more than ten apps moved to my sd card. With the last two leaks that problem has gone away. For some reason these phones don't like apps on sd cards.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
wow. one would think that would be a serious software flaw, Ill see if ZEUS will fix
thanks!
UPDATE: 48hrs running ZEUS and not a single issue to report..
i reboot my phone for the heck of it and everything loads as it should.
thanks all.
Sorry if this is the wrong place to post - just wanted to share my unpleasant experience.
I've bricked my phone in a peculiar way - it appears to be a hard brick, non-responsive to any buttons. Plugging in to the computer gets me the dreaded qhusb_dload QPST download mode. Not a good sign.
It wasn't due to faulty ROM flashing, either. I made a bad edit to /system/etc/vold.fstab fiddling with the way the internal and external SD cards get mounted - mmc1 instead of mmc2. After one reboot, I had some sd card corrupted errors. Proceeding to format the card may have been my fatal error. By the second reboot, I was bricked. D'oh. I imagine I had accidentally mounted a partition of the internal emmc that is critical to normal operations, then tried to wipe it.
From what I've read, a USB jig won't do much good, but it's worth a try.
Anyone messing around with their /system folder, be warned.
That's sux, but on a good note, $50 and a little waiting will get your phone back, or you could just warranty that sucker ;-) give more refurb units to some other xda members lol
I sense another refurb sale on ATT.com. Sorry to hear about that, sounds bad. No guts no glory right?
I purchased this as a refurb, too. The cycle continues...
Not sure how the whole exchange process will work in this case. I mean, I can exchange for a different phone, or a new Skyrocket and pay the difference, but I really had my heart set on a cheapo skyrocket. Perhaps if I take this up with Samsung instead?
Ur 90 warranty is over already? That sux then. I personally would pay $50 and get it de-bricked, its the cheapest/best option.
I didn't expect much in the way of warranties because I purchased this refurbished. With Samsung customer service I didn't have much luck. However, I just got off the phone with AT&T, and they're overnighting me a replacement, which is cool. They have a 30 day policy on any web store items, so I'm covered. Anyways, lesson learned
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
RussianBear said:
check this thread, please: http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
Are you in thw process of bringing that to the skyrocket?
silver03wrx said:
Are you in thw process of bringing that to the skyrocket?
Click to expand...
Click to collapse
we need all the help we can get. just a bunch of curious noobs, ya know
the main discovery we did with sensation was to make the emmc visible to any pc it's connected to, then overwriting whatever was messed up (like the hboot) with a stock version of that file.
in theory, you should be able to do this to any phone running on a qualcomm chipset once it's in the qhsusb_dload mode. still lots to test, but anyone is welcome to participate, of course!
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
silver03wrx said:
Do you have a skyrocket that your testing on?
Obviously you know its much different then hboot
On htc.
Click to expand...
Click to collapse
nope, just sensation. they both run on a qualcomm chipset though, so i'm just speculating here.
the bricks we're "saving" right now are for people that executed s-on without fully reading the instruction, thereby leaving them in qhsusb_dload mode. your cases might be specific to a different area, but the principal is still the same:
find what is messed up and replace it with the correct file via open emmc
Big progress made for APQ8060 and MSM86xx processors. Sensation hard brick solution coming very soon and SkyRocket/T-Mobile Galaxy S II solutions already solved...
What's this I smell? Possible de-brick
Sent from my SAMSUNG-SGH-I727
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
amnher said:
I also experience this problem on my xperia L
I messed up with vold.fstab and now my phone can't enter flashmode or it doesn't turn on also
Click to expand...
Click to collapse
i have the same problem xperia miro
any updates ?
I wanted to start a thread for those of us that have bricked our Sensation by formatting the SD card while using a AOSP style or AOKP ROM.
Let's use this thread to collaborate ideas and ways to possibly un-brick our devices.
What we know
-Formatting the SD card in past versions of AOSP and AOKP caused the device to "brick" due to possibley reformatting the NAND memory or at least the eMMC partition.
-Our devices are unresponsive and are only recognized by a PC in "download mode"
-AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device(Thanks to T-Macgnolia for this explination)
-Only hope may be to try JTAG and RIFF box.
So let's try a think tank and see what happens. If you have any experience with JTAG and RIFF Box PLEASE put in your 2cents.
I am willing to tear my Sensation apart and go at it with a RIFF box since I just ordered a Galaxy Nexus from Google.
I will start researching JTAG and RIFF tonight, but I figured some one should start a thread like this to clear up the HTC Unbricking Project thread.
You got two thanks from me for this, one here and one in the Unbricking Project thread in the development forum. I am like you I can see this subject clogging up the Unbricking Project thread, so this is a good idea here if members will just use it.
Now as for how to revive devices that fall victim to the awful bug that was in the AOSP and AOKP ROMs. I truly hate that such a bad bug was not noticed before so many had fallen victim to it. I also hope someone or a group of someones can come up with a working solution. But from my knowledge JTAG will more than likely be the only option to revive these devices. I hope I am wrong though. Best of luck to all of you.
I don't know much about JTAG at this point, but if it's the only way I'm willing to go for it and share my experience. As it stands now, my Sensation is just a nice expensive paper weight, so I'm not afraid to tear it down
Well best advice I can do is tell you to start eoing searchs on Youtube. Here is a link to the only video I have found on the Sensation so far. You will need to try to find s video that shows the tear down process that will get you to the point the video I linked shows. But at least the video shows the proper way to attach the JTAG and external power supply. I suggest you aleo see if you can not get in touch with josh from Mobile Tech Videos as I know he can give you some very sound advice on JTAGing a Sensation, or just about any other device for that matter. He is known as connexion2005 here on XDA. It also might not hurt to drop ole AdamOutler a PM asking if he has any advice or input.
well im in this boat with my bricked sensation xe, im taking my phone upto http://www.fonefunshop.co.uk/ on wednesday to get it jtaged with the riff box.
but on some good news, if you read the updates on the riffbox it says it can jtag a htc phone via usb (without opening it) but you need a riffbox plugged in to open the software... so if someone could make a hack to open the software without the box connected you might be able to flash the phone
http://www.jtagbox.com/
Guys,
I'm going to RMA my phone with HTC (i got the SD card brick format issue with AOSP)
Assuming the whole of the internal memory got wiped - HTC cannot tell anything can they? So they should repair it with no hassle?
Any advice is appreciated.
just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?
I want to confirm that jtag solution works ... I bricked my phone and now its back to life
I am not the one who actually done the jtagging thing, I will ask him to post a tutorial here on how to do it step by step ...
heavy_metal_man said:
just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?
Click to expand...
Click to collapse
The latest Open Sensation builds have that problem corrected, check the change log for more details.
Swypesation
szunyimen said:
Hello pplz,
I just wanted to let you know about my story:
I had lots of unused crap that was left behind by different ROMs and APPLICATIONs on my sd card, so I used this app called SD MAID.
Then when my phone's battery dead that day, the phone turned off and I could never revive it...
I had AOKP rel 34, the one just before milestone 5.
SO probably that was the cause of the brick.
BE CAUTIOUS with any kind of sd card related app on AOSP/AOKP!!
Click to expand...
Click to collapse
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...
It seems like JTAG w/ RiffBox is the only way....boooooo.
Does anyone have or know someone with a box, or at least where to get one???
Alipk52 said:
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...
Click to expand...
Click to collapse
I don't really know what happen to Alipk52's Sensation. But I can tell you this, the bug that was in the AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device. Now with the internal memory formatted this means you have no bootloader which means the device can not boot, which means brick. So yes the SD card format bug did cause bricking.
Hi!
I've read about jtagging withot soldering but via usb cable. So, maybe someone will compile the software emulator of riff box presence...
I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2
kmmxracer said:
I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
they will replace the board.
szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
Sending your phone somewhere out whitout knowing the person ? Pretty risky.
Sent From My Sexy Sensation Running Aokp.
szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
The problem you had was not the one described in this thread, and I would put money on him not using JTAG on it at all. I find that often if I let my phone battery die completely it will not turn back on, even if I leave it on charge.
I have to charge it up a bit, unplug it, turn it on, then plug it back in again.
http://forum.xda-developers.com/showthread.php?t=1205983
i think this guy was on to something. if we could create a generic copy of the sensation using this program, with imei and other sensitive things removed and then flash it back using that program. thoughts?
I would just like to offer my Sensation as a sacrifice to the cause. It's bricked either because of the AOKP SD brick or failure to update to the ICS radio before upgrading from 2.3 to 4.0.
Sent from my HTC Sensation using Tapatalk 2
Not updating the firmware only causes bootloops, not a brick.
You'll know if it's proper bricked as it wont even charged.
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Hello,
Because this would save a lot of people's phones including mine, would be great if you post your steps so we can follow.
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
yosup said:
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Click to expand...
Click to collapse
I just duplicated the issue again, "no sdcard found"..etc... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Answer to "a." Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
You said: "It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue."
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know. Google will restore my apps like before but I disabled this function. However it will detect application updates same 5 updated every time I restore it.
You said: "Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?"
Damn!, I'm just not sure, I'm really sorry but I wish I would have THOUGHT of posting HERE before YESTERDAY!...
Now is there a log file I can send out? So people can see whats going on inside this thing. Like I said so much time has gone by, and once I was able to get the camera working and transfer apps to the external card, and all that I basically went numb and stopped messing around. And I would like to point out, that
"Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
If it wasn't for the 10 post threshold I could have been more help. I read every single post in this thread up to the point where I fixed the problem.
Had it all in my head at the time but when I found I couldn't post with-in the >>Encryption Unsuccessful<< thread?! I wasn't sure why.
I even started a separate identity ( Barney Fyfe ) thinking that would allow me to post something.
And from what I read at the time, I thought, rather understood it to mean that I was locked out by some Admin here... Or ?!
Sorry, really, I did not realize I had to get 10 or more posts >>here<<
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Wdustin1 said:
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No just very busy. I just posted this yesterday!?
Wadda' ya want from me eh!?..............
swayjd said:
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
Click to expand...
Click to collapse
Read my first reply.
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them.
I'm going to attempt to get the horrifying memories back!
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Red_81 said:
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
Click to expand...
Click to collapse
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
- - - - - - - - -
Hey people, my name is Pat Doherty.
Because of this dork I'm about done. I Do not NEED this kind of thing. I got my own stresses to deal with these days. And don't need some immature nerd slamming my attempt at helping out here.
I can be reached if you put anything you want in front of patdoherty dot net.
my site patdoherty dot net.
c'ya!
P.S.
You said:
"I'm not sure what a 34gb SD card is."
Really now!?
Are you serious!?
A SanDisk 32GB micro SD chip, "32gb" ( screen printed right on the chip ) = 32 gigabytes
Barney Fyfe said:
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
but dude, you gave us nothing.
please as another noob could you post exact details of your discovery? like what you did to get the inscription unsuccesful to come up repeatably,and what did you do get your phone to access the internal memory? an what exactly did you flash to get it all to work
You brought up a fix to an issue that is getting very high attention right now. You were not able to tell people how to recreate the fix. People are looking for a scientific method (think repeatable steps) to fix this issue that is affecting quite a few people.
I'm sorry if I hurt your feelings. I've been watching the Encryption Unsuccessful thread for a very long time. I was stating only what I observed. There have been others who had suggested a similar fix, but it has not been repeatable.
You are a talented artist and obviously have alot going on. I hope for others' sake you can give them some steps to follow. If so, you may just be the "chosen one"
Barney Fyfe said:
It's comments like this that kept me from being more proactive in posting in the first place!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
First of all, I'll commend you for sharing a positive outcome despite experiencing this dreaded issue. However, this is something being dicussed at the DEV thread level, which assumes a deeper level of detail than the average General or Q&A topic.
Serious people are giving serious consideration to the matter. Example, Woodrube is a well respected Vibrant / Transformer / Nook user, and he's invested a lot of time collaborating with Captivate users to pool our resources and build our knowledgebase here.
Whether you continue your participation is up to you. Hopefully your method will be a viable part of the discussion.
Barney Fyfe said:
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them. I'm going to attempt to get the horrifying memories back!
Click to expand...
Click to collapse
Barney Fyfe said:
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Click to expand...
Click to collapse
Regardless how anxious we get, life always comes first. Take care of business. Just keep in mind that a lot of XDA veterans are putting their minds to this issue, and more details will help isolate the cause & effect. In general, details on your ROM, kernel, and any specifics would be helpful.
Barney Fyfe said:
I just duplicated the issue again, "no sdcard found"..etc
Click to expand...
Click to collapse
By saying "duplicated the issue", we're all going to assume you encountered the "Encryption Unsuccessful" screen again. Do you recall any specific steps you took to "duplicate" this issue? Since you were able to duplicate it several times, people troubleshooting the issue will benefit to know how you induced the matter. The goal is to discover what actually triggers this. Then, we'll get closer to finding a resolution.
Were you using the phone at the time - ie. the EU randomly appeared? Did it just reboot on its own and result in a dimmed boot animation screen? After you hit "reset," did you simply go into recovery and perform a NANDROID restore? Was there anything specific you did after getting the EU screen? Battery pull, reboot into recovery, flash other roms or kernels, etc? Did you previously connect it to your PC using MTP?
Barney Fyfe said:
... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Click to expand...
Click to collapse
It seems you "resolved" your issue by simply doing a NANDROID restore via recovery. Was it really that simple? Or was there anything else (other roms or kernels flashed) prior to doing the restore.
If this is the case, then your experience starkly contrasts what most others have experienced - ie. no longer having access to the internal sdcard even in recovery (so a saved NANDROID backup wouldn't be accessible, etc).
Barney Fyfe said:
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
Click to expand...
Click to collapse
The "swap" is the work around being used to swap emmc & sdcard in vold.fstab - ie. to then have the phone recognize the external sdcard as the internal (since the internal sdcard is no longer accessible for 99.9% of the others with this issue).
Barney Fyfe said:
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know.
And I would like to point out, that "Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
Click to expand...
Click to collapse
Everyone who's gone through this has experienced that same level of dread and anxiety. We can all relate.
Thanks for the nod my friend and I am still on the case but as you say life comes first.
There have been some developments in the SGSII threads that I'll post in the Dev thread.
Barney Fyfe said:
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
Click to expand...
Click to collapse
thinks, I wanna try it on t959 with the EU bug.
USB problem
Hello, the same happens to me an hour ago. No charging no connection to computer but if the phone is powered off as soon as I connect the charger the phone boots up but no charge.
Captivate with CM9.
Barney Fyfe said:
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Click to expand...
Click to collapse
What the OP said seems more of luck.
B.S. ALERT!!!!
I cant believe i actually came back to this thread to waste my time again!!, reading a thread that is supposed to help fix a problem i am afflicted with, but is instead filled with A BUNCH OF [email protected]$%@# [email protected]#@#$T!!!!!
Dude, if want to help people you must understand that in order to do this you need to explain "exactly" what it is you are talking about. No one can trust your information based on your "belief" in it. Software is a very techinical thing, which means to explain it you need to speak in technical terms. If you cant do that, do some more reading. Otherwise you arent helping anyone but yourself....Thanks, but NoThanks.
Several times this past week, my Galaxy S has complained because it thinks I removed the SD chip, though, of course, I had not. It has also sung the "I'm out of power and will shut down now" song, but when I plug it in, I find it still has plenty of battery life. (Was it complaining about the chip, not the power with that song?)
I don't think anything was lost from the chip the first time or two, but this last time I know that it lost some Kindle books, so who knows what else is gone. The 16G Samsung chip is down to 1.2G free.
I'm currently backing up the SD chip and will install another one, but I thought I'd ask if anyone has other thoughts re the source of the problem. The phone is less than a year old.
Thank you kindly.
Try another card first. My bet would be the card is faulty. If you try another one and still have the same issue I'd call Samsung. As far as the battery issue goes get a new one. There have been a lot of reports of battery issues, ROMs rebooting, etc. Most of them where fixed by just getting a new battery.
I'd definitely try to find the cause of the problem before your warranty expires.
I had my microSD holder fail after about 18 months. The early symptoms were that it didn't quite want to "click in" sometimes when I was inserting it. While a relatively inexpensive fix (under $15 for the part off an eBay vendor), getting someone else to deal with the installation is nice.
NanaSarah said:
Several times this past week, my Galaxy S has complained because it thinks I removed the SD chip, though, of course, I had not. It has also sung the "I'm out of power and will shut down now" song, but when I plug it in, I find it still has plenty of battery life. (Was it complaining about the chip, not the power with that song?)
I don't think anything was lost from the chip the first time or two, but this last time I know that it lost some Kindle books, so who knows what else is gone. The 16G Samsung chip is down to 1.2G free.
I'm currently backing up the SD chip and will install another one, but I thought I'd ask if anyone has other thoughts re the source of the problem. The phone is less than a year old.
Thank you kindly.
Click to expand...
Click to collapse
I suggest you take that card out and keep it out. I was getting the same problem after i flashed a custom rom and it destroyed my 32gb chip and i lost a lot of important data.
u170who said:
I suggest you take that card out and keep it out. I was getting the same problem after i flashed a custom rom and it destroyed my 32gb chip and i lost a lot of important data.
Click to expand...
Click to collapse
The custom rom DID NOT destroy your sdcard. You either accidentally formatted it or did not unmount it from your pc and it corrupted the data. Custom roms from this forum will not and can not destroy the sdcard. More people would be complaining and the devs would be run off xda if that happened. Stop spreading lies.
eollie said:
The custom rom DID NOT destroy your sdcard. You either accidentally formatted it or did not unmount it from your pc and it corrupted the data. Custom roms from this forum will not and can not destroy the sdcard. More people would be complaining and the devs would be run off xda if that happened. Stop spreading lies.
Click to expand...
Click to collapse
I definitely didn't do either, but i know my duties of protecting the the devs. Things happen and something corrupted the Rom. Most definitely my own fault for not flashing properly or just because there are gremlins living in my phone that refuse to move out. But, thats why i didn't name which rom was it that was related to the problem. Chill out eollie, just trying to help.
If you read what you posted you said it happened after flashing a custom rom. That to most people means you are blaming the custom rom. There is safety checks and balances put in place to protect that stuff. Plus flashing a rom will never modify your sdcard. If anything it will just add some folders when you boot. Again if there was rom out there doing that then people would have reported it. User error is the only explainable answer.
You also told the person to take out the sdcard and leave it out...that also implies you are blaming a rom and not yourself.
Furthermore, I dont care if you want to post the name of the rom. Protecting devs is not my job. But stopping false info about the roms is something I will do. To new people they see these kinds of statements and think Im not going to try to flash that it might mess up this or that. And that decision is based on some false accusations. That is not fair to the community nor the devs.
My screen cracked after reading this post ..but I didn't say which post
Sent from my Galaxy Nexus using xda premium
eollie said:
If you read what you posted you said it happened after flashing a custom rom. That to most people means you are blaming the custom rom. There is safety checks and balances put in place to protect that stuff. Plus flashing a rom will never modify your sdcard. If anything it will just add some folders when you boot. Again if there was rom out there doing that then people would have reported it. User error is the only explainable answer.
You also told the person to take out the sdcard and leave it out...that also implies you are blaming a rom and not yourself.
Furthermore, I dont care if you want to post the name of the rom. Protecting devs is not my job. But stopping false info about the roms is something I will do. To new people they see these kinds of statements and think Im not going to try to flash that it might mess up this or that. And that decision is based on some false accusations. That is not fair to the community nor the devs.
Click to expand...
Click to collapse
Eollie, my suggestion to take out the card was so she could avoid losing data on it. There really isn't any animosity toward devs or roms inferred there. Telling her to leave it is not going to solve her problem.
Beastmode said:
My screen cracked after reading this post ..but I didn't say which post
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey Erik, glad you have a sense of humor, lol. .. Keep it light, keep it real, right? I really do appreciate your hard work and wish i had the time to get into helping you guys dev.
That happened to me on my G1 after I took it in for screen repair.
My screen broke, but my swap file was on my sd card, so I knew that the sd reader was fine because the phone was getting notifications after boot. After I took it in for repair, they fixed the screen, but my phone wasn't booting up, so they told me that I was running a nexus one rom on it and they could fix it for 20 bucks. I yelled at them for blaming me for the problem, then I went into CWM Recovery, and it told me that there was no sd card. I tried pulling the sd card and pushing it around, and even got it to boot once. So yeah, did you take it into any cheap repair shops, cause they can break phones instead of fix them.