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
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...
I have a samsung galaxy s, gt-i9000. It was on the t-mobile network. It stopped working one day and is now stuck on a boot loop. (It does go into download mode)
Can anyone help me? ps. I do not know the original firmware names etc.
Hooolagon said:
I have a samsung galaxy s, gt-i9000. It was on the t-mobile network. It stopped working one day and is now stuck on a boot loop. (It does go into download mode)
Can anyone help me? ps. I do not know the original firmware names etc.
Click to expand...
Click to collapse
If your phone goes in to download mode you can flash, using Odin, a full stock firmware.
Have you ever update it since you've bought it?
umberto1978 said:
If your phone goes in to download mode you can flash, using Odin, a full stock firmware.
Have you ever update it since you've bought it?
Click to expand...
Click to collapse
I have a problem saying Cant Mount sdcard
I have the exact same problem as ysr84.. When i click "reboot system now" it just goes back into the boot loop.
Also.. My phone does go into download mode.. I have tried to flash using Odin3 but get the image as ysr84.. My phone then repeats the boot loop sequence..
PS. I do not know which firmware the phone started with, I have been flashing with JVR.
Since I bought the phone I have not tried to update it, I think there was no available update.. =/ not 100% sure..
Although when flashing with JVR I get the "Can't mount etc"
Android system recovery <3e>
Enter: OK Key, Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
_____________________________________
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
Successfully copied meida files.
--Wiping data...
Formatting /data
E:format_volume: rfs format failed on dev/block
/mmcblkop2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'KOR'
Successfully applied multi-CSC.
^This is the message I get after a fresh install using Odin3 with repartition selected. I had used the firmware package JVR.
ysr84 said:
I have a problem saying Cant Mount sdcard
Click to expand...
Click to collapse
Which firmware you tried to flash...and how? If you want more help about flashing follow http://www.hdtechvideo.com
anukilimanoor said:
Which firmware you tried to flash...and how? If you want more help about flashing follow http://www.hdtechvideo.com
Click to expand...
Click to collapse
Hello, I have tried to flash my phone with 'any' firmware as I do not know which firmware my phone was on before.
It maybe a trouble with partition.
You can try to re-virgin your phone by flashing an old eclair (JM8/JM9) firmware always using odin with pit 512, re-partition flagged.
Be careful if using a copy with bootloader.
After that (if phone boot regurarly) you can get any gingerbread firmware, obviusly if you used in the previous step bootloader for eclair firmware, than you'll get a copy of gingerbread with it's bootloader.
But i'm not sure this helps you.
Hope you solve this, guy.
umberto1978 said:
Be careful if using a copy with bootloader.
After that (if phone boot regurarly) you can get any gingerbread firmware, obviusly if you used in the previous step bootloader for eclair firmware, than you'll get a copy of gingerbread with it's bootloader.
But i'm not sure this helps you.
Hope you solve this, guy.
Click to expand...
Click to collapse
What do you mean by bootloader?
Hooolagon said:
What do you mean by bootloader?
Click to expand...
Click to collapse
If you, using 7ZIP, extract the archive PDA.TAR.MD5, from a package firmware with 3 files+pit512, you'll find boot.bin and sbl.bin.
boot.bin --> primary bootloader
sbl.bin --> secondary bootloader
I hope you don't mean what does a bootloader with your question.....
You'll have to try flashing different ODIN or Heimdall Stock builds. Unfortunately, it may or may not fix your problem. Make sure you have a USB Download Jig just in case because you'll probably get times where it looks like it won't turn on and its the only way to get it back up and running. If all else fails and your warranty is still intact, use it. These are the early signs of internal SD Card failure. If warranty is not an option, you should be able to use the external as your primary partition and lose the internal completely. Its what I'm doing currently on my i9000M with the infamous broken internal SD Card. My internal SD Card is gone completely but everything is running under my External SD Card perfectly.
Okay, so it's included within the three files + pit. That's okay, I thought there was more then four files after the extraction.. I am downloading JM8... Will tell you how I get on.
This time it said...
Android system recovery <2e>
Samsung recovery utils
for BML
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
_____________________________________
E:copy_dbdata_media:format SDCARD:
Formatting SDCARD...
format_root_device: /dev/block/mmcblkop1format_r
fsdevice -> /dev/block/mmcblkop1
format_vfat_device -> argv[1] :-F
format_vfat_device -> argv[2] : 32
format_vfat_device -> argv[3] :-0
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcbl
kop1
update media, finished
#MANUAL MODE#
-- Appling Multi-CSC...
Installing Multi-CSC
mps_dat value: KOR
copy_multi_carrier from: KOR
multicsc : can not acces tp /system/csc/KOR/system/
copy_common_data
^That's what happend when I flashed with JM8, (I had only flashed with PDA and repartition unchecked, due to phone and csc missing from the download.)
I will now click reboot system now...
dawgpound6985 said:
You'll have to try flashing different ODIN or Heimdall Stock builds. Unfortunately, it may or may not fix your problem. Make sure you have a USB Download Jig just in case because you'll probably get times where it looks like it won't turn on and its the only way to get it back up and running. If all else fails and your warranty is still intact, use it. These are the early signs of internal SD Card failure. If warranty is not an option, you should be able to use the external as your primary partition and lose the internal completely. Its what I'm doing currently on my i9000M with the infamous broken internal SD Card. My internal SD Card is gone completely but everything is running under my External SD Card perfectly.
Click to expand...
Click to collapse
Could you perhaps guide me on how to do so, I also think my internal SD CARD is also "buggered"..
Thanks in advance..
Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..
Sure. This is what I did on my i9000M. Internal SD Card is useless so everything is now running off my External 8 GB microSD.
Go to this page and grab Heimdall and JVT build:
http://forum.xda-developers.com/showthread.php?t=1196179
Heimdall: http://www.glassechidna.com.au/products/heimdall/
JVT: http://www.multiupload.com/QMORULUWRQ
ODIN may work but I haven't tried it out myself and the packages above are made specifically for Heimdall. Set up Heimdall along with its specific drivers (included in Heimdall) to allow it to flash the phone.
- Make sure you have an external SD Card in your phone and make sure its formatted to FAT32.
- Flash the Heimdall JVT build with repartion checked using Heimdall
- Once it reboots, it'll try to format the SD Card but fail to do so and give you an error message. Ignore it and reboot the phone.
- It should now boot into Stock JVT firmware. If you go to your Storage under settings, you'll notice that Internal and External SD Card will be unavailable which is expected. You'll have 2 GB of internal storage for apps and whatever other things.
- You have two options here: 1) Continue using stock JVT; 2) Flash a custom ROM.
So let's say you want to flash a custom ROM like Cyanogenmod or MIUI. Fire up Heimdall again and go back into download mode. Flash the CF-Root for JVT kernel by Chainfire using Heimdall:
http://forum.xda-developers.com/showpost.php?p=15188469&postcount=9
This will allows you to flash CWM files. You can now install Cyanogemod or whatever custom ROMs you like.
Switching the primary partitions:
Cyanogenmod has a setting where you can switch the primary partitions in Cyanogenmod settings.
Cyanogenmod Settings --> Application --> UNCHECK use internal storage --> Reboot. Your External SD Card will now be the primary partition.
For myself, I am currently running Galnet's MIUI ICS. It doesn't have the Cyanogenmod settings above. I instead use the vold.fstab trick to switch the two partitions. If you navigate to "system/etc" folder, you'll see a file called vold.fstab. Open it with Notepad++ or some other note editor. You'll see the following (this is only for Galnet's MIUI, other ROMs will have something similar. Just switch the partitions like below):
Code:
# internal sdcard
dev_mount sdcard /mnt/sdcard/external_sd auto [U]/devices/platform/s3c-sdhci.0/mmc_host/mmc0[/U]
# external sdcard
dev_mount emmc /mnt/sdcard 1 [U]/devices/platform/s3c-sdhci.2/mmc_host/mmc2[/U]
Switch the two underlined around and push the vold.fstab back into system/etc/ and put the correct permissions. Your external card will now be your primary partition and your internal SD card (unavailable) is the external.
So why switch the partitions? You don't necessarily have to but if you want your phone storage to be neat, do it as it changes your sdcard mounts around, etc. You'll also get back USB mounting functions which you can't do with the internal storage being unavailable and the primary partition.
Hooolagon said:
Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..
Click to expand...
Click to collapse
Yeah unfortunately, you have the dreaded Galaxy S bootloop. Internal SD Card is probably toast. You can test this by removing the External SD Card and trying to boot. It most likely won't get as far. What happened is that ODIN flashed Android to your external card and trying to boot off it.
I have tried to use heimdall, and once it had loaded and the phone rebooted I did get the error message, however after ignoring this, once I had rebooted the phone it goes back into the boot loop.?
Hooolagon said:
I have tried to use heimdall, and once it had loaded and the phone rebooted I did get the error message, however after ignoring this, once I had rebooted the phone it goes back into the boot loop.?
Click to expand...
Click to collapse
Have you tried reformatting your external SD Card? Just format it to FAT32 and then try again. Also, first boot may take a few minutes. You can verify that its booting fine by using logcat if you have ADB installed on your computer.
Flash jm9 mate, not jm8. Seems to resurrect better. With odin. Pit 512 with Repartition.
Sent from my GT-I9000 using xda premium
Hooolagon said:
Woah WOAH WOAH HAHAHA!... Its alive... slightly! It turns on with the galaxy S logo and does some sort of sound thing.. =/ then turns off! But wahay!... Thanks Umberto1978..
I did this by first flashing JM8 PDA with repartition off...
Then flashing JM1 PDA PHONE AND CSC WITH 512 PIT...
on restart this happened..
Click to expand...
Click to collapse
I am at work but will give this a shot... I also found a lot of people resolved problem by using JM8 with repartition and 512 pit
then with JPM & pit 803 with no repartition ticked...
Use Odin 1.3... 1.8 wont allow you to tick and untick with a repart file...
Will post results tonight... its been two days and i have tried everything...
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.
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