I'd recently flashed the Cognition new build. Yesterday morning I woke up (3 days later) and found that my phone was stuck at the white and blue AT&T screen.
I preformed the Odin 1-click (as I have many times in the past<I'm not a noob to Odin>) I got my phone into a reboot but now it gets stuck at the Galaxy S screen and then goes dark.
Naturally, I used Odin again with different degrees of failure.
1. Gets stuck at file analysis.
2. Gets stuck halfway through and a blue, green or black screen appears.
3. Stuck at the AT&T screen again.
I've used Odin about 25 - 50 times in the last twenty-four hours.
I've also used the other Odin using the I897UCJH2 PDA file that's provided.
The phone booted directly into recovery and gave this error:
E:Can't Mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media: Can't mount SDCARD:
copy default media content failed.
And then it went back to the aforementioned black screen of hell.
I have build 1007 in case that's relevant.
I NEED HELP! Preferably a genius.
im having the exact same problem.
please help
I'm not sure if it matters too much, but it could certainly have had something to do with the kernel the newer Cognition would have installed when you upgraded to it.
Are you using I897UCJF6-final-OCD-REV or I897UCJI6-OCD-REV02-Low?
Most people have the first one, I would definitely try the second if it wasn't working.
The last option is to use Odin3 v1.7 (which you seem to have) and using that to update the kernel to a CM7 one and try to install CM7 onto your phone (and then reverting back to 2.1 stock if you wish).
Not sure if any of those options would work, but give me a yell if you need any help with doing any of the above.
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
You will get your phone working, just be patient and go step by step.
Thank You Both
Thank you both but neither of those two options worked.
I was hopeful that the CM would fix it. I played around with that thought yesterday.
I know the difference between ODIN 1-click and ODIN3 v1.70. I've tried both and neither can get me back up and running. I'm hopeful that someone comes to the table with some resolution. This is frustrating.
EDIT:
Oh and I forgot, I've actually used both I897UCJF6-final-OCD-REV and I897UCJI6-OCD-REV02-Low
If you can get into recovery you can get into download mode.
If you tried one-click, what happens when you try to flash back to stock?
I'm able to get into Download Mode AND Recovery.
That's not the problem.
What happens is that when my phone reboots after ODIN 1-click or ODIN v1.70 my phone boots like its supposed to boot and then it gets to the Galaxy S screen and at that point it just craps out and the screen goes black after a few minutes. I think that the problem is that the internal sd card won't mount. When I'm in recovery it says:
"E:Can't mount /dev/block/mmcblk0p1
(I/O Error)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please us UI me nu for format and reboot actions"
When I try to format the internal SD using system recovery it says the same thing. I'm able to get my computer to recognize the internal sd card in recovery BUT when I try to access the drive it asks me to format the drive (INTERNAL SDCARD being the drive). It then calls me a sack of SH17 and the computer tells me that it's unable to mount the internal SD.
The problem seems to be that my phone has not mounted any memory what-so-ever. If I were able to perform a masterclear that might help but without it being able to get to the home screen that presents a problem.
It's sh177y because I'll have to end up returning it on warranty AND for that I have to mail it back to Samsung and wait for them to return it to me. I can't go that long without my phone. There are business things that I need this phone for.
Sorry that was just a tiny rant.
You did not read the thread I linked to.
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click. When the partitions are formatted squirelly, the computer can't recognize the phone as such. Give that a try. You'll get there, be patient.
?
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Bwrandon said:
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Click to expand...
Click to collapse
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
gorgy76 said:
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
Click to expand...
Click to collapse
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
I wish you the best of luck.
ive had similar issues as described in this thread before on ONE pc i have and it can be a real PITA!
Im no real expert but i DO know the pc i use has voltage issues, basically it is running everything fine but things cant seem to charge or external devices tend to act weird occasionally off the usb. What i have done to minimize the similar issues you are describing is
1) plug the usb directly into the back of the pc, basically try different usb ports, some seem to get better voltage/stability.
2) unplug any external devices using usb *printers and whatnot*
3)Alternate PC *sorry this is my end all since i found i have no issues on my laptop*
It doesnt 'sound' like your phone is fubar'd but that your pc isnt getting the strongest connection. again this is comming from someone who had pretty much exactly what your describing and thats what i found
edit: also saw your warranty posting. From me on their 4th captivate and seems to be the final stable one *HORARY!* i can tell you that they will send you a new phone first and you send your defective one back..just do it in the timeframe or they WILL charge your att account
The only thing that I can think of is... Put a kernel that has CWM loaded on to it as recovery (maybe speedmod kernel), boot into recovert (and thus into CWM).
Try deleting all data/cache/etc on it, then try reboot it. Other wise, try and install a ROM straight from CWM (via .zip file, if you can somehow get it on your sdcard).
I'm stuck with phone pc-pc screen. I'v flashed multiple times and went back to stock too without issue. But now... I am stuck at that screen and no button combo works. Ordered a jig but that will take days to get here.. Dont know what to do. And its a work phone. lol Any other things to try?
I'm having a similar issue. I can get into download, and it's recognized by odin. But when I try to write or wipe it just sits at the zimage and does nothing. I've even left it over night to no avail.
Bwrandon said:
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
Click to expand...
Click to collapse
can your pc still recognizes your phone and copy files towards internal sd card? can you enter 3e recovery? does you lost 3 button combo? file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system. it is realy important not to neglect those default settings as this is the usual reasons for bricked phones that would corrupt the installation process. many people forgot this process due to excitement and ended up with a paper weight phone.
clemmie said:
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
Click to expand...
Click to collapse
gorgy76 said:
file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system.
Click to expand...
Click to collapse
You just can't make it clear enough for some people.
clemmie said:
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click.
Click to expand...
Click to collapse
Clemmie,
"Try installing the specific driver package that comes with one click."
I'm not sure if you read my OP; I've already done that. I've actually done that several times. I understand how to use ODIN 1.00 and 1.70. I've been using them since they were released.
The lagfix/overclock issue that has been mentioned. I understand that. Fixing it is the problem.
Have you tried my solution? It's definitely worth a try :/
Related
Hi,
I flashed the Pre rooted JP3 from http://forum.xda-developers.com/showthread.php?t=748131 and then installed the [UTIL] One Click Lag Fix 2.0 from http://forum.xda-developers.com/showthread.php?t=751864
I used the phone for a couple of hours and then all of a sudden everything kept crashing.
I booted into the clockwork recovery and reset to factory and then was not able to boot.
I tried flashing back to I9000UGJH2 with Pit512 and Odin and after it flashes successfully the phone starts I see the galaxy S I9000 and then it shows me a grey battery sign and then a busy circle sign and then gray battery and keeps repeating.
When I boot without the usb cable it shows me the Galaxy I9000m sign and then just turns off.
When I tried reflashing the JP3 from the site above and after it finishes it comes to the Android System Recovery <3e> and displays the following message:
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (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
copy default media content failed.
When I boot it moves past the Galaxy I9000m screen shows me the galaxy screen with animation and sound, the screen then goes of leaving me with a black screen and the buttons lit.
I cannot format the internal SD card and I cannot seem to get the hone to boot into android, I can boot into downloader.
Any help would be appreciated
P.S. I have ticked the repartition option in Odin
Odin should theoretically work. I've never clicked repartition myself however a lot of people do seem to recommend it.
If you're out of things to try and you want to give the latest (not publicly released) version of Heimdall (my Odin flashing software alternative) a go let me know and I'll PM you the download link.
That gray battery with a spinning circle sounds like the charging screen when the phone is off. Have you tried and let it charge up over night?
The battery is full.
I managed to get the I9000UGJH2 rom up and running by inserting an external sd card.
But here are some issues:
Once booted neither of the SD cards are recognized
If I power down / reboot phone, it will not start again, it shows the I9000m screen and turns off.
I suspect whatever the one click lag did to my SD cards needs to be reversed.
Ok,
So after tonnes of playing around with the device. I can confirm that it has something to do with he internal SD card.
I need to somehow format the entire internal SD card so that even Odin can see it. I tried using the stock recovery and clockworks with no luck.
It just wont see the card.
Any suggestions?
Phone won't reboot ODIN says PASS, Frozen on Galaxy S home screen
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks
galaxys00 said:
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks
Click to expand...
Click to collapse
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.
I used to get this on my htc dream try going back to original firmware the only I found it to work was rip a rom to pieces get misc.img then enter console via recovery and flash_image misc misc.img then something else but cant seem to remember think its mount-o rw,remount -r yaffs2 /dev/block/mmcblkop3 /system. dont quote me on this try typing the error into google
Sent from my GT-I9000 using XDA App
rumy said:
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.
Click to expand...
Click to collapse
The lagfixes do not repartition anything so this is (most likely) an issue that is not related to the lagfix.
Try going back to somthing like JF3 with the 513.pit file and repartition enabled.
The exact same thing happened to me - installed JP3 then lagfix. Phone was unstable after so I tried to reflash via ODIN (with repartition) and no matter what I did I could not successfully reflash my phone or get it to boot.
Only solution - returned it to the store as a DOA and got a replacement device.
Upon further research, it is known that JP3 screws up the internal SDCARD. Marks it as read only or something like that - search google for JP3 sdcard for more details.
Bottom line - your phone is bricked. Sorry to be the bearer of bad news.
I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135
rumy said:
I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135
Click to expand...
Click to collapse
That installs a different Linux distro underneath android and is totally unrelated! (Not to mention not doable in the state the phone is in)
OT: I don't believe you should give up quite yet. Try flashing a new firmware and afterwards, install Clockwork recovery!
From there you can format your internal SD. You will lose all your data but I strongly believe it will help fix your problem from what I have read here so far!
Edit: I added a warning to the flash guide in my FAQ for I9000M owners for now!
hey try this
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.
ice3186 said:
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.
Click to expand...
Click to collapse
I'm not sure what you mean. I am pretty sure he used Odin to flash the firmware. I think you are talking about the same program he already is using.
Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.
snapper.fishes said:
Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.
Click to expand...
Click to collapse
"Do not uninstall google talk" is not something you need or want in an faq. It's called a frequently asked questions because they are frequent. I have never before seen someone who tried or even wanted to uninstall google talk (not to mention that this is a goggle os and removing central apps like that is bound to produce problems). And if you mess around with root like that you have only yourself to blame for not doing enough research!
Sent from my GT-I9000 using XDA App
Good idea.
Downloading now will try and post. Fingers Crossed!
OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up
Calm down and tell us exactly what you did. It sounds like the initial problems that occurred on early recovery. The download mode should still be reachable. I don't think recovery can completely brick your phone.
rumy said:
OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
The problem is related to the message
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (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
copy default media content failed.
If you research this error via Google you will find several references to JP3 screwing up the permissions/structure of the internal SDCARD.
I spent several days trying to fix this issue on my phone and no matter what I did (Clockwork or no) I could not get the phone to reset/recognize the SDCARD.
As I said, my only recourse was returning the phone for a replacement. I really hope you find a fix but I think it unlikely.
I turned on my phone today to find that it mysteriously shut off...I went to turn it back on, and it just sits at the first screen forever (the one that says GT-I9000), so I pull the battery and boot into recovery. In the command line section, I get:
Code:
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
My guess is that it's some sort of a partitioning error, but I really have no clue...is this a fixable error? Also, if it makes a difference, my phone is the Canadian Bell version (GT-I9000M), purchased back in September. I've been using i9000 ROMs since I got it though, and they seem to work flawlessly (much, much better than using whatever is out there specifically for the I9000M, anyway).
Thanks in advance!
your phone is fried, just take a quick gaze upon the forums, you have a very common problem, call bell, get a 100 dollar credit and a new phone in 1 week
C.L.Android said:
I turned on my phone today to find that it mysteriously shut off...I went to turn it back on, and it just sits at the first screen forever (the one that says GT-I9000), so I pull the battery and boot into recovery. In the command line section, I get:
Code:
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
copy default media content failed.
My guess is that it's some sort of a partitioning error, but I really have no clue...is this a fixable error? Also, if it makes a difference, my phone is the Canadian Bell version (GT-I9000M), purchased back in September. I've been using i9000 ROMs since I got it though, and they seem to work flawlessly (much, much better than using whatever is out there specifically for the I9000M, anyway).
Thanks in advance!
Click to expand...
Click to collapse
Try formatting your internal sd card via recovery 3e or CWM (what ever you use).
androidsl said:
Try formatting your internal sd card via recovery 3e or CWM (what ever you use).
Click to expand...
Click to collapse
When I try to format it using 3e, I get the same error message as on entering recovery move (can't mount). I've also tried several 3e factory resets and cache partition wipes, and Odin reflashes, but no luck from any of it.
Try flashing with these steps. I didn't have my internal SD die but I could not mount or format mine. Flashing with the 3 part older firmware and then upgrading to a new firmware without repartitioning has saved me several times. Let me know if it works for you.
http://forum.xda-developers.com/showthread.php?t=818556
It happened to me as well, but mine was because battery was dead.
So the obvious advise is to charge the battery completely before you do anything.
Sent from my GT-I9000 using XDA App
The battery is sufficiently charged, I'm pretty sure
After flashing to JPY through Odin, when it finishes and says pass, the screen goes blank, and then the only thing that will work is download mode (holding the power button to turn it on doesn't produce a bootloop). In the morning, I'll probably try the non-Odin method.
C.L.Android said:
The battery is sufficiently charged, I'm pretty sure
After flashing to JPY through Odin, when it finishes and says pass, the screen goes blank, and then the only thing that will work is download mode (holding the power button to turn it on doesn't produce a bootloop). In the morning, I'll probably try the non-Odin method.
Click to expand...
Click to collapse
Read the Entire First post in this thread hopfully it gets you running again.
http://forum.xda-developers.com/showthread.php?t=905975&highlight=JL2
Good Luck.
Flash using odin xxjpk than latest rom like darky v8.1
Sent from my GT-I9000 using XDA App
Did you follow the whole post I showed you? The symtoms you are describing sounds like you jumped directly to flashing jpy which will not work. You need to flash the 3 part jpu first.
They advice to flash jl2 may work as well. Jl2 has actual code changes to address sdcard issues. You may experience issues going to jpy afterwards though.
Sorry...I meant JPU, not JPY
I flashed JL2, which bootloops at the galaxy s screen (where it says GT-I9000M), and can't access recovery mode (it can access download mode though)
What should I do from here?
okay, that is fine. Now you need to flash with an older firmware, then a newer one. 3 part jpu with repartition, then jpy without repartition. If that doesn't work, you may have a dead sd. But I was bootlooping on JL2 just before I fixed mine. Here you can read this thread too where I posted fixing mine.
http://forum.xda-developers.com/showthread.php?t=892534
P.S. its supposed to not boot on the first flash (black screen). Thats why you need to flash it twice. It takes some code from the older firmware and some from the newer.
Tried, and that didn't work, so I'm assuming that my internal SD card is done; thanks for the help, though
does Samsung have an official statement on their "new phone + $100" thing I've seen around? I can't imagine that's something the store I bought my phone at will want to help me with
My friend works at Bell. He told me they are sending phones in for repair or replacement. Takes about a week. He didn't know if they are still giving out $100. He didn't think so.
Crappy about the phone. Was worth a try.....
So the story goes I installed Assonance on my Captivate from Official 2.2. Started having problems with the phone being stuck in Landscape mode. This problem followed when I installed Firefly. So I decided to try to go back to JF6 and clear everything. Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen. Can't get into Download mode with volume down + power or volume up down + usb. Need advice to try to get phone fixed/replaced, i'm stuck using a BlackBerry Bold. Any help please?
Google usb jig
CM7
Figured
Yeah that's what I figured. The only thing I'm curious about is the landscape mode issue following me around on different ROMS. After I hopefully unbrick the phone do you think it would be worth taking it to ATT?
Go to radioshack, 99 cents, use the video below for reference. You need 3 100k OHM resistors, and they run .99 cents for 5 of them. Use that to kick it into Download Mode and reflash. As for returning it to AT&T, if the orientation problem continues, I would if this doesn't fix anything.
http://www.youtube.com/watch?v=D0aoabVtPJ8
What Kernel did you flash before everything went haywire? This is a classic sign of an i9000 kernel being flashed to a Captivate.
Forget download mode for the moment, can you get back into recovery?
It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.
geokhentix said:
It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.
Click to expand...
Click to collapse
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.
clemmie said:
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.
Click to expand...
Click to collapse
hmmmn I agree. too many bricked phones not disabling lagfix and clock default values in their kernel when flashing back to stock. seems many forgot that procedure. every dev always states here to disable lagfix when flashing new rom and set back default clock values in current kernel. the very first step neglected PITA to troubleshoot.
Before you go and buy anything, did you try this method (sorry, if you said you did)? It always works for me, especially at the "Phone--!--Computer" screen.
FROM: How to unbrick the totally bricked captivate. [Click the > after "Originally Posted by thekurrgan" for the full source.]
thekurrgan said:
So far this has been the only sure fire method I've found to 100% get around any brick situation regardless of firmware, etc. This only works for the captivate, not any other galaxy s variant.
Situations: phone-!-Computer / no download mode
Black Screen / RST_STATUS 0x0
Procedure:
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Connect usb cable.
5. Hold volume up + volume down + Power.
6. Insert battery.
7. Release POWER BUTTON ONLY.
Click to expand...
Click to collapse
If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7
mcord11758 said:
If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7
Click to expand...
Click to collapse
It says nowhere in the OP that he used one click; as a matter of fact:
jonp92 said:
Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen.
Click to expand...
Click to collapse
I've seen this many many times, and it is usually a result of a non-disabled lagfix or OC kernel. I've been down this road with a few people. He may be trying to use one-click now, but without being able to get into DL mode he's stuck. I'm trying to help him get into DL mode, as are other posters. Let's just focus on getting him to DL mode.
buy this:
http://cgi.ebay.com/ws/eBayISAPI.dl...69781&ssPageName=STRK:MESELX:IT#ht_623wt_1139
SOLVED: when having trouble with your computer not making a good connection to the phone, try your USB HUB on the mother board. it totally fixed my problem!
So here it is. I received a cappy from a buddy at work.
Basically, she is running cognition (FROYO BASED) rom, not sure of the kernal, and Cwm.
i can get the phone to reboot into RED CWM recovery, and even into DOWNload mode.
The phone was shut off during a factory reset. the battery died.
(IDK the girl was a dumbass and did it from settings on the phone not in CWM )
The phone will boot, ONLY after a factory reset from CWM but the setup google accs f/c's and the only thing i can get it to do is volume up/down pull the notification bar down and power off recovey dl mode...ect ect.
Task manager say's there are no APPS installed on the phone running? yet when i go LVL 2 RAM clear, the phone says 13 apps closed..
I think the Stock APK's have been deleted, since i cannot get into menu at all.
Since she factory reset the phone, and wiped the SD CARD, ALL CWM recoveries she created are GONE.
I have Cleared the cache, and wiped dalvik code, fixed permissions.....
I'm very familiar with the VIBRANTS, not the cappy's so this is a challenge to me.
my Vibrant has connected with all the usb drivers from samsung, but the cappy cannot. I've even downloaded the drivers for just the CAPPY, uninstalled all others, and Still not recognized, yet my vibrant does?
i've installed i think every driver on here for captivates, kies downloads, even went to the samsung website and Downloaded from there.
STILL NOT CONNECTING.
Even DL'd the AIO cappy toolbox (very nice to have for my VIBRANT)
Still no avail.
THE PHONE CANNOT MOUNT THE EX SD CARD. So that idea's out.
all my drivers are correct for the 32 bit vista OS. even tried on my GF's 64 Windows 7.
Still no avail.
I've installed the drivers with the phone in DOWNLOAD mode even, still not connecting.
Rebooted the computer after removing and also reinstalling drivers.
Changed between 3 diff cords, all work for my VIBRANT,
still no avail.
Any idea's would be greatly appreciated.
Thanks.
PelvicThunder said:
So here it is. I received a cappy from a buddy at work.
Basically, she is running cognition rom, not sure of the kernal, and Cwm.
i can get the phone to reboot into RED CWM recovery, and even into DOWNload mode.
The phone was shut off during a factory reset. the battery died.
(IDK the girl was a dumbass and did it from settings on the phone not in CWM )
The phone will boot, ONLY after a factory reset from CWM but the setup google accs f/c's and the only thing i can get it to do is volume up/down pull the notification bar down and power off recovey dl mode...ect ect.
Task manager say's there are no APPS installed on the phone running? yet when i go LVL 2 RAM clear, the phone says 13 apps closed..
I think the Stock APK's have been deleted, since i cannot get into menu at all.
Since she factory reset the phone, and wiped the SD CARD, ALL CWM recoveries she created are GONE.
I have Cleared the cache, and wiped dalvik code, fixed permissions.....
I'm very familiar with the VIBRANTS, not the cappy's so this is a challenge to me.
my Vibrant has connected with all the usb drivers from samsung, but the cappy cannot. I've even downloaded the drivers for just the CAPPY, uninstalled all others, and Still not recognized, yet my vibrant does?
i've installed i think every driver on here for captivates, kies downloads, even went to the samsung website and Downloaded from there.
STILL NOT CONNECTING.
Even DL'd the AIO cappy toolbox (very nice to have for my VIBRANT)
Still no avail.
all my drivers are correct for the 32 bit vista OS. even tried on my GF's 64 Windows 7.
Still no avail.
I've installed the drivers with the phone in DOWNLOAD mode even, still not connecting.
Rebooted the computer after removing and also reinstalling drivers.
Changed between 3 diff cords, all work for my VIBRANT,
still no avail.
Any idea's would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
First, see if you can find out which version of Cognition she was running (Gingerbread- or Froyo-based).
Once you have that information, I believe you should be able to download the appropriate ROM on you computer and copy it to the microSD card (adapter or whatever method you need to do to get it there). Since you can get into CWM recovery, you could try flashing the ROM from there. Assuming it's a full wipe rom (and you're not concerned about keeping apps installed on the phone), it should reset things to a more workable state. (If you are worried about apps remaining... I don't know what to say at this point, since you can't get to Tibu.)
If that doesn't work, you could try the one-click back to stock (realizing that you're having connectivity issues, I'll get to that in a second).
When you connect the phone in download mode to ODIN, does the yellow COM:# show up?
If you have tried ODIN on your Vista computer, try running ODIN as Administrator.
I've had some luck in the past getting the phone to be recognized (assuming Froyo) by doing this:
1. With nothing connected to computer, start ODIN (one-click to stock would be good).
2. Pull battery on phone.
3. Reinsert battery, but do not power on.
4. Hold Vol+/Vol-/, and insert USB cable.
5. Wait for it to kick into download mode, release buttons, and wait again.
6. See if ODIN recognizes it.
jmtheiss said:
First, see if you can find out which version of Cognition she was running (Gingerbread- or Froyo-based).
Once you have that information, I believe you should be able to download the appropriate ROM on you computer and copy it to the microSD card (adapter or whatever method you need to do to get it there). Since you can get into CWM recovery, you could try flashing the ROM from there. Assuming it's a full wipe rom (and you're not concerned about keeping apps installed on the phone), it should reset things to a more workable state. (If you are worried about apps remaining... I don't know what to say at this point, since you can't get to Tibu.)
If that doesn't work, you could try the one-click back to stock (realizing that you're having connectivity issues, I'll get to that in a second).
When you connect the phone in download mode to ODIN, does the yellow COM:# show up?
If you have tried ODIN on your Vista computer, try running ODIN as Administrator.
I've had some luck in the past getting the phone to be recognized (assuming Froyo) by doing this:
1. With nothing connected to computer, start ODIN (one-click to stock would be good).
2. Pull battery on phone.
3. Reinsert battery, but do not power on.
4. Hold Vol+/Vol-/, and insert USB cable.
5. Wait for it to kick into download mode, release buttons, and wait again.
6. See if ODIN recognizes it.
Click to expand...
Click to collapse
Thats my problem, the cappy does not see that there's an EX SD card there at all? says no files, but i've tried to push a cognition rom to the EX SD and use CWM to flash it to get it to boot, but the phone cannot see that there's an EX SD, but the SD card is fine, even my vibrant used it..
ODIN as ADMIN? tried that and nothing, still no yellow com port,
i know how to use odin, as my VIBE has been "Bricked" a few times lol
the vol up/down button combo does nothing, just shows up as a charging screen, the only way i can get the phone to download mode is through CWM.
the phone is running a FROYO based cognition ROM. or that's what her bf put on there.
This may sound stupid and simple but is the device set on mass storage from the settings menu? If you know.
Also have you tried mounting your sd cards in CWM?
Rhiannon224 said:
This may sound stupid and simple but is the device set on mass storage from the settings menu? If you know.
Also have you tried mounting your sd cards in CWM?
Click to expand...
Click to collapse
lol THATS MY PROBLEM> the phone thinks it boots normally, but i cannot get the settings menu. like the "SETTINGS APK" file was deleted when she formatted the SD!
but i was just playing around and i got google voice search to pop up!
then from there i used my WIFI and setup the google settings, then i went to the market grabbed CWM and used the cognition rom i've already downloaded, and used it!
then the GREEN CWM booted, and it still cannot MOUNT EX SD card. so the flash failed.. HMMMMMM
As of now i am gonna go into the rom i DLed (cognition) and try to DL Root explorer and hard push the Settings.apk file to the system. HOPEFULLY from there i can get my settings back to restore the phone.
Realizing that it's a long shot at best due to connectivity issues, have you tried using ADB?
If so, you could push the ROM you need to the internal SD.
so, used root explorer to move the NEW cognition froyo rom from the EXternal SD to the INTERNAL SD. from there i used CWM recovery to flash the rom, the rom flash was successful, but now the phone is stuck in bootloop on the AT&T world phone screen.
and CWM will not LOAD. FML
Looks like i'm gonna have to take this apart and get to the internal SD card. =/
Can you get to CWM with the Vol+/Vol-/Power combo - hold those past one AT&T screen and when you see the second one, let go?
Adb was not an option at that point, the phone couldn't recognize it even had a phone attached to it.
but now that i'm stuck in bootloop and with no CWM recovery OR DL MODE, yeah the jig isnt' workin... HAHA
i guess its just a paperweight now.. Owell, i tried.
i held it for about 3 mins... lol and the jig i got for my VIBRANT isn't workin either. I didnt know these phone's can lose the 3 button combo reset? i often flash I9000 roms to my vibe, thats why i have a jig, but i didnt think cappy's would do that unless i flashed an i9000 rom to it? lol
Just because I'm not sure if you tried it - have you tried plugging the cable into a different port on your computer? If it's not one directly connected to the motherboard, that can sometimes cause problems getting the phone to be recognized.
Also - does the phone show any signs of recognizing there is a cable inserted (like charging)?
tried every port. No the phone only acts as if it wants to display the batt charging symbol, but does not show, I cant believe it, i actually think i bricked a galaxy s.. haha
Another long shot, but you could try the One-click unbrick. Since it's Heimdall-based, there's always a chance.
Wow, didnt know that even existed. Definately gonna be useful for my Vibrant, haha i'll give it a shot.. THANKS, i'll report back after i try it.
I hope it does something. With the connectivity issues you're seeing it's starting to sound a little like hardware issues.
I'm going to throw out a checklist of stuff, knowing that you are already experienced with ODIN and ROM flashing, simply because I know I usually can use some sort of checklist to make sure I've caught everything.
- Redownloading/reinstalling drivers, rebooting before connecting phone
- Redownloading/reinstalling ODIN package
- Redownloading ROM to flash
- Hold V+/V-, inserting USB cable
- Remove battery, hold V+/V-, insert USB, insert battery
- Hold V+/V-/HOME softkey
- Hold V+/V-/HOME/Power
- If download mode reached, allowing phone to sit connected for long time
- If download mode reached, connecting phone after opening ODIN
- If download mode reached, connecting phone before opening ODIN
- If download mode reached, connecting phone after ODIN, disconnecting, reconnecting phone
That's all I can think of for a checklist of stuff to try/retry.
I appreciate the help but i've tried all of those options several times, The jig did work to get it into DL mode, but from there i'm still in the same **** position, my computer will not recognize that the phone is connected.
Is it possible that the phone somehow lost its drivers? what i mean by that is, the phone acts different with different USB ports, completely.
On one port it says unknown device, another USB android composite device.
Its as if the phone's changing as i change ports. Very FRUSTRATING!
i think it could be a hardware issue myself, but how could a corrupt drive work so well? To the T every time i've used the jig DL mode fired up, but my computer still cannot find the drivers to run it. Hell i've even tried using winusb drivers package to force install the phone, still no avail.
Like i said, I really appreciate the input, I figured if i couldnt figure it out, someone on here had some EXP in doing this lol i've just never had a driver problem give me so much trouble. IDK, bout ready to turn this paper weight into a pile of ash.
If you can get into cwm, have you tried doing another hard reset/factory wipe?
Thats the problem, earlier i COULD get into CWM, and hell i flashed the new rom perfectly!
now it is stuck bootlooping, therefore i just used the Jig, and first few times it didnt work, now its stuck bootlooping, download mode is attainable, and still NOT connecting to my pc via usb.
mrhaley30705 said:
If you can get into cwm, have you tried doing another hard reset/factory wipe?
Click to expand...
Click to collapse
Nvm, reread your post. Have you tried flashing a different rom?
PelvicThunder said:
Thats the problem, earlier i COULD get into CWM, and hell i flashed the new rom perfectly!
now it is stuck bootlooping, therefore i just used the Jig, and first few times it didnt work, now its stuck bootlooping, download mode is attainable, and still NOT connecting to my pc via usb.
Click to expand...
Click to collapse
Try a different computer? also, which version o of odin are you using? I've found 1.3 & 1.82 to work best.
!PROBLEM SOLVED!
Hi there,
I hope I am posting in the right place, I hate clutter. I also hope there is something that can be done about this:
I was trying to install a ROM and as usual I used ODIN to go back to stock (JFD) and from there on I would use the One Click Root and then via ClockWork flash the ROM I wanted to try.
This time the ROM said (yes, it was talking) that some partition had not enough space. So, when I went back to ClockWork I saw an option to Partition the drive.. so I did that, and from then on only nightmares...
Nothing would flash properly, even via ODIN. I would get error message about MBR not being able to mount and such. After countless hours of black screen after the Galaxy S logo I finally managed to get a Eugene ROM flashed via ODIN, but now I have a new issue - I cannot install anything, no Titanium, no ClockWork, because my Application Storage is 0B. My external SD is its normal size (a 16GB card, shows 14.83 I think), but the internal storage is 14GB or so and there is virtually NO Application Storage..
* I tried re-flashing things - nothing works other than the Eugene ROM. No JFD, no JI6, nada..
* Would not manage to use an update.zip from the manual recovery (I get the stock Samsung Recovery, it sucks!)
* Cannot install ClockWork and try to fix it from there (or flash another rom via CWR)
* I tried to re-partition via ODIN - no dice.
* I tried to re-partition with Partition Magic (I know... that was my desperate attempt at 1 am after 14 hours of struggle) and it doesn't seem to work (duh).
I am out of ideas and I could really use some help. Did anyone have this issue and what was the solution?
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Thank you, I will give it a try and let you know how it goes! Much appreciated!
german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse
german103 said:
I had this issue, I don't remember the exact steps but I do remember I used "parted" to repartition.
http://forum.xda-developers.com/showthread.php?t=1046220
edit: I remembered: delete the smaller partition, then ODIN to stock w/ repartition checked, and you should get you app storage back.
Click to expand...
Click to collapse
Okay, no idea to use "parted". I did download the zip file with the six little guys, but now what? Android SDK? Oh my... no clue...
Any chance for a step by step?
So I download the Android SDK and got the 6 files into the "tools" directory, but now I have no idea what to do...
UPDATE: Okay, I managed to get the ADB going, but when I try to push them files with the command it says failed to copy (the path) "Permission denied"
SOLVED!
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
just put a froyo bootloader on an the 1900 will go away
hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
No dice. Didnt work for me
hachaduryan said:
Guys, problem solved. Here is how in a nutshell:
So, I saw this post - http://forum.xda-developers.com/showthread.php?t=1081732 and although it is for the I9000 I figured I didn't have much to loose anyways. So I did look for EZbase ROM as one of the users suggested (http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/) and got busy. Finding the files was hard (because of expired links and such), but the link above seemed to work.
Once I collected all the files I performed the process just as described (with the partition checked) and ended up with the Galaxy S I9000 boot (instead of Vibrant) and it was in a boot cycle.
Then I managed to bring the phone to Download Mode (key combo is different now, it is power and Vol Up, not as it used to be) and flashed JFD via Odin (checked the re-partition here as well, although I don't know if that mattered).
And a few minutes later I ended up with a working stock Vibrant. The funny thing is that when you boot the device it first shows the I9000 boot image and then switches it to Vibrant (but I really don't give a damn about that).
So there it is! Hope this helps some poor souls who are in the situation I was.
Cheers!
And it worked!
Click to expand...
Click to collapse
So it seems that there are easier methods to solve this issue now.. glad you worked this out