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 :/

Major phone issues (hardbrick?)

I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
Edit: resolved. After trying like a bazillion times it finally worked

mikel.canovas said:
I tried flashing the ics source port but forgot to flash cm7 first... It flashed fine and I followed the procedure to flash. The phone would turn on but always go straight to recovery. I figured this was because I didn't go to cm7 first, so I went to flash it but I kept getting errors. I went to flash stock, it started going so I walked away. When I came back my phone was just a white screen and odin was stuck at sbl.bin. So now I can't boot up the phone, there's no bootloaders, just a black screen whenever I try to do anything. The thing is, I can get into download mode just fine through button combos which leads me to think it's not bricked. However, odin/heimdall will not recognize it... Anyone know what to do?
Edit: resolved. After trying like a bazillion times it finally worked
Click to expand...
Click to collapse
Glad it worked, the day when a Cappy dies is a sad one...

No clue what I did

Hey everyone, I tried looking around but didn't see anything else like this, most people at least have access to the download mode, unlike me. I was installing UNiPoRN and CWM kept freezing for some reason during flashing, so I used Odin to try to flash UCKD5 from http://forum.xda-developers.com/showthread.php?t=1092021 But it kept failing for some reason, and this last time when I went to put my phone into download, I get a single green pixel towards the bottom right of the screen, no download mode nothing, how ever my computer recognizes that my phone was attached. When I try to turn on the phone normally, I have a diagonal row of green dots, but nothing like the rainbow effect. Does anyone have any clue whats wrong and what I can do to fix it? Let me know if you need more information!!
Thanks thanks thanks in advance!!

USMCJ00lz said:
Hey everyone, I tried looking around but didn't see anything else like this, most people at least have access to the download mode, unlike me. I was installing UNiPoRN and CWM kept freezing for some reason during flashing, so I used Odin to try to flash UCKD5 from http://forum.xda-developers.com/showthread.php?t=1092021 But it kept failing for some reason, and this last time when I went to put my phone into download, I get a single green pixel towards the bottom right of the screen, no download mode nothing, how ever my computer recognizes that my phone was attached. When I try to turn on the phone normally, I have a diagonal row of green dots, but nothing like the rainbow effect. Does anyone have any clue whats wrong and what I can do to fix it? Let me know if you need more information!!
Thanks thanks thanks in advance!!
Click to expand...
Click to collapse
Try the one click method, if your computer recongnizes then that is good...try these links and there is a new odin, well has the updated Gingerbread.
see my signature links to ISET page: http://forum.xda-developers.com/showthread.php?t=1610374
but here are the links to look for one click:
http://forum.xda-developers.com/showthread.php?t=1524081
newer odin:
http://forum.xda-developers.com/showthread.php?p=27286083#post27286083

Yes, as mentioned from bigjoe2675 use the newer up-to-date Odin http://forum.xda-developers.com/showthread.php?t=1705260 And flash the GB Bootloaders afterwards to fix the Rainbow distortion on the boot screen.
2.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
If you have rainbow distortion, you still have Froyo bootloaders. You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin.
Click to expand...
Click to collapse

I tried the one click, and it says kernel upload failed. And as for the pixels, I know what the rainbow looks like, I had it when I first installed ICS, however this is not the same thing (at least I don't think so, it looks nothing like it)

USMCJ00lz said:
I tried the one click, and it says kernel upload failed. And as for the pixels, I know what the rainbow looks like, I had it when I first installed ICS, however this is not the same thing (at least I don't think so, it looks nothing like it)
Click to expand...
Click to collapse
Checklist...
1) try a new download, sometimes files get corrupt..
2) try new USB port..
3) have a beer
4) install or uninstall kies drivers...then try new gb odin
5) have another beer...
As far as the pixel...not sure did you do it at at time?

Make sure you flash the bootloader after you had success with the restore to correct the "pixels" which I had before a couple of times. The random pixels are the corrupted bootloaders (I think) which should be corrected by flashing the proper one (GB Bootloaders)
Sent from my SAMSUNG-SGH-I997 using XDA

I kinda had a similar problem earlier when I was trying to install legend 4 rom. My phone would flash a boot, then nada. No button combo's worked, nothing. I got the idea to pull the battery, and I achieved the same results upon power up (glimpse, freeze, no button reaction). So, I pulled my battery again, held the volume rockers and got into download mode. Once I did that, I used Odin to go back to stock GB.

USMCJ00lz said:
!!!
Click to expand...
Click to collapse
status update...you good to go...?
check or hold!?!

Bootloop with a twist

I'm kind of at my wits end, which may not be saying much
I've had my note 5 for 4 or 5 weeks, rooted and tried every custom ROM. I got curious this morning when I found I was on OH6 baseband, and wanted to update to OI5 before flashing to loco's OI5 ROM. I downloaded the files from the resource thread and flashed both the modem/baseband and bootloader with Odin 3.10.6. Phone booted back into android, checked new baseband and all was well. Placed new ROM on my phone and went into TWRP. Well, tried to, but it was stuck, sorry I don't remember the verbage, but something along the lines of unenforced kernel, but it stopped right there.
Went back to Odin, flashed TWRP 2.8.7.1, same thing. Did it again, same results. Odin again with baseband and bootloader. Same thing.
It gets worse.
Decided, OK, I'll fix you, so I'd start fresh. I went to sammobile and download OI5, the newest firmware. Takes over an hour to DL from that site, unless you want to pay for the faster service. Anyway, finished downloading, flashed with Odin, phone started to boot, then gets stuck in a bootloop righ after T-Mobile logo. Let it do this for 30-45 minutes with no luck, flashed Odin again, same results. I had the older firmware on hand, so I flashed OH6, but I get a failed result. Thought maybe bad file so I tried OGE firmware, getting the bad flash message with this one too. Re-downloaded OH6 from sammobile, but got same fail flash results. Tried different USB port on my computer, different USB cords (3), tried a different computer with same results for each file, including bootloop and failed flashes.
Wew!!
Any suggestions at this point? Any insight would be greatly appreciated.
Referenced firmware:
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar.md5
N920TUVU1BOH6_N920TTMB1BOH6_N920TUVU1BOH6_HOME.tar.md5
N920TUVU2COI5_N920TTMB2COI5_N920TUVU2COI5_HOME.tar.md5
edit: I played around some more after searching on the note 5 bootloop subject. Found a site dedicated to s6, which was close enough for the time being. I found if I hold the power and volume down it will cycle power down, but not completely power off. So what I did was cycle off and immediately hold home, power and volume up, with the thinking I would either get into TWRP or samsung power menu, so I could clear cache and devlac. Got into TWRP (which I couldn't before ?!?#?) and wiped, installed forever loco.
Looks I'm good to go, but I suppose forever patience is key here.
You can close this up.

Sounds like Mr toads wild ride... glad you are back up and running.

dandroid7 said:
Sounds like Mr toads wild ride... glad you are back up and running.
Click to expand...
Click to collapse
I was scratching real hard for a while. Still, didn't find how to turn a bootloop note 5 completely off other than getting into either android or custom recovery.
Plus, I fully expected my files to be gone, but they weren't!! Meaning none of the Odin firmware took, even though on the OI5 the little android told me he was erasing "everything".
This won't deter me from continuing my exploits, but I might start writing some things down. LOL

Delete please.

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?