Related
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.
Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.
Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.
This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:
spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Solved
Thanks, also works for i727 skyrocket
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse
Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk
** Newer 4.4.2 version (UCUCNJ1) available HERE **
Here are a set of stock rooted Android 4.3 packages for the AT&T i317 Note 2 (firmware version UCUBMK6).
There are options flashable from custom recovery (CWM, TWRP) or, if you'd rather, via Odin. They are built from the 12/17/2013 stock OTA for the AT&T I317 in all their bloated glory.
**They do not include the MK6 bootloader or tz files **
** IF YOU ARE ALREADY ON THE MK6 BOOTLOADER (OR ABOVE) FLASHING ANY OF THESE PACKAGES WILL TRIP THE KNOX COUNTER **
These packages are intended only for the AT&T version of the Note 2 and include the modem and kernel for this phone. Flashing on any other North American Note 2 will result in a soft brick and require a re-flash of the modem/kernel specific to your phone. Flashing on any other phone will likely require a complete reflash of your phone's stock firmware to recover - do not attempt. The other standard disclaimers apply - while these packages have been tested and work on the AT&T i317, you assume all risk in flashing.
First a word on the MK6 bootloader - it has been reported that it is "locked". This is only partially true. If it were completely locked, we would be unable to flash custom recovery or kernel files from download mode - as is the case with the AT&T Note 3. What the MK6 bootloader prevents is downgrading the bootloader to any prior version. So, if we're going to call it locked, it's a "bootloader revert lock" but not a "firmware flash lock". A pain in the a$$, particularly if you want to revert your phone to 4.1.2 stock, clear the download counter with triangle away, unroot, and have your phone looking the same as it did on day one.
The main issue with the MK6 bootloader - If your phone is still covered by warranty: The MK6 bootloader implements one of the Samsung KNOX Secure Boot components: an "e-fuse" that gets set to "1" as soon as you flash something custom on your phone. Once set (so far anyway) this cannot be reset to "0". If this flag is tripped, a service center may use this to deny warranty repair coverage.
Given this, taking the OTA is not recommended for anyone thinking of flashing custom firmware at any time in the future. With that in mind, there is no MK6 bootloader or tz file in these packages. However, a 4.3 bootloader is needed in order for wifi to function. Fortunately we have a 4.3 bootloader available that permits revert to lower versions courtesy of the leaked MJ4 firmware provided by designgears. It is provided here to complete the install.
Here is what you have available:
All firmware packages include the system firmware, kernel, and modem from UCUBMK6. They are rooted with the as of Dec '13 current version of Chainfire's SuperSU. They include Linus Yang's build of busybox. They do not include recovery, bootloader or tz (you install the last two separately via Odin if needed)
All packages completely replace the contents of the system partition. If you are coming from another stock-based i317 firmware wipes should not be necessary.
**NOTE** Odin ZIP packages should be unzipped ONCE. The extracted MD5 file should be placed in the PDA slot in the Odin app. Do not change any other options. If the phone shows up on top as COMn and the MD5 checks out OK in the status window, you are good to click Start. **
AT&T UCUBMK6 i317 *Odexed* Stock CWM Note 2
AT&T UCUBMK6 i317 *Deodexed* Stock CWM Note 2
AT&T UCUBMK6 i317 *Odexed* Stock ODIN Note 2
If you *are not* running Official 4.3 (MK6) or newer bootloader:
After flashing one of the firmware packages above flash the bootloader package below in Odin to get wifi working (sorry, no option available for CWM/TWRP). I've included the Odin executable just after if needed.
Bootloader needs to be flashed only once. See post #2 for information on how to check what version of bootloader you have installed.
** Warning - do not attempt to flash MJ4 bootloaders if you already have the MK6 bootloaders - this will soft brick your phone - see post #2 for more **
AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY)
If you *are* running the Official 4.3 (MK6) bootloader:
After flashing one of the stock packages, you may need to flash the MK6 tz.img and optionally the param.bin from the MJ4 leak. This is likely to be so if you are on the MK6 bootloader and have previously reverted to 4.1 firmware. The zip below contains two Odin packages. If after flashing the stock package and you are on the MK6 bootloader, try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
AT&T i317 ODIN 4.3 UCUBMK6 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY)
Need Odin ? --> Odin 3.07
For completeness's sake I've included separate packages for the ucubmk6 modem and stock kernel & recovery.
CWM AT&T i317 UCUBMK6 Stock *Modem* Note 2
CWM AT&T i317 UCUBMK6 Stock *Kernel* Note 2
CWM AT&T i317 UCUBMK6 Stock *Recovery* Note 2
Here are links to custom recoveries specific to the I317 (AT&T Note 2):
PhilZ Advanced CWM Edition
TWRP Recovery
*** After you boot the phone, run the SuperSU app. You will be asked if you want to disable Knox. Your best course of action here is to answer yes.
• Thanks to Chainfire for SuperSu - we wouldn't have root access on 4.3 without his work (we should all be donating to him or buying his pro version)
• Thanks to designgears for the initial 4.3 leak, which gave us the 4.3 bootloader/tz allowing revert to earlier bootloaders
• Thanks to Linus Yang for the busybox build
• Thanks to dicksteele for helping test odex & odin packages
[FONT="]
[/FONT]
FAQ - Issues related to 4.1 to 4.3 upgrade/downgrade, etc
My files on my SD Card disappeared! or I'm out of space, but why?!?
When moving to 4.3 from 4.1 Android remaps the SD Card from /data/media to /data/media/0. All your files are still there, just inaccessible from your PC via USB connection, or from standard file managers. Root-capable file managers/explorers can still see the files and can provide a fix. See this thread for a permanent solution (assuming you are done with 4.1.x):
http://forum.xda-developers.com/showthread.php?t=2274218
(Note that if you revert to a 4.1.x rom you will need to reverse this process).
I can't restore CWM/TWRP backups made in 4.1.2 now that I'm on 4.3 (or visa versa)
I believe this may be a variation on the above issue. try moving (not copying - as you may run out of space) your cwm or twrp backup folder from it's relative location in media to media/0 or the reverse and try your restore again.
** last note on this issue - philz recovery has an option to toggle sdcard location to media/0 which can help with seeing backups, etc - not sure about twrp
When I revert from 4.3 to 4.1 Gmail won't send messages
Go into Settings/Apps and clear data and cache for Gmail
I tried to flash the MJ4 bootloaders on top of the MK6 bootloaders already on my phone and now I get a message about kies and my phone won't boot
This is how the MK6 bootloader demonstrates its hostility toward downgrade attempts... While you may be stuck in download mode, you do not need to reflash an entire firmware package to escape. The easiest way out is to succesfully flash a custom recovery Odin package. This will clear the error condition in download mode and your phone once again boot correctly. See the recovery links in the OP to find an Odin package for your preferred custom recovery.
I'm not sure what version of bootloader I am running - how do I check?
There's a simple app called "Device Info" available on the Play Store (it's the one published by JPHILLI85) which will display your bootloader version. The only permission it requests is phone status/id. Or you can open up terminal emulator and type "getprop ro.bootloader" if you don't want to install an app (assuming you have already installed Terminal Emulator).
I would like to get back to a pure stock unrooted configuration - how do I do this?
First, if you have the MK6 bootloader this is currently not possible - at least as far as what will be displayed in download mode. If you are on MJ4 or below, the simplest way to do this is to flash back to 4.1.2 using the stock UCAMA4 Odin package, cf-auto-root, run triangle away, run SuperSU to completely remove root, boot recovery and do a factory reset. After this you have the option to take the OTA and update to UCUBMK6 if desired with stock everything - but it will be a one way trip with the previously discussed "revert locked" bootloader. This is the short version, there are guides available in the general section, which offer variations on this with different files. Note that the UCALJ2 ODIN package offers an option for those with the MK6 bootloader as it does not include the bootloader or tz files (thus is does not soft brick the phone as described above). In that scenario you stay on the MK6 bootloader so you don't get a complete revert (no ability to run triangle away, but you can get back to 4.1.2 and factory reset).
Here are links to the Odin stock packages for reverting and the relevant threads:
UCUBMK6 Downgrade to UCALJ2 (general guide - Thanks @perez6991 !)
How to OTA to 4.3 MK6 from LJ2 4.1.1 (with MK6 bootloader!) - Thanks @dicksteele !
Stock UCALJ2 ODIN package for those with MK6 bootloaders
TZ and (Optional) PARAM for those with MK6 bootloader
Stock UCAMA4 ODIN package for those with MJ4 bootloaders
General instructions for those with MJ4 bootloaders (use instructions but not files) **
** A note on this last link for those with MJ4 bootloaders - the instructions are sound, but the files provided include the LJ2 package and older versions of cf-auto-root and triangle away. Use MA4 instead and locate the current versions of the other two Chainfire apps (I've provided links in the previous sentence - for cf-auto-root make sure you grab the "SAMSUNG-SGH-I317" file) **
----------------------------
How to get Screen Sharing (AllShareCast) working - http://forum.xda-developers.com/show....php?t=2542509 (thanks to @joshuaburnsjr for tracking this down)
In other news ....
Technology is magic - you shouldn't let poets lie to you >>>> * <<<<
--------
:good::laugh::good: Big thanks to those who have contributed to my Android mischief fund :good::laugh::good:
Awesome work for a Retired Contributor, Sir.
Thanks, Zen. Will have to give it a go once I get tired of looking at my "normal" status.
I've been trying everything on this base and it is perfect. If something does not work for you, you did something wrong. Not trying to be an ass, but I've been running it for three days now and it's solid. I have over 150 apps. (edited from 200 since I cleaned a lot of crap out I never used)
Backups of apps are great, but if you want a true cherry ROM, install your apps from scratch. I did.
Yeah, it's a pita, but it's a good time to decide what you really need. And it's done right. You don't have to wonder if your backup program hosed it up, is it a ROM issue, whatever.
Google Play keeps a good history of what you have installed so it's not that hard to find old or new apps you have loaded.
Enjoy. It was an pleasure and honor to assist.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thank you!!!
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Omg thanks Zen....
Enviado desde mi SAMSUNG-SGH-I317 usando Tapatalk 4
!!!!
Thank you thank you thank you!!!!
Just wanted to say: you saved my day! So glad I don't have to curl up in the corner of my bedroom crying because I bricked my phone ...
I just flashed everything and it worked just like you said!
No problems at all. Just wanted to let you know.
Thanks so much for your hard work, so we can enjoy 4.3 on our devices! :good:
Just for informational purposes, my phone came from: 4.1.2 Stock TWRP (2.6.3.0) rooted
esprit1st said:
Just wanted to say: you saved my day! So glad I don't have to curl up in the corner of my bedroom crying because I bricked my phone ...
I just flashed everything and it worked just like you said!
No problems at all. Just wanted to let you know.
Thanks so much for your hard work, so we can enjoy 4.3 on our devices! :good:
Just for informational purposes, my phone came from: 4.1.2 Stock TWRP rooted
Click to expand...
Click to collapse
Good news.
Thanks for the info about where you flashed from. What TWRP version was it?
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Thanks not only for the ROM zen, but also thanks for clearing up the bootloader nonsense as well.
This is the first place I've seen it clearly stated for users. I've tried explaining in the past, but is been misinterpreted due to the way I've phrased things. In the future I'll just link this thread to explain.
--》Sent from my mind to your screen
funtimez said:
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Click to expand...
Click to collapse
It sounds like something is hanging around from your previous rom. Since you have a backup I'd recommend the following (note that this will wipe your phone and require a TiBu restore or Play Store app reload):
1 - Take a full backup using Titanium Backup
2 - Copy everything from your SD cards to your PC
3 - Flash the 4.3 package
4 - (You can skip the bootloader since you already flashed it, unless your twrp backup restores an older bootloader)
5 - While in recovery, do a factory reset (this will wipe everything)
6 - Boot phone, check that wifi works, and other standard functions are ok
7 - Restart phone, and confirm that the problem you saw before is gone
8 - If the problem is gone (i.e. the phone reboots successfully multiple times with no lockups), continue on...
9 - Copy the contents of your SD cards back to your phone - check to make sure everything is copied - the USB driver for the Note 2 can be a bit selective at times (also refer the the FAQ in Post #2 - confirm that sdcard information has been removed from /data/media and is in /data/media/0)
10 - In TiBu, restore ONLY user apps (you can restore app+data, but in some rare cases you might need to clear data) - do not restore any system apps. (Alternative - you can restore apps directly from the Play Store as dicksteele noted in a previous post - this may be cleaner, but you will lose any data associated with the apps - your call and ymmv).
11 - Reboot phone, and confirm everything is OK.
Hopefully this clears the issue for you. If it does not, you may need to do a full wipe between steps 2 and 3 above, clearing /data and your internal sdcard before starting the install. If so, make sure you have access to stock odin packages to reload your phone OS just in case. There are threads on this in the General section, but I'll post links to the files in post #2 as well.
Awsome. Thanks so much, needed root works great ::good:
funtimez said:
I flashed the deodexed file in twrp and rom loaded fine. Then I flashed the bootloader in odin-I made sure it was the pda slot and hit start. Rebooted phone and was stuck at first screen saying galaxy note 2. So I flased the deodexed rom again in twrp anf everything loaded fine and wifi worked but when I went to reboot it gets stuck at the first screen again. Tried flashing again but didnt work. Then I tried fix permission and it worked, bit when I went to reboot it would get stuck again. After trying a bunch or other stuff like wiping and fixing permission I was able to go back to 4.1.2 jedi that I had a backup of. All seems fine fo4 now but would still like to be on 4.3
Click to expand...
Click to collapse
Piggybacking on Zen's reply, which TWRP are you using?
I've been using 2.6.3.0 and 2.6.3.1 and I've had issues with restores. You may want to try PhilZ Advanced CWM Edition. Zen has a link in Post #1.
I'm using the latest version 6.00.8 and it's been restoring great. You can flash it from TWRP and reboot to recovery from TWRP and Philz with come up.
EDIT: If you're going to use Philz recovery for Wipe Data/Factory Reset, choose Clean to Install a New ROM.
Thanks for replying I figured it out by the time u guys replied. I updated to the latest version of twrp,I was on a old 1. Then I factory reset and wipe delvic and what not then did a full wipe. I then installed 4.3 Ron and didn't wipe cache and delvic but got stuck in bootloop. So I wiped again and flashed again and this time I wiped cache and delvic and everything it working just fine now including reboots. Thanks for this awesome update and the help from u guys
Dude............this ROCKS!!!! THANK YOU!
AT&T Galaxy Note II Android Development > [ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4
Thanks for this Zen. I've been patiently waiting for someone to do this. You are the man!
Thanx Zen for this...:thumbup:
I'm going to have to add this my one stop shop for sure...
Bajan out...
SENT FROM SAMMY i317 USING TAPATALK
Thanks!
Running 4.4 to test it out, but I'm keeping this as my fail safe.
Went exploring other ROMs due to deodex 4.3 not being out at the time, but I'm glad you put in work to organize it
and offer 3 different versions of it. Thank you!
So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.
I was on CM 10.2.1
I upgraded to CM11 - I get no wireless data. My phone works but I have no APNs and I could not add them.
I tried SlimKat 9.0 same issue with the APN
I upgraded my CWM to 6.4.0.7 as I heard that caused issues when upgrading to CM11.
I bought Mobile Odin and flashed that way as I thought it might help.
Ive done the following to fix my APN
1) Loaded an old one from working CM 10.2.1
2) Run Root Tweak with the fix APN for CM11 checked
3) Done the airplane mode trick
4) Attempt to add one manually
Does anyone know why this is happening and more importantly how to correct this issue?
Yes I did pore through other threads on how to fix this but no avail.
Thank you
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
audit13 said:
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
Click to expand...
Click to collapse
Bootloader = I747UCDLK3
Modem = I747UCDLK3
Yes I get data when I load a backup of CM 10.2.1
Thanks
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
Thanks for the quick reply. That sounds hard. From what I'm reading going back is treacherous.
So these are the steps.
1. Load this firmware via ODIN -> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.zip -- What about gapps? Is that in this zip?
2. Run triangle away. (Do I need to do this?)
3. Contact my carrier to unlock my sim. (If this is carrier unlocking ie taking my att phone to Sprint etc, why is this needed?)
4. Get OTA updates. Will this come automagically because I'm on 4.1.1 and does it matter if my flash counter is gt 1?
5. Root phone via Odin with this file CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5.
6. Install CWM if it went away when I went back to firmware - Of course it would because I'll factory reset my phone in step 1.
7. Flash away to a 4.4.4 Rom
Did I miss anything?
Step 4 is the one that scares me -- That one is out of my control. Either I get the OTA or I dont. Anyway I can "request" the OTA?
Thanks again
Be Well
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
audit13 said:
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
Click to expand...
Click to collapse
To stick with 10.2 or not to that is the question. Everytime I flash or do anything like this on my phone - I get a small lump in my throat knowing I'm dancing in the razors edge of bricking it.
I know how you feel, but I've done it enough times and just accept the fact that I may brick the phone. Jtag service would cost me around $75 so I'm willing to take the chance. I'd be less willing if the phone still has warranty.
Flashing back to stock and running OTA updates is the safest route.
If you don't sim unlock while on stock 4.1.1 and you want to sim unlock your phone in the future, you will need to be on a stock or virtually stock ROM in order to enter the unlock code.
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
ddunleavy2 said:
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
Click to expand...
Click to collapse
In a terminal or adb shell you can enter this to check your bootloader:
Code:
getprop ro.bootloader
In a terminal or adb shell you can enter this to check your modem (should match the baseband your phone reports in About):
Code:
getprop gsm.version.baseband
I don't believe either of these commands require root unless stock has getprop locked down tighter that AOSP ROMs; I just entered them in a user shell.
There are a couple of firmware updates for your device beyond MJB, NE4 and NJ1. Some users, myself included, had GPS problems that were a bit of a pain to fix on newer 4.4 AOSP based ROMs with the MJB firmware, but data was ok with MJB. Also, you'll need newer firmware if you decide to test drive the lollipop alphas that are floating around. There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route. You're already on MJB so there's no going back
The terminal worked
Bootloader and baseband = I747UCUEMJB
What???? I might need more updates for all the roms out there.....ugggh.
"There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route."
If I decide to use these flashable firmware updates on XDA from a trusted developer or OTA its same as this: going forward and NEVER going backward when getting firmware updates?, yes?
yes. downgrading bootloader will almost certainly cause a brick.
"all i can really do , is stay out of my own way and let the will of heaven be done"
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
+1
"all i can really do , is stay out of my own way and let the will of heaven be done"
You guys are on point.
Last night I received another OTA to 4.4.2.
Baseband now at NE4.
Thanks again for taking the time to answer all this -- Really really appreciate it.
EDIT: Can I still use this to root my phone via ODIN or is there a different process for this baseband?
CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5
I load this into ODIN, plug my phone in download mode and root away. Does either the file I use change or do I have to use something other than ODIN?
Thanks again
To get root, I would flash a custom recovery and flash supersu from recovery, then let supersu disable know.
The file you named looks to be outdated as it refers to the s3 as d2att. Since unified builds were released, the s3 is now referred to as the d2lte.
I have ROM Manager installed. It has an option to "Flash Clockworkmod Recovery". I just tried it and it failed and I think thats because I dont have root. In the past I've had to root my phone via ODIN, then flash custom recovery then MOD away.
In the past I rooted the S3 via ODIN. With this new 4.4.2 version do I still root via ODIN provide I find the correct file because -> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 this one is probably for a 4.1.1 version phone?
I would not flash anything for the d2att at this point.
Try this:
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download supersu zip from here and place it onto an external SD card or copy it to the phone's internal storage: http://download.chainfire.eu/695/SuperSU/
In Odin, uncheck everything except f.reset time. Flash Philz. When you see reset in the status window, remove USB cable, pull battery, replace battery, boot into recovery, flash supersu, reboot.
I am fairly certain that AOSP, or at least CM, de-unified in the past few months. Not that it matters much, other than for the confusion it causes.