Database Info

unrecoverable soft brick even with USB JIG

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 think Kies just bricked my phone...

My phone is a SGH-i896, Samsung Galaxy S Captivate from Rogers,
I am extremely frustrated. My phone isn't rooted. I recently found out my phone was available for a 2.2->2.3 update so I decided to do it.
I downloaded Kies and connected my phone to the computer. Kies picked it up and told me to initiate the update. I did. After a while it told me there was an "error" with the update and I'd have to do an emergency firmware repair... what the hell? I proceeded to do what it asked me to do an emergency repair, but even that failed and it told me to "try again later"...
So, I tried "again later" but this time instead of getting the digger android I when I initiated the recovery mode (Hold volume up+down and connect the USB) I get the "phone-!-computer" screen. Now I'm stuck like this.
I searched around and someone said if you hold volume up+down and then hold power, and then when you see the BSOD, and it flashes, release power and it should boot up in download mode... but when I attempt there it just flashes then goes back to the BSOD.
What are my options to fix the phone aside from going to a service center and most likely having to send it in for repair?
Kies broke my phone. Ugh.

Vinhwut said:
My phone is a SGH-i896, Samsung Galaxy S Captivate from Rogers,
I am extremely frustrated. My phone isn't rooted. I recently found out my phone was available for a 2.2->2.3 update so I decided to do it.
I downloaded Kies and connected my phone to the computer. Kies picked it up and told me to initiate the update. I did. After a while it told me there was an "error" with the update and I'd have to do an emergency firmware repair... what the hell? I proceeded to do what it asked me to do an emergency repair, but even that failed and it told me to "try again later"...
So, I tried "again later" but this time instead of getting the digger android I when I initiated the recovery mode (Hold volume up+down and connect the USB) I get the "phone-!-computer" screen. Now I'm stuck like this.
I searched around and someone said if you hold volume up+down and then hold power, and then when you see the BSOD, and it flashes, release power and it should boot up in download mode... but when I attempt there it just flashes then goes back to the BSOD.
What are my options to fix the phone aside from going to a service center and most likely having to send it in for repair?
Kies broke my phone. Ugh.
Click to expand...
Click to collapse
In your case, try (from a powered-off state) holding Vol+/Vol-, and then plug in your USB cable. That should kick you to download mode. If you still get the phone--!--pc screen, just try flashing from there. As far as ODIN and other programs are concerned, that's download mode.

jmtheiss said:
In your case, try (from a powered-off state) holding Vol+/Vol-, and then plug in your USB cable. That should kick you to download mode. If you still get the phone--!--pc screen, just try flashing from there. As far as ODIN and other programs are concerned, that's download mode.
Click to expand...
Click to collapse
Doing this still shows the phone--!--pc screen... I've tried tons of combinations and fiddling around with it but nothing works it seems.

Vinhwut said:
Doing this still shows the phone--!--pc screen... I've tried tons of combinations and fiddling around with it but nothing works it seems.
Click to expand...
Click to collapse
Just so we can give you clear directions, at the end of this, where do you want to be? On the stock rom, on a custom rom, Froyo, Gingerbread, etc? The steps to do those different things will vary what you need to do.
As a first step in all of those, though, you'll need to use either Heimdall or Odin to flash your phone, and you should have the Samsung drivers downloaded and installed (if you haven't already).

I want to be able to upgrade it to 2.3 more or less. If that's not possible, just to get my phone back in working condition... I'm close to calling Rogers to see what they can do if I can't figure this out on my own.
I guess I'll look up some information on Heimdall/Odin then about flashing (I really have limited knowledge in this area) - will doing any of this void my warranty?

Vinhwut said:
I want to be able to upgrade it to 2.3 more or less. If that's not possible, just to get my phone back in working condition... I'm close to calling Rogers to see what they can do if I can't figure this out on my own.
I guess I'll look up some information on Heimdall/Odin then about flashing (I really have limited knowledge in this area) - will doing any of this void my warranty?
Click to expand...
Click to collapse
I was hoping that would be your response. Go to this thread. TRusselo whipped up a bunch of Odin one-clicks to get you back to stock Rogers packages, one of which is called "2.3.3 Gingerbread WITH bootloaders" (you can CTRL+F for that exact phrase). That should get you back to a working state.
Just make sure you don't pull out the cable or lose power while you're using it. That would guarantee you'll end up having to send it back.
And technically, it will and won't void your warranty. Flashing anything but stock stuff directly from Rogers probably voids it, but if this works properly, it's going to look exactly the same as if they did it, so you should be fine.

