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
I think I've made a fairly large mistake going from MIUI to Darkys.
I was on MIUI v3 (based on CM7) for a short while, but wanted to try something else. I chose to try Darky's v10.1.
I opened ODIN, and chose to flash a 512 pit along with Ficeto's JVH rom (in accordance to this guide). After doing this, my phone is stuck in a bootloop of showing Samsung Galaxy S GT-i9000 screen.
I can still access Download Mode, and my Recovery Menu is very limited (restart, wipe/factory reset, wipe cache partition). I've tried all of those but am not sure what to do to get my phone back on its feet again.
Any help is greatly appreciated!
Download any stock firmware or EZBase.
I have a stock Froyo ROM (Full UGJH2 including SBL) that I tried flashing with a 512 pit but it is still stuck in a boot loop. Actually, now it is showing the Galaxy S GT-i9000 white lettering, then turning off completely.
I fear that I have forgotten to disable the lagfix before flashing with ODIN, however, I never applied one...unless it is applied by default, and has to be specifically removed.
After flashing Ficeto's JVH I get this info in Recovery 3E...
Reboot system now
Apple Update from SD card
wipe data/factory reset
wipe cache partition
-- Copying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet, please use UI menu
for format and reboot actions
--Wiping data...
Formatting /data...
E:format_volume:rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed
Click to expand...
Click to collapse
Your probably best to go to the Ezbase thread(just search it), download the 3 files for either 2.0(Froyo) or 3.0(GB) depending on what you want, the Ezodin and Ezpit, flash using the guide there and start fresh. Let me know if it works!
Thanks for the recommendation! I've made some progress in Flashing EZbase 2.2.
When I try to reboot the phone however, I am still stuck in a boot loop of white Galaxy S GT-i9000 letters.
I now have access to an advanced recover menu ClockworkMod Recovery v2.5.1.0 SOK ULFK. I've checked my lagfix options, all of them say ENABLE LAGFIX: Convert to xxxxxxxxxx. I'm assuming this at least means that none are currently ENABLED, as I don't have the option to disable any of them. I'm looking at an option called CONVERT, where I can choose to convert my filesystem....Should I select one of the following?
Convert to EXT4
Convert to JFS
Convert to EXT2
Convert to RFS
When I try to access Install ZIP from SD Card it tells me E:Can't mount /dev/block/mmcblk0p1 and E:Can't mount /mnt/sdcard . Is this the source of my problems?
Well, I've been flashing various combinations of pits and roms for the past 3 or 4 hours. I'm not exactly sure what did the trick, I was not able to mount or format my internal SD at all. But, after several attempts at the EZBase ROM, followed by trying to flash to 2.1, finally worked. I got into my UI in 2.1, poked around for a second, and then flashed to Ficeto's JVH which worked.
I've now wiped the device and installed Darky's 10.1 JVH successfully. I wish I had a more detailed answer to how I did it exactly, it was quite a crap-shoot
Nice to see you got it going, don't know why EZbase didn't work straight away.
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