Related
I am currently on the MK1 build. In the P600 CF-Auto root thread, as I understand two files needed, One is for the root which is autorootp600mj4.tar.md5 and the other is for recovery which is the stock mj4 recovery, Okay all that being said. Now the question. Can I flash autoroot600mj4.tar.md5 for root, but instead of using the stock mj4 recovery, can I flash the stock mk1 recovery that was post in the P600 CF-Auto root thread. (Refer to Post #144)
Thanks,
Jeff
it could make sens. who got an answer for us please?
yopmania said:
it could make sens. who got an answer for us please?
Click to expand...
Click to collapse
Amen!!
landj1 said:
I am currently on the MK1 build. In the P600 CF-Auto root thread, as I understand two files needed, One is for the root which is autorootp600mj4.tar.md5 and the other is for recovery which is the stock mj4 recovery, Okay all that being said. Now the question. Can I flash autoroot600mj4.tar.md5 for root, but instead of using the stock mj4 recovery, can I flash the stock mk1 recovery that was post in the P600 CF-Auto root thread. (Refer to Post #144)
Thanks,
Jeff
Click to expand...
Click to collapse
yes you can
Thanks
lsherif said:
yes you can
Click to expand...
Click to collapse
Thanks for the info!!!
J
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
landj1 said:
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
Click to expand...
Click to collapse
Rooting has nothing to do with boot looping issues you are referring to, these were TWRP problems .
After seeing many people ask questions about Knox on a regular basis about what they can or can't do, I have decided to create this thread that will hopefully make things clear for those searching information about Knox on our devices.
So first things first.
What exactly is Knox?
Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Knox on Wikipedia
Click to expand...
Click to collapse
F.A.Q
Q. I have Knox firmware on my device, can I still root, flash custom roms, and kernels?
A. Yes, yes you can. Procedure is the same as it has always been. If you have questions search the forum or ask in this thread. Your Knox counter may trip doing any of this so continue to next FAQ for info.
Click to expand...
Click to collapse
Q. What will trip my Knox counter?
Flashing custom recovery or kernels will trip Knox counter, so avoid them at all costs if you want or need to keep that counter at 0x0. Some root methods will also trip this counter, keep reading if you want to avoid this.
Click to expand...
Click to collapse
My Knox counter is tripped, how can I reset it?
Once tripped, the counter CANNOT be reset.
Click to expand...
Click to collapse
Q. How can I root and not trip Knox?
We can currently use the TowelRoot method by geohot for 4.3 and 4.4.2. Follow link below to thread. It does NOT work on 4.4.4
TowelRoot
Click to expand...
Click to collapse
Q. How can I downgrade my firmware?
You cannot and Odin will fail at any attempt to do so. Do not try to bypass this and try to downgrade another way, you run a high risk of bricking you device! This applies to any device that has been officially updated from 4.3 and up from OTA, Odin, or Kies. If you must downgrade for any reason, flash an older rom in custom recovery only. That is the only way to downgrade. Knox Bootloader will not and cannot be removed, so learn how to get along with it.
Click to expand...
Click to collapse
Q. How can I avoid bricking my device? I have seen people say flashing will brick anything with Knox bootloader.
Do not flash firmware for other devices. Do that and you will be okay. On some devices you can flash other firmwares, if you have questions about this you can ask in this thread.
Click to expand...
Click to collapse
Q. Will tripping the Knox counter void my warranty?
As I stated earlier, there have been cases of people successfully filing insurance claims on their devices. However if you really care about warranty, you may want to avoid tripping this counter to be on the safe side.
Click to expand...
Click to collapse
Q. I see an odd message when I start up my device and it says something about SEAndroid kernel not enforcing, what is this and how do I fix it?
It is normal, you either flashed a custom kernel or custom rom with modified kernel. Do not let it bother you but if you flash back the stock unmodified kernel it will disappear. There is also the possibility you performed an unsupported root method and your device is bootlooping, if this is the case, then flash back to stock firmware with Odin to fix and use an updated root method like TowelRoot
Click to expand...
Click to collapse
And if you have any questions feel free to ask
Nice work bro. Should answer a lot of questions for folks.
Haters Made Me Famous
Deviant Team Member
Forgot to reserve, but mine! I'll use this in case Sammy changes something in the next version of android
Never know
And if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for this post!
After rooting using TowelRoot, should you install SuperSU or some other su?
Sizzlechest said:
After rooting using TowelRoot, should you install SuperSU or some other su?
Click to expand...
Click to collapse
SuperSu from the Play Store
The Sickness said:
SuperSu from the Play Store
Click to expand...
Click to collapse
Thanks! It won't trip Knox, right?
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
Nope, perfectly safe
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
A custom recovery or kernel trips Knox
Good. It prompts you to disable Knox, so I thought that might trip it.
I need help with update
Sorry people, it has been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
It's having root that is keeping you from updating. Not tripping Knox.
I'd download the latest firmware. From sammobile or shinyside's links. And use Odin to flash.
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
lordodin912 said:
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
Click to expand...
Click to collapse
It might be possible but I don't know the procedure. I imagine it must be very unconventional, otherwise we would see it very often
Thanks, SEAndroid kernel not enforcing worried me.
Hmmmmmm wish I were a bit more fluent in this area.....itd be nice if you could just replace/repackage the tar file....then mabey id get off MDL....just read something about repacking tar files for odin and apparently you cant pull and repackage the system without breaking the signature (of the system) therefore odin wont flash....but imma noob in this area. If anyones got any info, please share
noobieneedshelp said:
Sorry people, it has no been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
Click to expand...
Click to collapse
Use this to go back to stock and fix Knox then root again with towelroot method.
http://forum.xda-developers.com/showthread.php?t=2336392
http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Legioss199 said:
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Click to expand...
Click to collapse
Yes, and it also means you can no longer use the Knox service.
I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!
koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.
Does this still void knox?
1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!
JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15
1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk
For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it
JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.
1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:
This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.
after flashing oxygenos 4.1.1 through twrp recovery when i rebooted my phone into recovery stock recovery came i dont have pc right now can anyone help it's very urgent
after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.
anup807 said:
after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.
Click to expand...
Click to collapse
Actually I don't have PC is there any other way
how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
https://www.youtube.com/watch?v=BYUycIr7xQo - try this.
If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.
You should flash twrp after flashing any rom. Then reboot to recovery to check if it works. Official roms flash official recovery...
Anova's Origin said:
If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.
Click to expand...
Click to collapse
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify
sauravid said:
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify
Click to expand...
Click to collapse
If kingoroot works, then yes, you can probably flash TWRP that way.
Anova's Origin said:
If kingoroot works, then yes, you can probably flash TWRP that way.
Click to expand...
Click to collapse
No rooting app is working did you know any app which can work
anup807 said:
how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
- try this.
Click to expand...
Click to collapse
Actually it requre root access. Do you know how to get root access without pc
You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).
Anova's Origin said:
You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).
Click to expand...
Click to collapse
Not working..bro
I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.
anup807 said:
I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.
Click to expand...
Click to collapse
Ohk bro