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
Related
Hi,
I've been a right royal idiot and have spent 2 days trying to get my SGS back into working order.
Flashed Bionix v1.7 Rom (didnt realise it was Vibrant), worked great with the exception that the headset socket logic to be back to front. No audio from external speaker, if you plug in headset you could then external speaker started to work.
I therefore flashed back my origonal ROM with ODIN but on reboot the update failed with can't mount /dev/block/mmcblk0p2 on /data (Invalid argument). After then reading the notes (Yep noob mistake) I realised I should have removed the voodoo lagfix the Bionix ROM had before flashing a new rom.
Having done some investigation it looks like mmcblk0p2 is an j4fs filesystem but nothing I seem to do seems able to change that. Tried to mkfs and ext2 filesystem on it but it seems to be working then aborts saying it wasnt cleanly unmounted and to e2fsck the partition, which I try and it errors with unable to set superblocks on /dev/block/mmcblk0p2.
Any and all help greatly appreciated
Find a full rom that have dbdata.rfs, cache.rfs in it. Flash via Odin with repartition ticked.
Sent from my GT-I9000 using XDA App
JM8 will restore the things your missing
I have tried that, Odin runs through with no issues, but on device reboot it errors with the same. I can boot into clockwork recovery and adb shell. Its really weird, I've done a complete dd dev/zero over that partion. I've mounted it in windows and formatted via that and yet when I reboot and look at the partition via windows, all the data is there. There were a couple of other partions that were j4fs (/datadata) if i wipe that partion using fat.format, when i remount it it mounts as rfs instead of j4fs (great), but when I do the same with /data (mmcblk0p2) it says success on format but when I mount, it still mounts as j4fs...any other ideas?
azzledazzle said:
JM8 will restore the things your missing
Click to expand...
Click to collapse
Will try JM8 and let you know
Tried JM8 Odin complete succesfully, on reboot complains about CSC (multicsc : can not access to /system/csc/KOR/system
copy_common_data E:Can't mount /dev/block/stl11 (invalid argument))
cant do anything with stl11 in adb, complains no such device (although /dev/block/stl11 file exists)
I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin: http://www.multiupload.com/L79EDKJIG3
Good luck!
bdl1969 said:
I've managed to recover my SGS with a flash of JPU which is a low level package including repartition with 512.PIT. Here's a download link to JPU if it helps. It's a 3 part flash in Odin:
Good luck!
Click to expand...
Click to collapse
Just tried this and error is back to origonal ie cant mount /dev/block/mmcblk0p2.
You didn't accidentally store those files on your Sim or SD card right?
(I know, beginners question but just to be sure )
So you can't use your phone at all atm? Just stuck at recovery screen?
I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App
curioct said:
I had this same problem last night in the end used odin 1.7. With older firmware and pit (512) files doing a full repartition and reflash with csc. And modem files this was a jp4 set i believe.
This would not then upgrade in kies so i flashed a jpy firmware over the top just the firmware file this time. Not sure but i think i could have skipped this stage and restored from the clockmod backup. Can anyone confirm?
Then i rooted the phone again then flashed a kernel with clockwork mod support and was able to go to recovery mode and restore with the back up i made before i started messing about, though i suspect a titanium backup or similar would have worked just as well.
Hope this helps you at one point last night all I had was an icon with the phone and a computer thought I had really bricked it this time but given what I've done over the last couple of weeks i am not sure that's even possible.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just tried with Odin 1.7, the JP4 romset still the same error on mmcblk0p2.
Just for avoidance of doubt in case I'm not doing this correctly,
In Odin I have Re-Partition, Auto_reboot, and F.Reset Time checked, Dump, Phone EFS and Phone Bootuploader Update are not checked. I'm using s1_odin_20100512.pit, and have tried Various European Roms including all the ones mentioned so far.
Fundamentally is the problem not that the filesystem type of the internal SD partition is j4fs? It seems the kernels dont know how to mount this type of filesystem, and for some reason I seem unable to change this. I cant even delete/format the data in these partitions.
cronoz, I believe mmcblk0 is the internal SD memory, which has 2 partitions. The first is a 2Gb Fat partition and the second is a 5Gb ext4(j4fs) partition.
Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App
lownoise said:
Try using hardcore's kernel. In recovery mode try to disable lagfix.
Good luck
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
thanks, can you point me in the right direction maybe a link just to ensure I download the correct file.
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yep, dont have any problem getting into Download mode
nivenj said:
Yep, dont have any problem getting into Download mode
Click to expand...
Click to collapse
then it's save to try
Yes the file system is the issue but repartitioning should reset that at lest it did for me last night. But only once i found a complete set of files. A *512.pit mine came with odin the main firmware in the pda box the modem file in the phone box and the csc file in the csc box once i had that mine refreshed just fine. If you have the right combination of those then I'm not sure what else you can do tbh
Sent from my GT-I9000 using XDA App
lownoise said:
It's in the development section.
Thread hardcore speedmod kernel.
Choose first download speedmod....
500.zip
Unzip and flash with odin.
You do have 3 button combo right!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?
nivenj said:
Well this thas put me a lot further forward thats for sure. So i Flashed speedmod-kernel-k13a-500hz.tar. This now bootsl the SGS. It complains bitterly, force closing just about everything, but it does boot. Just about all apps force close, but I can set debugging mode and get in via adb (although the roms not rooted (JP4) :-S).
I can boot into recovery and choose the speedmod Lagfix option. It correctly identifies that /data is ext4. I disable lagfix and the new config is set to convert data to rfs on next reboot. I reboot and it goes through the conversion, backup of /data /datadb and /cache, it then generates md5 checksum and the aborts saying there is not enough space on internal SD. Not sure how to fix this part. When I enable debug mode I can see 2 partitions in windows a 1.8Gb and 5.3Gb, Both are empty apart from my update.zip in the 5.3Gb partition.
EDIT: Also tried the Yes, with factory reset without backup option, this seems to work but on reboot /data is still ext4 :-S
Any other ideas how to proceed now?
Any Full Roms with the speedmod kernel you could recommend?
Click to expand...
Click to collapse
you can try darky's resurrection rom which is a complete rom with pit file 502
http://forum.xda-developers.com/showthread.php?t=940671
If that fails you can also try to flash jpy or js3 with the 802 pitfile
hmm i think the 2 partitions are the main problem....... It's kind off strange that you only can see the update.zip. How did you create the 2 partition???
Ive been trying darkys res rom, the only problem I think though is that it does say that lagfix has to be removed (ie not ext4 partitions) before installing, and that I suppose is the underlying problem of why I cant get it to work.
I just realised it wasnt 2 partitions, its the Internal and external SD cards, the 1.8Gb seemed to be corrupt, I managed to format it via the SGS menu and it shows the correct 8Gb now.s
EDIT: Hmmm just noticed something, its seems that although it appears I can delete and add files to my internal SD card via windows, it doesnt actually do anything on the card. This very strange :-S
Been having problems since flashing a Rogers stock Froyo Kernel yesterday. I made it back to stock but found I couldn't upgrade to any 2.2 ROMs, it seems that the ext4 lagfix was still activated on the Internal SD card and this prevented me from remounting anything on it or formatting. I am now stuck in recovery mode, although it is possible to get into download mode as well. I have access to CWM, and I've been farting around with wiping caches, formatting partitions, etc.
I have attempted everything I can think of to try to flash back to stock, including the Captivate tookbox 2.6 for Rogers, and the Odin 1-Click with the Master Clear option. Nothing seems to work. I get the classic message:
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA
The real problem seems to be that there is no update.zip on the internal sd card for me to use as a backup to flash back to stock. I am having no luck with the two software packages above, but it seems that if I could push my own backed-up update.zip I made a few days ago to the internal sd, I could get past this.
I need help. Please give me some advice.
Call off the dogs- after I installed the driver package that was included with Odin 1-Click I managed to get a master clear and a flash to the AT&T stock.
I must have spent 3 hours installing different driver packages today.
This has worked for me, depending on how bad the problem is...
Assuming the phone will boot, this will format the internal SD card.
GSM Master Reset: *2767*3855#
pkley said:
This has worked for me, depending on how bad the problem is...
Assuming the phone will boot, this will format the internal SD card.
GSM Master Reset: *2767*3855#
Click to expand...
Click to collapse
Thanks, I appreciate the reply. I couldn't get past recovery mode, so I couldn't access the dialer. I ended up getting the ODIN 1-click to flash the AT&T stock ROM, then I flashed back to my native Rogers Eclair.
Just in the process of getting Stock Froyo back on the handset.
A little information is a dangerous thing...
Evening,
After trying nearyl everything I found online to get my phone back into a working state I finally gave up and decided to ask
you for help.
So, it all began with me trying to flash the Jelly Bean Port onto my SGS in the hope it would fix my constant crashes and other problems
I had after another flash.
I got it working at some point, but it did not react when I plugged it in the usb port as mass storage device or any other mode for that matter.
So I tried some other solutions.
A couple tries later i started getting the "cant mount /dbdata" error which i fixed with a solution from this forum using a dbata.tar as PDA, using the JW4 firmware.
However because I wanted the usb to work I tried again to get jelly bean to run, without success.
I'm no unable to boot the phone passed "Enter your password to decrypt storage" or in any other mode.
When flashing I keep getting "Failed to mount /data" which seems to disappear at times when the external sd is inserted.
My Computer regocnizes the Phone as two different drives, even when i remove the sd...
So yeah.
The moral of the story is: I cant get the phone to run on any mode except jellybean and there without usb connection, if i get passed the decrypt thing.
Currently all flashing leads me to the recovery screen saying:
"Can't mount /data " and "Cache wipe failed" after that it just bootloops.
So, can anyone help me out?
P.S. I can at all times enter recovery and download mode.
Hey
If u can enter download mode, why dont u flash 2.3.6??that should clean all your problems..
Plus if you upgrade to JB your external sd-card wont be mounted to ur system...(you cannot alter any data directly to your external sdcard...
There are 3 ways to solve your prob..
1.use CWM..
--goto mounts and storage, then hit external sdcard..
2.use your external memory card directly with ur system..that means without your phone
3.(long method)
Transfer ur data to internal sdcard then use a file manager and transfer to external memory card
Cheers
If I Helped, dont mind Hitting the Thanks button...
Flashing an old Stock Rom mostly fixes all problems for me and should do the same for you
Sent from my GT-I9001 using xda app-developers app
Hi,
Thanks for the answers.
Flashing an old Stock Rom mostly fixes all problems for me and should do the same for you
Click to expand...
Click to collapse
I tried this approach and flashed the JVU Version from samfirmware.
It leads to the following error:
Code:
Failed to mount /sdcard (file exists)
(...)
Format_volume: rfs format failed on /dev/block/mmcblk0p2
During the boot up, after the first flash.
Note: The external SD-Card was not in the phone, as well as the sim card.
After that it starts bootlooping.
If I insert the external SD-Card before the flashing process i only get:
Code:
Format_volume: rfs format failed on /dev/block/mmcblk0p2
And the Phone starts to bootloop again.
I've tried to google this and I get two reactions:
The internal SD is fried.
Format the internal SD using CWM.
I believe I did try the second approach, but i would greatly appreciate a short guide on how-to properly format my internal SD
There are 3 ways to solve your prob..
Click to expand...
Click to collapse
I was under the impression they had fixed that bug in V6.
Anyway, it's not the real problem since I would rather get my phone to work again, before I go ahead and try out jelly bean again.
The ics semaphore.tar odin kernel from the semaphore thread has worked for everyone I've suggested it to.
For some reason it seems to work where other flashable packages don't, worth a try.
Sent from horseback.
First of all I flash stock firmware. / 3 PDA files, MODEM, CSC / odin with the pit512 and Re-partition.za second is that the flash / ICS, JB / clearing script to use the kernel, then the full wipe and cwm JB installation ....
adytum said:
The ics semaphore.tar odin kernel from the semaphore thread has worked for everyone I've suggested it to.
.
Click to expand...
Click to collapse
Did you mean this Semaphore Thread?
If so, just tried it, didnt work, still get the same error as before:
Code:
Format_volume: rfs format failed on /dev/block/mmcblk0p2
misacek said:
First of all I flash stock firmware. / 3 PDA files, MODEM, CSC / odin with the pit512 and Re-partition.za
Click to expand...
Click to collapse
At this Point, I get the first error concering the formating, see above.
If I still continue and manage to get JB to work (I event tried the kernel cleaning script). I get locked out because of this "Enter password to
decrypt storage" Error. Which is known to be fixed by performing a factory reset, which I cant do, because of the first error.
f_erin said:
I get locked out because of this "Enter password to
decrypt storage" Error. Which is known to be fixed by performing a factory reset, which I cant do, because of the first error.
Click to expand...
Click to collapse
try and enter any password five times until prompted that this will wipe the card, than you should be able to do so
So, today I decided to buy a new smartphone after one last try of getting my old one to work.
I used the default guide to flash JellyBean and now it works ...
I guess it was scared or something, I'll keep using it to check of fluently it works for now and bought and sd reader to solve the usb issue.
So this thread can be closed.
Thanks to all for their tips.
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