Related
i have rooted my note 3 and no knox trip. I think that CWM is not included in the de le vega root package. If this is not the case how do i flash a ROM on my phone? And is this possible without tripping Knox?
metrobigboss1981 said:
i have rooted my note 3 and no knox trip. I think that CWM is not included in the de le vega root package. If this is not the case how do i flash a ROM on my phone? And is this possible without tripping Knox?
Click to expand...
Click to collapse
De La Vega doesn't trip Knox. It gives you Root.
Flashing ANY recovery or other ROM will trip Root. So you can't if you want to keep you Knox at 0x0.
^ that.
Unfortunately, if you don't want to trip Knox, root is all you get. Check out Xposed framework for some more options in modding your stock rom, installing that and Wanam really go a long way towards customizing your phone. Just be VERY careful, and make sure you read everything, bootloops are a very real danger when screwing around with them, make sure you know how to push files via adb.
kitsunisan said:
^ that.
Unfortunately, if you don't want to trip Knox, root is all you get. Check out Xposed framework for some more options in modding your stock rom, installing that and Wanam really go a long way towards customizing your phone. Just be VERY careful, and make sure you read everything, bootloops are a very real danger when screwing around with them, make sure you know how to push files via adb.
Click to expand...
Click to collapse
What he said. There's also a zip to disable all the Xpozed functions in case you bork your phone, but of course you need a custom recovery to flash the zip. That's why knowing adb and having it setup and working is important if you want to go that route.
alrights guys I didn't see this anywhere in ur forum so here it is, after exchanging my s4 for a replacement, I got it with 4.3 and all this Knox nonsense already installed, Now I don't really care that much for samsung's warranty but I went out and look for a way to root our latest without triggering Knox counter just head on to the thread below and check it out... it has a catch but I would say it's worth the trade off.
http://forum.xda-developers.com/showthread.php?t=2565758
lol Dude, we just discussed this in another forum and this has been discussed in many forums. :silly:
Anyways... I've used this Verizon method on my buddies ATT Galaxy S4 with a locked bootloader on a 4.3 MK2 baseband. It does not trip the KNOX flag. There are no "trade-offs." It functions well. Chainfires AutoRoot works as well.
So with this method you cannot make a nandroid backup OR even restore one?
HTCMDA said:
So with this method you cannot make a nandroid backup OR even restore one?
Click to expand...
Click to collapse
I have not tried to make a nandroid with a locked BL and will try tomorrow (damn sure it won't work). Best bet is to try Online Nandroid Manager. Nandroid backups require a custom recovery, it has nothing to do with having root.
Ive been out of the rooting world for a while, but with research, Ive caught up a little. However I do have a couple of questions;
With this method, can I still install a custom vanilla rom with 4.3/4.4?
If not, what are the benefits?
knipp21 said:
Ive been out of the rooting world for a while, but with research, Ive caught up a little. However I do have a couple of questions;
With this method, can I still install a custom vanilla rom with 4.3/4.4?
If not, what are the benefits?
Click to expand...
Click to collapse
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
xdapowerapps said:
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
Click to expand...
Click to collapse
I dont really care about the warranty, if its samsung and not t mobile.. But that isnt a def answer yet.
And ok, I guess Ill hunt the threads to see how to install the recovery. Thanks man
knipp21 said:
I dont really care about the warranty, if its samsung and not t mobile.. But that isnt a def answer yet.
And ok, I guess Ill hunt the threads to see how to install the recovery. Thanks man
Click to expand...
Click to collapse
Well, even some of the T-Mobile apps now recognize if you have root and could possibly use that as proof that you voided your warranty. Tmobile/Samsung, vice versa, won't be much difference. You'd just have to find a store person that isn't knowledgeable on the subject and get a replacement. Good luck.
yea about that!
Yea I notice after I posted LOL.. a and here I was thinking I found the "holy grail" of rooting LOL!! but anyway those that Need to know just like it has been said.. this will get u rooted with out triggering Knox. this only applies to those that upgraded OTA or got their S4 already with JB 4.3 in it.. like I did after a warranty exchange... HOWEVER if u install any Custom Recovery u will trigger the counter VOIDING ur warranty FOREVER!!! LOL well maybe not but at least til someone (and who knows if someone ever will) figures Knox out. So think twice before you do anything, cause no here will take responsability for your actions...
HAPPY FLASHIN!!
Just did this to my T-Mobile SGS4. It worked just as described. The Knox counter wasn't tripped, but Custom is indicated on the Download screen (Vol Down+Home+Power).
Here's what my Download screen now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Thanks for the link to the other thread. :good:
Now I can use Titanium Backup, Greenify, ADB - rooted, esFile Explorer - rooted. Not needing a Custom Rom or Custom Recovery yet. And, to get it back to un-rooted, there are instructions in the other thread about that.
Rob
rlichtefeld said:
Just did this to my T-Mobile SGS4. It worked just as described. The Knox counter wasn't tripped, but Custom is indicated on the Download screen (Vol Down+Home+Power).
Here's what my Download screen now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Thanks for the link to the other thread. :good:
Now I can use Titanium Backup, Greenify, ADB - rooted, esFile Explorer - rooted. Not needing a Custom Rom or Custom Recovery yet. And, to get it back to un-rooted, there are instructions in the other thread about that.
Rob
Click to expand...
Click to collapse
Just remember, you won't be able to make full nandroid backups (give Online Nandroid Manager a shot if you want to try).
xdapowerapps said:
Just remember, you won't be able to make full nandroid backups (give Online Nandroid Manager a shot if you want to try).
Click to expand...
Click to collapse
IFAIK, until I plan to flash a custom ROM I shouldn't need a full Nandroid. I can always flash a stock ROM, and between the Google Backup/Restore and TiB, I should get almost everything back. Music/Video, etc are all on the MicroSD.
Unless I'm sadly mistaken. This is my first foray into messing with the SGS4. I was very active flashing on my HTC HD2, starting with various builds for WM6.5, and then moving on to SD builds of Android and then NativeSD with cLK, etc. I was running Tytung's KitKat until I got this phone in December. I work for a small company and the SGS4 was my Christmas Bonus. The HD2 was just too long in tooth to keep up with all the advances in Android. But, since you could flash everything - radios, bootloaders, recoveries, builds, etc., I could change out/update my version of Android almost daily.
Rob
rlichtefeld said:
IFAIK, until I plan to flash a custom ROM I shouldn't need a full Nandroid. I can always flash a stock ROM, and between the Google Backup/Restore and TiB, I should get almost everything back. Music/Video, etc are all on the MicroSD.
Unless I'm sadly mistaken. This is my first foray into messing with the SGS4. I was very active flashing on my HTC HD2, starting with various builds for WM6.5, and then moving on to SD builds of Android and then NativeSD with cLK, etc. I was running Tytung's KitKat until I got this phone in December. I work for a small company and the SGS4 was my Christmas Bonus. The HD2 was just too long in tooth to keep up with all the advances in Android. But, since you could flash everything - radios, bootloaders, recoveries, builds, etc., I could change out/update my version of Android almost daily.
Rob
Click to expand...
Click to collapse
The beauty of a nandroid backup is that it takes a snapshot of your phone as it stands. Within five to eight minutes, you can restore your phone as it stood before it messed up. No re-downloading apps, changing settings, replacing system apps (i.e., installing Note 3 My Files and Gallery), etc. It saves the hassles of slow TiB/Helium restoration, especially if you have hundreds of apps. Sure, you can start fresh and manually restore things, but having it done within eight minutes without lifting a finger is extremely nice to have in your arsenal. Has come in handy several times for me since I test ROMs very frequently.
Congrats on your bonus, a very nice bonus indeed. It is a great phone. I was thinking about switching to a Note 3 or waiting for the S5 but this phone is perfect for my hands. Note 3 with an Otterbox Defender case is too big for my taste and the S5 is still a ways off. Plus, the development for this phone has far exceeded my expectations so I'm a happy camper for now.
xdapowerapps said:
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
Click to expand...
Click to collapse
What method did you use to install a custom recovery? I saw this in the thread:
Important - please read
If you fail to read this, you will be taunted.
1. You can't install custom recovery and custom ROMs using this technique. See Safestrap for a way to install some custom ROMs.
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store.
In Wanam, tick "Security Hacks", "Fake System Status".
Click to expand...
Click to collapse
Did you use the safestrap like he suggested? I just got a replacement from t-mobile, i can't be stuck on tw lol.
root is still better then no root lol thank you for the info.
This is all great info, on rooting 4.3....
but how do you UNROOT ?
Xx_Joe_Wireless_xX said:
This is all great info, on rooting 4.3....
but how do you UNROOT ?
Click to expand...
Click to collapse
Go into SuperSU, then click permanent cleanup.
You have to make sure busy box is removed as well, or system will show custom
Sent from my SGH-M919 using XDA Premium 4 mobile app
Is there a way to get back to the stock rom???
Sent from my SGH-M919 using xda app-developers app
KRAZYADROIDMASTER said:
Is there a way to get back to the stock rom???
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
If the only mod you did was to follow the instructions in this thread, then you aren't changing the ROM, you are only giving yourself Root privileges.
To Unroot, go to the thread in the original post, and look at the second message in that thread.
Here's the link to that exact message:
http://forum.xda-developers.com/showpost.php?p=48392024&postcount=2
You will be
1) removing BusyBox
2) Using SuperSU to "Full Unroot"
If you've done more than was laid out in the original message in that thread, then you will probably need to
3) Remove any Custom Recovery
4) Flash an original ROM
There are several threads discussing getting back to a Stock ROM.
Rob
Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!
Steameffekt said:
Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!
Click to expand...
Click to collapse
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
If I flashed back to stock, did a factory reset, would it still say custom?
Steameffekt said:
If I flashed back to stock, did a factory reset, would it still say custom?
Click to expand...
Click to collapse
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk
effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
effortless said:
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Makes sense and I probably will flash a custom recovery. I just don't understand the fuss with people wanting not to trip knox if they're not even gonna use it.
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
un-answered question............
I don't know why I have not asked this before, but here it goes..........
First, I just want to say that I could care less about Knox...
(my phone already has the knox pox)
But for future reference if I had a brand new Note 3 with official stock NB4 baseband
and I rooted it successfully using Towelroot (or root de la vaga) would it be possible
to simply rename a custom rom like Hyperdrive to "update.zip" and copy it to the
internal sdcard then boot into the stock NB4 recovery and flash/install "update.zip"?
If the only problem with this method would be the fact that a different kernel would
also flashed along with the rom it would be an easy fix by just removing the kernel
from the custom rom file before flashing the update.zip?
I know that more likely than not this method would not work.
But if it did work it should not trip the knox right?
Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
Sent from my SM-N900T using xda premium
re: modile odin - knox
Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible". Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!
Misterjunky said:
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!
Click to expand...
Click to collapse
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?
re: knox - mobile odin
Eudeferrer said:
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?
Click to expand...
Click to collapse
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!
Misterjunky said:
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!
Click to expand...
Click to collapse
My bad. I guess I misunderstood you the first time. Thank you for your response.
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.
lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.
itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I used the method from this thread http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484 to root my SM-T800. So I'm on BOE3 right now with root. I want to update to BOJ1 and keep root.
When I do an update check, it tells me that I can't update because my device is modified. How do I get the update and keep root? Is there a guide that I have overlooked?
Thank you for the help.
I have noticed that the updater refuses to work not only when you have root, but sometimes even when you have TWRP installed without root. Anyways.. there are many options there, but I have no idea if they work without tripping knox bit (who cares about it anyways?).
The first thing you can try is to run the full unroot procedure from inside of supersu. This will remove root, and then you can try to install OTA update again. If that still doesn't work, you can backup your data, flash the KitKat ROM with odin, and then install OTA update. Or alternatively, just flash the latest Lollipop image (this will lose all your data and mods, and trip the knox).
Akopps said:
I have noticed that the updater refuses to work not only when you have root, but sometimes even when you have TWRP installed without root. Anyways.. there are many options there, but I have no idea if they work without tripping knox bit (who cares about it anyways?).
The first thing you can try is to run the full unroot procedure from inside of supersu. This will remove root, and then you can try to install OTA update again. If that still doesn't work, you can backup your data, flash the KitKat ROM with odin, and then install OTA update. Or alternatively, just flash the latest Lollipop image (this will lose all your data and mods, and trip the knox).
Click to expand...
Click to collapse
Unless I'm misunderstanding, won't that make me lose root? I want to keep root.
All you need do is flash the firmware with FLASHFIRE. You will then keep root without tripping knox.
See the kingroot guide for more info.
http://forum.xda-developers.com/showthread.php?t=3129484
micheal1981 said:
Unless I'm misunderstanding, won't that make me lose root? I want to keep root.
Click to expand...
Click to collapse
Once you update to the latest ROM, then you can get root again, by flashing cf-autoroot or something else. (Again, this will set off the knox bit, but it's useless anyways)
ashyx said:
All you need do is flash the firmware with FLASHFIRE. You will then keep root without tripping knox.
See the kingroot guide for more info.
http://forum.xda-developers.com/showthread.php?t=3129484
Click to expand...
Click to collapse
OK. I just wasn't 100% sure that method would work for the newest update. Time to find where to download the latest firmware.
Alright, I flashed BOJ1 with Flashfire and I still have root. My bootloader says BOE3. Do I need to flash the BOJ1 bootloader? I believe the answer is yes, but just want to make sure.
micheal1981 said:
Alright, I flashed BOJ1 with Flashfire and I still have root. My bootloader says BOE3. Do I need to flash the BOJ1 bootloader? I believe the answer is yes, but just want to make sure.
Click to expand...
Click to collapse
If everything works then no, but may as well if you want the latest.