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.
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 :/
Ok I have looked at thread after thread and saw some similar issues but no real solution that has worked for me. Long story short, my brother tried updating his SGS4G and "says" the cable came out during update. Basically phone was stuck in communication with pc screen. After tons of trial and error button combos, jig, etc. I was about to give up as I couldn't get it into download mode. Well got bored so tried again and somehow got Odin to recognize the phone and started to flash the K1. Unfortunately, it failed before completing and now I can get the phone into DL mode but Odin nor the PC will recognize it. It sort of boot loops a couple times then loads up to home screen for a few seconds during media scanning then trips right back to Galaxy S 4g screen and starts the boot loop deal over again. I was able to check before it cut off and it has unknown baseband. Is there any other way to get Odin to recognize while in download? I have done all the steps then plug in phone etc. Odin just sits there and PC said usb not recognized. Tried 3 different PCs with XP, Linux, and Win 7. Is the baseband the issue for getting it recognized now? If I can ever get Odin to recognize I was hoping to manage a full backup to stock and then worry about the baseband issues but for now I am stuck and would have pulled all my hair out by now but I am bald. Any advice or pointing in the right direction would be great.
Edit: Thanks for the help. After tons of attempts I got Heimdall to recognize and got it flashed back to stock.. Still isn't recognizing all the time but hopefully it will enough to allow me to root it before I give it back to him. Thanks again I read and read and tried all sorts of stuff multiple times.
If you can get into download mode. Just start ODIN whether it recognizes phone or not and see what happens. And double check your settings are correct in ODIN. Make sure u have latest version as well. Or try Heimdall.
EDIT: Go ahead and tell us whether you were on FROYO or GB. And why were you flashing K1? And what is K1? KC1?
Are you using FB's GB Ext4 Starter Pack?
Odin can sometimes be a pain. If the computer gives you the "un recognized device" keep trying. Tried different cable and USB port and reinstalling drives and such? Lots of others have had luck using the one click.. Heimdel package. But, I'm an Odin fan... If you get any sign of life from PC while it loops, that's a start.
if you have adb loaded, have you tired to spam the reboot download command while the phone loops?? Its another way to see if it does/can get into download mode..
Did you get it working? If so mark the the title [SOLVED].
Alright, I was running LiquidSmooth 4.4.4 rom when I got an OTA update from them. I downloaded it and when to install it, and ever since, my phone will only boot to the liquidsmooth splash screen and just sit there. I tried to use CWM to recover to my last backup, and now it's completely gone. I'm back to download mode only, not CWM recovery. I figured I'd at least get the phone working and use Odin 3.07 on Windows 8 to flash it. Downloaded drivers for the verizon version of the GS3, installed, rebooted and set to work. Well, Odin won't see my phone. At all. I don't know how to make it connect so I can flash it. Anyone got any advice?
I have kies installed, but it isn't running.
I cannot boot into my phone whatsoever.
I had the usb repaired, and it will charge when plugged in and off.
Someone please help. It's been two weeks and I've tried everything I can think of.
Eroth said:
Alright, I was running LiquidSmooth 4.4.4 rom when I got an OTA update from them. I downloaded it and when to install it, and ever since, my phone will only boot to the liquidsmooth splash screen and just sit there. I tried to use CWM to recover to my last backup, and now it's completely gone. I'm back to download mode only, not CWM recovery. I figured I'd at least get the phone working and use Odin 3.07 on Windows 8 to flash it. Downloaded drivers for the verizon version of the GS3, installed, rebooted and set to work. Well, Odin won't see my phone. At all. I don't know how to make it connect so I can flash it. Anyone got any advice?
I have kies installed, but it isn't running.
I cannot boot into my phone whatsoever.
I had the usb repaired, and it will charge when plugged in and off.
Someone please help. It's been two weeks and I've tried everything I can think of.
Click to expand...
Click to collapse
Try to find a Windows XP PC instead...
well through sheer will and button pressing, I managed to persuade the tech gods to open a hole in the sky and allow me to get back into CWM. I'm restored and up and running again. Chalk it up to "No idea what broke, no idea what fixed"
/thread closed.