Related
I updated my phone to Cognition 2.1.2, and think i bricked it. I was on Cognition 2.1.1, i disabled the lag fix as per the instructions, and then installed cognition 2.1.2 with Rom manager. when my phone rebooted it seemed to work fine. Then i realized that there was no calculator app installed anymore. I went into the settings screen, but when i clicked on any of the options it would highlight, but not do anything. I rebooted, but i got stuck on an ATT boot loop.
I then pulled the battery, got into the download mode with the button combo, and did an odin oneclick back to stock. however, when it rebooted it went into the stock recovery console and gave an error message "cant mount \dev\block\ stl11"
After that i tried updating with odin 3 to JH2. Everything went ok, but when it reboots it still goes to recovery, but this time it gives me a differnet error
Code:
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E: Can't mount /dev/block/mmcblk0p1
(No such File or Directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
I can boot into download and recovery with the button combos
I can use adb when in recovery , I'm not sure what to do though (I can't mount with shell, nor can i get to su
I can't get to ClockWork Mod Recovery as it was'nt the last update.zip, and when i try to reinstall packages it says
Code:
E:can't mount SDCARD:update.zip
Installation aborted.
I'm pretty sure this has to do with the lag fix. I think that odin can't wipe the ext4 partition even though i disabled the lag fix.
Please help, am i completely bricked? If so should i return to att even though its been rooted? I guess i could say it was from the OTA.
I would suggest making sure that you disable the lagfix by
Code:
adb shell
touch /sdcard/voodoo/disable-lagfix
Reboot, and it will probably say "converting back to rsf blah blah blah" It takes like friggin 10 minutes to disable
Then I would try to replace the update.zip with the clockwork recovery update.zip. I uploaded it here: http://dl.dropbox.com/u/115587/update.zip To do this I would use
Code:
adb push [local path to update.zip] /sdcard/update.zip
In my case since I'm using a mac (I put it in my downloads folder) I did
Code:
adb push ~/Downloads/update.zip /sdcard/update.zip
Then try to go into recovery mode and reinstall packages, hopefully clockwork will come up and you can restore a good version of your phone
Hope it helps
Laundry? Do you have insurance on it?
Sent from my 42 node TI 89 cluster
i dont know a whole lot about adb or even know if this is possible, but is there a way to reformat the internal sd card in adb like there is in the stock settings menu? if you reformat that should get rid of all traces of anything including lagfixes correct?
I am unable to use the touch command because it can't mount the Internal SD. it gives me
Code:
touch not found
even when i touch files that i now were there.
I wonder if i could flash the voodoo kernal back on to it if it would take care of it. is there a .tar of it that can be flashed with odin 3?
Is there a way to see what partitions are on the internal sd, and like di11igaf said, is there a way to reformat with adb?
Also i don't think warranty covers putting it through the laundry and w/ insurance it costs like $125 to replace
Wow this one is a bit of a headscratcher.
Have you tried manually flashing in a voodoo compliant kernel just to see if it will boot? It's not mounting the internalSD, which is bizarre, but I do know that stock kernels can't read EXT4 data- now I don't know why your internalSD might get switched over, and I have very little expectation that this will work, but at this point what's the harm?
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
I have flashed a voodoo kernel but it just tries to create the ext4 partition, fails and reboots. The problem is that there is now no /dev/block/mmcblk0p1 or /dev/block/mmcblk0p2. There is still a /dev/block/mmcblk0 but since we both tried to flash stock with Odin we no longer have root to attempt recreating the partitions. We also can't flash anything from recovery since there is no /sdcard.
We need a rooted ROM that is flashable with Odin. The e3 recovery also has an option to reformat the internal sdcard but I've only found it with i9000 ROMS where the captivate power button doesn't work to select it.
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is able to mount your SD again, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Zilch25 said:
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is seeing that, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Click to expand...
Click to collapse
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Devin5277 said:
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Click to expand...
Click to collapse
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Another thing that might be worth trying... though doubtful. Do an Odin 1 click, yank the battery as soon as it completes before it gets a chance to boot again. Restart Odin and get your phone back into download mode, and flash in the Voodoo kernel, see what errors it spits out on first boot (if any)
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
Zilch25 said:
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Click to expand...
Click to collapse
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Devin5277 said:
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Click to expand...
Click to collapse
Sorry I didn't mean to come off harsh My theory here is that SOMEHOW voodoo is writing EXT4 data to the internalSD outside of the NAND area and in some cases it's corrupting it in such a way that the internalSD cannot be read by the stock kernel (since it has no EXT4 support) so in theory if you can get the internalSD mounted again it can be reformatted to allow a stock kernel to return to use... if this is the case, or at least close enough to what's happening it would fully explain why the froyo kernel with repartition couldn't touch the internalSD (It couldnt mount or read it due to the limitations for file systems in a stock kernel)
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
kakalaky said:
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
Click to expand...
Click to collapse
Is this after using a Voodoo kernel? And are you attempting to perform the ffdisk and parted commands while using a voodoo kernel, or stock? I'm just trying to gather as much information as possible on this problem, so forgive all the questions
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Trump211 said:
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Click to expand...
Click to collapse
Nah, make sure you have the phone plugged in when you turn it on and go into recovery. For some reason plugging it in when it's already in recovery doesn't work. At least it doesn't for me...
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Trump211 said:
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Click to expand...
Click to collapse
Not sure =/ I had it running last night without too much issue, but I did have to juggle it around a bit before it would find the device. You might want to try doing an adb kill-server before you try to connect in case the system still thinks its running
Hello!
I'm from Greece and I've come up with the following situation with my I9000 running stock 2.2 XWJPH!!
I've had lagfix installed and three days ago I wanted to take a full backup with my Kies!! So I had to unlagfix! Worked fine and went through Kies etc
After all this I came back to my OCLF but every option to install again OneCLickLagFix was Unavailable and was saying something about the playlogo and playlogos1 files!
Anyways somehow I managed to work it out by renaming these two files!!(After this I've found out that I should have checked Restore boot animation " first!!)
After the install of Lagfix it rebooted with a blank black screen doing nothing!!!!Today I had in my hands a USB jig so I got into Download mode and using Odin flashed two or three froyo ROMs (stock for the time, either with one PDA file or with the three files together with the .pit file) and one tweaked 2.2.1 but the best result was getting the following into the Samsung recovery menu:
update media please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
I tried wipe data/factory reset και wipe cache partition but situation is the same....only the format internal sd-card will save me?
But this way I'm going to lose my backup of titanium, right; Is there some way to get my Titanium backup folder from the internal_sd? Or maybe it's not in the internal_sd so everything is ok?
Adb also works somehow (I think), when I leave the phone to boot into normal mode without getting into the recovery menu (this happens just after flash only for once) and leave it till it gets to the coloured "S"!!
How can I give it a complete flash so as to recreate those folders that it is asking for?
Every way of help appreciated!
Thanks!
Even Format of internal sd didn't change anything!!Just tried it!!
pamarakos said:
Hello!
I'm from Greece and I've come up with the following situation with my I9000 running stock 2.2 XWJPH!!
I've had lagfix installed and three days ago I wanted to take a full backup with my Kies!! So I had to unlagfix! Worked fine and went through Kies etc
After all this I came back to my OCLF but every option to install again OneCLickLagFix was Unavailable and was saying something about the playlogo and playlogos1 files!
Anyways somehow I managed to work it out by renaming these two files!!(After this I've found out that I should have checked Restore boot animation " first!!)
After the install of Lagfix it rebooted with a blank black screen doing nothing!!!!Today I had in my hands a USB jig so I got into Download mode and using Odin flashed two or three froyo ROMs (stock for the time, either with one PDA file or with the three files together with the .pit file) and one tweaked 2.2.1 but the best result was getting the following into the Samsung recovery menu:
update media please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
I tried wipe data/factory reset και wipe cache partition but situation is the same....only the format internal sd-card will save me?
But this way I'm going to lose my backup of titanium, right; Is there some way to get my Titanium backup folder from the internal_sd? Or maybe it's not in the internal_sd so everything is ok?
Adb also works somehow (I think), when I leave the phone to boot into normal mode without getting into the recovery menu (this happens just after flash only for once) and leave it till it gets to the coloured "S"!!
How can I give it a complete flash so as to recreate those folders that it is asking for?
Every way of help appreciated!
Thanks!
Even Format of internal sd didn't change anything!!Just tried it!!
Click to expand...
Click to collapse
After so many tries finally 2.2.1 warked....shall I leave it there? In fact isn't it a little bit faster than stock 2.2?
Thanks!
Well, if it ain't broke don't fix it.
snapper.fishes said:
Well, if it ain't broke don't fix it.
Click to expand...
Click to collapse
I've lost the H/G icon from the bar at the top next to the signal, so I don't have HSDPA or GPRS internet through my carrier!!
Can you help?
Thanks!
Go to Rom Kitchen build a rom with the CSC for your country/network .
http://forum.xda-developers.com/showthread.php?t=817703
jje
Dear all, I tried now for two full days to resurrect my i9000, with no success so far. I hope one of you can give me a hint where my problem/error lies.
A bit of background: The phone was bought without a contract (no branding) and with android 2.2 (or 2.1?) installed. Afterwards I upgraded to ginger bread with kies, all worked fine for months.
The day before yesterday (after I installed and updated some apps) the phone was quite slow, so I wanted to reboot it. The booting was looped for a couple of times, and as it made it finally to boot, it was almost not reacting anymore. I uninstalled the apps I recently installed and then the phone froze. Now the phone wasn't able to exit the boot loop anymore. I searched this and other forums and learned about recovery mode, download mode, flashing and bootloaders and all these things. And indeed, in the recovery mode, there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
Finally I convinced myself, that simply - for what ever reason - android needs to be reinstalled. Long story short: I tried different versions (from 2.1 to 2.3.6) with bootloader, with 1 or 3 files, with different versions of Odin3 (1.7, 1.82, 1.85), with or without repartitioning (pit files 214 [EDIT:I meant 512!] and 803, the later succeded as well, but gave me error messages in the recovery mode). All with the same outcome: Now the phone boots up to the blinking S logo ("splash screen"?), and stays there forever (2h+), while the S is not stuck, but blinks and turns b/w in circles. I let it do this over the last night (connected to my laptop, so it would not decharge) and the next morning it was off, so I guess at some point after 2 hrs it gave up. I found a couple of comparable posts, but my situation I found no where... (not really a boot "loop", neither gets it stuck, but can't complete booting plus wiping and/or flashing, no matter which version, seems not to help).
If any one kept on reading until here and knows something that might help (and/or that I have overlooked so far) I would be more than grateful for a hint!
Thanks a lot!
try flashing the 2.3.5 JVT Firmware with 512.pit and repart. I do not know any firmware which uses those strange .pit files you used(except one or two very old Fimrwares which are using the 803.pit file).. If the phone doesn't boot after doing that you can try formatting your SD in recovery. According to that Errormessage you get in Recovery it could be possible that something is wrong with yout internal Memory. Formatting the internal Memory could solve your problem. After doing both your Galaxy might boot again. If not it could be an Hardwareissue too. In this case just flash the latest official Firmware and send it to samsung and let them repair ist Attantion: All Files like pictures, videos or whatever on your Internal-Memory will be deleted if you format your internal memory!(that apps are deleted after flashing schould be known by everyone )
Detailed method given here
Detailed method given here
http://forum.xda-developers.com/showthread.php?t=846913
use the tutorial to boot to stock firmware, this should put your phone back in business....
no success
Thank you two for your fast answer!
Unfortunately it didn't do the trick
As I wrote 214 I meant the "normal" 512 pit file (d'oh!), sorry for that, orangerot.
I noticed something strange: I left the phone turned off for some hours today, and after the reboot there was again the boot loop I had in the very beginning (until the white Logo), and going to recovery mode there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
I tried a wipe that led me to the following:
Code:
-- Wiping data...
Formatting /data...
E:format_volume rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
asking google for that I found a thread (in german) on handy-faq.de (samsung_i9000_galaxy_s_forum/225311-geraet_gewiped_bootschleife), in which the contributors came to the conclusion the only way would be (and was in the end) the samsung repair service.
Interesting is, that after a reboot I was again at the same position as before (glowing S) and no error message in the recovery mode. From this starting point I tried again to flash (with JVT, 512.pit through Odin3 v1.85, as you suggested), with no visible change of behaviour: still booting only until the glowing S, no error in recovery mode, wiping doesn't help but finishes without error.
If anyone has some additional idea I would appreciate to hear about, otherwise I guess I try to flash an official Android version (any idea how to find out which is the most recent official version updatable from kies?), and bring it to the samsung partner.
Thanks a lot!
I have had athat happen before, try flashing darky's resurrection edition via odin. It worked for me.
Here: http://www.darkyrom.com/community/index.php?threads/odin-darkys-resurrection-edition-10-1-gt-i9000-only-for-now.3237/
still not recovered
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
boronian said:
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
Click to expand...
Click to collapse
Ahh man...
Okay, there are a couple of more things you can do,
1. Try darky resurrection rom V9.2 (I think your issues maybe due to some lagfix problems/mounting filesystem incorrectly etc.) Try the 9.2 in odin, make sure that you have checked the "Repartition" as ON and have a PDA and a PIT file selected.
http://www.darkyrom.com/community/index.php?threads/odin-rom-darkys-resurrection-edition-9-2.895/
2. And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful):
http://forum.xda-developers.com/showthread.php?t=845708
If all that doesn't work, then I don't know what will.... I'm sorry.. I don't know what else you could do. Try a repair centre as a last resort I guess.
Did you try to format your internal sd? Wiping and formatting are two diffrent things.. And in your logs I only see that you are wiping your data.. So just try formatting your internal sd. i think you will find it under "mounts and storages" in cwm. I've read before that this may help to solve this problem. if this does not help it could be that your internal sd is broken. In this case you have to send it to the samsung repairservice. but make sure you flash the official JVI firmware to remove the clockworkmod, so they cannot see that you have flashed your mobile cause if the recognize it they may refuse tu repair your mobile
Try darky resurrection rom V9.2
[...]
And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful)
Click to expand...
Click to collapse
After I installed Darky's resurrection 10.1 I had troubles to get in recovery mode... and loads of errors the few times I managed... last attempts didn't bring me to the modified but the "original" recovery menu. I think I don't dare to try Darky's ROM 9.2 after this experience. And for messing around with EXT4 and Linux I don't feel ready at all, thanks though for the link! Now I am back on a stock version and again the old picture.
Did you try to format your internal sd?
Click to expand...
Click to collapse
I thought when I use the pit file and check the repartition box it will reformat the internal sd?? If not... this cwm... I didn't quite get what exactly it is. Isn't it an android app? How can I use it, when I am not able to boot?
And then: is JVI and JV1 the same? If not where is the difference?
Thanks again! (And sorry if my questions are silly)
No, repart only reparts the system partition off the phone. the internal and external SD are not going to be formatted while reparting. If it would behave like that all your photos, videos, folders and so one would have been deleted. Apps are deleted because they are saved on the system-partition.
CWM is a recovery which has some more features than the stockrecovery. You get it with flashing a CustomRom(they usually all have CWM) or an CustomKernel(e.g. CF-Root, Semaphore etc.).
You can acces CWM by holding Vol-up+homebutton+powerbutton at boot and release them when the Galaxy GT-I9000 screen appears. Its just like getting into the Downloadmode but instead of pressing vol- you have to press vol+. Once you are in CWM you navigate to mounts and storages(with vol-up/vol-down you can go up/down and with the powerbutton you select an option) and format your internal sd there. After that everything may be fine again If not you have to send it to the samsung-repair-service after flashing the official JVI-firmware to delete CWM and so on. JVI and JV1 are not the same.. JVI ist the last official firmware(2.3.3) while JV1 is a leaked, unoffical firmware. So you have to flash JVI befor sending you phone to samsung while JVI ist the last official firmware.
back to life
Dear orangerot, dear B-1P
thanks for your patience!
Then I knew the cwm, I just didn't know it was called that way.
last attempts didn't bring me to the modified but the "original" recovery menu.
Click to expand...
Click to collapse
So the "modified" recovery menu I talked about was the cwm. In the last attempt with Darky's Rom I couldn't get back to that cwm... maybe I released the 3 buttons at the wrong time? Don't know.
However, in the mean time I gave the phone to a service partner of Samsung, and they sent it to Samsung. Today I got it back and everything works again. Unfortunately they didn't give any details on what they did (except for new installation of the OS, which didn't help for me...).
So for me this problem is solved (for now...)
Cheers!
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
--Copying media files...
E:failed to mount /sdcard (no such file or directory
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. Please use UI menu for format and reboot actions.
Media files copy failed.
--Wiping data...
Formatting /data...
E: format_volume: rfs format failed on dev/block/mmcblk0p2
Formatting /dbdata...
Formating /cache...
Data wipe failed.
-- Applying Multi-CSC...
Installing Multi-CSC
Applied the CSC-Code 'ATT'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
frenzisor said:
My Cappy is having some serious issues! It used to run slimROM 4.2 and untill the night that it started illuminating the ceiling of my room with the ATT bootloader logo. I woke up checked it out and... nothing would run. System kept rebooting without end. As I am a somewhat knowledgeable flasher got into recovery mode and flashed my rom again. It went to the ATT bootloaders then it showed the slimROM logo as if it were to load it and then the screen went off. Dead!
I tried Heimdall SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click without any success.
Last, I tried returning it to stock using ODIN and this is the error message that I get
.
That's it. I think my /sdcard is dead. Are there any other possibilities and maybe a chance to bring my phone back to life? Please help!!!
I will be generous to anyone who can help.
Best
Click to expand...
Click to collapse
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Booting of External SD card
BWolf56 said:
When you tried Heimdall, did you use a different USB port?
Also, is that quote from Odin/Heimdall? If so, you might wanna try other GB versions (Heimdall UCKF1 worked for me before when Odin KK4 didn't).
Another thing, do you have a external sd? If so, try booting with it in.
Click to expand...
Click to collapse
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
frenzisor said:
I the quote is from Odin. What is extremely weird is that right after i posted this. My phone booted into GB. I then proceeded to see what my storage was doing and it turns out that I am somehow (I am not sure how this happened) i am running of my External SD card. My phone still can't see any internal SD card. Any suggestions?
Should i try to use ROM manager and flash recovery and try a ROM from there?
I am still worried that my Internal SD is not working.
Click to expand...
Click to collapse
***First of all, don't touch ROM Manager, it doesn't do well with the Captivate.
Custom recovery is flashed through kernels with Odin 1.18 (or 1.17). You simply grab the .tar file and put it in the PDA slot while you phone is in download mode. (On stock GB, you'll want Corn kernel)
Now my guess is that your external sd needs reformat. Backup w/e is on it (same with your internal if you can access it from your pc) and full format it to FAT32. If that alone doesn't fix it, wipe your internal as well.
I am trying to get my Son's Captivate back up and running.. while it has no phone service, he uses it all day long. It was running Cyanogen Mod 10 .. he sat it down to eat.. when he came back the screen was black with the buttons lit up and no response.
He did a battery pull to restart it and it came back looping Error to mount /SDcard and a count down.
I got it into recovery and am not able to mount /data or /emmc. And it is failing to install a ROM from zip.
I tried using "I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click" and it runs through the process.. flashing Kernal, Modem, FactoryFS, DBDataFS and CACHE successfully.. then the device reboots and goes through a few things on screen, and fails on Formatting /data ( E:format_volume: rfs format failed on /dev/block/mmcblk0p2 ) but everything else says success. Hitting "reboot system now" says that it cant copy the log because of failure to mount /emmc.. then reboots to the same recovery and does the copy of Media and Appling Multi-CSC (their spelling mistake not mine) over again.
Flashing back to a CWM 6 recovery and still no mounting of /data or /emmc. And it just boots right into the recovery.
I tried --repartition with Heimdall and it said it uploaded the S1JE4.pit fine. Same things..
So is there anything I can to to test the internal storage to KNOW if it is faulty or is there anything else I can do?
I would really like to get this thing working again for my little dude.. he is so sad as all heck to not have his Android Buddy. :crying:
Seems likely internal sd may be dead, particularly if someone ran ICS on it at some point. If you have an external sd card, at least 8GB, this thread may help-
http://forum.xda-developers.com/showthread.php?p=21439417
you could use cm10.1 instead of the ICS rom mentioned in the thread.
Sent via Monty Pythons Flying Circus