Related
Hello xda community,
mainly my problem is in my Samsung Galaxy S3 (international) device, it's bricked !!!
Device: Samsung Galaxy S3 [international] 16GB
ROM: N.E.A.R 1.2 [ http://forum.xda-developers.com/show....php?t=2126059 ]
Kernel: N.E.A.K. Kernel 2.5
Yesterday i downloaded the Note 2 keyboard for Samsung s3, but after i flashed it i realized it was for the leaked rom, so apparently
it didn't work, and all was normal, after about 30 minuites, i was browsing on my device, the device suddenly restarted so it first shows
the first screen: Samsung Galaxy S3 Logo .... but nothing else ... Stucked on that screeN ... i'm pretty sure it's not from the keyboard ...
-restarted my device [returned to SGS3 Logo]
-removed battery [returned to SGS3 Logo]
-tried to enter recovery mode (CWM) [returned to SGS3 Logo]
-removed external SDCARD
-removed SIM nothing happened still stuck on that logo.
i can only enter the download mode so I :
-tried to flash a stock rom [4.1.2 and 4.1.1] using Odin [ with 3.07, 3.04, 1.85 versions], but odin keeps on saying FAILED with red color.
- downloaded the RESCUe FIRMWARE, followed the steps assigned here : [http://forum.xda-developers.com/show...35&postcount=6 ],
but odin says : failed to partition, invalid PIT.
- downloaded the CheckROM EvoHD [http://checkrom.com/threads/resurrec...%84%A2-v4.896/], ODIN > FAILeD
- found this thread [http://forum.xda-developers.com/show....php?t=1916796 ] and started with the steps assigned in the .pdf file but when I tried to flash the bootlaoder >>>> FAAAIL
NOW I THINK THE PROBLEM RESIDES IN THE FILE SYSTEM, i tried to re-artition with the below PITs,
- PIT section: I tried to re-partirion the device with three different files:
1) with the PIT: [http://invisiblek.chickenkiller.com/...-i535-16gb.pit ] i found it form here [http://forum.xda-developers.com/show....php?t=2075861 ]
2) with the PIT : [GT-I9300_mx_20120329.pit] , I downloaded it from xda (can't find the link).
3) and the PIT file that comes with the Rescue Firmware.
ALWAYS stuck on: "Get PIT for mapping" > after googling and xda-ing I 1) tried another cable, 2) changed the compatibilty to windows XP in the ODIN settings, 3) tried on an XP desktop >>> but still the same message "Get PIT for mapping ... "
That's all, i really appreciate it if anyone could find me a sloution for this issue.
-[ THNAKS IN ADVANCE ]-
Hmm seems to me more like a hardware failure of some sort.
So you flashed a bootloader and it failed? But you still can power up your device and go into download mode?
that`s also weird because normally if you screw up the bootloader your device shouldn`t be powering on at all (happened to me once with my old phone).
Did you have any other weird behavings of your phone? Like unusual freezing before the device rebooted?
Scarface1991 said:
Hmm seems to me more like a hardware failure of some sort.
So you flashed a bootloader and it failed? But you still can power up your device and go into download mode?
that`s also weird because normally if you screw up the bootloader your device shouldn`t be powering on at all (happened to me once with my old phone).
Did you have any other weird behavings of your phone? Like unusual freezing before the device rebooted?
Click to expand...
Click to collapse
Scarface1991 > my S3 just stuck on that logo screen, and there is noway to flash anything, as i mentioned upward: when i flash anything Odin keeps on telling me " FAIL " ... I don't think that the bootloader is screwed, because the device is powering up, and whenever I tried to flash anything it keeps on saying FAIL but only when i try to re-partition the device using a PIT file it do some processing and then on Odin will stuck on " Get PIT for mapping "
-[ BY MISTAKE I POSTED THIS THREAD IN THE !9305 TROUBLESHOOTING SECTION >>> AND I COPIED THE BELOW REPLIES FROM THERE AND DELETED THAT POST ]- -[ 15/4/2013 ]-
Cundis said:
First, this is the wrong place if you have the i9300. This is for i9305.
It's not cool when this happens. Excactly this happened to my mothers S3 also while it was in her pocket and not being used.
Only thing I could get it into was download mode. Otherwise stuck on Samsung screen. I did'nt try to flash something on it because she was afraid of her warranty.
When she brought it to the store they told her the motherboard needed to be replaced. Was not repairable at all they said. She was not rooted and got it for free.
If you live in EU there is a new law that states that rooting does not void guaranty. They have to proove that it was the root process that caused the brick.
I really hope you'll be able to solve this out!
Click to expand...
Click to collapse
> hhh my bad,
first thank you for your concondolences , and am afraid this is the only solution, but lets say the motherboard is corrupted or whatever > the whole device even shouldn't power up ... i don't know, i hope there is a solution for this ...
Reads to me like wrong firmware or kernel flashed and destroyed PIT partition .
A JTag repair may be cheaper than a Samsung repair .
quote
If you live in EU there is a new law that states that rooting does not void guaranty. They have to proove that it was the root process that caused the brick.
FACT that is not a new law and applies only to the vendor of the phone does not apply to any third party warranties like Samsung's limited warranty .
FACT if you are in the EU and your phone vendor says no warranty its rooted . You will have a job to get them to accept EU law and may need to take them to court .
Personally i would just act dumb and say you think it has the sudden death syndrome problem that's p[posted all over the web .
jje
hi all , my phone died about a week ago, ive tried flashing it with all sorts using odin, tried the kies restore method aswell all to no avail,
I cannot get passed the white Samsung gt-i9300 writing , I cannot boot into recovery, I can however get into download mode, odin recognises the phone, but whatever I flash it wants a pit file for, and when I input various pit files it just gets stuck at mapping pit (something like that)
displayed on download mode is the following :
ODIN MODE
PRODUCT NAME :
CUSTOM BINARY DOWNLOAD :NO
CURRENT BINARY : SAMSUNG OFFICIAL
SYSTEM STATUS : CUSTOM
FIRSTLY notice there is no product name , upon reading up on this it means the phone has suffered sudden death syndrome, firstly if this is the case is there a way I can fix it?? secondly if not how likely is it that Samsung will fix it ?? considering it has custom firmware on it ?? shoud the custom firmware matter as from what I read its to do with a bad emmc which is hardware right ?
any advice or help will be appreciated
thanks
okz19
Nothing you can do, motherboard needs replacement. Your binary count is zero but phone was rooted, even so you should be able to get a warranty repair.
Contact Samsung and tell them SDS has happened.
Also, questions go in the Q&A forum, not general. A search would have returned many similar posts.
I have a probably soft bricked i9300 that I have inherited from my brother. Since it is almost impossible to do anything with my HTC Desire, I would like to get this S-III running and use it.
According to my brother's explanation Viber was locking on the Phone so he got into recovery menu, pretty much pressed every option that he could found without knowing what he is doing. You may call it a monkey test. He is kind a over-confident non-technical guy.
Now the phone stays in non animation Samsung i9300 logo. Phone does not charge, I can get into download mode. Odin tells that it can't find the PIT file and When I give PIT file, it does not do anything.
Download Mode Screen Says
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
My questions are:
- Are there anything like a wiki page that puts everything together, so that I can see if I miss anything? I am not familiar with the android jargon. I am having hard time understanding all the parts. For example there are several PIT files, which PIT is proper for me?
- If nothing can be done with Odin/Kies/Heimdall, can someone connect with JTAG and correct it?
- Are there any professional who can make this JTAG (or whatever operation) for me that I can find in this forum? (Device is a grey market item so Samsung service is not an option for me)
Best regards
Zorbey
Product name is blank, emmc chip is blown so new motherboard required. If you searched and read this post why ask the same question?
My GT-I9300 international galaxy S3 gone brick itself, all of a sudden its stuck at the boot screen (white samsung ... text). I was using Cyanogen Rom 12 Unofficial Lollipop 5.1 for around 3 weeks (Everything Works Fine with few Lags and Reboots rarely in a day). I used various method's from noob to expert solution but didn't find success
Tried to reboot into recovery but no go, when i hold the buttons it just continues to reboot and reboot, only showing the white text.
Tried to reboot into download mode and that worked, i though fhew, i got a breath and not all is lost(Phone itself).
In Download mode,
It says : Product name = (Blank)
Custom Binary Download = No
Current binary = Samsung Official
System Status = Custom​
Tried to recover with kies, but it complains that it cannot install new firmware (after i downloaded the firmware, extraction, and all instruction followed).
Tried with odin (several original roms with my region and the one from kies) but with no luck, odin complains "There is no PIT partition.".
Tried to repartition with GT-I9300_mx_20120329.pit but then it does SET pit and hangs on "Get PIT for Mapping".
Tried One Click Method but failure is what resulted.
Didn't Tried JIG Method (will buy if nothing works).
Is there any chance to save my phone ? I'm getting really desperate here.
:fingers-crossed:A Beer is sure to one that gets my problem solved :good:
---Waiting for Good---​
So you just rebooted without changing ANYTHING before and then the device was stuck like you explained?
Have nearly the same problem.
Was using the original Samsung firmware. One day I want to power it on and I had the loop. It stucks on the white Samsung texts.
I cannot go in recovery mode, but I can go into Download mode. But whatever I try, there is no chance to flash an image with or without any pit-file. Always "There is NO Pit--Partition."
And: In my download mode, the product name is there. "GI-9300", no blank in my case.
Is there any chance to save our phones? :\
Thanks!
Did u try installing only a cm kernel through odin
This should bring you recovery
Bad news, blank PRODUCT NAME in download mode implies either broken motherboard, or at least broken eMMC, to the point that bootloader can't read board name.
Hard brick, don't waste your time, unless you want to replace eMMC or motherboard, which is currently not worth the money.
where to get PIT?
prabhu1980 said:
Did u try installing only a cm kernel through odin
This should bring you recovery
Click to expand...
Click to collapse
What is a cm kernel and where do i get it?
//edit: Cyanogenmod Kernel? I tried to patch "Kernel_Odin_I9300XXEMG5.tar.md5" with Odin, but it's still the same error. "There is no Pit-Partition".
JustArchi said:
Bad news, blank PRODUCT NAME in download mode implies either broken motherboard, or at least broken eMMC, to the point that bootloader can't read board name.
Hard brick, don't waste your time, unless you want to replace eMMC or motherboard, which is currently not worth the money.
Click to expand...
Click to collapse
In my case, it's not blank. It shows: PRODUCT NAME: GT-I9300
So I think, there is still a chance, right?
Nobody got an idea?
EDIT: Nevermind.
Is my Samsung Galaxy Note 2 Bricked ?
I got the phone from Ebay on July 6,2015 everything was great
But on the morning of Sep 21st looking at my gallery pictures, I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right the phone restated saying "Samsung's firmware upgrade encountered an issue" so the next day did some research first before trying anything. I downloaded Odin3 and entered download mode & flashed the Samsung it restarted had it on for 3-4 hours
then turned it off & turned it on later to find it would not go pass the Samsung logo so I went to hold the off button shutting the phone off that happen 2 times and on the 3rd try turning it on It did not come on at all. Went to see if google had anything on this some say it is bricked and need to use a jig so I got one from a USA seller on ebay and returned it because it did not work at all. Not the phone still won't come on & I can't enter download mode, how do I fix this, is it a boot loader problem? is it hard bricked? do I need to take it to someone if so who & how much would that cost? you think.
Other Info of the phone
70% of battery is on the phone
It's factory Unlocked
Root Software I tried to use was (Kingo SuperUser)[Root]
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
dseldown said:
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
Click to expand...
Click to collapse
Should I post this in the Troubleshooting Forum?
The pictures I took on the phone disappeared all 300+ pictures disappeared .I am the only one using the Samsung
and it was on my table all that day. So I went to google to find a photo recovery software & found a software called
Wondershare Dr.Fone for Android (you can find videos on youtube) & using the software it can do 2 things, auto root the phone to find the photos and bring it back to normal or you Have to have your phone rooted. The auto root setting was not working on the Wondershare Dr.Fone for Android software so I went to the google play store on my Samsung and found a root app that a lot seem to like as it was 4.4 stars, went to install that the app stated I should have "Kingo SuperUser" on my computer so had that put on the went to root the phone & it did not work.
I got a screen on the Samsung saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Youtube had a video on this same problem so I went to Sammobile's site and download the firmware what was
"2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies. After I downloaded that I downloaded Odin3_v3.10.6 opened it had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion then Entered Download mode on the Samsung & hooked it up to my computer
then I hit start about 30min later it Passed with a green light and everything seem back to normal 3 hours later I went to turn the Samsung off and latter that night when I went to turn it on it got stuck at the Samsung logo that happen 2 times and on the third time it did not come on & so can't "enter download mode" and the "usb Jig" did not
work. What happen & what do I need to next. Do I take the phone to someone to fix this.
Short version of the story
.Pictures I took 300+ disappeared so when looking for recovery software
.Found a software called "Wondershare Dr.Fone for Android" (the software had "2" Options for recovering. 1 the software would
Auto Root and bring the Samsung back to normal after recovering the pictures or I would have to had the phone already rooted.
. When to the google play store with the Samsung, found a root app download that & "It stated I should download "Kingo SuperUser" to my computer so I did that.
.It failed & got a screen on the Samsung Saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
.Went to Sammobile's site and download Firmware 2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies
.Download Odin3_v3.10.6 had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion
Entered download mode & the Samsung passed
.Everything was back I had it on for 3-4 hours then shutdown the phone later that night went to turn on and it got stuck
at the Samsung logo 2 times and on the 3rd time it would not turn on nor enter "Download Mode"
.Got a "usb Jig" & that did not work and now I am here wondering what do next & what happen to my Samsung Galaxy Note 2 do I need to take to someone to fix it ?
Samsung Galaxy Not 2 Unlocked
SCH-I605V version (Verizon)
my battery was %70 full
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
dseldown said:
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
Click to expand...
Click to collapse
I guess it's the hardware? as It won't come on nor enter Download mode.
Now what, Do I take it somewhere? to fix it what ever it is ?
http://mobiletechvideos.com/
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
SamsungNoteFan said:
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
You cant take it but you can mail it. They unbricked my phone awhile back when something happened. It was good service. I rec'
Click to expand...
Click to collapse
Hi all,
I am stuck. Here is my sad story.
I have an ATT S7 that I was attempting to load the S7 Tmobile image using Odin. After hitting the encryption error in odin, my searching led to the PrinceComsey version and that got around that problem. I then hit a Fail(Auth) error and tried a few other suggestions that I found. The last part I tired as ticking the "update phone bootloader" option. Odin failed again, this time, the phone was stuck in recovery menu loop. I tried to clear and restore to factory settings, but couldn't get out the loop. Finally, it stopped booting the base menu and now I get the wonderful blue screen exclamation mark that tells me I need to use Samsung's Emergency recovery. I can't even turn the device off now. The only other thing I can get it to do is to get to the download screen.
From all I have read, it seems the next step is to upload a valid stock image with Odin and that should be that. So that's where I am stuck. I have tried a couple different images, but they all fail in one way or another. I think what I need help with is figuring out which image is the right one to install. At this point I just want to get back to a working phone, so an ATT image is fine for now, but would ultimately want to get to a Tmobile image now that I have switched carries.
Any help is much appreciated!
Use smartswitch to restore stock software.
Also, try to use the right forum , you probably get more help
Oh dang... I claim temporary insanity for putting this in the S6 forum. ugh.
In any case, thanks for the response. I got it all figured out. Here are some tidbits in case it is helpful to someone in the future.
1) Yes I tried the emergency recovery using smart switch. It turns out that you need the device serial number. It also turns out that on my ATT supplied S7, there is no s/n etched on the back. And just for laughs, it isn't even printed on the original box. So if you do not have it written down and your device isn't functioning. You are SOL.
2) After several failed attempts, the magic formula was the modified Odin and the Jan'17 SM-G390T build that I found. I selected all four files for flashing and the n-th time was the charm.
3) I am now running the Tmobile build of Nougat on my ATT S7 with everything working as it should. That includes the phone using the tmobile signal booster that the ATT build couldn't find and has wifi calling available. It is exactly as I wanted.