Hello everyone, so long story short I accidentally flashed my Tmobile Note II SGH T889 with the ATT rom (I317UCALJ2_I317ATTALJ2_ATT.zip) while trying to go back to stock. Now in download mode my phone reads as if it's an ATT model, I'm not even sure how an ATT firmware flash passed on odin. Phone wont boot and I cannot access recovery mode as it just spits " Firmware upgrade encountered an issue." I cant upload a pic due to external links, but the phone says "Product Name: SGH-I317" when in download mode, or are as my phone reads "ODIN MODE".
I've tried flashing every version of the stock Tmobile roms via odin 3.12 and all of them fail at the very end. I don't know what to do anymore. Any insight into this is much appreciated, thank you!
Update: I managed to flash TWRP through odin, but flashing stock MD7 through custom recovery still lands me in a bootloop.
Was the phone purchased new or used? Do you recall see the T889 model # in download mode before flashing?
It was given to me used by a family member. It was in functioning condition but running very buggy so I wanted to flash stock and go from there. I do not recall seeing the SGH-T889 model # in download beforehand as I really wasn't expecting to make such a foolish mistake. The phone is unquestionably an SGH-T889 though, confirmed by the back cover and the IMEI sticker behind the battery.
The only way to really confirm that the phone is a T-Mobile note 2 would have been to boot int download mode. Since the att firmware flashed in Odin with no errors, I'm inclined to believe that the phone motherboard was actually from an att note. I have never seen Odin allow such cross flashing.
Maybe open the phone and examine the motherboard to confirm model number?
I could open the phone and search for the model number on the mobo, but why on earth would the back sticker read as an SGH-T889? This is a funky situation.
It could be a frankenphone. The motherboard from a t889 will fit in a i317 amd i317m and vice versa.
Related
i have a bell galaxy note 2, after i flashed some custom ROM, my phone stop working, i have found similar problem on the sprint form, but doesn't know how to fix, please help.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
i try odin a bell stock still doesn't work, and when i boot into recovery it keep saying is a RWC rogers phone, does that have something to do with the problem? i also try kies too, still no luck.
minghaoji said:
i have a bell galaxy note 2, after i flashed some custom ROM, my phone stop working, i have found similar problem on the sprint form, but doesn't know how to fix, please help.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
i try odin a bell stock still doesn't work, and when i boot into recovery it keep saying is a RWC rogers phone, does that have something to do with the problem? i also try kies too, still no luck.
Click to expand...
Click to collapse
This has nothing to do with development.
However unless you have a backup. You'll need to return your phone for a new one.
antiochasylum said:
This has nothing to do with development.
However unless you have a backup. You'll need to return your phone for a new one.
Click to expand...
Click to collapse
sorry i posted wrong place, where can i get help, i am new to this, and how do i delete this post
Make sure you odin a rom that included the radio and kernel. Preferably a return to stock type thing. If that didn't work did you back up your efs partition?
Also what did you flash exactly?
OP please read the Forum Rules on posting in the correct Section, Moved & Thank You
I had same situation as you few days ago, I messed up my Rogers note ii with flashed 7100 rom to my i317m. I lost baseband, network imei. Luckily, after I flashed root injected FACTORY Stock rom to my rogers phone, the problem had been fixed, here is the link where you can download the root injected FACTORY Stock rom for you phone. Hopefully, you will get your phone fixed
http://forum.xda-developers.com/showthread.php?t=2004650
jjzeng said:
I had same situation as you few days ago, I messed up my Rogers note ii with flashed 7100 rom to my i317m. I lost baseband, network imei. Luckily, after I flashed root injected FACTORY Stock rom to my rogers phone, the problem had been fixed, here is the link where you can download the root injected FACTORY Stock rom for you phone. Hopefully, you will get your phone fixed
http://forum.xda-developers.com/showthread.php?t=2004650
Click to expand...
Click to collapse
Yeah i flashed this one no lucks, i think my parition is messed up, wonder if anyone has a back up efs file for my phone
Aridon said:
Make sure you odin a rom that included the radio and kernel. Preferably a return to stock type thing. If that didn't work did you back up your efs partition?
Also what did you flash exactly?
Click to expand...
Click to collapse
i flashed a rogers rooted stock version rom on my phone, so now after i did recovery it just keep on shows is a RWC in the recovery mode doesn't matter which stock rom i flash, and its saying a BMC in the download more product name. so its really messed up. because i unlocked the phone from bell, so the guy at bell told me i void the warranty on it. now i don't know what i can do to fix my phone.
Pit CSC file
any idea where i can find a pit file for my bell note 2 so i can repartion it, or that's something only samsung has it
This was a big issue with the gs3 and they've come up with a solution in that thread so given the similarities I would think that would work with some tweaking for the different partitions on the note 2. Check out the gs3 forum & maybe get in touch.. they might be able to help.
Sent from my SGS3 using my finger
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
Hi guys, I'll admit I'm a noob, but I'm trying my best to understand the ins and outs of flashing ROMs. I recently purchased a used S4 SGH-M919. The problem is the phone has i337 AT&T firmware on it. (I'm pretty sure it's a stock ROM and not rooted). I need to find a way to use the Tmobile network on this phone, so I have been trying revert to stock by flashing the stock M919 ROM on the phone using odin. Odin repeatedly fails before the flash begins. Odin dislays "FAIL! (Auth)" and the phone displays message "SECURE CHECK FAILED : aboot". I have tried several different .tar.md5 firmware files from sammobile. I have tried several USB cables and every USB port on my PC. The phone isn't quite bricked, it still boots fine it's just the network unusable with my t-mobile sim and the at&t firmware.
Do I need to wipe the phone and do a kernel flash? I'm lost and any advice would be appreciated
Thanks in advance,
Ryan
pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.
are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website
XeoNoX said:
pull out the battery and MAKE SURE the PHYSICAL sticker behind the battery says model SGH-M919 (not SGH-M919V) but exacly SGH-M919.
if that has been confirmed then download the ODIN image from sammobile
Download the latest M919UVUFOH3
install via odin using the PDA or AP slot depending what version of odin u have it will say PDA or AP.
btw: you are getting SECURE CHECK FAILED : aboot". error because you are either flashing wrong image or too old of a image and the boot wont allow it.
Click to expand...
Click to collapse
c_irie said:
are you sure that it is not a stock I337 ? If it is, it would be much easier to just obtain the SIM unlock code to use it with T-Mobile, I337s are really difficult to root and the sim unlock code is free and takes less than 5 minutes on the at&t website
Click to expand...
Click to collapse
Thanks for the replies fellas. I am sure it's a stock SGH-M919. The sticker beneath the battery says so. I've already tried using the most recent firmware from sammobile (ending with OH3) with odin and I receive the same error no matter what. I've even tried multiple versions of odin and have used PDA or AP accordingly.
c_irie, It's not a stock i337, I've read about the bootloader issues and Loki regarding that model. I would really prefer to do a clean M919 flash, but do you think I could use a sim unlock code from at&t with my current situation?
This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
rkham said:
This may not be useful information, but here's exactly what is displayed at the top of the screen when I boot into download mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.
XeoNoX said:
seems like someone sold you a "hybrid S4" the casing with sticker of the m919 but the "motherboard" of a I337...
was probably a "fixer upper" normally from those shady mom and pop cell shops/ebay/craigslist. consider that you got yourself a sgh-i337 even tho the outside doesnt say so...the board inside matches that of a i337 i will gaurentee u.
Click to expand...
Click to collapse
Thank you for opening up a new realm of possibilities for me. I hadn't thought of that. Why would someone re-brand a i337? Do you think odin is failing because I have the wrong image for a i337?
Problem solved for now. I went ahead and assumed that it's actually an i337. I followed the suggestion above and requested an unlock code from at&t using the imei found in settings. I didn't think it would work, i figured the phone was stolen, but the code from at&t worked and I can use the t mobile network! thanks guys. I'm kind of bummed that it's an i337 since it will be difficult to root if i ever go down that path.
glad we where able to help you out. Sorry to hear that someone kinda scammed you and sold you the wrong phone. To be honest with you tmobile phones have a slightly higher resale value too...i hope you didnt pay the extra premium..esp since it was a fixer upper phone. well anyways glad you got it all figured out. btw: the att s4 on tmo is missing a band but you can possibly unlock it to have all the tmo bands.
http://forum.xda-developers.com/showthread.php?t=2291589
Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.
rkham said:
Yeah it's definitely not the device I was hoping to receive. I've discovered a few issues. I haven't been able to use internet at all without wi-fi, and the mic doesn't work in calls for some reason so I use speaker phone. Other than that, it seems to be working very well.
Click to expand...
Click to collapse
if you have used a factory ODIN image and flashed it and you have all those problems then im sorry to say it was probably a "fixer upper" phone that wasnt fixed properly. sorry to hear you are having all those problems...that sux. i always thoroughly test new phones IN PERSON before i buy them. i do the sim card test, screen color test, mic test, speaker test, model number test. and a voice and data and wifi test.
installing tmobile on att version
f irst of all you have to have root second you need to install a custom recovery such as TWRP. then you need to download the Wicked V.10 zip.then boot into recovery mode white data cache partition and dalvik cache partition.actually install the zip file you downloaded for the wicked v10 Rom. But make sure download the tmobile version because it willautomatically change your CSC settings
maybes this will help
Ok first things first. You have to be rooted and already have a custom recovery installed like TWRP or CWM. If u aren't rooted then try the king root apk. Once u have root access then you can go to download mode on your phone. Most of the Phones the power button & volume down at the same time will take you to download mode you have to search on Xda for the custom recovery version that is for your phone model it also has to be the Odin compatible ".tar" file. I use Odin 3.9 just because it seems to work better but after u have everything I've listed the install Odin 3.9 on your computer. Once that is done u have to remember where the custom recovery u should have already downloaded is located. Right click on the odin icon and click run as administrator make sure that you click on the BL button because that is where you will place the custom recovery.tar file. when you click on the BL button it will open up a window where you can search for the custom recovery that you downloaded earlier once you find it click on it and it will automatically go to the BL box then you click Start and just let Odin finish doing what it has to do when it says complete unplug your cable from the computer out phone reboot your phone hold volume up that should take you to your custom recovery once you have your custom recovery installed you can backup your whole system install zip files custom roms. things of that nature I hope this helps feel free to msg me if u have problems
I pulled out an old samsung galaxy note 2. The t-mobile model sgh-t889 i believe. i was trying to upgrade it to android 4.4. I found somewhere saying the official at&t roms work for this phone. I tried the most recent one. I317-UCUCNJ2-Stock.tar.md5. this was the file I used. Odin failed almost at the end. Now the phone is frozen in odin with a complete blue bar. Any ideas? i want to flash the tmobile stock rom again but i don't want to make the situation worse?
Hopefully, a locked att bootloader was not flashed to the phone.
All you can do at this point would be to power off the phone, boot into download mode, and try flashing the latest stock rom from sammobile.com.
I have an AT&T Note II from the US and I currently live in the Republic of Georgia. I bought it from a friend when my Nokia workhorse finally died after 8 years.
Friend told me about the situation up front and I found that the it was a pretty simple solution, punch in some numbers, get through a couple menus then no prob... except the phone was 4.4.2 and not 4.1.1.
Looked online for a good 4 days and finally decided against my better wishes to try to flash to 4.1.1. Got it done but it got stuck on the pulsating Samsung screen for a ton of time. I made the fateful mistake of pulling the battery to restart it.
It is unresponsive except for a frozen empty battery gif that generally appears before the charging batter gif appears when you connect it to a charger.
Phone will not go into DL or Recovery mode.
Plz help
Where did you get 4.1.1 and how did you flash it?
Try leaving it in the charger for a few hours and try to get into download mode.
I looked in a lot of different places and had troubles getting the file. I encountered a lot of dead links or file sharing sites that had ad loops. After about the 5th or 6th site I found KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5 . but I dont recall from where exactly.
I popped it in using Odin as instructed by the many guides that are on the internet.
I am now able to get it to boot through all four splash screens (Note II -> samsung -> AT&T -> samsung) and now it is stuck on the pulsating Samsung for as long as I allow it.
Any tips on what to do next?
Was the phone factory reset after flashing with Odin?
If the phone was running a 4.3 or newer bootloader, flashing an older bootloader or an incompatible bootloader/modem combination can hard brick the phone.
Att never released a full firmware for the phone after 4.1.1 so you need to be selective as to what can be safely flashed.
You need to find a flashable stock kk ROM.
I was able to get a 4.4.2 and reflash it to the original state. It is still SIM locked though.
If the phone is an sgh-i317 and it is not running 4.1.1, you'll have to unlock using a code from either the carrier or an unlocker.
There is no free method.
Im in Georgia and never used the said carrier so their support is reluctant to help me.. I tried flashing the 4.1.1 and that soft bricked it in the first place. Do you know of any good unlock software?
I don't know of any free software to unlock the phone.
Did you ask for an unlock code here: https://www.att.com/deviceunlock/request/#/unlockstep1
Another way is to buy an unlock code from eBay.