Related
Just got this small update for koodo i747m. Anyone know what is in it? Sammobile also has the full file already.
k29er said:
Just got this small update for koodo i747m. Anyone know what is in it? Sammobile also has the full file already.
Click to expand...
Click to collapse
That is odd, Telus has it too and Koodo is just Telus' subbrand. 4.4 Kitkat is supposed to be just around the corner and yet they pushed this 4.3 update (according to Sammobiles firmware page) seems like a waste if 4.4 is only weeks or a month away to be pushing any 4.3 updates.
Wonder if this is a bug fix until KitKat is out, as 4.3 is aweful and full of issues on the Canadian S3 atm.
I'm downloading the full firmware now to take a look but its a slow download, got an hour to wait >_<
How big was your OTA update?
dbzgod said:
That is odd, Telus has it too and Koodo is just Telus' subbrand. 4.4 Kitkat is supposed to be just around the corner and yet they pushed this 4.3 update (according to Sammobiles firmware page) seems like a waste if 4.4 is only weeks or a month away to be pushing any 4.3 updates.
Wonder if this is a bug fix until KitKat is out, as 4.3 is aweful and full of issues on the Canadian S3 atm.
I'm downloading the full firmware now to take a look but its a slow download, got an hour to wait >_<
How big was your OTA update?
Click to expand...
Click to collapse
38MB?
I have been on custom ROMs since 4.3 came out. Just odined
back to stock 4.3 today to be ready for 4.4 and suddenly its updating. I thought it was 4.4 till I notice it downloaded in less than two minutes.
And it auto updated with the Knox warranty bit tripped.
k29er said:
38MB?
I have been on custom ROMs since 4.3 came out. Just odined
back to stock 4.3 today to be ready for 4.4 and suddenly its updating. I thought it was 4.4 till I notice it downloaded in less than two minutes.
Click to expand...
Click to collapse
I opened up the ROM and took a look around and it seems to be only a bug fix/Updated build of 4.3 is all, but it is only for Telus, Koodo & PC mobile, since Telus acquired it not too long ago.
The acquisition might be the reasons why this 4.3 update got pushed to begin with to accommodate as it was Telus simply needed to have a 4.3 piece of software made for that propose.
I haven't tested the rom since it does not contain the CSC for Bell or Rogers and I only have access to my mothers S3 (something I wish not to mess up since its a Bell S3)
It's possible that the other carriers might have this out too but I don't see any reason for it since KitKat supposedly is to be released this month for all Canadian S3's.
A read out of the the additional CSC included in this is in fact SPC (PC Mobile):
?xml version="1.0" encoding="UTF-8" ?>
<CustomerData>
<GeneralInfo>
<CSCEdition>ED007</CSCEdition>
<Country>Canada</Country>
<CountryISO>CA</CountryISO>
<Region>NA</Region>
<SalesCode>SPC</SalesCode>
<NbNetworkInfo>3</NbNetworkInfo>
<NetworkInfo>
<MCCMNC>302220</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
<NetworkInfo>
<MCCMNC>21407</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
<NetworkInfo>
<MCCMNC>302221</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
</GeneralInfo>
<Settings>
Is the build number for that update really is I747MVLUEND2 ?
petenatas said:
Is the build number for that update really is I747MVLUEND2 ?
Click to expand...
Click to collapse
Yes, the main reasons to this update is just a addition for PC mobile that Telus acquired, but also probably the new roaming agreement between Telus and Verizon too most likely:
http://www.sammobile.com/2014/05/05...ting-minor-update-that-adds-roaming-on-telus/
At any rate, don't worry about this small patch. KitKat should be here within this month. (I hope they don't delay it anymore)
can anyone put update I747MVLUEND2 for telus because i have rooted phone and l have loosed my OTA ,,?? thanks !!!
Guys, I have a question:
I got a Koodo GS3, updated tp 4.3 I747MVLUEND2. I tried to root this thing with CF Auto Root, as it was mentioned online. No good, couldn't root, and when I looked into the download mode, it shows custom binary and custom system status.
Is that safe to flash back to I747MVLUEMK5 cause I saw the post has the rom for this firmware with/without KNOX. If yes, can I flash the one without KNOX? (My phone got KNOX trip and now it shows warranty bit:1)
todj09 said:
Guys, I have a question:
I got a Koodo GS3, updated tp 4.3 I747MVLUEND2. I tried to root this thing with CF Auto Root, as it was mentioned online. No good, couldn't root, and when I looked into the download mode, it shows custom binary and custom system status.
Is that safe to flash back to I747MVLUEMK5 cause I saw the post has the rom for this firmware with/without KNOX. If yes, can I flash the one without KNOX? (My phone got KNOX trip and now it shows warranty bit:1)
Click to expand...
Click to collapse
Since the Knox warranty bit is now 1, that means the warranty has been manufacturer's has been voided. Not a big deal if the warranty on your phone is over.
Now that your phone has the 4.3 bootloader, you cannot flash any ROM via Odin, TWRP, or CWM that attempts to downgrade the bootloader. Attempts to downgrade could brick your phone.
You may be able to flash back to mk5 using Mobile Odin.
audit13 said:
Since the Knox warranty bit is now 1, that means the warranty has been manufacturer's has been voided. Not a big deal if the warranty on your phone is over.
Now that your phone has the 4.3 bootloader, you cannot flash any ROM via Odin, TWRP, or CWM that attempts to downgrade the bootloader. Attempts to downgrade could brick your phone.
You may be able to flash back to mk5 using Mobile Odin.
Click to expand...
Click to collapse
Thank you for the advice. Wonder if I could use the Telus rooted rom with KNOX removed, which is I747MVLUEMK5 I found in the forum for my Koodo GS3.
did it work? I am in the same boat. Roms don't recognize this crazy bootloader and a lot won't install on it.
todj09 said:
Thank you for the advice. Wonder if I could use the Telus rooted rom with KNOX removed, which is I747MVLUEMK5 I found in the forum for my Koodo GS3.
Click to expand...
Click to collapse
As I understand it, that is a 4.4.x loader while the telus loader we have is for 4.3. Does that mean that it won't brick the phone to update because it is to a higher version? Since the bootloaders actually came out around the same time I am not sure what constitutes an upgrade/downgrade. Sigh, why did they make this so troublesome!? I actually tried flashing I747MVLUEMK5 from recovery but it won't allow it because the downgrade safeguard doesn't recognize this firmware. I am tempted to find an odin file and flash via that but the warning scared me and I'm not sure if it will brick. Could someone chime in on if this is safe and if it is, where to find the odin files? Is it possible to flash a recovery zip via odin? I don't think so.
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
Fam...
I bought a LTE Samsung 10.1 P605 from Verizon some months ago. It came with 4.3 already on it factory. I have been able to root it but that is all. I would love to get to a custom rom but with the Verizon boot loader issue not sure if totally possible get around the lock with 4.3.
I have read P605XXUCNE2 has been made available for the P605 LTE 10.1 models but my device does not show from it for update. I have gone to Sammobile and downloaded the P605XXUCNE2 (Nomadic) download listed for it.
Issue:
- Kies does not show for an update nor I see no way to push this rom NE2 manually
- Odin fails each time I try to push P605XXUCNE2 I assume due to boot loader
- Odin will not let me install TWRP (openrecovery-twrp-2.7.0.1-lt03ltexx.img) posted for the LTE model
So I cannot install a OEM firmware like NE2... How can I force or push a firmware to this darn device if ODIN fails? Am I locked in no mans land since I pushed a model that has 4.3 already on it? Am I stuck since it is a Verizon LTE model...?
Anyone can provide any steps who know a little about this model how I can get NE2 on it or TWRP even though OBIN says fails each time I try??
Model came as 4.3 with firmware P605VVRUCNC2
I'd guess the issue is that your device is not an SM-P605. Your device is an SM-P605V. The latest firmware SamMobile is showing for the 605V is NC2 (which should be 4.4.2, not 4.3).
blindmanpb said:
I'd guess the issue is that your device is not an SM-P605. Your device is an SM-P605V. The latest firmware SamMobile is showing for the 605V is NC2 (which should be 4.4.2, not 4.3).
Click to expand...
Click to collapse
Thx...I read it work...
With this info is there a way to get TWRP to install on the 605V?
I am pretty sure you are screwed if you want to flash Roms. Probably best bet is to sell it pay off what ever you owe or break contract and go to T-Mobile or buy WiFi (better for flashing Roms if you can handle not having LTE)
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello all, it's been a while since I understood the S3 firmware situation but I appreciate the advice.
I recently received a ATT S3 which is at OTA firmware 4.3 (MJB) and carrier SIM unlocked. I would like to arrive at CM12 with Philz recovery. I would appreciate suggestions on my best firmware upgrade route given the situation.
I understand the bootloader has been Knox'ed, so I may only upgrade (never downgrade) my Bootloader. However, I do not know the implications of KNOX on modem updates. I hear flashing a custom Recovery or Firmware will cause Knox to go to 0x1. Is it true or false that a tripped Knox (0x1) will PREVENT any further Modem or Bootloader updates? If this is true, it means I cannot use the upgraded 4.4.2 OTA modem (or later updates, if they are ever made) if I attempt flashing Cyanogenmod now (at 4.3 MJB). Is the new 4.4.2 modem worth it? Can 4.4.2 OTA still be rooted/custom recovery'd?
I am considering inserting an ATT SIM and allowing the the 4.4.2 OTA update to occur. Then I plan to use TowelRoot to apply Root from the phone itself. Then using EZ-Recovery (I used this on my VZW S3? But current seems to be Flashify?), I plan to flash Philz custom recovery from the phone itself. Then I plan to reboot into custom recovery and Clean install CM12 from the phone itself.
Does my planned approach have any issues? And what is this I hear about using Terminal commands to unlock the AWS1700 band (T-Mobile) semi-permanently? (I have a SGH-i747, not 747M. Posts seems to imply it only works semi-permanently on 747M?) I would like to keep my options open if possible. And is the ATT Knox 4.3 (MJB) firmware bootloader-locked? I was under the impressions all ATT S3 (d2att) were bootloader unlocked. (Answer here?: http://forum.xda-developers.com/galaxy-s3-att/help/bootloader-locked-t2990174 )
Thanks again for offering your opinions, there are many ways to skin a cat but I've been having a hard time matching the old methods I am aware of with the new tools. Thank you.
Edit: This thread has been helping explain the bootloader/modem pairing issues I can't understand. I am just unsure if newer = better.
http://forum.xda-developers.com/showpost.php?p=61782091&postcount=3
Regarding Stagefright bug, which is why I want to update to CM:
http://forum.xda-developers.com/showpost.php?p=62116470&postcount=6
My suggestion would be to run ota updates until you are running the latest modem and bootloader.
Flash Philz using Odin, perform a full wipe, install rom, install gapps.
Knox will not prevent installing roms, recovery, modems, or bootloader. Once on the latest kit kat, there is no need to install alternative bootloaders or b modems.
Hi, I doubt towelroot would work, as it's most likely been patched. (the exploit towelroot used). I believe the 0x1 is the warranty bit. I wouldn't think stock OTA update wouldn't be possible after, however. I'm not the one to verify this I'm on the I747M and I know the ATT stock images for the later releases are not available. So I cannot advise you there.
I'd say either use odin to flash cf autoroot.
or odin to flash recovery then supersu zip install to gain root.
I did search for ways without tripping the counter but like usual I was too late to the party to use towel root. But my warranty is out anyways.
Thank you for the insight. I think I will do just that, there are some ODIN-flashable 4.4.2 images provided by a helpful member here, but I do not want to do them out-of-order and potentially brick the device.
Since this phone has been completely abandoned by Samsung and ATT, I see no harm in voiding the Knox bit. If any applications complain, I can always use Xposed to fake it I suppose.
I will keep my fingers crossed that Towelroot will work. The last update ATT permitted was back in 2014, so there is a slim chance it may work. I will see when I do the OTA update.
Thank you! :good:
Hey all, as a followup I used OTA updates on stock combined with the procedure described here to achieve what I wanted. Knox has been tripped, of course.
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Some caveats:
I had to use a weird debug menu to get the unlock code ATT gave me to work. If I tried it as instructed by ATT as soon as the phone turned on it rejected the code. The #* instructions in the first post here worked and I was able to use the code ATT provided.
https://forums.att.com/t5/Samsung-D...code-for-galaxy-s3-does-not-work/td-p/3963728
I had to pull the battery after ODIN said "PASS" (as described in the video) to prevent the custom recovery from immediately being reverted to stock on reboot. When running SuperSU for the first time I had to try once, get stuck, then reboot and try again to "Remove Knox" properly.
I had to visit TWRP's site to download the newest Odin flashable TWRP TAR. The TWRP Installer Play Store app did not work when I had the CWM installed that was linked in the tutorial. The reason for needing TWRP is that CWM did not allow proper installation of the CM12.1 TK_Gapps "stock" version. I suggest anyone else in my position simply use TWRP Odin flashable TAR from the get-go. Also, simply hold down the Recovery mode button combo as soon as Odin forces a reboot rather than pull the battery.
For the record, Google Wallet Tap-And-Pay does not show up as an option in the app on the latest CM12.1 nightly (8-7-2015). Everything else seems to work. (CM12.1 for d2att recommends having the NJ1 bootloader/modem combo anyway.)
The TowelRoot method would have worked if I stopped at the 4.4.2 NE4 OTA update.... and theoretically would have preserved Knox. (At least until I flashed a custom recovery.) The OTA updates I received were a really big 4.3 MJB => 4.4.2 NE4 update (~500mb) then another, very small 4.4.2 NE4 => 4.4.2 MJ1 update (~20mb). I set my phone's clock ahead 24 hours to force the ability to immediately update.
Thank you @audit13 and @serathe for the tips. I hope this is instructional for anyone else in my position.