Thanks jm, I'll give this a try and post my results

Good luck. Just make sure to read the directions very carefully - it should be pretty self-explanatory, but it's better to be as safe as possible.

All fixed following jmtheiss' instructions! Thanks plenty!

Glad to hear you are back up and running Vinhwut. And jmtheiss, you provided clear instructions to get him there. That's how help should be given.

I'm in a little trouble here.

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.

[SOLVED] Infuse 4G is Bricked and I need serious help on it

I have searched these forums over and over for an answer. I have come with nothing, and so I figure I will try and ask myself.
I have a Samsung Infuse 4G. A while ago, I decided to upgrade it via Samsung Kies. It bricked from the upgrade, and so i used GTG Unbrick to fix it. While GTG did not fix it, Kies actually completed the emergency recovery, and it worked again.
Slowly, over time, the phone just kept having problems. It wouldn't let me save new contacts, it kept having errors whenever I connected to 4G, and most recently, I was not able to even access my home page or any of my apps cause it kept crashing. I figure if I run it through Kies, it will fix. Well, I was wrong. Its now bricked again. i have spent the last three hours going through many solutions.
Odin wont get passed the Factoryfs section of the process, heimdall keeps telling me it needs a new driver, but then after I get the driver, it doesnt run, kies just doesn't do anything, and GTG does the same thing as odin being it uses Odin.
I really need help. This phone is pretty much my house phone, and I have important calls that I am supposed to recieve in the next few days. If anyone can solve my problem, I'll thank you forever, thats all I really have to give. i wish I could do more, but either way, please help me. I'm currently trying Odin again, and I have tried the Re-partition option, but I'm still getting nothing.

If it is getting stucked during the process, it might be a faulty usb cable. Try another one, switch ports and even PCs if you can.
Sent from my sweet & buttery Infuse

If you are using Kies, I take it that you are not rooted.
Are you able to put your phone into download mode?

I thought my situation was hopeless too but if you can get into download mode you are good, pull battery and hold both vol up and down together, plug in cable to computer then insert battery, volume up once from there and you should be in download mode.
I think you are trying to use Heimdall from the GUI you don't have to do this if it is installed correctly, I was making the same error for a while, but all you need to do is double click the .jar (back to stock one click) from your file tree and it opens up all for you then select the pit or partition option or whatever the check box is hit flash and your good, it might fail once but it will go on the second or third try works great like magic after you use this correctly you will never Odin again.
Thank very much to all the cool people on here sharing their knowledge you guys rock!!

So sorry for the late response. Ok. so, I can get it into download mode. The USB cable is not the issue, nor the comp, cause it does this on every comp.
It is not rooted, but I have just learned that it is no longer under warranty, so I plan to root the little demon asap.
Can someone link me to the latest version of Heimdall maybe. I feel that would help a lot.
And lastly, even ATT didn't know what to do with it.
I'll be on all night if anyone can help.

Sorry for the double post
I have been trying to operate Heimdall. However, everytime I hit flash, it says it needs a different driver. I install the suggested driver, and even then, it still does the same thing. I remember this happening last time and I gave up on heimdall.
Please if someone could help, I will give you thanks.

So I have no clue what I did, but I somehow finally got heimdall to work. It may have been the cord, or the port, idk, but my phone is back online. Thanks for the help provided. You all get thanks

Help! my sm-n915t bricked

Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:

ton8_22 said:
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
Click to expand...
Click to collapse
You sound like you have a problem similar to what I had.
I was downloading 6.01 to install using KIES 3 and got no recognition from my Windows 7 based computer when I connected up and ran KIES.
I had the Sammy 1.55.5 USB drivers installed.
What I did it was use KIES,not KIES 3.
Samsung says KIES 3 but that turned out to be wrong in my case,although I'm not sure why?
I'm now running M/M and happily gutting the bloat out of it.
It feels better than new now!

Solved
Anyway, I already solved it!

ton8_22 said:
Anyway, I already solved it!
Click to expand...
Click to collapse
i have the same problem....
how did you solve it?