I had previously tripped Knox.
So I updated to NAB using this method: http://forum.xda-developers.com/showthread.php?t=2657447
Everything worked like a charm.
Knox was reset to 0x0!
Did anyone else have this experience?
toviaheli said:
I had previously tripped Knox.
So I updated to NAB using this method: http://forum.xda-developers.com/showthread.php?t=2657447
Everything worked like a charm.
Knox was reset to 0x0!
Did anyone else have this experience?
Click to expand...
Click to collapse
Are you sure you had 0x0? Did you just rooted or Custom recovery?
slow_one said:
Are you sure you had 0x0? Did you just rooted or Custom recovery?
Click to expand...
Click to collapse
Absolutely certain I had 0x0 after flashing using that method.
Prior to manually updating I had Knox 0x1
I Rooted and Custom TWRP.
I followed EVERY step in that step-by-step. With ONE exception, I mistakenly flashed the Engineering Bootloader BEFORE following that tutorial.
toviaheli said:
Absolutely certain I had 0x0 after flashing using that method.
Prior to manually updating I had Knox 0x1
I Rooted and Custom TWRP.
I followed EVERY step in that step-by-step. With ONE exception, I mistakenly flashed the Engineering Bootloader BEFORE following that tutorial.
Click to expand...
Click to collapse
but how did you trip the Knox the 1st time?
slow_one said:
but how did you trip the Knox the 1st time?
Click to expand...
Click to collapse
The first day I had the Note 3 I tipped Knox when I rooted and flashed recovery,
Well if you could list what firmware you came from? What bootloader you had previously etc etc
It may help Developers with the fight against knox
Sent from my SM-N9005 using xda app-developers app
st3chn0 said:
Well if you could list what firmware you came from? What bootloader you had previously etc etc
It may help Developers with the fight against knox
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
I was on MJ4 running the MJ4 Engineering bootloader.
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
As far as I know there is no MJ4 engineering bootloader. The engineering bootloader is NA4 which is the first kit kat leak and the bootloader is is unlocked.
Sent from my SM-N900P using Tapatalk
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
You mean this http://forum.xda-developers.com/showthread.php?t=2655674 ??
Walter.White said:
You mean this http://forum.xda-developers.com/showthread.php?t=2655674 ??
Click to expand...
Click to collapse
I think what freeza did is morph the NA4 engineering with the NAB bootloader thus creating a daily usable NAB bootloader.
Sent from my SM-N900P using Tapatalk
JonSCSL said:
I think what freeza did is morph the NA4 engineering with the NAB bootloader thus creating a daily usable NAB bootloader.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm not so certain. I believe that unlocked bootloader was obtained the old-fashioned way, by it landing in the right hands. If what you've suggested were true, then why release it as unique? The OP of that thread makes it pretty clear that it's a very nice item to have and we won't know if another is coming.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I'm not so certain. I believe that unlocked bootloader was obtained the old-fashioned way, by it landing in the right hands. If what you've suggested were true, then why release it as unique? The OP of that thread makes it pretty clear that it's a very nice item to have and we won't know if another is coming.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I thought that the only unlocked bootloader that we had was NA4. Didn't know we had 2 unlocked bootloaders
Sent from my SM-N900P using Tapatalk
toviaheli said:
I was on MJ4 running the MJ4 Engineering bootloader.
Click to expand...
Click to collapse
I just believe it's the fact you have an engineering bootloader..... The bootloader you are now on is that is the engineering one or stock?
Sent from my SM-N9005 using xda app-developers app
st3chn0 said:
I just believe it's the fact you have an engineering bootloader..... The bootloader you are now on is that is the engineering one or stock?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Yes. Right now I am on the Engineering Bootloader for NAB
I was previously on MJ4 Stock Rooted.
I Flashed the NAB Engineering Bootloader
Then I flashed this: http://forum.xda-developers.com/showthread.php?t=2657447
toviaheli said:
Yes. Right now I am on the Engineering Bootloader for NAB
I was previously on MJ4 Stock Rooted.
I Flashed the NAB Engineering Bootloader
Then I flashed this: http://forum.xda-developers.com/showthread.php?t=2657447
Click to expand...
Click to collapse
can you post a screen shot? of the 0x0
kaos420 said:
can you post a screen shot? of the 0x0
Click to expand...
Click to collapse
Make a video
Sent from my SM-N900 using Tapatalk
Okay, so let me see if I have the steps correct on this.
1. You flashed a custom recovery and rooted your device, thereby tripping Knox. Did you use CFAutoroot or Kingo? The recovery would have tripped knox anyways, but just checking for root method.
2. You started with MJ4 or did you upgrade to MJ4 and if you upgraded, was Knox tripped before? (I started with MI3, some had MI5). This is mainly to find out if you tripped Knox before or after MJ4.
3. While on MJ4, you flashed the NAB engineering bootloader.
4. You ran the one-click to update to 4.4.2
If you can clear up points 1 and 2, you could probably turn this into a guide to help others.
evilvoice said:
Okay, so let me see if I have the steps correct on this.
1. You flashed a custom recovery and rooted your device, thereby tripping Knox. Did you use CFAutoroot or Kingo? The recovery would have tripped knox anyways, but just checking for root method.
2. You started with MJ4 or did you upgrade to MJ4 and if you upgraded, was Knox tripped before? (I started with MI3, some had MI5). This is mainly to find out if you tripped Knox before or after MJ4.
3. While on MJ4, you flashed the NAB engineering bootloader.
4. You ran the one-click to update to 4.4.2
If you can clear up points 1 and 2, you could probably turn this into a guide to help others.
Click to expand...
Click to collapse
any updates on this.. ??
procedure..methods..etc/..confirmation
xinfinityoO said:
any updates on this.. ??
procedure..methods..etc/..confirmation
Click to expand...
Click to collapse
I call BS all the way.
Sent from my SM-N900P using XDA Premium 4 mobile app
I think we all got trolled? :/
Related
Thanks for the helpful responses.
For anyone viewing this I was attempting to consolidate my 5 hours of reading into a nutshell.
Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Yes me7 is so far not vulnerable for romming but safestrap is a option soon to be for all me7 users. Big mistake if you wanted a bootloader workaround like loki to have custom recovery. I mean we can't say to claim the device defective as that can be seen as warranty fraud but your actions..
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2
AndroidSlave said:
Thanks for the response. So then nothing can be flashed via Odin aside from a pure stock ME7 ROM?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep thats all that can be flashed in odin. On the s3 you could flash custom recovery via odin but that required an unlocked bootloader.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Can we still root with the software update mj4 or do we have to wait on a new root file.
Sent from my NOTE 3 using Tapatalk
stevenb691 said:
Can we still root with the software update mj4 or do we have to wait on a new root file.
Sent from my NOTE 3 using Tapatalk
Click to expand...
Click to collapse
1. Take the update after flashing back to stock to get it
2. Download and Save to phone either stock rooted ROM or or any other rooted ROM
3. Odin TWRP, when it reboots hold volume up/home to boot into recovery
4. Wipe and flash rooted ROM
This is how I did it and works well. If your trying to keep the knox flag from tripping this is not the method you wanna use.
Knox safe. http://forum.xda-developers.com/showthread.php?t=2484095
Sent from my SM-N900P using Tapatalk
What if you're Knox flag is already tripped from a previous root will this still work?
Sent from my SM-N900P using XDA Premium 4 mobile app
dunjay said:
What if you're Knox flag is already tripped from a previous root will this still work?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes. Not the KNOX Safe ROOT method though, once you trip the binary counter it is considered permanent.
Kompster said:
Yes. Not the KNOX Safe ROOT method though, once you trip the binary counter it is considered permanent.
Click to expand...
Click to collapse
To clarify. You can still use the knox safe methods if your knox is already flipped. It just won't reset the knox. However if your flipped already you might as well use cf auto and twrp
Sent from my SM-N900P using Tapatalk
I just got my SGN3 today, got the MJ4 update and then odined TWRP 2.6.3.7-hltespr... Working great!!!
I'm not sure if this is the right place for this or not but I came across this method through Google. It worked for my Verizon Note 2 with the OTA 4.3 update. I also used Foxfi until the update. With Titanium Backup, I froze the KNOX security and Foxfi works again without asking to contact VZW. Thanks to the Devs who are responsible for this method. I hope it is ok that I shared the link.
http://forum.xda-developers.com/showthread.php?t=2565758
Works
loonz29 said:
I'm not sure if this is the right place for this or not but I came across this method through Google. It worked for my Verizon Note 2 with the OTA 4.3 update. I also used Foxfi until the update. With Titanium Backup, I froze the KNOX security and Foxfi works again without asking to contact VZW. Thanks to the Devs who are responsible for this method. I hope it is ok that I shared the link.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
I had my phone unrooted and on 4.3, ran the install.bat and it's rooted!
I can confirm as well. Thank you!
Sent from my SCH-I605 using XDA Premium 4 mobile app
Unlocked too?..I heard root is possible, but bootloader unlock is not.
Sent from my SCH-I605 using Tapatalk
Don't know about unlocking the bootloader. I haven't found anything for that yet.
Sent from my SCH-I605 using xda premium
This method also worked for me, however I had to restore back to stock 4.3 with odin first.
Thanks!
Congrats! You successfully perma locked your bootloader by taking the 4.3 OTA.
droidstyle said:
Congrats! You successfully perma locked your bootloader by taking the 4.3 OTA.
Click to expand...
Click to collapse
For those of us who don't care about the bootloader, your statement is moot.
vortmax said:
For those of us who don't care about the bootloader, your statement is moot.
Click to expand...
Click to collapse
This is the case for me. I just needed root for Titanium backup primarily.
At least people will know there is a way to root it. Hopefully one of the devs will figure out how to unlock the new boot loader.
Sent from my SCH-I605 using xda app-developers app
Do I need to downgrade verizon note 2 to 4.1.1 for carrir unlock?
b1ackplague said:
I had my phone unrooted and on 4.3, ran the install.bat and it's rooted!
Click to expand...
Click to collapse
Do I need to downgrade verizon note 2 to 4.1.1 for carrier unlock?
Also I have a metro pcs samsung s4 that I need to carrier unlock do u have any idea's?
wirelessjunkies said:
Do I need to downgrade verizon note 2 to 4.1.1 for carrier unlock?
Also I have a metro pcs samsung s4 that I need to carrier unlock do u have any idea's?
Click to expand...
Click to collapse
I don't think that downgrading is possible without tripping the KNOX security counter. As far as the s4, this root version should root the phone, and I believe that I have read somewhere about a safestrap app thst allows you to flash roms and such.
Sent from my SCH-I605 using xda premium
I have had no success with this method as yet. I run the script, and it seems to run fine, then after it's rebooted, when it says to run SuperSU, and let it update if it asks, the update always fails. Has anyone else experienced this problem? Found a way around it?
wirelessjunkies said:
Do I need to downgrade verizon note 2 to 4.1.1 for carrier unlock?
Also I have a metro pcs samsung s4 that I need to carrier unlock do u have any idea's?
Click to expand...
Click to collapse
This phone is global unlocked hence you don't need to downgrade to 4.1.1....let me know the purpose so that v can suggest
Sent from my SCH-I605 using XDA Premium 4 mobile app
Awesomesauce!!
Just got it to work. thanks !!
Darmelc said:
Just got it to work. thanks !!
Click to expand...
Click to collapse
Did you have to downgrade it to make it work?
Sent from my SCH-I605 using Tapatalk
cpomike13 said:
Did you have to downgrade it to make it work?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I did not have to downgrade to make it work.
Sonofabitch it worked...I bought my Note 2 cash, JUST after it had received the 4.3 update (sigh) I understand about the no bootloader thing, but being able to use Titanium Backup again is awesome
so i downloaded the update today, tried using kingo but it failed, i can confirm that rooting with chainfire auto root works just perfect on the new ota update.....here is the link to download it
http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I used chainfire auto-root for 4.3, using ODIN, can I still use this? how?
Sent from my iPad using Tapatalk
Thanks for the link, unrooted my phone Monday to be able to get the update and I've hated my phone since then. Took the update last night and need to root again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Well this trip Knox?
Lukaslukasm said:
Well this trip Knox?
Click to expand...
Click to collapse
yes
I'm on 4.3 and rooted with Kingo but showing official with Wanam Xposed. Do I need to undo that and go back to stock in order to get the update?
Thus version works for all variats?
veeeyesee said:
so i downloaded the update today, tried using kingo but it failed, i can confirm that rooting with chainfire auto root works just perfect on the new ota update.....here is the link to download it
http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
OUr sprint phones are smn-900p not smn-9005? so your saying the above zip worked on your sprint phone?
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
JimSmith94 said:
I'm on 4.3 and rooted with Kingo but showing official with Wanam Xposed. Do I need to undo that and go back to stock in order to get the update?
Click to expand...
Click to collapse
You wont be able to install the frimware unless your device status reads official ( menu- setting- about phone- status ). So unfortunately you will either have to wait for a modified version of the firmware or revert back to stock with odin tar and then take the OTA update.
Yes smn-9005 is what most of us on NABD (& NAB ) used to root our phones.
Sent from my Coleco ADAM
I can also confirm that the link provided roots the sprint variant of n3
Sent from my SM-N900P using XDA Premium 4 mobile app
thats good to know
boodie said:
Yes smn-9005 is what most of us on NABD (& NAB ) used to root our phones.
Sent from my Coleco ADAM
Click to expand...
Click to collapse
What a relief
---------- Post added at 01:27 PM ---------- Previous post was at 01:24 PM ----------
Beandip-Javier said:
I can also confirm that the link provided roots the sprint variant of n3
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you lose the engineering bootloader?
You can also flash with Odin either philz or twrp. ... Keep in mind this rom will reflash stock recovery. .. so uncheck auto reboot in Odin and boot into twrp or Philz using vol up home and power and flash su zip
This has a kit kat bootloader that as of right now is not ! Not! !!!! Not !!!! Able to Downgrade .... so once you have nab you can't use any 4.3 roms. ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Im on MI5 still
Epix4G said:
You can also flash with Odin either philz or twrp. ... Keep in mind this rom will reflash stock recovery. .. so uncheck auto reboot in Odin and boot into twrp or Philz using vol up home and power and flash su zip
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
0x0 so im still waiting lol
About20ninj45 said:
0x0 so im still waiting lol
Click to expand...
Click to collapse
Same here. I'll wait for Kingo to support KitKat.
Does flashing the unroot tar wipe the device, or at least the apps? I assume that method does not trip Knox 0x0?
hmmm
blognc said:
Same here. I'll wait for Kingo to support KitKat.
Does flashing the unroot tar wipe the device, or at least the apps? I assume that method does not trip Knox 0x0?
Click to expand...
Click to collapse
I would assume not, and i dont think you would trip knox by using a stock tar of your current most up to date firmware,
pbedard said:
Who said that ??
Sent from my SM-N900P using XDA Premium HD app
Click to expand...
Click to collapse
Who said what? ??
I didn't see freezas engineering bootloader but that is still not very easy to get back to 4.3
Sent from my SM-N900P using Xparent BlueTapatalk 2
JimSmith94 said:
I'm on 4.3 and rooted with Kingo but showing official with Wanam Xposed. Do I need to undo that and go back to stock in order to get the update?
Click to expand...
Click to collapse
About20ninj45 said:
You wont be able to install the frimware unless your device status reads official ( menu- setting- about phone- status ). So unfortunately you will either have to wait for a modified version of the firmware or revert back to stock with odin tar and then take the OTA update.
Click to expand...
Click to collapse
As I said, my phone DOES read official, thanks to Wanam Xposed. I don't get any "modified" error message when I look for updates, just "the latest updates have already been installed". Do I need to undo Kingo and Wanam or has the update just not reached the DFW area yet?
Sorry
JimSmith94 said:
As I said, my phone DOES read official, thanks to Wanam Xposed. I don't get any "modified" error message when I look for updates, just "the latest updates have already been installed". Do I need to undo Kingo and Wanam or has the update just not reached the DFW area yet?
Click to expand...
Click to collapse
I misread that, try running the xposed framework disabler, reboot, and try to redownload the software. If you get the message " your device is up to date', then it probably means it hasnt rolled out to your area yet.
I tried this but the phone just boot looped when it said it was booting into recovery after flashing the tar....
Sent from my SM-N900P using XDA Premium 4 mobile app
You used the cf auto root for 9005 .... International note 3
Cause I have used it 3 times and no one else has had any problems with it make sure it's the one for kk
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
You used the cf auto root for 9005 .... International note 3
Cause I have used it 3 times and no one else has had any problems with it make sure it's the one for kk
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I used the one from the first post.... it does its thing then it reboots the phone and it says recovery booting and just boot loops
Sent from my SM-N900P using XDA Premium 4 mobile app
Sent from my SM-N900P using xda app-developers app
This should work if you are stock 4.4.2 (KitKat)
Chainfire's Autoroot.
http://forum.xda-developers.com/showthread.php?t=2656334
Please use this as a starting point to read about what you are going to do.
It's not hard, but you should read up on the procedure before doing it. Regular bootloader (which you probably already have) is sufficient. You shouldn't need the engineering bootloader. I didn't.
Good luck. (Read First, Do second).
If you care, this method will trip the Knox flag to 0x1.
JimSmith94 said:
If you care, this method will trip the Knox flag to 0x1.
Click to expand...
Click to collapse
So the best route to go with out knocking this knox flag to 0x1 would be?
Sent from my SM-N900P using XDA Premium 4 mobile app
johny005 said:
So the best route to go with out knocking this knox flag to 0x1 would be?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'd recommend this method: http://forum.xda-developers.com/showthread.php?t=2658315
JimSmith94 said:
I'd recommend this method: http://forum.xda-developers.com/showthread.php?t=2658315
Click to expand...
Click to collapse
So this just gets you root, no custom recovery which means no custom rom. Can you still flash zips with the stock recovery?
gottria said:
So this just gets you root, no custom recovery which means no custom rom. Can you still flash zips with the stock recovery?
Click to expand...
Click to collapse
Every custom recovery will trip Knox so I haven't installed one. I think you can flash custom ROMs as long as they don't include or require a custom recovery. Yes, you can flash zips with the stock recovery.
JimSmith94 said:
Every custom recovery will trip Knox so I haven't installed one. I think you can flash custom ROMs as long as they don't include or require a custom recovery. Yes, you can flash zips with the stock recovery.
Click to expand...
Click to collapse
Still reading the other thread but this is what I'm questioning from that thread.
JSnively said:
Kingo does not work on KitKat.
Click to expand...
Click to collapse
Correct, that's why you have to Kingo root on MJ4 before going to NAB. Then you'll still be rooted on NAB.
JimSmith94 said:
Correct, that's why you have to Kingo root on MJ4 before going to NAB. Then you'll still be rooted on NAB.
Click to expand...
Click to collapse
Thanks, I was getting confused because the OP asked about rooting on KitKat.
gottria said:
Thanks, I was getting confused because the OP asked about rooting on KitKat.
Click to expand...
Click to collapse
I'm talking about the method in the other thread I linked to. With that method you Kingo root on Jelly Bean 4.3 MJ4 and when you upgrade to KitKat 4.4.2 MAB you're still rooted. It is a workaround until Kingo works on KitKat.
is there a way to obtain root and not trigger Knox?
Sent from my SM-N900P using xda app-developers app
bman55 said:
is there a way to obtain root and not trigger Knox?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
JimSmith94 said:
I'd recommend this method: http://forum.xda-developers.com/showthread.php?t=2658315
Click to expand...
Click to collapse
:laugh: