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:
Related
Does this mean that it is safe to update to me7 and then root per the instructions?
When I look at the software update choice on the phone it says that settings failed??
pego99 said:
Does this mean that it is safe to update to me7 and then root per the instructions?
When I look at the software update choice on the phone it says that settings failed??
Click to expand...
Click to collapse
Not only, NO! But HELL NO! If you're on MDK do not take update to ME7. You can, however, flash roms based upon ME7 - - like Hyperdrive.
Sent from my SCH-I545 using Tapatalk 4
wtherrell said:
Not only, NO! But HELL NO! If you're on MDK do not take update to ME7. You can, however, flash roms based upon ME7 - - like Hyperdrive.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
pego99 said:
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
Click to expand...
Click to collapse
Because ME7 has a locked bootloader
Luke
pego99 said:
I did and the root worked. Why was this a bad idea? I want to be able to move apps to the external SD card.
Click to expand...
Click to collapse
Now, you cannot flash a custom recovery nor custom roms. I hope you gain much by moving perhaps a gig of apps to your SD card - - you have paid a very high price to do so. Now your only option for custom roms is safestrap. I wish you the best of luck.
Sent from my SCH-I545 using Tapatalk 4
I will not be running other Roms. Just would like a nandroid backup. Is safestrap safe for this?
Sent from my SCH-I545 using Tapatalk 2
Look at the general questions area.... I think somebody talks about ss and nandroid... they said that it can backup roms, but not stock.
This sounds plausible because HashCode, the SS Dev, said that he bas to work more on SS before you can do anything with stock rom... even backup
Sent from my SCH-I545 using xda app-developers app
lukesdiesel said:
Because ME7 has a locked bootloader
Luke
Click to expand...
Click to collapse
Wrong, VZW never had an unlocked bootloader...both MDK and ME7 are locked.
Why are so many people misinformed?
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
Wrong, VZW never had an unlocked bootloader...both MDK and ME7 are locked.
Why are so many people misinformed?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Because people think as long as they can flash ROMs, it's unlocked. You and I know it's only a workaround, but most users don't.
I'd much rather have to use Loki than SS, as cool as SS sounds.
Sent from my SCH-I545 using Tapatalk 4
I'm a long time lurker and I use the search function for everything. Can't seem to find what I need.
I have a rooted me7 with safe strap..
I'd like to know what proper steps to take to got to mj7,which I believe is the last update.
Any information is much appreciated thank you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
dsmendiola said:
I'm a long time lurker and I use the search function for everything. Can't seem to find what I need.
I have a rooted me7 with safe strap..
I'd like to know what proper steps to take to got to mj7,which I believe is the last update.
Any information is much appreciated thank you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Remove safestrap using the directions in the Safestrap thread (http://forum.xda-developers.com/showthread.php?t=2441441)
Then follow the "Update to VRUEMJ7 and Keep Root" thread (http://forum.xda-developers.com/showthread.php?t=2504408)
dsmendiola said:
I'm a long time lurker and I use the search function for everything. Can't seem to find what I need.
I have a rooted me7 with safe strap..
I'd like to know what proper steps to take to got to mj7,which I believe is the last update.
Any information is much appreciated thank you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't do it.
Get something that you can flash based on the newer firmware.
If you have safestrap and you like the ability, don't update to MJ7.
k1mu said:
Remove safestrap using the directions in the Safestrap thread (http://forum.xda-developers.com/showthread.php?t=2441441)
Then follow the "Update to VRUEMJ7 and Keep Root" thread (http://forum.xda-developers.com/showthread.php?t=2504408)
Click to expand...
Click to collapse
Thank you! Much appreciated.
Sent from my SCH-I545 using XDA Premium 4 mobile app
tech_head said:
Don't do it.
Get something that you can flash based on the newer firmware.
If you have safestrap and you like the ability, don't update to MJ7.
Click to expand...
Click to collapse
I did enjoy the ability, but then I started messing with xposed framework and noticed those tweaks are what I cared for. Touchwiz doesn't bother me and with the touchwiz tweaks it makes it similar to custom rom.
I do however will only go to mj7 if there is root method, which I've read there is..
Thanks for your input.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Yea, but the root is an installer from China......
Sent from my SCH-I545 using Tapatalk
tech_head said:
Yea, but the root is an installer from China......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No, using that method to retain root through the OTA does not use Vroot. I used that method successfully and am on mj7 and have root.
No Chinese stuff
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
No, using that method to retain root through the OTA does not use Vroot. I used that method successfully and am on mj7 and have root.
No Chinese stuff
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
You can keep root through the upgrade.
What happens if you need to flash your device??????
THen you need vRoot.
I'm just saying, I won't move to a new OTA unless there is a reliable root method.
With my luck something goes south and I need to re-root after a flash.
tech_head said:
You can keep root through the upgrade.
What happens if you need to flash your device??????
THen you need vRoot.
I'm just saying, I won't move to a new OTA unless there is a reliable root method.
With my luck something goes south and I need to re-root after a flash.
Click to expand...
Click to collapse
Yes if you were on one of the previous basebands you could take the mj7 OTA and keep root. Like shown here : http://forum.xda-developers.com/showthread.php?t=2504408
And yea.. As soon as you're on mj7 you're stuck there, no going back. If you had to flash mj7 for some reason after all that, then you would be left with the choice of using those Chinese root methods. But that guide that was already mentioned above by another poster worked prefect for me.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
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
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? :/
Ive been out of the loop for a while and was wondering if it is possible. If so how? Thanks for the help!
Sent from my SCH-I545 using XDA Premium 4 mobile app
chicagows said:
Ive been out of the loop for a while and was wondering if it is possible. If so how? Thanks for the help!
Click to expand...
Click to collapse
This question belongs here: http://forum.xda-developers.com/showthread.php?t=2406222 (the HD Q&A thread).
chicagows said:
Ive been out of the loop for a while and was wondering if it is possible. If so how? Thanks for the help!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wonder if what is possible?
decaturbob said:
wonder if what is possible?
Click to expand...
Click to collapse
Install HD16 on Stock NC5.
k1mu said:
Install HD16 on Stock NC5.
Click to expand...
Click to collapse
if that can be figured out but I think you be a hero. Root is needed somehow
decaturbob said:
if that can be figured out but I think you be a hero. Root is needed somehow
Click to expand...
Click to collapse
If you want a pre-rooted stock KK Surge has a method in place. This approach allows for SS Recovery.
http://forum.xda-developers.com/showthread.php?t=2726868
If all you are looking for is Stock VZW 4.2.2 perform via Odin wipe or no wipe methods. This approach will kill root and SS Recovery.
http://forum.xda-developers.com/showthread.php?t=2735172