Related
I am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
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
Travelling in the Philippines and my wife's rooted 4.3 N900T (otherwise stock and Knox 0x0) is having issues with keeping cellular lock (Globe) and WiFi lock. Both signals drop periodically whereas my own N900T running Effortless rev 7 (4.4.2 NF4) is rock solid. Given that the phones are identical and she didn't have his problem prior to travelling I am assuming this is related to the older radio FW on 4.3. I'm looking for a fix with minimum changes to the phone (don't want to risk screwing up the phone when it is sometimes functional, limited tools on hand and very slow internet speeds). My initial thought was to do an OTA update to 4.4.2, but since the phone is rooted it will not allow this. I then looked for guides how to go from 4.3 to 4.4.2, but most threads assume 4.4.2 is already installed. I'm looking for advice how to fix the radio / FW problem. Open to flashing just the radios (does that trigger KNOX?) or doing OTA updates (unroot and wait for OTA or download and sideload files?). Any suggestions are welcome.
Found this regarding WIFI issues on 4.3. Trying turning off power saving and scanning to see if this helps. Would still be interested in advice regarding updating to 4.4.2 via OTA and if I can flash newer modems without triggering KNOX while remaining on 4.3.
follow this guide by effortless himself
http://forum.xda-developers.com/showthread.php?t=2765014
guaneet said:
follow this guide by effortless himself
http://forum.xda-developers.com/showthread.php?t=2765014
Click to expand...
Click to collapse
Thanks for the reply.
I have seen the effortless guide, but it assumes odin'ing a stock NK3. I can do this as a last resort, but I'm assuming the safest way to do this type of upgrade would be to start with stock MI7, then do the OTA to 4.4.2 so I get the bootloader, then do the NK3 or OTA up to NK3, then follow the rest of the guide? In this process I would need to backup my data e.g. using TI backup and restore later. Was hoping someone knew how to unroot manually, e.g. delete su files?, so I can OTA up to NK3 w/o doing the back up. Or would the latest modem or some newer version higher than the one from 4.3 work with 4.3 MI7?
Sent from my SM-N900T using XDA Free mobile app
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.
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.