Related
This has been replaced by Universal Root de la Vega!
Question & Answer
"Root de la Vega" What kind of name is that?
It's named after Ralph de la Vega, CEO of AT&T Mobility.
Can I flash custom recovery/kernel/rom without tripping KNOX flags?
No, Flashing a custom ROM will trip the flag
No, Flashing a custom Kernel will trip the flag
No, Flashing a custom Recovery will trip the flag
Will this set a tripped KNOX flag 0x1 back to 0x0?
No.
Can you help me with the drivers?
No, but you can head over here for help with drivers.
How do I get into download mode?
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
Will rooting or downgrading or flashing stock trip the Knox flags?
No, KNOX flags will not be tripped!
Will root survive a factory reset?
Yes, it does.
Will root survive an OTA update?
The Sprint Note 3 has survived an OTA update, you only need to perform the sdcard steps again to get root. However, you should NOT take OTA updates, it is possible for them to patch the root method with an OTA update.
Do I need have to fully wipe my phone when rooting?
Yes. If you don't you will get lots of nasty force closes. I have yet to find a way around it.
Does Xposed Framework work?
Yes, it has been updated to work fully with the Note 3.
Will rooting report system as custom and display an unlocked lock on the initial boot screen?
Yes. It can be removed by installing Xposed Framework with Wanam Xposed and enabling Security hacks > Fake system status.
Titanium Backup is giving me problems, how can I fix it?
Check out this thread. If you are still having issues, please take your concerns to the dev, they are not related to rooting.
How do I open a 7z file?
With 7zip or IZArc!
Can I do this on OS X/Linux?
No, not until heimdall is updated to support the Note 3.
Can I unroot?
Yes, use SuperSU full unroot option or flash stock.
I am getting a "Prevention Information" popup after running a root app, how do I disable it?
From terminal emulator or adb shell as root, run; pm disable com.sec.knox.seandroid
Or freeze the Knox apps with Titanium Backup.
I am getting Force Closes after flashing, how can I fix it?
Make sure you are flashing the CSC file! If you are, try flashing AP and CSC separately.
Good stuff. did this yesterday and it worked like a charm.
Thank you so much!
just to confirm, i can remove/freeze system apps, run ad blocker, xposed, etc, with just root, right? I have never not fully "unlocked" a device and just stayed with the stock ROM. So just want to confirm before using this. And thanks btw for your hard work on this.
And one last one...Im pretty sure I wont be able to get OTA's so how would one go about updating once an OTA has been released without tripping knox?
EDIT: I just saw the 2nd post with all the FAQ...some reason it didnt show before until after I posted. But still wondering about the OTAs
droidkevlar said:
just to confirm, i can remove/freeze system apps, run ad blocker, xposed, etc, with just root, right? I have never not fully "unlocked" a device and just stayed with the stock ROM. So just want to confirm before using this. And thanks btw for your hard work on this.
And one last one...Im pretty sure I wont be able to get OTA's so how would one go about updating once an OTA has been released without tripping knox?
Click to expand...
Click to collapse
You can do all of that fun stuff with root
I am unsure on the OTAs, haven't had any roll out yet.
I can also confirm, worked like a charm. Did it today, and didn't lose any data. Phone was how it was pre root, but with added SU goodness.
Sent from my Psion 5mx
Hey designgears,
Nice to see you're still at it. Your old Cognition ROM (eclair iirc) was one of the first ROMs I ran on my SGS1 Captivate, years ago, before I settled on CyanogenMod. Didn't see you in SGS3-land, but here you are again with the Note3. Hey-ohhhh.
Thanks.
Rooted through this method today. It worked like a charm. Now my Note 3 feels invincible. Thank you!
Sent from my SM-N900T using xda app-developers app
Ok. Here we go. I've been on android for a long time and never heard of KNOX. What the hell is this and do we need it?
Sent from my XT1056 using Tapatalk now Free
EDIT: I forgot--Google is my friend. Nvm
I'm sorry if this is too off topic but, while it IS wonderful to have a root method like this and I'm VERY grateful for it, most of what I read online states that a custom recovery will mess with knox and cause issues. I dint know if I could keep an android phone and not flash custom roms! I'm still within my return window with t mobile (I'm coming from Sprint) and I'm actually thinking about trading for a nexus 4. Hope we get a functioning recovery soon!
Sent from my XT1056 using Tapatalk now Free
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
hdad2 said:
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
Click to expand...
Click to collapse
Same thing
Sent from my SM-N900T using xda app-developers app
hdad2 said:
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
Click to expand...
Click to collapse
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
jimmydigital00 said:
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
Click to expand...
Click to collapse
+1
Sent from my SM-N900T using XDA Premium 4 mobile app
jimmydigital00 said:
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
Click to expand...
Click to collapse
No need to root again, I just separated the two files.
This worked like a charm. Thanks DG!
Sent from my SM-N900T using XDA Premium 4 mobile app
Finall got all files downloaded gonna flash tomorrow after work Thank you so very much designgears, chainfire and all testers for the hard work that brought us root to the G-Note 3 you guys snd XDA are unstoppable!!!
:thumbup:
Sent from my SGH-T889 using XDA Premium 4 mobile app
Works perfectly. Donated!
I can also confirm that if you bork stuff while rooted, you can Odin the stock rom over everything and start over without throwing the Knox flag.
I know that flashing a custom recovery or custom ROM will trip the KNOX counter...BUT...
1. is it possible to adb sideload (after Root de la Vega)?
and...
2. if you CAN adb push and pull, can we pull the framework-res.apk, modify it to our liking and push it back...or will this be the same as flashing a custom ROM which will trip KNOX?
I am curious because I'd like to enable unlimited wifi tethering like I did on my old Galaxy S III by creating a flashable zip (however with Note 3 I wouldn't make it flashable, just push)
Thanks for your work putting this together.
It was real easy to do, and root certainly is appealing. One thing I need is device-level encryption, and that is so far unavailable on a rooted N3.
I've even tried Xposed Framework with Wanam Xposed, and checked System status via TriangleAway:
Counter = 0
Binary = Official
System = Official
But somehow device still won't encryp. Back to stock I go (a 3rd time)...
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to research back to a 0x0.
I used Oden to apply the Chainfire root. After rebooting, Knox told me it prevented an unauthorized app from accessing secure area of the phone. Then SuperSU FC'ed. I went to play, updated it SuperSU, and opened it. After a brief pause, it asked "Do you want to disable Knox?". I pondered that question intently, and in about 10ms, answered OF COURSE! It the successfully disabled knox.
After, go into the play store, and download "Rom Manager". Open it up, and click on the first tab. "Recovery Setup" (Even if it says that you already have CWM recovery installed, still do these steps) After clicking on that tab, on the list "Install or Update recovery" Click on ClockwordMod Recovery. Then click on our device name. A box will pop up suggesting you have Wi-Fi (If you're not already on it), just click OK. And then it'll automatically download it and flash it. There you go.
Sorry if this has already been posted. People might think that there is a different way to root 4.3, just here to help.
Took part of this from erkme73
Thanks .. worked like a charm
Thanks a lot. This method worked for me and very quickly! Thanks!
Thnaks for testing this out. This method worked for me. I had the old CFautoroot before and it didn't work for me, so after downloading the CFautoroot that's specifically for t-mo version, this worked for me.
I didn't even have to go and download a custom recovery. I managed to have the stock recovery on.
Previous to 4.3 I flashed Robinson's stock root-injected 4.1.2 rom. Would this method work for me? And can I skip the CWM recovery part?
ungraph said:
Previous to 4.3 I flashed Robinson's stock root-injected 4.1.2 rom. Would this method work for me? And can I skip the CWM recovery part?
Click to expand...
Click to collapse
If you use ODIN to flash the 4.3 stock, then you'll lose root, and then you'll have to do this method to get root back. You already have root. Wait until Mr. R puts out the root injected 4.3 so you won't lose your root.
nmw407 said:
If you use ODIN to flash the 4.3 stock, then you'll lose root, and then you'll have to do this method to get root back. You already have root. Wait until Mr. R puts out the root injected 4.3 so you won't lose your root.
Click to expand...
Click to collapse
I flashed Robinson's stock root-injected 4.1.2 via Odin and I installed the 4.3 update via Kies yesterday so I lost root. I was wondering if this method would work for me.
It worked for me through ODIN. My mistake was using the old CFautoroot that was for the note 2 international. Once I used the one for t-mo, it all worked exactly as the OP stated - I stopped before the recovery installation since I didn't need TWRP or CWM
is it possible to be rooted and still use knox?
nmw407 said:
It worked for me through ODIN. My mistake was using the old CFautoroot that was for the note 2 international. Once I used the one for t-mo, it all worked exactly as the OP stated - I stopped before the recovery installation since I didn't need TWRP or CWM
Click to expand...
Click to collapse
Just did exactly what you said and it works! I gained root on stock 4.3.
bones718 said:
is it possible to be rooted and still use knox?
Click to expand...
Click to collapse
From what I have seen with my phone NO... But hey still very early. The root method here is great. I found that I had to also uninstall Knox completly with TiBu and seems to hold. I found booting back into recovery even with Knox on Freeze it still would interfere ... Just my limited experience speaking here also.
Thanks again for the root method. Seems 4.3 is pretty smooth, I installed exposed and Wanam and all is good, Also flashed Devil Kernel and good good so far.:victory:
youStolemylaptop said:
There you go.
Sorry if this has already been posted. People might think that there is a different way to root 4.3, just here to help.
Took part of this from erkme73
Click to expand...
Click to collapse
Worked like a charm. Thanks for posting the steps!
This method works but i did a master reset to start "fresh" after rooting and i got on the Tmobile 4g lte screen loop.
Any ideas?
lmarranzino said:
From what I have seen with my phone NO... But hey still very early. The root method here is great. I found that I had to also uninstall Knox completly with TiBu and seems to hold. I found booting back into recovery even with Knox on Freeze it still would interfere ... Just my limited experience speaking here also.
Thanks again for the root method. Seems 4.3 is pretty smooth, I installed exposed and Wanam and all is good, Also flashed Devil Kernel and good good so far.:victory:
Click to expand...
Click to collapse
What do you meant by interfere?
DKM119 said:
This method works but i did a master reset to start "fresh" after rooting and i got on the Tmobile 4g lte screen loop.
Any ideas?
What do you meant by interfere?
Click to expand...
Click to collapse
Mine hung on that screen for longer than I wanted (started getting nervous) but eventually the phone finished loading up
Sent from my SGH-T889 using xda app-developers app
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to revert back to a 0x0. This means you can't downgrade your firmware and if you try, even via Odin, it wouldn't let you and lock your phone. Just a heads up. OP shouldve posted this in the post but if you don't mind flashing custom rooms etc, then by all means go ahead.
ungraph said:
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to research back to a 0x0. This means you can't downgrade your firmware and if you try, even via Odin, it wouldn't let you and lock your phone. Just a heads up. OP shouldve posted this in the post but if you don't mind flashing custom rooms etc, then by all means go ahead.
Click to expand...
Click to collapse
I'll edit it in right now to let everyone know.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
it's work on my NOTE2
Thanks
I thank the OP for updating the post to reflect the Knox issue... but I think anyone with a Note 2 should have already been aware of such issues when rooting. Even if they weren't around for the "modified/binary count/triangle away" disscussions... those that did root, still had to deal with those issue and heard all about them... and now that we've headed towards that next phase of OTA's... it's hard to think anyone has not seen/heard/read something on Knox itself... I can hardly go 5 topics without seeing something related to Knox posted within the first 2 pages... I commend the OP for updating... but how can people be so careless with a phone that cost $400-700. Especially when the first rule of xda is "read first" followed by rule two "at your own risk"
Ultimately, I tripped out about the whole "modified status won't allow OTA's / void warranty" at first and in the end it was patched... I hope for everyone's sake, this gets the same solution... like Coug, I'm holding out for the moment, but I do have faith
Sent from my SGH-T889 using xda app-developers app
PhxDroid86 said:
I thank the OP for updating the post to reflect the Knox issue... but I think anyone with a Note 2 should have already been aware of such issues when rooting. Even if they weren't around for the "modified/binary count/triangle away" disscussions... those that did root, still had to deal with those issue and heard all about them... and now that we've headed towards that next phase of OTA's... it's hard to think anyone has not seen/heard/read something on Knox itself... I can hardly go 5 topics without seeing something related to Knox posted within the first 2 pages... I commend the OP for updating... but how can people be so careless with a phone that cost $400-700. Especially when the first rule of xda is "read first" followed by rule two "at your own risk"
Ultimately, I tripped out about the whole "modified status won't allow OTA's / void warranty" at first and in the end it was patched... I hope for everyone's sake, this gets the same solution... like Coug, I'm holding out for the moment, but I do have faith
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
In a perfect world this is completely true, but this isn't a prefect world. Most the post I see about Knox is "what is Knox" instead of people searching. That's why we have so many people already bootlooping trying to go back to 4.1. I'm glad the op updated the Knox warranty but because I'm pretty sure there will be some people shocked by theirs being tripped.
On a side not Vroot and kingo will root without messing up the Knox. Just Google them. They were removed from xda because some suspicion of virus, but I didn't have s problem
Sent from my SGH-T889 using xda app-developers app
So if you flash Mr. Robinson's stock root injected update you lose root. He has ripped out knox so if you use this method, you shouldn't have any issues and regain root?
Hi there,
I haven't been updated on rooting and all that jazz in a while, so please excuse my ignorance.
I have a Galaxy S3 (SGH-T999) on 4.1.2. It's stock rooted, but I don't have a custom Recovery or anything on it. I didn't (and don't) want to trip the root counter.
Is there a way to upgrade my phone to 4.3, have root working, and not trip the root counter? (Basically, what I currently have, except on 4.3)
Also, I Googled this new Knox feature I've seen people talk about, it seems like a lot of people here don't like it-- should I not want it on my phone too?
Happy holidays,
-Proxin
The counter is easy enough to reset if still on 4.1.2, so your best bet is to install a custom recovery through odin, then flash docholiday's 4.3 stock deknoxed rom and the new modem, and the at&t kernel for working wifi. This way you can use triangle away to reset the flash counter. If you install 4.3 with 4.3 firmware, you will not be able to root without tripping the knox counter.
Hope this helps
Sent from my GT-N8013 using xda app-developers app
masondoctorjt said:
The counter is easy enough to reset if still on 4.1.2, so your best bet is to install a custom recovery through odin, then flash docholiday's 4.3 stock deknoxed rom and the new modem, and the at&t kernel for working wifi. This way you can use triangle away to reset the flash counter. If you install 4.3 with 4.3 firmware, you will not be able to root without tripping the knox counter.
Hope this helps
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
From what I understood back in the day when I got root, if you installed a custom recovery, you either triggered the counter or lost all your data/wiped the phone. Is that still the case?
Edit: Or was it un-tripping the counter that caused the data to wipe?
If you want 4.3 touchwiz, root, and a warranty, all at the same time, don't take the official update.
Instead, flash the 4.3 ROM zip, 4.3 modem, and a compatible kernel, using twrp or cwm recovery.
If you ever need to odin, do not use any version newer than MD5 or you are stuck with Knox and can never go back.
Sent from my T999L on PACman
Proxin said:
From what I understood back in the day when I got root, if you installed a custom recovery, you either triggered the counter or lost all your data/wiped the phone. Is that still the case?
Edit: Or was it un-tripping the counter that caused the data to wipe?
Click to expand...
Click to collapse
It still triggers the counter, but it can be reset. It did not wipe my data, but backup just in case. Resetting the counter did not wipe data either. But do not update to the official 4.3 if you want to root and still have a warranty.
Sent from my GT-N8013 using xda app-developers app
Uh oh. I searched around for guides on updating like you guys said, and followed the guide here which promised root, 4.3, and no root counter... and now I can't use root, even though I installed a pre-rooted ROM.
I'm on 4.3 now, but don't have the ability to use root. I don't seem to have the Knox thing though.
I don't understand why I don't have root on a rooted ROM... what should I do?
Edit: This is the exact version I used: root66_TMO_T999UVUEMJC.tar.md5
Proxin said:
Uh oh. I searched around for guides on updating like you guys said, and followed the guide here which promised root, 4.3, and no root counter... and now I can't use root, even though I installed a pre-rooted ROM.
I'm on 4.3 now, but don't have the ability to use root. I don't seem to have the Knox thing though.
I don't understand why I don't have root on a rooted ROM... what should I do?
Edit: This is the exact version I used: root66_TMO_T999UVUEMJC.tar.md5
Click to expand...
Click to collapse
To fix root, enable developer options by pressing build number 7 times, then enable root access for apps and adb under dev options.
MJC is TW 4.3 which includes knox. AFAIK the root66 version has knox removed from the rom, but it is impossible to remove it from the bootloader.
Adreaver said:
To fix root, enable developer options by pressing build number 7 times, then enable root access for apps and adb under dev options.
MJC is TW 4.3 which includes knox. AFAIK the root66 version has knox removed from the rom, but it is impossible to remove it from the bootloader.
Click to expand...
Click to collapse
I checked in developer options after pressing the build number 7 times, but I don't see anything about enabling root in there...
Do I have to re-root somehow? If so, will that throw off the counter?
Proxin said:
Uh oh. I searched around for guides on updating like you guys said, and followed the guide here which promised root, 4.3, and no root counter... and now I can't use root, even though I installed a pre-rooted ROM.
I'm on 4.3 now, but don't have the ability to use root. I don't seem to have the Knox thing though.
I don't understand why I don't have root on a rooted ROM... what should I do?
Edit: This is the exact version I used: root66_TMO_T999UVUEMJC.tar.md5
Click to expand...
Click to collapse
That's why posts need read completely. It clearly says it will trip the Knox counter in 4.3 in the second paragraph of the first post under "4.3 notes" sorry that happened though.:banghead: Maybe someday someone will come up with a knox bypass in the bootloader.
Sent from my SGH-T999L using xda app-developers app
masondoctorjt said:
That's why posts need read completely. It clearly says it will trip the Knox counter in 4.3 in the second paragraph of the first post under "4.3 notes" sorry that happened though.:banghead: Maybe someday someone will come up with a knox bypass in the bootloader.
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
I don't understand-- it seems like it says Knox is removed in order for root to stick:
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.
Click to expand...
Click to collapse
I took it to mean root will flag the Knox counter so it has been removed from the images.
The wording is very ambiguous...
I'm pretty close to just nuking my install and starting over with CyanogenMod, not caring if I trip the counter or not. Is it possible to do so with the current setup, or will I end up with a brick/semibrick somehow? I figure I might as well, since rooting will likely trip the counter anyway.
Yes lol
Sent from my SGH-T999 using xda app-developers app
pgarcia777 said:
Yes lol
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
"It has been removed", it being Knox haha. That's how I understood it...
So yes, it's possible to get CyanogenMod working without a brick or semi-brick coming from this version I installed?
Yes, I could have been worded better. You can flash other
ROMs but make sure they don't include an older bootloader or your device will brick from what I understand.
Sent from my GT-N8013 using xda app-developers app
masondoctorjt said:
Yes, I could have been worded better. You can flash other
ROMs but make sure they don't include an older bootloader or your device will brick from what I understand.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I ended up just saying "eff it" and hopped onto CyanogenMod. Probably tripped the root counter, but by now I just don't care anymore.
Thanks for helping me in this thread though, I appreciate it.
Take care and happy holidays.
You did trip the Knox counter.
Just so anyone else reading this thread knows, if you value your warranty DO NOT UPDATE TO 4.3 VIA ODIN . Instead, flash the 4.3 rom , kernel, and modem zips in CWM or TWRP recovery.
Do not Odin MJC (or MK4 for you T999L people) if you want root and warranty, as once you are on the Knox boot loader you can't go back.
Sent from my T999L on PACman
Adreaver said:
You did trip the Knox counter.
Just so anyone else reading this thread knows, if you value your warranty DO NOT UPDATE TO 4.3 VIA ODIN . Instead, flash the 4.3 rom , kernel, and modem zips in CWM or TWRP recovery.
Do not Odin MJC (or MK4 for you T999L people) if you want root and warranty, as once you are on the Knox boot loader you can't go back.
Sent from my T999L on PACman
Click to expand...
Click to collapse
One of the things that bugs me about forums, finding information is a pain the butt. I just want to get my device back to stock so I can get OTA updates, GPS doesn't suck, and can use Wifi. I don't care about root anymore or using custom roms. I'm learning Objective C right now to branch into iOS development. I'm sick of the Android ecosystem, to be frank.
I'm on Wicked Rom with Android v4.1.1
Baseband T999UVDMD5, Kernal 3.0.65-DeviantKernel_07
I'm downloading T999UVUEMJC_T999TMBEMJC_TMB.zip right now, along with root66_TMO_T999UVUEMJC_2.7z
Which one do I need to flash? if root66 gives me root, then cool I'll take it, but as I said, I don't care. I'll be using Mobile Odin since I'm on a mac and I sold my PC. If I need to install Windows via bootcamp then so be it, but I really don't want to.
If I need to update the rom, kernel, modem, etc all separately where do I find those files? *scratches head*
I just want to be absolutely sure, so here goes. I am on stock, rooted 4.1.1 at the moment. If I just let AT&T run the 4.3 update, I can still keep/reroot root, I just can't go back to 4.1.1 correct?
Sent from my SAMSUNG-SGH-I747 using a failing xda app-developers app
Djspinister said:
I just want to be absolutely sure, so here goes. I am on stock, rooted 4.1.1 at the moment. If I just let AT&T run the 4.3 update, I can still keep/reroot root, I just can't go back to 4.1.1 correct?
Sent from my SAMSUNG-SGH-I747 using a failing xda app-developers app
Click to expand...
Click to collapse
Yeah, that's correct. If you go stock 4.3, via the OTA update, you will lose root initially. You can, however, always re-root. The most effective method to root after 4.3 is to Odin TWRP, boot to recovery and then flash SuperSu and the knox remover tool via recovery. Install SuperSU from the play store and run it to update the binary when prompted.
Won't let me thank you on the mobile app, so I'll do it when I get home from work, thank you! Wonder what happened to the premium version I paid for. Took my money and ran lol
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Installing the OTA 4.3 update will also install Knox. Rooting will trip the Knox counter which will void your warranty. If you have no warranty left, tripping knox will now be a problem.
You should also know that Knox can sometimes interfere with obtaining root.
audit13 said:
Installing the OTA 4.3 update will also install Knox. Rooting will trip the Knox counter which will void your warranty. If you have no warranty left, tripping knox will now be a problem.
You should also know that Knox can sometimes interfere with obtaining root.
Click to expand...
Click to collapse
So one person saying you can root no problem, another one saying you might be able to root, might not? This is why there should be a very clear sticky at the top of the forums for everyone to read about just 4.3 and all there is to know about it. Because maybe's are pretty terrible when it comes to flashing/unlocking/rooting/bricking your device.
I don't care about warranty, I'm getting the S5 shortly, I just want to be able to root after the update, is that possible with lets just say the Auto root program, or is it not possible? By possible, I mean I won't have to go out and trade 7 cows for a horse and plow a 600 acre field with said horse.
EDIT: I think I've fingered it out, Thanks for the help fellas.
Djspinister said:
So one person saying you can root no problem, another one saying you might be able to root, might not? This is why there should be a very clear sticky at the top of the forums for everyone to read about just 4.3 and all there is to know about it. Because maybe's are pretty terrible when it comes to flashing/unlocking/rooting/bricking your device.
I don't care about warranty, I'm getting the S5 shortly, I just want to be able to root after the update, is that possible with lets just say the Auto root program, or is it not possible? By possible, I mean I won't have to go out and trade 7 cows for a horse and plow a 600 acre field with said horse.
EDIT: I think I've fingered it out, Thanks for the help fellas.
Click to expand...
Click to collapse
There is no question about it. You can root even after 4.3 OTA. I've done it half a dozen times. Audit is right that you will trip the warranty but since this isn't an issue ...
The usual methods of rooting including CF Auto-Root don't always work and the method I've used with success each time is Option 2 in the thread below. The knox removal script disables knox ...
http://forum.xda-developers.com/showthread.php?t=2538991
Sounds good man, I'll hit that up when I get home, thank you!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks
Knox II will trip with any root method; none known that won't trip Knox for Note 4.
CF Auto Root will work in Odin for your OE1 build but you're limited to CM12 or Noterized Stable for custom ROMs; the others won't boot and full Odin stock tars won't work and there's no OE1 tar either. This is not a standard Sprint OTA; I don't think a OE1 tar will be released; it's long overdue.
If you're still interested, there's a request for stock OE1 recovery; it needs to be backed up and shared in order to help some other rooted OE1 users to take the next OTA to 5.1.1 whenever that releases. Without it, you would be waiting on a tar as well; stuck. To get the recovery backed up, root in Odin (root only), download Flashify in Google Play and backup the stock recovery before you upgrade to TWRP. Share that gem with others that need it. Here: http://forum.xda-developers.com/showthread.php?p=61456449
Still with me? Next you would need TWRP to backup your stock rooted OE1 for a backup if some flash or mod goes awry.
Finally, you could modify the stock Rom or flash Noterized and back it up as well. Keep all these recommended backups in a safe place like on your sdcard and duplicates on PC hard drive.
Read, be careful and ask the questions when you don't understand and you'll avoid the problems others have unexpectedly ran into or got stuck with. OE1 is basically a broken update that shouldn't have got pushed.
Sent from my SM-N910P using Tapatalk
eankk said:
ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks
Click to expand...
Click to collapse
I don't think so without root access
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
There is no oel stock recovery no one has it
Sent from my SM-N910P using XDA Premium HD app
Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though
eankk said:
Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though
Click to expand...
Click to collapse
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk
samep said:
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease
eankk said:
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease
Click to expand...
Click to collapse
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk
samep said:
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nope everytime I took it to a sprint store I flashed it back to complete stock and made sure that the newest version of Android was on it. He is like your knox sensor is tripped. Then I said. "I messed up my phone bad and had to flash stock firmware back on it (when I got the note 4, the chick who sold it to me used to work for Samsung and we where talking about rooting, and then I asked about the sensor if it can be reversed she said, once it is tripped not even samsung can fix it) and damn I did not know sprint was cracking down on root. That's crappy
Links and steps to root OE1, backing up stock recovery
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.
samep said:
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.
Click to expand...
Click to collapse
^^ Sticky this beautiful answer to the ever lasting-never ending redundant OE1 question. Eventually we'll need some thread pruning.
So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?
Mship said:
So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?
Click to expand...
Click to collapse
Consider the facts as we know them. Sprint shouldn't have released it; it's the ugly duckling of a long string of unlocked bootloaders for dancing phones on Sprint. There's a new OS lock intended to protect the owner of a lost phone from easily being written over to bypass a screen lock with a battery pull and Odin tar. But there should also be a user switch to momentary bypass this so Odin wouldn't have been totally broken to rightful owner. Maybe Samsung didn't intend for that to happen and Sprint didn't know better? But since as some have reported that Bluetooth is not fully functional; Sprint should have caught that. I'd say they both collectively hold the blame since it wasn't immediately addressed. I'd blame Sprint more for not halting the update, infecting more users. Hopefully, they're trying to fix that. Maybe they were but decided to work on 5.1.1 update instead?
If it walks like a duck, quacks like a duck...; it must be a duck. It sounds odd to many here, from what I've read. But this is an ugly one. They both should own it, admit it, fix with an immediate update and move on. Until then, make the most of it; apparently, you can't expect a fix by taking it back to Sprint and some warranty replacements had the update pre-installed or quickly updated. Just plain wrong; a definition of insanity.
Maybe mostly opinionated but specifically, are there exceptions to the above for those that got OE1? I think there were some that said the only drawback is not being able to downgrade or recover a soft bricked phone. I could be wrong but just impressed by those OE1 users that have commented.
Edit: short answer is yes because users could update in KIES and that would make Samsung directly to blame for those users. Silence seems to indicate the bugs exist. And may signal a user need to wait for tars to be released which indicates Samsung deems the release as stable.
Sent from my SM-N910P using Tapatalk
Update
So I just got a new update, does anyone know anything about it?