Database Users

Just bricked My shiny new S4 and im going on holiday tomorrow!Help me please !

I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints

Gavin01 said:
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Click to expand...
Click to collapse
All you need to do is search google. No one spoon feeds you in real life so no one shouldn't spoon feed you here also.
http://forum.xda-developers.com/showthread.php?t=2261573
You need to follow these instructions but you need to download your correct firmware.
Sent from my SAMSUNG-SGH-I337

Use Odin to flash stock firmware by following this guide, I assume that you have the i9505, if so then flash this CWM,

thanks i need to find the right rom now
thanks fingers crossed
EDIT
im guessing this is the right rom
I9505XXUBMEA_I9505OXXBMF1_XEF.zip

thanks guys weve done it!
its resurrected!
cheers

I stuffed my phone up again and thought id post here instead of making a new thread.
flashed the latest modem which in turn has for some reason fubored all my dialling out and messages etc so i cant use the phone for anything other than browsing .....
I9505XXUBMEA_I9505OXXBMF1_XEF.zip<<<<<<<<<<<<this is what i used last time and it didnt work this time
so ive now tryed this one I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
my phone is a sim free s4.
the second one appears to work but wont get passed the lock screen with out continuous errors. (i note i now have the knox label in the bootloader)
How do i find the latest stock rom for my phone? so i can start again?
thanks

I had exact same issue so i falshed XXUFNB9 from sammobile and now im rooted runnin cm11 m9 .
Do suggest UNISTALLING samsung usb drives from pc and reinstalling fresh new ones for your device snd then flashing. I flashed 4 different firmwares. It was only until i reinstalled s4 usb drives my phone becsme alive. Dunno how but i reckon usb drives is the issue

[Q] Help finding a specific stock ROM - i9505

Hi all,
Long time lurker, first time poster
I've been experimenting with a spare i9505 that I have, flashing roms etc (it was having serious wifi issues so I was trying to fix it)
However something's gone wrong and I now have the 'Firmware upgrade experienced an issue' screen, and Knox Warranty is 0x1. I don't really care about it as it's a spare, but I'd like to flash a ROM to it so that it at least works.
I'm not exactly a power user when it comes to this stuff, more an 'enthusiastic amateur'. I followed instructions in a similar thread to flash TWRP and use that to Advanced Wipe before flashing a new ROM, which I've done, but the threads I've found feature loads of ROMs and I don't know which one to use. I found a couple that I tried to use, but Odin is failing every time and SW Rev Check Fail pops up on the screen, which I believe (from more lurking!) means I'm trying to use the wrong firmware.
Was hoping someone here could point me in the right direction!
Just to recap the phone status:
- S4 i9505
- UK based (came from Vodafone if that matters?)
- Firmware update encountered an issue
- Knox Warranty Void 0x1
- Previously running 4.2.2
Thanks guys

Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk

aayushkhajuria2842 said:
Knox warranty void cannot be recoverd till now
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I'm not worried about the warranty, I've read up on it and I know that's a lost cause. I just want the phone to work really as it's currently displaying 'Firmware update encountered an issue' on boot. I only mention the 0x1 thing as from my research I understand that it limits you in terms of what ROMs you can install, meaning I would need a particular one to get the phone working again.
Thanks!

Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk

aayushkhajuria2842 said:
Then install stock firmware via odin first
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
... That's kinda the point of my post. I know what I need to do, I just don't know which file to use.
For example, this thread http://forum.xda-developers.com/showthread.php?t=2250824 has a bunch of stock firmware files, but I don't know which one I would need to download, for my specific circumstance.

What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:

Joku1981 said:
What firmware u tried to install? If u tried to install android 4.3 or android 4.4.2 maybe ur bootloader is updated and u cant flash android 4.2.2. Give us more info :fingers-crossed:
Click to expand...
Click to collapse
I was worried that might be the case.
OK so I've tried two md5 files so far:
I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5
I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
To PROPERLY go back and re-cap from beginning...
- Phone was stock, wi-fi didn't work (worked for a bit, then cut off and wouldn't come back on)
- Ran CyanogenMod Installer to update and hopefully fix the issue
- Install was successful but didn't fix wi-fi issues
- Used Odin to flash the 2nd md5 listed above, went back to stock but wi-fi still didn't work
- Tried to flash the 1st md5 listed above, didn't work and must have errored at some point as now I get that 'Firmware upgrade encountered an issue' message.
- Looked up the issue in a thread on here, followed instructions to flash TWRP, boot into Recovery > Wipe > Advanced wiping everything bar last two options, and then 'install your stock recovery firmware'
Only issue I have now, I don't know which file that is As I say the last two I tried (above) give me the SW Rev error, so they're clearly incorrect.
I don't care about warranty, and I don't care about root either really... just want the phone to work again, even on stock!

Well. Step by step:
- You will have to WIPE all
- If the phone is branded to Vodafone is one thing, if not is other.
- I let u the correct firmware for ur phone with Vodafone: HERE or HERE
- If ur phone is unbranded the correct firmware is: HERE
- Download it and flash it through ODIN
- If u have problems with ODIN, paste it here and good luck :highfive:

Awesome! Thanks man, the phone came from Vodafone initially but I don't think it's branded (no logos on the phone, no Vodafone logo on boot)
I'm downloading both just to make sure. Will let you know results ASAP! Thanks again :good:

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

Soft Bricked phone and now ODIN flash failing help!

So I upgraded from 4.4.2 kitkat to 5.0 lollipop. However, I soft bricked my phone by installing the wrong xposed SDK. Now I'm trying to flash 4.4.2 kitkat back onto my bricked phone and then update back to lollipop. Problem is ODIN is not wanting to flash the g900a stock rom back. It gives me an error saying 'SW REV CHECK FAIL : [ABOOT]FUSED 2 > BINARY 1' does anyone know how to fix this as I'd like to fix my phone soon!

