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
Related
These are root injected FACTORY Stock Odin Flashable Images. You flash them 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.
Big thanks to my one beta tester stevessvt as I don't own this device and he requested this and then tested a few of my broken tries before this one worked.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet. Also helpful if you flashed other ROMs or kernels and just want to get back to a good base to start from, this is all stock but will still leave you with root to easily move forward.
You can get ODIN here
and the drivers for the SGH-T889 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.
MCT: Mobilicity
GLW: Wind
VTR: Videotron
Instructions:
First, Download Image:
Tmobile Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror 1: root66_TMO_T889UVUCMK7_2.7z
JellyBean Release 4.1.2 (June 2013)
Mirror 1: root66_TMO_T889UVBMD1.7z
JellyBean Release 4.1.2 (March 2013)
Mirror 1: root66_TMO_T889UVBMB4.7z
JellyBean Release 4.1.1 (January 2013)
Mirror 1: root66_TMO_T889UVALL4.7z
Mobilicity Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_MCT_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_MCT_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_MCT_T889VVLALJ4.7z
Wind Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_GLW_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_GLW_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_GLW_T889VVLALJ4.7z
Videotron Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_VTR_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_VTR_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_VTR_T889VVLALJ4.7z
Second, Extract and Flash:
Extract the root66_TMO_T889UVALJ1.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_TMO_T889UVALJ1.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/openrecovery-twrp-2.3.3.2-t0ltetmo.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.
Bonus Downloads:
CWM Flashable Modem: modem_CWM_T889UVALK8.zip || modem_CWM_T889UVALL4.zip || modem_CWM_T889UVBLL4.zip
ODIN Flashable Stock Recovery: TMO_recovery_T889UVALK8.tar.md5 || TMO_recovery_T889UVALL4.tar.md5 || TMO_recovery_T889UVBMB4.tar.md5 || TMO_recovery_T889UVBMD1.tar.md5
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 the T-mobile 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 UVALJ1 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 guinea pigged this fine piece of rooted software. It's perfect. System status reports Normal. No tripping flash counter at all. I was bone stock, never rooted yet until now.
Need some help please
Very new to this but willing to take the dive.
If I follow this procedure I will have a Factory (Stock) N7105 phone without all of the T-Mobile bloatware???
Thanks.
Does this have unsecured boot.img ?
No...the is bone stock TMo t899uvalj1, it just happens to be rooted already. Complete with all the pre installed bloat like stock. It won't trip th flash counter though and your status says normal, not modified.
Some have had issues resetting the flash counter because of it being modified. Anyone able to confirm that with this + flash reset counter will make it 0?
I suppose I could be the guinea pig..... will report back!
Edit: I would like to confirm that this.... WORKS! Flash counter shows 0 after it was stuck at 1 for me.
teshxx said:
Does this have unsecured boot.img ?
Click to expand...
Click to collapse
From mrRobinson:
nope. only system image is all that was modified with the two files (su and superuser.apk)
thanks so much for this!
I've used this on the sgs3 and felt so secure knowing that i just need to uninstall su and i can walk into a T-Mobile store and return it.
one question, can i manually write any recovery without tripping the counter like on the sgs3, or is the note 2 different in the way it detects a trip?
konceptz said:
thanks so much for this!
I've used this on the sgs3 and felt so secure knowing that i just need to uninstall su and i can walk into a T-Mobile store and return it.
one question, can i manually write any recovery without tripping the counter like on the sgs3, or is the note 2 different in the way it detects a trip?
Click to expand...
Click to collapse
Without the device I'm not clear on that myself. It seems that once a non stock recovery is there the device either won't allow a reset ot increments the counter.
Added recovery section to OP. Would be curious to see if installing a custom recovery that way after rooting with this method trips the counter or still prevents it from being reset. Anyone willing to try and report?
mrRobinson said:
Added recovery section to OP. Would be curious to see if installing a custom recovery that way after rooting with this method trips the counter or still prevents it from being reset. Anyone willing to try and report?
Click to expand...
Click to collapse
I will, since i had to replace my phone. The micro usb port wouldnt charge or connect to pc. Edit: Still says modified
deeznutz1977 said:
I will, since i had to replace my phone. The micro usb port wouldnt charge or connect to pc. Edit: Still says modified
Click to expand...
Click to collapse
I dont mind that. In download mode is the counter tripped? Modified status will happen with busy box even. And if you flash pure stock it'll go away. I'm more concerned with the download mode counter.
mrRobinson said:
I dont mind that. In download mode is the counter tripped? Modified status will happen with busy box even. And if you flash pure stock it'll go away. I'm more concerned with the download mode counter.
Click to expand...
Click to collapse
yup 1
deeznutz1977 said:
yup 1
Click to expand...
Click to collapse
And can you reset it with the app or will it stay at 1 now that it sees a non stock recovery?
Any ideas on how to flash this using heimdall or adb on OS X?
mrRobinson said:
And can you reset it with the app or will it stay at 1 now that it sees a non stock recovery?
Click to expand...
Click to collapse
zero
deeznutz1977 said:
zero
Click to expand...
Click to collapse
so when you put the recovery on there it went to 1. then you reset it to 0 with the app and it is staying at zero across reboots?
didn't someone mention they the counter wouldn't go to zero for them when they rooted the other method?
Only if they have any recovery other than stock.
MOONSSPOON said:
Any ideas on how to flash this using heimdall or adb on OS X?
Click to expand...
Click to collapse
Though I haven't tested it, I'm not sure why Odin through virtualization wouldn't work.
Odin works differently than adb, but I'm not sure about heimdall.
I flashed this last night. It worked perfectly. THANK YOU!
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.
Hi,
I recently bought the Samsung Galaxy S3 on T-Mobile, to replace my Motorola Droid X on Verizon. Love the new phone, but miss my root capabilities - aka there's a bunch of bloat. There's an OTA not being forced for 4.1.1, but when I tried to root that, I soft bricked and got stuck in a boot loop at the pulsing Samsung. I grabbed ODIN and was able to push the stock 4.0.4 back into it and get it working again, baseband T999UVLH2, Kernel 3.0.8-925100, build IMM76D.T999UVALH2. Is there a way to root this phone, or a stock rooted ROM I could push up with ODIN?
I'm not looking to load custom ROM's, just have some of the abilities I had on my DX when it was rooted and get rid of some of the stock crap that I don't need.
I originally tried to do this with Samsung Galaxy S3 Toolkit v6.0, and soft bricked the phone. I followed the directions online, and did it as instructed, but yeah. Any help would be greatly appreciated.
All you need to root is the touch 6.0 clockwork mod recovery tar file which is available on xda as zip file and the odin version 3+ and follow instructions thats all thats needed to root, make sure you also put the superuser app inside the root of your sd card meaning connect your galaxy s3 to computer then open the root sd card and put it inside there, i believe there is a clockwordmod touch that already comes with superuser so you may not have to worry about putting superuser in root. here i'll grab links for you now. u dont checkmark anything on odin except select pda and browse for the tar file. Here is guide for your device with download links.
The clockworkmod touch recovery version is by far best and always works well with almost all roms.
I would also recomend you use liquidsmooth rom or if you want to test out the new android 4.2 cm but camera doesn't work on 4.2 cm10.1 now however it's a very nice custom rom
Btw, make sure you flash the superuser.zip file that you placed in your sd card while you are in clockwork mod recovery otherwise you wont comlete the root. to get into cwm you gotta hold volume up home button and power button at same time.
http://www.theandroidsoul.com/how-to-install-cwm-touch-recovery-6-0-for-t-mobile-galaxy-s3/
Or even easier you can go here:
http://forum.xda-developers.com/showthread.php?t=1949687
[Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates!
Just flash the root66 udljva file and it is just pure stock prerooted. Just follow the doc's instructions and all will be good.
Sent from my galaxy nexus using Tapatalk 2
rawdaddymagraden said:
Or even easier you can go here:
http://forum.xda-developers.com/showthread.php?t=1949687
[Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates!
Just flash the root66 udljva file and it is just pure stock prerooted. Just follow the doc's instructions and all will be good.
Sent from my galaxy nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks to both of you, I'm rooted, exactly the way I wanted to be. I couldn't get CWM to flash in stock recovery, nor could I get Root66 to flash in recovery, so I just pushed it with Odin. All I need to do now is get CWM Touch on it, and I'll be set. I'm reinstalling my root apps as we speak.
Thanks again!
Odin cf auto root is the quickest and simplest.
seattlestexan said:
Thanks to both of you, I'm rooted, exactly the way I wanted to be. I couldn't get CWM to flash in stock recovery, nor could I get Root66 to flash in recovery, so I just pushed it with Odin. All I need to do now is get CWM Touch on it, and I'll be set. I'm reinstalling my root apps as we speak.
Thanks again!
Click to expand...
Click to collapse
Flash cwm via Odin uncheck auto reboot. Then go straight to recovery then reboot. I'd wipe cache and dalvik while in there though.
http://forum.xda-developers.com/showthread.php?t=1809307
[RECOVERY]TWRP 2.3.1.0 touch recovery [2012-10-15]
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
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!
calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T using XDA Free mobile app