Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks
My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?
this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness
You will need to unroot your phone and have the stock recovery.
Thank you for both replies gentleman
audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.
mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.
The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.
I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse
I rooted my dad's phone a while back ago so he can use tethering in case of emergencies etc. He recently got a smart watch and I wanted to updated it so that he can use it. But it has not been touched since that day. I essentially want rooted stock rom, I'm unaware of where to find that the closest I can find is StockMod kitkat. Which seems to not work on ATT phones? I just want to make sure that I don't brick his only phone on christmas. So is there something I should be aware of?
His model is SGH-i747
Baseband
i747UCDLK3
Build number
jro03
So how do I go about upgrading it? Can I just flash TWRP and flash any rom using TWRP?
I found this, so I should install new TWRP, then flash a specified kernel then flash rom? would this be safe route?
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
audit13 said:
Some of the latest ROMs require a 4.4.2 bootloader and modem.
The simplest and safest way to get the latest bootloader may be to flash back to unrooted stock 4.1.1 and run OTA updates until the phone is running the latest KK ROM. You can then flash TWRP or CWM and a custom ROM.
Click to expand...
Click to collapse
Would this require flashing with ODIN? I just want it so that it works with root is not required anymore.
Yes, you would flash the 4.1.1 stock ATT ROM via Odin. I prefer Odin 3.07.
You cannot install OTA updates with root.
You can try flashing just the bootloader and modem but I prefer the long slow route of OTA updates.
I rather do it this way, manually so my dad can enjoy it today. I was wondering how can I update it's TWRP? it's at 2.3 but the TWRP manager keeps crashing when I update it.
I highly recommend the latest d2lte version of Philz Touch for recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Ok I ****ed up, flash that kernel and did whatever and bam ****ed up. Not working... ****, I still ahve download mode and Recovery but it will not boot into the OS. I get a flash of samsung and then nothing else happends...****
I decided to flash stock DLK3 in odin. Then let the updates take it course (my dad doesn't need root) Where Can I find the file?
The stock ATT firmware is on sammobile.com.
If you want root, OTA to the latest 4.4.2, install Philz, flash supersu via recovery.