Related
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 :/
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
I pull out my battery and let it discharge for about 15 secs and hold volume buttons then connect USB cable and finally insert battery while still holding volume buttons of course, it'll get you into download mode. Never failed me. I've had my phone not even turn on the screen, it stays dark during a screwed up flash with odin. I then flash UCKI2 with bootloaders and then flash to gingerbread ROM I like. If you plan on installing custom ROMs your phone will semi-brick numerous times. If its showing a phone, exclamation mark and computer with a message saying firmware flashing failed. That is perfect! Just make sure you have Samsung USB drivers and simply flash using odin, it'll show COM and a number like 5 (COM5) then just flash. I'd advise you to remove any external SD card and restart before using odin it acts up. Hope this helps
hupo224 said:
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
Click to expand...
Click to collapse
The "Phone - ! - PC" will be your download mode screen. Just download from there.
However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen.
If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Click to expand...
Click to collapse
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
asasione said:
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
Click to expand...
Click to collapse
100% - I had similar experience with my first flash but after a few goes at it and 3 or 4 "soft-bricks" all has been great!
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
It seems I got it in download mode this morning with the jig. Just trying to get my damn pc to read it. Sometimes the right drivers work sometimes they don't. ugh
Connection issue in my sig
Any chance you have another pc to try it with? Or possibly another cable?
Going to try one click on ubuntu...
Ive had issues in the past before with certain USB ports on my PC not reading the phone.
Try plunging in your phone to a different USB port and it can make a world of difference with the driver issue (even if you have to plug it in the back of your PC).
try one click unbrick in the android development page
hupo224 said:
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
Click to expand...
Click to collapse
Are you running x64? If so are you running the 64 bit drivers?
I also had the same issue a couple of times, which is technically called a "soft brick" . You could resolve this issue using ODIN flasher and reverting back to stock. Now coming to USB problem in windows, this is a known issue with windows (especially Vista and Win7) and samsung!! The remedy which I found is as follows :-
1.Disconnect the phone from USB
2.Remove samsung USB driver software from your windows PC.
3.Reboot and then navigate to C:\Program Files\ (assuming that C:\ is your windows OS partition)
Delete "samsung" folder.
4.Download latest samsung USB Drivers for captivate and install.
5.Reboot the phone.
6.Open ODIN and connect your Phone to PC.
It should detect the COM Port by now. Try this and get back
"Thanks" , If I helped U
Hello all, any help would be greatly appreciated.
My wife's phone has been rather buggy so I decided to root and rom it. Rooted the phone with the oneclick method. Moved on to getting CWM up and running (it is what I'm familiar with from my G2x). I liked what I was seeing with the Valhalla Final rom OP and decided to give it a try. Read the instructions to install but things have steadily gone down hill.
I am comming from stock. I did a NANDROID backup. Wiped, wiped, wiped and then flashed the ROM. I do believe that I just didn't read carefully enough where it says I "must have pre-installed kernel" . When I rebooted I got a pixelated screen unreadable screen. There was a voice in the background describing what was going on but I plugged along and waited the 5-7 minutes. Figured if it didn't work correctly I would just go back into CWM and restore my nandroid backup. However I can no longer get back into CWM or the recovery prompt that comes before CWM. I just get the Galaxy S 4g screen which then goes to the weird pixelated screen and then it continues in a boot loop.
I tried to follow this debricking thread but got stuck a couple of times. First, that I can't find the boot.bin and sbl.bin files. I google around and found this but the download link no longer works. Does anyone have the boot.bin and sbl.bin files handy?
Also, the Zadig program to install the Heimdall driver doesn't show me any driver options. I suspect that this is because Heimdall or Zadig had not run on the computer before I had the phone properly connected. I saw that it was the Samsung Composite driver that was being asked for. Not sure if I found the correct one but either way it didn't work. I was unable to get the computer to recognize the phone (also phone would continue on its boot loop, also it doesn't change anything whether I am holding down the volume buttons when I turn the phone on or not).
I have stayed up half the night looking for something but am wondering if I just straight up bricked the phone and need to send it to someone with JTAG experience. Let me know if there is something I am missing or some suggestions you have.
Go here:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The problem is that you tried flashing a gingerbread rom even though your phone still had Froyo bootloaders. If you flash a gingerbread rom using one of the one click files mentioned in the guide, you'll be able to flash more GB custom roms.
Don't worry your phone is fine, you just need to read a little more and you'll be good to go.
Thank you very much for the link, the post is very through. I am getting stuck because my phone appears to not want to go into "Download Mode." Every time I press the up + down vol buttons and plug in the usb I just get the attached images and they go in an infinite boot loop.
I have tried every usb port on the computer and followed the instructions near the first of the post and uninstalled all ports which had Android or Samsung associated with them. I also tried all the different ways I could to get into download mode based on this link.
I am currently in the process of uploading a clip of the infinite boot loop I am in on Youtube and will post it if it helps.
Again thank you all for your help. The XDA community is the best!
That is the rainbow screen indicating you need GB bootloaders. Just pull your battery. You need to flash twice - second time checking the 'flash bootloaders'.
For the driver issue/phone not recognized by the computer - There is a tool in the guide called USBDeview (in the notes). Use it to make sure you have uninstalled all android related/unknown drivers. Go into uninstall programs and make sure you uninstall Samsung drivers. Restart your computer. I also run the CCleanner reg cleaner. Then restart computer again.
For Download Mode - Pull battery. Plug your USB into your computer only. Make sure you are pushing both the volume up and down buttons simultaneously. Without putting battery back in, plug your USB cable into your phone while continuing to hold volume up and volume down buttons. Keep holding volume buttons with USB plugged into phone and computer and put the battery back in.
Start guide over and read thoroughly.
Fb that's the screen I got coming back from nand back up!!! I had to flash a diff kernel with Odin to fix it
Thanks for all your help. Ironically I was doing everything correctly, but my usb cable had gone bad on me the night that it all happened. So thanks all, espicially lumin30 for the excellent guide and for FBis251 pointing me to it. After switching to a working cable and completing lumin30's guide all is now working great!
As a random side note the driver section showed up slightly differently for me (the device I had to pick was [usb composite] but once I figured that out everything went well).
Glad you figured it out
My sidekick was soft bricked so i used odin to recover it. now when i plug it in it goes immediately to the download mode screen and is recognized by odin. problem is is it restarts after min or so. odin starts flash modem passes, kernel passes, but while flashing the factoryFs, it gets to 53% and the phone restarts and it fails. it does this in oneclick odin and also in odin3. any help would be much appreciated. the phone wont work unless plugged in and it restarts every min.
Have you used Odin before?
If not, try downloading a new recovery image for your device.
You'll have to use the ability to search the interweb to get yourself one. Go get it.
Try reinstalling drivers for your phone on your OS. Reinstalling JRE (Java Realtime Enviroment) backup and clear your sdcard, then do as you have been doing before and let me know if you can get somewhere, thanks!
Sent from my SGH-T839 using XDA
yes, ive used orin before with no problem. my little girl plugged my phone while it was flashing and causing it go to the phone-!-computer screen. I was able get it out of that but now its doing what i stated earlier. i been lookin for the image you mentioned but it seems all the links but so far all the link are bad or have the fbi warning on it. imma keep trying to look for it though.
Ive reinstalled the drivers several times, changed usb ports, i only have one usb cord that i could get to work so im stuck s far as that goes. not sure how to do the jre but ill google it, in all the threads i read on here your the first to mention jre. i havent had a sd card in the phone since it messed up, should there be? i let you know if it works. thanks