Develop Bugs

[Q] Flashing a rooted ROM - HELP!

I'm pretty new to all this, I had a Rogers Captivate that had been crashing on me. Everything suggests that if I changed my software it would work.
So I managed to to flash a newer AT&T ROM on to the phone via Odin. (I was pretty chuffed with myself)
However, as soon as I put my sim into it, it became locked. I paid an online service to get an unlock code, but the IMEI number I delivered to them didn't match the network, so I messed that up.
Now I've noticed that I could flash a rooted ROM via Odin, which should save me having to unlock, right ?
I went to the thread http://forum.xda-developers.com/showthread.php?t=1621350 and looked for a suitable ROM (preferably supported).
I went for the PAC ROM, but noticed there is no tar file in the download.
The other ones I wanted to try either suggested it was flashed by another method than Odin (I might be wrong) or the download links for the files themselves were no longer working.
Also, there is talk about Gapps. What is this and what is the process for installing it ?
Thanks in advance for any help you can give me.

Hi there,
You'll need to specify that the phone is still on the Rogers network, as that's how they access the database. Ie., if you have a phone that was supplied to Rogers, the IMEI will be associated with Rogers and if you tell them it's ATT, they won't be able to find it - regardless of what ROM you're running.
Unfortunately, as far as I'm aware you do have to pay to unlock the ROM again but I'm not an expert on this - I know that I had the same problem you did and they told me to put it in as Rogers instead - that got me my unlock code.
I have a rooted Milestone 2 which is running JB now, and it is still operator locked unfortunately.
Apparently the GalaxSim Unlock tool is good but I don't know if it retains your IMEI - I know it does back up your EFS though. Maybe it's worth a try?

Before doing anything with your IMEI i suggest you to backup your efs folder. There's a software for this too.
[sent from my awesome Samsung Captivate Glide]
[AT&T rooted stock ROM]

thank you
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?

