Develop Bugs

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.

Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...

B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.

drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP

when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip

dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.

drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks

dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.

drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....

Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT

dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.

pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.

I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.

Odin back to pure stock working fine.. some of my apps fore close though

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.

Anyone wanna pull just the baseband for cwm zip?

[HOWTO] [ROOT] No Tripping Flash Counter [Tmobile / Wind / Mobilicity / Videotron]

This is a completely stock ODIN flashable ROM with root injected into the system image.
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
4.3 Image Notes: With 4.3 images, KNOX is removed in order for root to stick. This will flag the Knox counter. Once you flash one of these 4.3 images you now have the latest factory stock bootloader, radio, etc. Flashing a prior bootloader can hard/soft brick your device. Please read and understand what you are doing.
You can get ODIN here
and the drivers for the SGH-T999 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
First download the stock odin tar that has a rooted system image injected into it:
Note: Always check the MD5 sums before using any of these! Thanks
MCT: Mobilicity
GLW: Wind
VTR: Videotron
T-Mobile Image
March 2014 - 4.3 JellyBean - New!
Note: This is based off of the stock image TMO T999UVUENC2
Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.
Perm Mirror: Download - root66_TMO_T999UVUENC2.7z
November 2013 - 4.3 JellyBean
Note: This is based off of the stock image TMO T999UVUEMJC
Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.
Perm Mirror: Download - root66_TMO_T999UVUEMJC_2.7z
April 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image TMO T999UVDMD5
Perm Mirror: Download - root66_TMO_T999UVDMD5.7z
January 2013 - 4.1.1 JellyBean
Note: This is based off of the stock image TMO T999UVDLJC
Perm Mirror: Download - root66_TMO_T999UVDLJC.7z
Note: This is based off of the stock image TMO T999UVDLJA (October 2012 - 4.1.1 Jelly Bean
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z
T-Mobile LTE Image
March 2014 - 4.3 JellyBean - New!
Note: This is based off of the stock image TMO T999LUVUBNC1
Download :: Download - root66_TMO-L_T999LUVUBNC1.7z
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image TMO T999LUVUBMK4
Download :: Download - root66_TMO-L_T999LUVUBMK4.7z
WIND Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image GLW T999VVLUEMK5
Download :: Download - root66_GLW_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image GLW T999VVLDMF2
Perm Mirror: Download - root66_GLW_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image GLW T999VVLDLL1
Perm Mirror: Download - root66_GLW_T999VVLDLL1.7z
Mobilicity Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image MCT T999VVLUEMK5
Download :: Download - root66_MCT_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image MCT T999VVLDMF2
Perm Mirror: Download - root66_MCT_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image MCT T999VVLDLL1
Perm Mirror: Download - root66_MCT_T999VVLDLL1.7z
Videotron Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image VTR T999VVLUEMK5
Download :: Download - root66_VTR_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image VTR T999VVLDMF2
Perm Mirror: Download - root66_VTR_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image VTR T999VVLDLL1
Perm Mirror: Download - root66_VTR_T999VVLDLL1.7z
Second,
Extract the root66 tar file from the .7z file you downloaded.
Put phone into download mode [ with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66 tar you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
If you are coming from a different rom base (non-stock) you will want to factory wipe/reset in recovery after flashing this.
OTA Updates:
Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process.
Non-Stock Recovery: If you have loaded a non-stock recovery (per below) you can simply use it to flash the OTA update flashable zip I've created. This is the stock OTA just modified to be flashable in CWM and TWRP and not lose root in the process. As such it still does all the checks so if you have deviated from the rooted stock image above by modifying system files this will fail.
Download: OTA Update UVALJ4 to UVDLJA
Download: OTA Update UVDLJA to UVDLJC
Third, (optional)
Note: On Jelly Bean releases it is possible and I'd say probable based on my experience with the Note II that loading a non-stock recovery will trip the counter no matter how you install it.
If you want to get clockworkmod recovery loaded so you can flash whatever you want, nandroid, etc then continue on....
Once rebooted you can essentially follow this thread to load the clockworkmod recovery. As long as you flash the recovery using the dd method with adb (or use terminal emulator from the play store) then you will NOT trip the flash counter. If you use ODIN to flash a custom recovery you will trip the counter.
Third, alternate if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
If you would like to install TeamWin Recovery Project then grab GooManager from the Play store and select the option to "Install OpenRecovery Script".
De-Bloater
If you've made it this far with a stock, rooted phone with cwm and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my Aroma installer based De-bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Recommended and still get a decent de-bloat.​
[Note: Flashing this with ODIN will not wipe /sdcard or /data. Keep that in mind depending on your usage.]
Bonus Downloads
Odin Flashable Stock TMO UVDMD5 Recovery - This is an Odin Flashable STOCK Recovery for TMO from UVDMD5 release - TMO_recovery_T999UVDMD5.tar.md5
Odin Flashable TWRP Recovery - openrecovery-twrp-2.3.1.0-d2tmo.tar.md5
Thanks
To get the injected root system image I followed pieces of
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
http://forum.xda-developers.com/showpost.php?p=22798858&postcount=32
so thanks to those guys. Neither of those worked out of the box needed a bit of tweaking.

Nice
Sent from my SAMSUNG-SGH-I717 using xda premium

I'm confused about this counter... Is the purpose really just so samsung can say no to a warranty claim? Is there a limit to the number of times the recovery can be flashed? I want to flash the new touch CWM but am afraid to do so if I only have so many times to flash a recovery.

silverton said:
I'm confused about this counter... Is the purpose really just so samsung can say no to a warranty claim? Is there a limit to the number of times the recovery can be flashed? I want to flash the new touch CWM but am afraid to do so if I only have so many times to flash a recovery.
Click to expand...
Click to collapse
Yes, the purpose of the counter is so that the manufacturer can reject service warranty if they see it tripped. I don't believe there is a limit of how many times you can flash. I might be wrong.

I just hope we can get a working Triangle Away on our devices.

cockwork
chadster214 said:
I just hope we can get a working Triangle Away on our devices.
Click to expand...
Click to collapse
Does using clockwork trip the counter?

Lawful123 said:
Does using clockwork trip the counter?
Click to expand...
Click to collapse
no, it does not.

mrRobinson said:
This is a completely stock ODIN flashable ROM with root injected into the system image. It is based off of T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar.md5
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
First download the stock odin tar that has a rooted system image injected into it:
TMO Image
Note: This is based off of TMO T999UVALEM that was posted in this thread, thanks to AdamLange.
Click to expand...
Click to collapse
Brilliant! Thanks!
Sent from my SAMSUNG-SGH-I717 using xda premium

Awesome!
Just to make sure I have this right then.
We can Root, install CWM, and then install custom roms without triping the counter?!?!
And then if needed I assume you can flash stock odin!
All with no trip of the counter?

If we use this, can we use the Galaxy S3 toolkit to install CWM? Or for that matter, can we just use the Rom Manager app from the app store and use it?

M9x3mos said:
Awesome!
Just to make sure I have this right then.
We can Root, install CWM, and then install custom roms without triping the counter?!?!
Click to expand...
Click to collapse
yes
M9x3mos said:
And then if needed I assume you can flash stock odin!
All with no trip of the counter?
Click to expand...
Click to collapse
yes. Once there is a way to reset the counter people won't care as much about not tripping it. Unless the reset method is difficult or dangerous but for now as long as you never initially trip the counter you can simply flash back to stock and your phone is still covered under warranty.

OK, I used this, and everything appears to have gone fine. I have root now. Curious though, when it booted back up, nothing appears to have changed, except superuser is there now. I thought it would have reset the whole phone back to factory new.

stevessvt said:
OK, I used this, and everything appears to have gone fine. I have root now. Curious though, when it booted back up, nothing appears to have changed, except superuser is there now. I thought it would have reset the whole phone back to factory new.
Click to expand...
Click to collapse
Nope. it'll overwrite anything in /system you may have done. but doesn't touch sdcard or /data.
So that means if you had a cm9 or aokp loaded and used this you'd boot into a bunch of errors more than likely and would want to manually factory reset.
Edit: also i had no way to test this so you are confirmation it is working. prob should have put that in the first post but was late last night and forgot. So sorry and thanks!
(you weren't at risk of tripping counter, i've done this before, worst case was system image wouldn't flash and you'd have to load the stock one via odin)
Edit2: plus you are like 20 min from me so if I broke your phone I'd have come and fixed it

Speaking of if I ever need to odin back to stock, I have the stock T999 rom from samsung, and it has 2 files in the zip, a .dll and a .tar. How do I use these to revert back to stock? I guess the .tar goes under pda, where does the .dll go? Or does it?

If you're worried about warranty just wait firva triangle away, personally I have insurance. I'll toss my phone in a lake and bring it back that way lol
Sent from my SGH-T999 using Tapatalk 2

stevessvt said:
Speaking of if I ever need to odin back to stock, I have the stock T999 rom from samsung, and it has 2 files in the zip, a .dll and a .tar. How do I use these to revert back to stock? I guess the .tar goes under pda, where does the .dll go? Or does it?
Click to expand...
Click to collapse
.dll goes in recycle bin.
.tar in pda.

mrRobinson said:
.dll goes in recycle bin.
.tar in pda.
Click to expand...
Click to collapse
Lol, OK....
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
anthonykash said:
If you're worried about warranty just wait firva triangle away, personally I have insurance. I'll toss my phone in a lake and bring it back that way lol
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
No reason to now. This works flawlessly

mrRobinson said:
.dll goes in recycle bin.
.tar in pda.
Click to expand...
Click to collapse
lmao, i dont see" recycle bin" on odin? jk

Awesome! i have been waiting for this. Does the rooted Rom comes with busy box installed?
Sent from my SGH-T999

How Do We Know If We Tripped Counter
I have a question, how do we know if we tripped the counter? I used ODIN to flash Clockword.tar and then I went into Clockwork to flash Superuser and flash a Stock T-Mobile ROM from Whitehawk. Once I booted i downloaded busybox and installed it to complete the rooting process. I never seen any warning triangles, the only thing I worried about was flashing the custom recovery in download moad, but its not a ROM so it should not have tripped the counter and any ROM flashed I have done, all have been in Clockwork MOD Recovery, never in download mode through ODIN

[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]

This is a root injected FACTORY Stock I317 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
4.3 Image Notes: With 4.3 images, KNOX is removed in order for root to stick. This will flag the Knox counter. Once you flash one of these 4.3 images you now have the latest factory stock bootloader, radio, etc. Flashing a prior bootloader can hard/soft brick your device. Please read and understand what you are doing.
You can get ODIN here
and the drivers for the SGH-I317 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
ATT Rom
January 2013 JB 4.1.2
Mirror 1: root66_ATT_I317UCAMA4.7z
October 2012 JB 4.1.1
Mirror 1: root66_ATT_I317UCALJ2.7z
Mirror 2: root66_ATT_I317UCALJ2.7z
Image supplied by Kirbo20. Please thank him for his time in getting the stock image to me.
Bell Rom
December 2013 JB 4.3 - New!
Download: root66_BMC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_BMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BMC_I317MVLALJ2.7z
Mirror 2: root66_BMC_I317MVLALJ2.7z
Telus Rom
December 2013 JB 4.3 - New!
Download: root66_TLS_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_TLS_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_TLS_I317MVLALJ2.7z
Mirror 2: root66_TLS_I317MVLALJ2.7z
Rogers Rom
December 2013 JB 4.3 - New!
Download: root66_RWC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_RWC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_RWC_I317MVLALJ2.7z
Mirror 2: root66_RWC_I317MVLALJ2.7z
Sasktel Rom
December 2013 JB 4.3 - New!
Download: root66_BWA_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_BWA_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BWA_I317MVLALJ2.7z
Mirror 2: root66_BWA_I317MVLALJ2.7z
Virgin Rom
December 2013 JB 4.3 - New!
Download: root66_VMC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_VMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_VMC_I317MVLALJ2.7z
Mirror 2: root66_VMC_I317MVLALJ2.7z
Second, Extract and Flash:
Extract the root66_xxx_I317MVLALJ2.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_I317MVLALJ2.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.4.4.0-t0lteatt.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.​
Miscellaneous Files
CWM/TWRP Flashable OTA Update: I took the stock I317UCALK7 update.zip that was posted by reinbeau (thanks!) and simply made it flashable with a non-stock recovery preserving root through the process. I see nothing in here that would wipe data but did not test it myself.
Download: root66_OTA_I317_UCALJ2_to_UCALK7.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the ODIN image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
More to come...

I noticed the Rogers and Sasktel hit Kies. Others should follow.

Can I still using this method after rooted with Cf auto root? Just curious. Because just want to return to stock and have root. Mine is messed up somtime is show device is normal sometime is modified.
Sent from my SGH-I317M using xda app-developers app

vincedoggy said:
Can I still using this method after rooted with Cf auto root? Just curious. Because just want to return to stock and have root. Mine is messed up somtime is show device is normal sometime is modified.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Absolutely.

Will try and giving the feed back later
Sent from my SGH-I317M using xda app-developers app

Thanks so much for doing this for us Canadians! I see that the Telus version is now available via Kies and was wondering if you could also do your magic for this firmware as well?
Edit: Just realized it's already in progress by you... thanks!!

You are the man. Thank you sir.

I am on ATT, would I use the Bell file? Or is ATT different?
Thank you for yiur work here.

alperin1 said:
I am on ATT, would I use the Bell file? Or is ATT different?
Thank you for yiur work here.
Click to expand...
Click to collapse
Gotta wait for the ATT to hit Kies.... hasn't happened yet. I'd expect soon.

Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app

If you have spare time, Can you also give us ATT/Rogers/Bell/Sasktel (unrooted) flashable firmware via Odin ? Since we need it to back to stock unrooted...

Thank you so much you just saved my Note 2

I could post but let me be clear. There are exactly two files different from pure stock here. /system/app/Superuser.apk and /system/xbin/su
If you open Supersu and tell it to remove root and uninstall you are 100% stock. There is zero difference. So quite a waste to put up another 700+mb file for 2 files that total maybe 1mb.

vincedoggy said:
Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
This DID reset everything to pure stock. The only thing you would want to do is wipe data. This doesn't touch your data partition so to completely factory reset simply boot into the stock recovery. Do a factory/full wipe, then flash this. If you have already flashed this then simply do the wipe in the recovery and I'll guarantee learning hub starts working.

vincedoggy said:
Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Posted a fix and reason why you've been locked out of learning hub in the Q and A thread you've posted in. Its explains how it happened and how to avoid it again. If all else fails then a wipe and reflash of Robbinsons rooted injected rom would be the next thing to do.
Sent from my SGH-I317M

I already posted the problem in QandA but no solution yet. Will try this then report so others can avoid thus happen. Thx.
Sent from my SGH-I317M using xda app-developers app

vincedoggy said:
I already posted the problem in QandA but no solution yet. Will try this then report so others can avoid thus happen. Thx.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
What dbzgod posted is a solution. To simplify, if you flash what is in this OP and no custom recovery with a data wipe you will not be modified and the apps will work. if you are coming from modified then just clear data in the apps as he said and you'll be fine as well.
As an aside, all the canadian variants root injection are up. Just waiting on ATT now.

Just curious then if this also includes the stock recovery?
I have CWM installed now and would need stock recovery if I am to fully return yo stock.
Thanks in advance. Really appreciate your work and time.

Nice work Mr Robinson :thumbup::thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

scourge18a said:
Just curious then if this also includes the stock recovery?
I have CWM installed now and would need stock recovery if I am to fully return yo stock.
Thanks in advance. Really appreciate your work and time.
Click to expand...
Click to collapse
Yes. This is full stock. Kernel, recovery, bootloader, modem, system,etc.

SuperSU Giving 1 Flash Counter. Trying to go back to stock rom with OTA.

Hello,
I’m looking for some guidance on getting my phone back to completely stock.
Steps I’ve done:
I have re-flashed back to the stock image using Odin. After doing so I wipe/reset. I then had a flash count of 8.
I then used Chainfires method and flashed with Odin to root device, which only installs super SU. I ran triangle away and still had a flash count as one. So I ran triangle away again and clicked the box that disables superSU for an amount of time. The rom went back to official with no flash counts.
Here is where I ran into problems. I ran super SU after seeing I had no flash counts to unroot the device. As soon as I opened superSU I got a flash count back to 1 again and could not update device from original firmware. I tried several different times including full wipe reset after I unrooted with superSU.
So what I did was re-rooted device using odin and install triangle away. I ran the exact same things as before by disabling SuperSU in triangle away and I was back to the official rom and no flash count. I then disabled superSU in manage applications and removed any notifications (force stop).
My phone was able to download the update as it recognized the stock rom, but then when I attempted to install it my phone it did its normal reboot for install and said install failed custom binary etc. Checked and again I had a 1 flash counter.
Possibly where I messed up?
Things I can gather or maybe I’m wrong. I downloaded stock image from Samsung. It was a TAR file. It is a 4.1 file. In addition I know it was for the T889 for T-mobile. Is there a possibility that this is the wrong file? Is there something else I should be flashing to phone with the PDA in any of other slots? Recovery file? Why when I attempt to run superSU unroot does it add a flash counter?
I do not have my original stock image. Phone T889 T-Mobile.
I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!

RSVRMAN1 said:
...I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!
Click to expand...
Click to collapse
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does

dwitherell said:
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does
Click to expand...
Click to collapse
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!

RSVRMAN1 said:
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!
Click to expand...
Click to collapse
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.

dwitherell said:
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.
Click to expand...
Click to collapse
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.

RSVRMAN1 said:
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.
Click to expand...
Click to collapse
I should clarify the factory images are from note2root DOT com

Going to keep trying to reflash: Just did it again and still keep getting a binary account right after I complete the Full unroot.
Why does it go from official to custom after this last step?
Following Chainfire
If you want to unroot for some reason :
From stock rom and root by Chainfire method all you need to do : Triangle Away app ,SuperSU / setting/ full unroot. Reboot into Recovery / Factory reset.
From custom rom : reflash stock image via Odin .reroot by CF auto root,reset counter with Triangle Away App,SuperSU/Setting/Full unroot . Recovery / Factory reset.
Can find stock firmware from here
Stock T889UVALJ1 & T889UVALK8 (Post 51) http://forum.xda-developers.com/show....php?t=1969551 ( Thank , TeshXX)
Stock + root http://forum.xda-developers.com/show....php?t=1975560 ( Thank , Mr.Robinson )

Tried a different stock firmware 4.1.2 T889 and now wont recognize T-mobile. Anyone have a link to the exact T889 stock firmware that I can just odin-install
Then triangle away/supersu reset and get OTA?
Really would like to get this working. Any help is greatly appreciated.

Try Mr Robinson,
http://forum.xda-developers.com/showthread.php?t=1975560
Sent from my SGH-T889 using xda app-developers app

[ROM][4.3][Dec-2013] AT&T I317-UCUBMK6/MJ4 *Stock* Rooted Odex/De-Odex/Odin

** 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=&quot]
[/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!