Well, Ive been flashing roms for a while now and I have an issue with my captivate.
Lets start in the beginning. I had my captivate on THS ICS rom and It was going great. But my captivate isn't that great anymore. The power button is broken, but I was able to go around that. (Sidenote: It turns on when I plug in the battery.) Anyway, I wanted to go back to stock because I did have the right bootloaders. (I couldnt get into download mode with the button combination. I thought it was the bootloaders fault. Im I wrong?) I wanted to switch to I9000 bootloaders but I had to start fresh. But before all that, I noticed that while I was on ICS rom, I was unable to go to download mode. I used to before, but it magically disappeared (I know it didnt, I know I did something to it but I don't quite remember when it happened.) So I was unable to flash a new rom, if I wanted to.
A couple of days ago, I bought a jig and it worked! It took me straight to download mode. So I decided to get my Captivate and make it go back to stock. So I opened Odin, it found my Cappy and I clicked start. But, it stopped at factoryfs.rfs. I waited a half hour and nothing. So I unplugged it and now it won't turn on. But it can still go into Download Mode and be seen by Odin but it just wont finish. I tried both odin one click and the regular odin. I looked everywhere for more than six hours and nothing came up. Please guys, if anyone knows what I can do to fix it, please reply.
I might have missed something, but just ask if you need any more info. Please help me.
Edit: I forgot to add this:
While I was on the ICS rom, I switched over to CM7 to see if the process of going back to stock would be easier. Thats when I tried to flash stock. It didnt work as well as I thought it would.
And I knew that I didnt have I9000 bootloaders because I installed the Icy Glitch kernel and each time I tried to have DIDDLE on it would go to deep sleep mode and I was unable to wake it back up.
As long as you can get to download mode you are fine. Try flashing a different stock from. Or using Hiemdell
I've tried both odin and Hiemdell. But with Hiemdell, it would always tell me that I dont have the drivers installed. So, it installs it for me. Even with the drivers installed, it keeps telling me that I dont have the proper drivers installed.
I have had this exact problem, where a bricked captivate can get into download mode but when restored to stock through a one-click, it freezes on the factoryfs.rfs. However, in my case after freezing at this stage, the phone was completely inoperable, and could not even enter download mode, so I am suprised yours could.
What works for me is to remove the battery, wait for a few seconds, put the battery back in, use the usb jig to enter download mode, and then WITHOUT the phone plugged into the pc, download and open this one-click file http://http://forum.xda-developers.com/showthread.php?t=731989.
Once the odin one click is open, plug the usb cable into the pc, and then into the phone. This one-click has never failed me. Hope this helps.
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Juiceboy125 said:
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Click to expand...
Click to collapse
Depending on the CWM recovery you're in, you can sometimes use the search capacitive key to do the same thing as the power button will do.
I had the same problem you had with Odin stopping on flashing a file, turns out I was using a third party USB cable. I switched to the USB cable provided by Samsung when I bought my cappy and problem solved. Hope that helps.
Sent from my SGH-I897 using XDA
Finally!
Well, I got my Cappy up and running again. While I was stuck in the CWM I just decided to install Gingerbread using a One click and it worked. Now I'm back to CM9. Thanks guys for the suggestions. I guess I just needed to wait and double check everything.
Related
I need help from you guys. I have a Rogers i896 Captivate.
Today 2.2 was made available as an update on Kies, and silly me, believing that it would work properly, decided to do the update.
Just so you know, I have completely stock 2.1 on my phone, unrooted, nothing.
I plugged it in, backed up my SD card, backed up my contacts, then started downloading the update.
It then said it couldn't get into download mode, saying to try again later. I do, same result.
i try booting the phone into download mode, and Kies starts trying to connect to my phone. After a while, my phone screen turned a very light blue, and Kies told me the phone was unresponsive, and to restart the phone. I do, and voila. I get the magical connecting icon. I can't find a picture, but I'm sure you know what I'm talking about. The icon of a phone connecting to a PC, but there's a yellow exclamation mark.
This happens every time I press the power button, or if I try and enter recovery mode.
I can however enter download mode. I just don't know what to do with it. I haven't used Odin, and don't want to risk further damage.
More than anything, I just want a phone. At this point, I'm willing to use a non-stock ROM, although I'd prefer a Rogers ROM mostly, as the GPS actually seems to work sorta.
If anybody could walk me through the process, or link me to something that can help me do this.
*edit*
Wait, hold the phone.
I tried it one last time, and this time I got a popup in Kies saying my last upgrade attempt failed and my device may be unusable. click here to restore the original firmware. Currently doing that, we'll see how it goes. *crosses fingers*
Just put the phone in download mode then click on the update firmware button in kies.
It will probably say it has to restore the firmware that's fine just click through and it should finish and you'll be on 2.2 pm me if you have more problems
Sent from my SAMSUNG-SGH-I896 using XDA App
Nevermind all. Panicpost. I've got it figured out. Crisis averted.
Mods, feel free to lock/delete/move if you like.
However, for those who might have the same problem, if you can get into download mode, while in Kies, click firmware update, then at the bottom it will tell you you can restore the original firmware. I did that and the problem was fixed.
Now I'm going to be an idiot and try the 2.2 again
Actually, I just noticed. After "bricking", and restoring the firmware, I now have 2.2
Better yet, none of my apps or anything are gone! It just reset my homepages, Widgets and shortcuts are missing, but everything else is good.
whatever haha.
Actually if your in Canada the update has been out for a week now, but glad you have your phone working. I started the 2.2 thread and its mentioned in that thread how to get the 2.2 through Kies without issue.
HELP! I was trying to frehsly install a rom..
so i used odin to "master clear" everything
it deleted everything!
hoping that in recovery mode, it'll let me "mount storage" so i can transfer my new rom into the phone, that didnt happen!!!
so, then i tried to go with odin 1 click to install i896 stock...
and it doesnt work , so i unplugged phone, and now i get that mobile phone error..
please help, the only thing i can do successfully do is put my phone in download mode! D:
PLEASE! PLEASE!
THANK YOU!
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Sent from my SAMSUNG-SGH-I897 using XDA App
Read carefully.....
ags on board said:
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Click to expand...
Click to collapse
+1
Go into the ODIN thread and read extensively. Since you can get into download mode, make sure that once you connect your phone you get the COM notification in ODIN. Mine always appears in the small box in the upper left portion of ODIN one-click (if you don't get this, reinstall the samsung drivers found in the ODIN thread and reboot. If you're running Win7, make sure you run ODIN as admin).
Master Clear does exactly what it says...it wipes all of your data. MC is only supposed to be used when your phone is on and fully booted up with USB debugging on.
Flashing back to stock should only take ~5 minutes max - if it halts unplug, pull your battery, wait a few seconds, and restart. If it continues to fail, try a different USB port. If using a PC, use the back USB ports. If it still fails, try a different system. (I had this issue this weekend and finally got it on the first run on my friend's laptop - not sure what happened, had flashed 5-6 times on mine previously).
Hope this helps. Once you're back to stock, be sure to thank designgears for his killer dev work!
EDIT:
PS It's pretty tough to brick a cappy - read extensively in the ODIN thread and you'll see what I mean.
Its always good practice to back everything up and know the step by step procedures before you ever do anything. Good luck!
Connexxions "how to" videos are VERY detailed and shows you step by step how to do just about everything on this phone. I highly recommend them.
don't panic, ur lucky that u can still get into download mode. that is just soft brick I think..
Sent from my SAMSUNG-SGH-I897 using XDA App
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
I was playing around last night with updating my phone with a different and everything was fine. Today, I installed the proper kernel and it installed and ran fine. I decided I would install a different kernel, one that has audio via USB for the dock and after I selected the file with Odin, I started the install and then I noticed Odin said something about it being finished and removed. Now I started my phone and it just sits at the screen that says Galaxy S. The phone will not start and I cannot get into recovery or download mode. I have tried every button combination I could find online. Does anyone have any suggestions on how I can get into either download mode to install the kernel again, or recovery so I can just install the zip to reload the software.
Have you tried a jig or adb to get into download mode?
Sent from 234 Elm Street
I have never been able to properly get adb working, I know I am doing something wrong, but I actually just finally got it working. I was able to use One Click Root to have it restart my phone into recovery mode and I was able to reinstall the software and kernel. Everything is going good now, except I can't use the kernel I wanted to use because I don't know if it has CWM3.
This is the kernel that I actually wanna install.
http://forum.xda-developers.com/showthread.php?t=916233
You have SOFT bricked it which means you can get it out of it without JTAG at this point. Go to YouTube and search ODIN 1 Click and watch the video I made to help flash stock firmware.
Any updates OP?
Have you tried taking out and reinserting the battery then volume up, volume down while inserting your USB cable? That saved me one time. Then I bought a JIG.
Thanks for all the help, but I actually figured it out. I had forgotten I installed bootloaders and it changed the button combinations for Continuum.
My phone has been all screwy for months. I recently given up on it and bought a new phone but it irritates me that I still cannot fix this old phone.
After attempting to flash a new rom onto my phone everything went wrong. When I attempted to reboot the phone the phone showed the SAMSUNG screen then goes to CWD for recovery. I cannot fix this at all. Eventually I decided to run GTG's Ultimiate Unbrick thinking that Odin3 would fix my situation. It continuted to give me FAIL with every attempt. Now, the phone won't even show the SAMSUNG screen or the recovery screen. It just stays black... What can I do? Junk it? Is it permanently broke.. This is so upsetting.
Are you still able to access download mode? If so then i would try Heimdall this time using THIS flash file. Flash it once, let it reboot, then shutdown and go to download mode again. Flash once more with the "flash bootloaders" box checked. Has always worked for me when i screw something up due to not paying attention.
If you cannot access download mode WHAT-SO-EVER, i'm afraid i am unable to help.
Good luck
DarK_DemoN said:
Are you still able to access download mode? If so then i would try Heimdall this time using THIS flash file. Flash it once, let it reboot, then shutdown and go to download mode again. Flash once more with the "flash bootloaders" box checked. Has always worked for me when i screw something up due to not paying attention.
If you cannot access download mode WHAT-SO-EVER, i'm afraid i am unable to help.
Good luck
Click to expand...
Click to collapse
Tried today to put it into download mode. The screen flashes on completely white and back off. I can hear it connecting and disconnecting from the computer repeatedly. Im guessing there is nothing at all I can do from here. This really sucks.
mramazingpanda said:
Tried today to put it into download mode. The screen flashes on completely white and back off. I can hear it connecting and disconnecting from the computer repeatedly.
Click to expand...
Click to collapse
Does it connect and disconnect by itself? If it does then sounds like a hardware issue. If you can get it to connect to your computer open the JAR flash file which will open Heimdall after a few seconds (10-20). Once it's open press the Vol-Up button on your phone and see if Heimdall can see it (should say "Connected" in green at the bottom right).
Give it to me lol I'll fix it
Sent from my dr0id running Liquid Smooth r0m
I had something similar happen to me a long time ago. I would try to put it in download mode and the screen would do something but then just shut off. I pulled up heimdall and it said it was connected. I might have just gotten lucky. Give it a try though.