pardoning edeaoh
hkcharlie said:
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?
Click to expand...
Click to collapse
Hi hkcharlie,
Have a look at the below thread to unlock your sim card. I used it on mine and my friend's S3.
http://forum.xda-developers.com/showthread.php?t=1846451
I suggest reading the "everything about captivate glide" thread here:
http://forum.xda-developers.com/showthread.php?t=1621350
I use CWMR (ClockWork Mod Recovery) from this post:
http://forum.xda-developers.com/showthread.php?t=1458153
You have to flash this acording to ODIN. Afterwards, you can download .zip files directly to your device for flashing, or download them on your computer and copy them to the devices SD card. Select them in recovery mode and they will install.
These two roms I've had a lot of success with:
http://forum.xda-developers.com/showthread.php?t=1945558
http://forum.xda-developers.com/showthread.php?t=2021374
They're both ICS. There is a cm10.1 JB (4.2.2) build as well, and it's *awesome* - but it is missing a few critical features so I won't recommend it for your first time.
Almost any ROM you flash from this forum will already be rooted. Being 'rooted' just means having a kernel that supports it (both ICS rom's above include a root-capable kernel) and a /bin/su and appropriate superuser apk.
Of course, back up your EFS - there are some apps on the market that will help you do this. And backup everything. And test your backup. And your warranty is void, your phone may explode, or impregnate you with mogwai. (do not get wet, do not feed after midnight.)
Happy flashing!

HOW TO: How I SIM unlocked my N7105, Includes downgrading to 4.1.1 and 4.1.2 insts

How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
This is how I did it. It worked for me. That's all I can say. It may or may not work for you. I'm no 'expert' so I can't answer any tech question. I found this by trial and error. None fatal. ( So far) I will take it for granted you know how to Root and use Odin. I'm also assuming you have installed the Samsung USB Drivers.
http://uploaded.net/file/xdloq4jw
If you are using one machine to do this remember to disable Kies before using Odin.
My phone was updated to 4.3 using Kies. I did this on my laptop as I didn't want Kies messing up anything on my computer that I was going to use for the rest of the process.
So stating with a stock phone.
Using Odin
http://uploaded.net/file/o2xcp01n
I rooted my Phone with
CF-Root
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
I then downloaded SuperSu from the market and ran that. It runs a fix to stop Knox.
I then installed ES File Explorer from the market.
Then I downloaded My Phone Explorer. I like this program and use it a lot.
http://www.fjsoft.at/en/
Using ES I backed up my EFS folder to my Sd Card
Using MyPhoneExplorer I backed it up again to my computer.
Better safe than sorry.
I then used Odin again to install the 4.1.1 Firmware.
I got it from here. There's 4.1.2 there as well for those that asked.
http://www.sammobile.com/firmwares/1/?model=GT-N7105&pcode=EVR#firmware
I then installed 4.1.1 by unzipping the file and using Odin.
I then use CF-Root again.
Using the *#Codes as below
Step 1. Insert a SIM on your Note 2, you should find the familiar “SIM network unlock PIN” window.
Step 2. Dial “*#197328640#” on your Note 2 to enter special menus.
Step 3. Choose “UMTS”.
Step 4. Next choose “Debug screen”.
Step 5. Choose “Phone Control”.
Step 6. Choose “Network Lock”.
Step 7. Choose “Perso SHA256 OFF” and wait about 30 seconds.
Step 8. Press the Menu button then choose “Back”.
Step 9. Choose “NW Lock NV Data Initiallize” and wait about 1 minute. *Then reboot your Note 2.
Step 10. Once rebooted, you should no longer get the Network Lock window any more and you should be able to get signal and data. *If you have trouble getting 3G/HSPA+ data, try setting the APN to your carrier’s settings although it should set automatically.
I did try this using 4.1.2 but Step 7 was missing.
I then updated back to 4.3 using Kies on the laptop and then CF-Root again through Odin on my computer. Fixing Knox by re downloading SuperSU and running that.
One SIM unlocked phone.
I then used Titanium to freeze all the Samsung and Google stuff I didn't want and also froze Knox.
MY phone is running stable and good. Auto update though says it has been modified so now it will not OTA. Which isn't a bad thing.
Thank you to the respective developers of the software I used.
I hope this helps others.

BorgCymru said:
How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
This is how I did it. It worked for me. That's all I can say. It may or may not work for you. I'm no 'expert' so I can't answer any tech question. I found this by trial and error. None fatal. ( So far) I will take it for granted you know how to Root and use Odin. I'm also assuming you have installed the Samsung USB Drivers.
http://uploaded.net/file/xdloq4jw
If you are using one machine to do this remember to disable Kies before using Odin.
My phone was updated to 4.3 using Kies. I did this on my laptop as I didn't want Kies messing up anything on my computer that I was going to use for the rest of the process.
So stating with a stock phone.
Using Odin
http://uploaded.net/file/o2xcp01n
I rooted my Phone with
CF-Root
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
I then downloaded SuperSu from the market and ran that. It runs a fix to stop Knox.
I then installed ES File Explorer from the market.
Then I downloaded My Phone Explorer. I like this program and use it a lot.
http://www.fjsoft.at/en/
Using ES I backed up my EFS folder to my Sd Card
Using MyPhoneExplorer I backed it up again to my computer.
Better safe than sorry.
I then used Odin again to install the 4.1.1 Firmware.
I got it from here. There's 4.1.2 there as well for those that asked.
http://www.sammobile.com/firmwares/1/?model=GT-N7105&pcode=EVR#firmware
I then installed 4.1.1 by unzipping the file and using Odin.
I then use CF-Root again.
Using the *#Codes as below
Step 1. Insert a SIM on your Note 2, you should find the familiar “SIM network unlock PIN” window.
Step 2. Dial “*#197328640#” on your Note 2 to enter special menus.
Step 3. Choose “UMTS”.
Step 4. Next choose “Debug screen”.
Step 5. Choose “Phone Control”.
Step 6. Choose “Network Lock”.
Step 7. Choose “Perso SHA256 OFF” and wait about 30 seconds.
Step 8. Press the Menu button then choose “Back”.
Step 9. Choose “NW Lock NV Data Initiallize” and wait about 1 minute. *Then reboot your Note 2.
Step 10. Once rebooted, you should no longer get the Network Lock window any more and you should be able to get signal and data. *If you have trouble getting 3G/HSPA+ data, try setting the APN to your carrier’s settings although it should set automatically.
I did try this using 4.1.2 but Step 7 was missing.
I then updated back to 4.3 using Kies on the laptop and then CF-Root again through Odin on my computer. Fixing Knox by re downloading SuperSU and running that.
One SIM unlocked phone.
I then used Titanium to freeze all the Samsung and Google stuff I didn't want and also froze Knox.
MY phone is running stable and good. Auto update though says it has been modified so now it will not OTA. Which isn't a bad thing.
Thank you to the respective developers of the software I used.
I hope this helps others.
Click to expand...
Click to collapse
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!

cz4r3n said:
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!
Click to expand...
Click to collapse
any update on that process.

would this work on a sgs3 t999 4.3? will downgrading to 4.1.1 result in a brick like on the att i747?
BorgCymru said:
How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
Click to expand...
Click to collapse

n0013z said:
would this work on a sgs3 t999 4.3? will downgrading to 4.1.1 result in a brick like on the att i747?
Click to expand...
Click to collapse
Absolutely no idea mate. I only tried it on my phone.

ive been looking for this
im having the same problem and hopefully this fixes it.
but about the updating to 4.3 using Kies, wont it trigger the SIM network Unlock Code again?

Hi, what android PDA did you have before doing the downgrade. I have read some posts that say that you can not downgrade if you have MK4 or later... I have a Galaxy note 2 GT-N7100 and I would like to test what you did with mine, but I'm not sure if its possible
Regards

maggr91 said:
Hi, what android PDA did you have before doing the downgrade. I have read some posts that say that you can not downgrade if you have MK4 or later... I have a Galaxy note 2 GT-N7100 and I would like to test what you did with mine, but I'm not sure if its possible
Regards
Click to expand...
Click to collapse
4.3 and then went back to 4.3

butirog said:
im having the same problem and hopefully this fixes it.
but about the updating to 4.3 using Kies, wont it trigger the SIM network Unlock Code again?
Click to expand...
Click to collapse
It didn't on mine.

It doesn't seem to work on SG Note 2 N7100.
Tried all the 4.1.1 fw from sammobile for all carriers here in PH (Globe, Smart, Sun and Open Line)
The menu code doest lead me to the Perso SHA256.
After the Network Lock menu it says Command don't exist or something like that.
Help me what to do please.

Zyrele said:
It doesn't seem to work on SG Note 2 N7100.
Tried all the 4.1.1 fw from sammobile for all carriers here in PH (Globe, Smart, Sun and Open Line)
The menu code doest lead me to the Perso SHA256.
After the Network Lock menu it says Command don't exist or something like that.
Help me what to do please.
Click to expand...
Click to collapse
All I can comment on is how I did it on mine. I don't have any other phone. Sorry.
Maybe try the UK one that I used. Once it's SIM unlocked you can put a local to you ROM on.

BorgCymru said:
All I can comment on is how I did it on mine. I don't have any other phone. Sorry.
Maybe try the UK one that I used. Once it's SIM unlocked you can put a local to you ROM on.
Click to expand...
Click to collapse
Hi,
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.

help me !
i have a Note 2 N7105.i did the exact steps.on the notification bar, i can see that i have signal, the phone is unlocked, but still, i cant use the network. it says NOT REGISTERED ON NETWORK. what do you think is the problem ?

cz4r3n said:
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!
Click to expand...
Click to collapse
I must say.... you are my SUPER STAR..... I have search everywhere and looked every corner of the website..... apart for paying around £20 to 40 to unlock the phone from someone... you have made my day.... I have been trying to unloack a phone that I have bought from ebay... it was locked to EE network in UK, your way of downgrading the firmware to 4.1.1 and use the code “*#197328640#” had worked... the phone has been upgraded wot 4.3 Jellybean, and the code does not work at all. However after down graded to 4.1.1 (as you have done) , I was able to use the code “*#197328640#” and unlock the phone, then I upgrade it back to 4.3 and now doing a firmware upgrade to 4.4..... the network block has ceased... so I guess the phone is now completely utterly unlocked forever....REALLY Thanks to your logical trial and error...
I must say, it took me some trial and error to reinstall the stock ROM, whick I had to use Philz recovery to completely clean up the device before I reinstall the stock rom.....
Any thanks again, and when I get a chance, I'll post my steps which had worked.
Cheers Mate,
Dave

Am glad to hear that

works great
Big thanks to BorgCymru for the how-to.
Just got a n7105 that was locked on EE/Orange (UK) that had KitKat 4.4.2 installed. Followed all the instructions but used cwmrecovery (to make backup rom) and it worked great for me. Tested with tesco, 3, o2 sim and all work.
Only thing to add that after installing firmware 4.1.1, the phone went to reboot but the screen became locked on the 'Samsung' logo. I removed the battery and booted into recovery to wipe partition and wipe cache. Rebooted and all was fine.

i been having issues unlocking with running 4.4.2 indeed to downgrade was the correct step, i am now unlocked

I know you posted the original post a while back, however I purchased a note 2 7105t off eBay and it was locked to Vodafone Australia. I actually got a code off their unlocking site and of course it did not work. I then contacted their customer service and waited 4 days for a call back with a unlock code and master reset code, once again did not work and I was told to take it to a Vodafone shop and they will send it away. One again, brick wall, as the shop said, "have you a proof of purchase from Vodafone". Nope I do not so they refused to send away and told me I was,"stuck with Vodafone".
Now I want to thank you for assisting me in unlocking my galaxy note N7105T 4.2.2 with your information. It worked like a charm.
The only question I have is if I now put an update firmware from 4.1.1 will the lock come back on? I see here a couple of members said they were fine, can I get verification on this please.

Hi Tamate. Once you unlocked it is permanent.

vadimo said:
Hi Tamate. Once you unlocked it is permanent.
Click to expand...
Click to collapse
No so... Did that way back, and last it while travelling, it locked itself! Still trying to find a way to unlock it (I'm now on Marshmallow!) Afraid downgrade back to 4.1.1 will do more damage (bricking the phone for good!)
BTW, how can I tell if my bootloader ever got upgraded?

Second Hand Note II, cannot get cellular data

I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.

GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/

absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse

Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.

Just use your father's sim card. Either it connects to the GSM network or it doesn't.

absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?

1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.

GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.

One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.

absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.

GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!

1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.

GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!

absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?

GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.

absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.

Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649

I already regret trying to add custom ROM.

Hello,
I tried to flash custom ROM, but something somewhere went terribly wrong.
I did read some guides on flashing before attempting this and did make some precutions as well.
Such as creating ROM backup with CWM and copying efs folder with Root browser.
Unfortunately I didn't succeed with the flash. Now the phone can turn on, but there is no network service, and IMEI number is missing.
I tried to go back to my original ROM, but that didn't fix the problem.
I tried to gather as much information as possible, but it seems that information on this device is a bit outdated. For example, I wanted to try to flash back to stock ROM with odin, but most links with stock ROM are down. The one that isn't down only provides .7z file instead of md5,tar file that is required by odin.
The device works, just can't connect to mobile network.
Is there something I could do?

Before flashing anything else, what baseband and bootloader is on the phone? The imei may be missing because the ROM is too new for the phone's current bootloader/modem combination.

Bootloader version is T999UVDLJA
Baseband version is UKNKOWN
I have finally found stock ROM in tar.md5 format, which is compatible with ODIN.

The t999 is the aws version of the s3 according to this: http://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
This forum is for the i747 and i747m (the AT&T and Rogers) version of the s3.
If the t999 is like the i747, do not flash any ROM via Odin that tries to downgrade the bootloader as this may brick the phone.

This makes just even more complicated.
When I go to settings -> About device, under model number I have SGH-I747.
When I double check this with Samsung phone info app, under model number I have SGH-I747.
In the same Samsung phone info app under PDA version I have I747UCDLK3 and under CSC version I have I747ATTDLK3
t999 only appears when I enter Download mode via volume down + home button + power button.

What does the label under the battery say about the model #?

Label under the phone is SGHT999.
Wow, this phone is weird...
I read on the forums that there is chance to restore firmware of the phone with KIES, so I tried that. At first I entered SGH-I747 model number and serial number of the phone and it failed. But after that I entered SGH-T999 model number and serial number of the phone and KIES started to update the phone.
At the moment I have android V4.3
Bootloader T999UVUENC2
Baseband T999UVUENC2
PDA version T999UVUENC2
CSC version T999MBENC2
Phone seems to be unrooted, IMEI number is visible, I can call again, but the phone's factory mode is on.
It seems that I had a SGH-T999 which somehow was tricked int thinking that it is SGH-I747.
At the moment I would just like to have a stock ROM for this phone without all the T-Mobile apps, would that be possible?

Does everything see to work?
The easiest way to root and remove apps would be to flash a custom recovery, install supersu and titanium backup. Then use titanium backup to remove the apps.

Yes, at the moment everything works.
I can call, receive sms, use wi-fi as well as mobile data.
The only problem is that phone has factory mode on Yellow text on black background. And it is heavily loaded with T-Mobile applications.
So I guess this phone is T999 then, right? How could it be that everywhere it had I747?
By custom recovery you mean custom ROM?

You need a custom recovery such as TWRP: http://forum.xda-developers.com/showthread.php?t=1809313
Download the tar version that can be flashed via Odin.
Download supersu and copy it to the phone. Flash recovery, boot directly into recovery without letting the phone boot the ROM, flash supersu, reboot. Install Titanium Backup from the Play store, remove the apps.

Thank you for sticking with me in this thread!
Could you please explain a little bit more what is TWRP? From the link provided I understand that is is a application that helps with custom rom flashing and backing up roms?
Shouldn't I do this at first - http://forum.xda-developers.com/showthread.php?t=1771687

Boot into download mode. Do you see anything about warranty bit 1? If you do, that means you have already tripped the counter.
Root is not required to flash a custom recovery.
If you are only interested in root, follow the other thread. If you want to be able to flash custom ROMs and backup the rom, you need a custom recovery which will definitely trip the counter.
Do you have any warranty left on the phone?

Yes, there is 1 next to warranty bit. What does it mean for me that I have tripped the counter?
At the moment I would just like to get rid of factory mode and remove those unwanted T-mobile APPS. I think I will be done with Flashing for quite some time
I don't have any warranty on the phone, It has been in the family for quite some time.

It would be 0 if the counter wasn't tripped.
To bring it right back to stock, you could flash one of the prerooted ROMs from the other thread. Just make sure you are flashing a rom that has the same bootloader that is currently on your phone. Hopefully, the stock rom will remove the factory mode.

I understand that the counter is only important if you need warranty, yes?
I actually just found a way how to remove the factory so that is one more thing less to worry about
And I rooted the phone with odin using the link few posts back.
Now for the final question, I understand that this rom is something along the lines that I'm looking for? http://forum.xda-developers.com/showthread.php?t=2501303

The ROM looks nice as long as you are running the correct bootloader and modem.
Installing a custom ROM only requires a custom recovery. There is no need to root or remove apps from the existing ROM since you are going to wipe the existing ROM before installing the new ROM.

I read through the thread and I understand that I have to flash T999UVUEMJC modem before flashing the ROM.
I'm not sure where the bootlaoder of this rom is mentioned. Only place where boot loader of my device T999UVUENC2 is mentioned is in change log "-Rebased to T999UVUENC2".

The official T-mobile firmware is here: http://www.sammobile.com/firmwares/database/SGH-T999/
Notice the last few letters in the firmware PDA?

Based on your post on the first page (post #7) you are on the NC2 bootloader and modem, which are compatible with the rom you are wanting to flash. (See the second line under the Disclaimer banner.) NC2 is the most current firmware for the T999 listed on the page Audit linked to.
(one explanation for how your device was reporting i747)
Is it possible that someone else flashed the i747 rom to this phone? Either someone doing you a favor or a previous owner? I747 roms will work on the T999, I frequently see people commenting on doing so successfully. You just need to have comparable bootloaders and modems. That and if the rom dev didn't accommodate the device in the updater-script the user must edit the script himself. In the unofficial cm12.1 thread for the i747 people were doing this often.

So the bootloader version is always the same as the modem version?
I understand that in my case I don't need to flash T999UVUEMJC modem, since the one I have at the moment is newer?
That is definitely possible, although, how it came to be I will never know, since I personally didn't buy the phone. But this would explain a lot.
Could you please take a look at this thread, I created steps I plan to do in order to flash the above mentioned ROM. It would really put my heart at ease http://forum.xda-developers.com/galaxy-s3-t-mobile/help/one-rom-flashes-please-double-check-t3111443

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!

If you're in Canada then just flash the Canadian firmware.

ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!

LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.

ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!

LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.

ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?

Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html

Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?

TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362

ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.

LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.

ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?

Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:

You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.

I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?

OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.

Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!