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 :/
Hey guys.
Earlier today, my phone ran out of batteries and shut down. When I rebooted it, everything was in stock settings of Octane 2.X. I have no idea why that happened, since I've rebooted the phone plenty of times before.
Since that problem didn't seem to have a solution, I decided to Odin and flash Octane 3.0 instead. The first time I used Odin, everything was fine. I Odin'd to KC1, just to remove any gremlins. Next, I tried to Odin to KI3. However, that was stuck.
In the end, nothing moved for several minutes, so I unplugged it and reboot my computer. My phone was still able to enter into download mode. I've also tried different USB ports. All have the same outcome.
Now, Odin recognizes my phone, but I can't get pass: <ID:0/013> Get PIT for mapping..
I've attached a picture of what's happening below.
I've searched for the solution to this problem, but the only solutions I've really found were about letting the phone rest for a while. Of course, I let it rest, but the same thing keeps happening.
Please help.
EDIT: Now it seems like I can't get pass <ID:0/009> Initialzation..
bkoon1218 said:
Hey guys.
Earlier today, my phone ran out of batteries and shut down. When I rebooted it, everything was in stock settings of Octane 2.X. I have no idea why that happened, since I've rebooted the phone plenty of times before.
Since that problem didn't seem to have a solution, I decided to Odin and flash Octane 3.0 instead. The first time I used Odin, everything was fine. I Odin'd to KC1, just to remove any gremlins. Next, I tried to Odin to KI3. However, that was stuck.
In the end, nothing moved for several minutes, so I unplugged it and reboot my computer. My phone was still able to enter into download mode. I've also tried different USB ports. All have the same outcome.
Now, Odin recognizes my phone, but I can't get pass: <ID:0/013> Get PIT for mapping..
I've attached a picture of what's happening below.
I've searched for the solution to this problem, but the only solutions I've really found were about letting the phone rest for a while. Of course, I let it rest, but the same thing keeps happening.
Please help.
EDIT: Now it seems like I can't get pass <ID:0/009> Initialzation..
Click to expand...
Click to collapse
Weird. I've had mine stuck at the PIT file before but rebooting my PC and the phone seemed to fix it. Does the phone boot up to an OS at all? Maybe get it into recovery, factory data reset, then try again?
Thanks for the response stephen_w.
I can't get into recovery, only download mode. I managed to get it to work again after reinstalling drivers and rebooting my computer.
However, I think Odin needs to be run with nothing in the background or something. After I Odin'd KC1 successfully, I tried to Odin KI3 (which progressed till factory). My girlfriend IM'd me and it suddenly stopped.
I'm gonna try redoing it all over again and seeing how that works. FML!
bkoon1218 said:
Thanks for the response stephen_w.
I can't get into recovery, only download mode. I managed to get it to work again after reinstalling drivers and rebooting my computer.
However, I think Odin needs to be run with nothing in the background or something. After I Odin'd KC1 successfully, I tried to Odin KI3 (which progressed till factory). My girlfriend IM'd me and it suddenly stopped.
I'm gonna try redoing it all over again and seeing how that works. FML!
Click to expand...
Click to collapse
Weird man. Have you tried the factory reset after KC1? I hate using that factory reset crutch but it's helped me plenty of times. Then again, maybe I just keep effing up my phone LOL
Seems like the solution was just to change computers. Weird how my sister's laptop used to be unable to use Odin, but now it can. Now I really wonder wtf happened to my computer. I used to be able to do everything on it.
bkoon1218 said:
Seems like the solution was just to change computers. Weird how my sister's laptop used to be unable to use Odin, but now it can. Now I really wonder wtf happened to my computer. I used to be able to do everything on it.
Click to expand...
Click to collapse
Definitely odd but I'm glad you got it going. Maybe the drivers got hosed? It's really hard to say I guess. If you get bored & get really curious about it, uninstall Kies Mini if you have it installed, uninstall the drivers, then go into the device manager and make sure there's nothing Samsung USB related or "gadget serial" left over. Then maybe reinstall Kies Mini and install the drivers from there.
Originally one cm7, tried out cm9 but apparently i never got the bootloader right so i was getting rainbows. I tried to switch to emancipation and that loaded up fine. went and made one more attempt to cm9 but no luck. i am not stuck at the samsung logo. If Odin connects it gets to the step that says setup connection but never moves past. What are my options? I don't even care what rom i'm on as long as i can use the phone. cm9 gives and error if i try and flash. i can still access red CWM. emancipation will flash and say complete but if i reboot it just sits as the samsung logo. i checked mounts and no matter what i cant mount system which i think is my problem. i can no longer see the phone from my pc either. so i don't believe i can get another rom to it from the pc.
Any help is appreciated, screen shots or explanation for dummies is much appreciated. I've done this before but have never been stuck like this where i couldn't get back to a working rom stock or otherwise.
Thanks,
Joe
Try qksters heimdal to stock and see. If no luck, try Odin again(gtgs unbrick)but try with every USB port until it works. Sometimes Odin likes to prefer a certain one. Anyways, I prefer using the heimdall package. A lot more easier in my opinion
Try a pizza taco sometime, if you don't know what it is, look it up then
did you wipe user data,cache,and delvic
yes. also finally got hemidall to load on the home pc but phone would never connect. even if i went through cwm and put it into download mode.
Kies wont see phone ive tried that too. pc sees it and load drivers but it wont connect. i cant even see it as a mass storage on the pc anymore. gunna try odin from my work pc. If anyone can help it would be great i need to fix this asap as im in the middle of purchasing a house and have quite few people im going back and forth with.
asadjewonxmas said:
yes. also finally got hemidall to load on the home pc but phone would never connect. even if i went through cwm and put it into download mode.
Click to expand...
Click to collapse
You need to install the drivers that come with hemidall before it will connect to your phone
Sent from my HTC PH39100 using Tapatalk 2
got odin to work. i needed a different usb cable.
I had a similar problem, except I was unable to flash any from after attempting to flash cm9. Im on vacation away from my computer so I was unable to Odin, I just kept using the three finger method to get into recovery. And kept trying to flash a different roms always getting stuck at the Samsung logo...after about 1-2 hours of continuesly flashing i was finally able to flash a rom-after my phone finally booted up I booted into recovery which was now red again and instead of flashing the kernel I just flashed cm9 again. Got stuck on Samsung logo booted into recovery which was once again rainbowish and reflashed and then I booted up into cm9!!!
So basically for those who are away from a computer just keep attempting to flash-it worked for me just took a looooong time
Sent from my SGH-I997 using XDA
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
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?