900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
http://i.imgur.com/rVnFwJM.jpg

help
keithross39 said:
900A? That's the AT&T model isn't it? That being the case, the locked bootloader on your device is only ever going to let you flash 5.0 if you had 5.0 on your device before you bricked....
Click to expand...
Click to collapse
That's good an all but where can I find a 5.0 in a tar format! My phone is literally bricked so I can't access it to flash the .zip files to it. I can't find a .tar of lollipop 5.0 anywhere no matter where I look all the links for ones have been taken down! You wouldn't happen to have one would you?

Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Not sure fella.....checked every hosting/firmware website I can think of, and all I'm seeing are KitKat firmwares.....
Have you tried Kies to see if it'll perform an 'emergency recovery/restore'?
Click to expand...
Click to collapse
Kies won't recognize my device! It just says it's not supported! ;-; this is really unfortunate I've been looking everywhere with what little time I have (I work and I'm in college and it's around finals season for the semester so that doesn't help with time to fix this). I've been scouring everywhere but can't find anything. This is really unfortunate and I don't have the money to afford to have my phone fixed ;-; I'm really hoping I can find a solution soon! Everytime I try to install a kitkat 4.4.2 rom it just says FUSED 2 > BINARY 1 or something along those lines. From what I've heard that means I can't downgrade. Like I said what happened was I installed the wrong xposed sdk and it soft bricked. Every lollipop 5.0 rom I've found is in zip format. Now this wouldn't be a problem if I had a custom recovery that could flash zips and the means to put the zip on the phone. The problem is I don't (yes I've tried using ADB it refuses to put the zip on the phone it only lets me put .tar.md5's on there with the sideload and everything else just returns an error). If you find a solution or anyone else does please let me know! I'm In very dire need of help!! Also, my phone it makes it to the samsung galaxy s5 powered by android screen and then after that I just hear the AT&T noise but the screen doesn't change it just hangs there. I've also tried a full cache wipe and system restore in the recovery menu!

First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
First of all.....The obvious....lol
These zips you mention, have you extracted them to see what's inside them.....
I know that sammobile and Samsung-updates provide their firmware .tars inside zips.....
Secondly, until someone makes an AT&T Lollipop firmware available, it looks like you're going to have to play the waiting game......at this point, I believe that with the correct firmware package, you WILL be able to recover your device....that may not be true further down the line if you continue to try 'potential' fixes.....
My advice is to leave it 'as-is' (unsatisfactory...I know) and wait for the firmware to become available......
Do you have an older device you can use in the mean time?
Click to expand...
Click to collapse
Yes I unzipped the zip. It was just files inside. I might just take it by an AT&T I'm pretty sure with all I've done to it the warranty is void but it's a worth a shot maybe they will take it in. I don't have an older device right now and I need to have some my phone soon as I have important usage of it with work. It seems I guess I don't have a choice left ;-; thank you though for all your help I'm very thankful for it

Note 3 Factory Data Reset Daily -

Ok - haven't seen this problem anywhere - all I see are posts and articles regarding how to get it off the Samsung screen during boot... Which is a Factory Data Reset... I have to FDR my phone daily.. not running anything custom (accept this was originally a Rent-A-Center phone - and I know they have a special system built in to kill the phone if its not paid for etc... Was paid off well over a year ago)
How do I fix this?? Do I have to root and install a custom ROM?? Do I have to do something else? Having to FDR every day, and sometimes twice is becoming rather annoying.

Flash your models stock rom through Odin .

JJEgan said:
Flash your models stock rom through Odin .
Click to expand...
Click to collapse
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.

AncientNerd said:
Do I have to use KIES for that, or is there a better way to do it? I have not flashed anything before... I know it is a little different than installing an OS on a computer.
Click to expand...
Click to collapse
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Awesome - Thanks!

ShaDisNX255 said:
Nope, you just download Odin (PC software) and download stock firmware (search in Sammobile or Updato) and look for a tutorial on how to flash software through Odin and you're all set
Click to expand...
Click to collapse
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!

AncientNerd said:
Ok - Update..
I have searched both Updato and Sammobile - nothing but European and otherwise non-USA Firmware - I also cannot get Odin - or frankly Kies to work either... Kies does not find the device, and Odin acts like it is there, but nothing I put in it is working..
CWM Recovery? Nada... Doesnt do anything through Odin - just stares at me -
ADB and FB? They briefly flash on my PC screen and vanish - no options to do anything... I have updated the Samsung USB drivers 4 times... So I am not sure what to do next..
Thanks for the help so far!
Click to expand...
Click to collapse
What's your phone's model? It doesn't have to be carrier-specific to be able to flash it.
Also, try TWRP instead of CWM recovery, devs seem to prefer TWRP overall.

SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.

AncientNerd said:
SM-N900T is the model number.. I'll give TWRP a shot next. Maybe I'll have better luck with it.
Could the RAC software be putting a wall up that I can't get through? I bricked a phone I was getting through them once because I tried to update Android through Kies (on an S5) and discovered they don't use stock ROM's with their phones.
Click to expand...
Click to collapse
I've got a N900T and I've found software in both Sammobile and Updato, I don't know why you're not finding anything (N900T is supposed to be T-Mobile's variant)
Anyway, I would try out the following tutorial: Link
I found it very useful when I wanted to completely flash my phone clean and root.
I am not sure about what roadblocks you could have of this phone being a RAC phone, but if you still want to give it a try I'd suggest you try out the tutorial I showed you