I have a Galaxy Note 2 SGH-T889. I have spent the past week reading and trying suggestions on this forum. I downloaded kies but it gets stuck connecting to the phone. I have tried several versions of odin. It gets to sboot.bin and write fails. I have tried the original firmware which took 2 hours to download. I refuse to pay for the upgrade in download speed for something I only need one time. I have tried the pit and firmware combination. The only thing that seem to register anything on the phone was when I tried the modem.bin.....it had a blue progress line but then it failed. I am starting to think it is a hardware problem.
How did it start? The phone was sitting on the desk when it came on and restarted. Then it stop when it got to the Galaxy Note II logo. I can get it into Download Custom OS mode but it will not go into recovery mode. Prior to that I had to data wipe and factory reset because it was having the logs process stopped and other processes popups. I had to wipe and reset about 3 times prior to the failure.
I was using the plain old firmware. I think the phone auto updated to the 4.3. I did not install any custom os. I just use the phone as a phone, the calendar and the camera pretty boring stuff. Did not know anything about odin, kies, soft brick, hard brick, jtag, emmc or sds prior to the failure. Not sure exactly what the difference is between t889, n7100, n7105 or n7108. I have downloaded the android toolkit and tried several of those options but it says to enable debugging but I have no access to the settings on the phone to enable debugging.
The way the phone crashed makes me think it had a hardware failure. If there is anything else I can try, I am willing to try anything.
Eva
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
andytiedye said:
Same happened to my note 2 [emoji21]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I am wondering if the phone was doing an auto update and got stuck in the process. I had my phone set to auto update. Maybe that is a mistake...I guess I should have made it ask before it updated at least then I would know what cause the problem.
Eva
Note 2 sgh-t889 boot.bin error
audit13 said:
Odin is failing at the sboot.bin file because the bootloader in the ROM is not compatible with the phone or the phone's bootloader is newer than the bootloader Odin is trying to flash.
Model # has been confirmed in download mode as being the T889? You're using the most recent stock ROM? Have you tried downloading from updato.com? You've tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
zevacat said:
Yes in the download screen is says sgh-t889. I have tried different computers. A laptop and a desktop., different cords and different ports. I just replaced the battery and the battery seems to charge fine.
Is there some place I can find a bootloader that would work for my phone? I have downloaded the 4.3 firmware from different sites. I am downloading the one from updato again and will give it another go.
I even tried the route 66 one ....nothing. I know it was 4.3 that was on my phone. I had checked on the t-mobile site and it said my phone had latest 4.3 updates prior to the crash since it was time to pay for my minutes.
Eva
Click to expand...
Click to collapse
Ok it finished downloading. I ran it with odin 3.12. This is the results.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
audit13 said:
You are flashing a tar.md5 file in the PDA slot of Odin 3.07?
Click to expand...
Click to collapse
That try was with the odin 3.12 using the ap slot. I did try 3.07 pda and the 1.87. Yes it is a a tar.md5 file.
Had an interesting occurrence. I restarted the laptop while the phone was connected to the laptop and the laptop went into an infinite start loop. At first I thought, oh great now the laptop is broken....:crying: But then I unplug the phone and the usb cable. The laptop started normal. I plugged the cable in and it still restarted without problem so whatever black hole the phone is in....it will pull in all connected device into the abyss.
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
audit13 said:
Failing to flash the sboot.bin file indicates that the bootloader is not for the phone, the bootloader being flashed is too old, or another usb cable is required.
Click to expand...
Click to collapse
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
I recommend flashing the most recently released stock rom, not earlier releases.
zevacat said:
with odin 1.87 it gets to Nand write.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I will download an earlier version and see what happens.
Eva
Click to expand...
Click to collapse
I can't seem to find an earlier versions all the 4.1. All the links come back as file not found. They did have a gt n7100 unbranded 4.4.2 kit kat N7100_ITV_N7100XXUFOE1_N7100ITVFOF1.zip so I am waiting for it to download. It says it will take about 2 hours. Or is there some other version that would be better? and where can I find it. Rapid Gator really stinks as far as downloads.
Eva
Flash the latest 4.4. Try updato.com.
audit13 said:
Flash the latest 4.4. Try updato.com.
Click to expand...
Click to collapse
They don't have a 4.4 for the sgh-t889 so which one would work best out of the other options 7100, 7105 or 7108?
Eva
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
audit13 said:
I forgot that T-Mobile version only went to 4.3 so flash the stock 4.3. Don't use any stock roms for the 7100, 7105, etc.
Click to expand...
Click to collapse
4.3 gets stuck after the sboot.bin. audit13 said "the bootloader in the ROM is not compatible with the phone "....so if the bootloader in the sgh-t889 is not compatible then I need a different bootloader don't I? Not sure where to find a different bootloader.
Eva
The only thing I can suggest is taking it to a cell shop that can flash it via jtag.
Related
I soft bricked my phone somehow, no clue. My phone was fine, battery died with no downloads, or anything running, went to turn it back on after plugging it in to find it bricked at the Samsung start screen.
I've tried restoring it with Kies, which won't recognize my phone is plugged in(??).
I've tried restoring it in Odin with Kies uninstalled, it keeps failing though.
Here's a copy of Odin's log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVBMD1_T889TMBBMD1_935627_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Note 2 has never been rooted, and I'm completely at a loss as to what has happened. I've tried different USB cords and slots around my laptop, but don't have another computer I can try it on currently.
Also, After trying Kies and Odin I noticed in the top left corner of my Note's screen, KNOX WARRANTY VOID changed from 0 to 1, not sure what that means either!
Any suggestions? I'm lost without my phone!
Edit:
After ODIN fails, my phone says unsupported version also in the top left corner. I've tried 3 different stock ROMs.
Edit 2:
And now I can't get into the boot menu, just the download menu.
Kies also won't recognize that my phone is connected now.
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
I've tried at least 4 different firmware versions, and am having no luck with any of them. Should I be looking for one that includes the OTA update from back in the winter?
Androidwizzard said:
Find latest firmware for your region and device and use Odin to flash it.
Regarding the file in your Odin log seems to be old firmware.
Click to expand...
Click to collapse
I have the same problem. any other sugestions?
Not yet, I've yet to find a firmware that works. :/
Jotapoggi said:
I have the same problem. any other sugestions?
Click to expand...
Click to collapse
FIX
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
Kittylee, take a look at this video " youtube . com / watch?v=GbAJH_mL6N4" I've downloaded the rar version of the clockwork recovery for my GT-N7100 from this site "galaxynote2root . com / cwm-recovery /" you have to choose the "RAR" version since it's thhe one odin uses.
OBS.: Remove the spaces from the links
It worked for me. try it.
:laugh:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
kittylee said:
Not yet, I've yet to find a firmware that works. :/
Click to expand...
Click to collapse
kittylee said:
Got it un-bricked! I was able to find the latest firmware on SamMobile's website, I can't link it though due to being a new user.
Click to expand...
Click to collapse
Which version of andriod is it?
I got a hold of a sprint s3 sph-l710 that has freedompop on it and wanted to flash it back to sprint stock firmware, during the flash in odin it got stuck at boot.img for about 4 hours so i finally stopped it. now the phone won't boot, it says upgrade encounted an error and to recover in kies. I dowloaded kies and it won't even find the phone. I can still get into download mode but it keeps hanging up now at sbl2.mbn. I've tried 3 different computer 3 different operating systems 2 different sync cords and all the usb ports on the computers and it still gets hung up. Also if it matters I don't think usb debugged mode was enabled and now I can't enable it since I can't boot into android. Any ideas would be great.
here's the log file from odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl2.mbn
Click to expand...
Click to collapse
Maybe try the latest nj2 firmware instead of nd8. http://forum.xda-developers.com/showthread.php?p=58297282
Worth a shot.
madbat99 said:
Maybe try the latest nj2 firmware instead of nd8. http://forum.xda-developers.com/showthread.php?p=58297282
Worth a shot.
Click to expand...
Click to collapse
Thanks I actually got it going. I was at a gas station and they had sync cables for $3 next to the checkout figured for $3 i'd give it a shot, got home started up odin, passed no problems
hey i know its not the same but i bricked my s3 as well (sprint) and before that happened i removed the power button because it was deffective. I can still get to download mode and trying to go to fastboot only brings up the firmware faulty screen. Is there anyway to fix this?
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user _low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user _low_ship.tar.md5 is the ROM I am using stocked not sure what firmware was on there before the phone just died normally and was stuck in bootloop the white Note 2 screen first screen I am pretty sure the drivers are installed correctly on the pc Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and generic ones installed as well .. no updates were installed nothing was installed for awhile on it never had no problems I had it for 2 years and it is rooted so no update on battery dying. Battery charge is stuck on grey battery as well, and in recovery mode has the e mount error in red and factory reset restore does not fix the bootloop the phone stays charged good. No custom rom. In Odin 3.09 I put file in AP and on top says set partition just stuck there eventually I think it fails I have tried a few ROMS and says COM4 in blue. Any expert advice needed and phone is in solid shape no abuse. Thank you. Is it a partition problem not sure what is going on?
Hey there,
it's been a while since I had a Samsung smartphone and used odin. Are you sure your USB cable is still ok?
Maybe try another one.
And are you sure you got the correct firmware, bootloader, etc. to flash this file?
Cheers
Ok thanks for replying yea the cable is brand new lil loose on the pc port but good if not moving it around yea this l900 stock rom should work right regardless what firmware version I got I am not sure what version is on there now and it is not the newest.. this a newer rom. I put the rom in the AP checked it ran it not sure what other files or bootloader I need the bootloader is for using older firmware basically rolls back right? I do not think there is any faulty hardware is there has to be programming ..
Follow_and_Feel said:
Hey there,
it's been a while since I had a Samsung smartphone and used odin. Are you sure your USB cable is still ok?
Maybe try another one.
And are you sure you got the correct firmware, bootloader, etc. to flash this file?
Cheers
Click to expand...
Click to collapse
Fixed was faulty cables ..
When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.
Which file is failing to flash in Odin?
audit13 said:
Which file is failing to flash in Odin?
Click to expand...
Click to collapse
TMB-T889UVUCMK7-20131209151709.tar
Is there one particular file that is not flashing such as system, recovery, etc? It would be shown in the Odin log window.
its just one tar file that I was trying to flash through ODIN.
the 2nd button ( I forgot the name of it, the one that replaces the PDA )
Can you link me the sequences which I should follow to get to the stock ODIN?
Thanks,
Post the Odin log.
filename:
T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.
audit13 said:
Is mk7 the most recent stock ROM? It doesn't seem to be based on this: https://www.sammobile.com/firmwares/database/SGH-T999/
The boot.img file failure leads me to believe the ROM is too old for the phone.
Click to expand...
Click to collapse
This is for T889.
I think the most updated one is https://www.sammobile.com/firmwares/download/56160/T889UVUCOH4_T889TMBCOH4_TMB
I am downloading this to try now
here is the new file that I tried to flash.
T889UVUCOH4_T889TMBCOH4_HOME.tar.md5
and here is the log
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Humour me but could you boot the phone into download mode and check the model #?
Have you tried using different USB cables and USB 2.0 ports?
Picture attached
Picture
Picture attached
Okay, the firmware looks good and the phone is running a 4.3 bootloader so the latest ROM from sammobile.com is the only ROM that can be flashed via Odin.
Did you get a chance to try different USB cables and USB 2.0 ports? Might try on a different computer too.
I tried different cables, will try another computer and see
Different computer didn't work either.
What else I can try?
It still fails to flash sboot.bin? The file is the bootloader which could mean the memory is damaged or the original Samsung USB cable needs to be used for flashing.
As a last resort, you could take the phone to a cell repair shop and ask them to flash the phone with a jtag cable or Octopus box.
byteless said:
TMB-T889UVUCMK7-20131209151709.tar
Click to expand...
Click to collapse
byteless said:
When phone boots, all I see is Samsung logo, it doesn't go beyond that.
The phone was running 4.x stock rom and never rooted.
I can get the phone into download mode, but nothing after that when I try to ODIN, it just don't take it.
I left the PC there for very long time, but it just doesn't flash.
I made sure that my drivers are updates, used new ODIN V3.09.
Got the latest GalaxyNote2/ SGH-T889/TMB-T889UVUCMK7-20131209151709 firmware
the PC does detect the phone, and odin does find COM7 port.
any help would be appreciated.
Click to expand...
Click to collapse
Your EMMC is bad probably.
using a note 2 today and it just decided to reboot on its own, and then never got passed the splash screen. i have twrp recovery installed. booted into recovery and couldnt do anything. couldn't mount anything, wipe anything, restore anything. all storage showed 0MB. kept giving errors that it couldn't mount any partitions (cache, system, etc.) something with error 16.
i tried flashing a stock rom with odin. that failed. just seems like it is totally corrupted and nothing can be written to it.
how does something like that happen just randomly???? any way back from the dead?
Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?
audit13 said:
Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?
Click to expand...
Click to collapse
yes AT&T note 2.
the stock rom i got from a link on this forum. i tried this one first, I317-UCUCNJ2-Stock.tar.md5, then this one I317-UCUCNE5-Stock.tar.md5
also tried re-partitioning after with this pit file, i317.pit
i tried using Odin v1.85 and Odin 3.07
What is the error message in the Odin log?
Tried using different usb cables and usb ports with Odin?
audit13 said:
What is the error message in the Odin log?
Tried using different usb cables and usb ports with Odin?
Click to expand...
Click to collapse
just tried it, same result. odin log? you mean the message output? here it is for when i tried with and without PIT file
Code:
[B]No pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
[B]With pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.
audit13 said:
Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.
Click to expand...
Click to collapse
tried different cables and ports and another ROM, I317UCAMA4.. still fails.
i think it's a lost cause.
I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?
Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.
audit13 said:
I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?
Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.
Click to expand...
Click to collapse
yes it shows as sgh-i317 when in download mode
roms were gotten from wherever one gets roms i guess