This may be a noobish question, and if so I apologize, but searching didn't come back with anything concrete.
I have an S7 Edge, the Exynos version, which I have rooted via Chainfire's autoroot. I have NOT installed TWRP or any other custom recovery.
Do I need to leave OEM unlock enabled, or can I safely disable it again without soft-bricking the phone? I gather from my search that having a custom recovery installed and disabling OEM unlock will cause a "soft brick", but will the same occur with only the root in place?
Thanks in advance!
Hi,
While I'm not sure, I don't know why you would want to disable it back. Is there any specific reason?
Since you still are running stock rooted firmware I believe it won't softbrick, but at the same time you are running a modified system (since you rooted), so I wouldn't risk - there's a "software status tag" which says if it's modified or not, when you unlock root access with Chainfire method it will trip Knox and put modified on the tag.
All the best,
~Lord
Sent from my Galaxy S7 Edge (SM-935F) using Tapatalk Beta
Related
I wanted to use CF AUTO ROOT and I cant find G935FD only the G935F. I dont know if i can use that. Can anybody please confirm this?
I verified SM-G935F (NRD90M.G935FXXU1DQD3, 7.0, 62a903c04886dfa3d26e04e07f3e72a3) woks on SM-G935FD.
will it trip the knox or knox safe it is?
asadnow2k said:
will it trip the knox or knox safe it is?
Click to expand...
Click to collapse
Root will trigger knox
teoboy said:
I wanted to use CF AUTO ROOT and I cant find G935FD only the G935F. I dont know if i can use that. Can anybody please confirm this?
Click to expand...
Click to collapse
basically the same phone just the FD has an extra sim slot
thats all
you can flash anything F related on FD, even the stock firmware
the following steps i do to root my SM-G935F and i don't will miss it.
the first method (TWRP with supersu-zip file and dm-verity disabler install was failed, bootloop)
The second try with CF-Autoroot have rooted it.
Bevore rooting with CF auto-root it's needed that you activate the developer options with oem-unlock and usb-debugging.
Than you make a factory reset about the android-own system recovery (home, vol+ and power)
at next you must change in the download mode without boot the "fresh" system and then flash the CF-Autoroot with odin.
Than you can start the fresh system without any first changes bevore rooting process have starts. The securityLogAgent warns you about unauthorized changes. you can disable this notice. And you must disable samsung knox too because it can behinds supersu. a example s-health will not work with rooted devices. one file edited and it works again.
see here. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
In the system app menu you can only stop it. Than you go fast to supersu, this app disable it.
Morning everyone,
I have searched and searched, is it possible to root these A3's as yet?
I bought this s a replacement for my son as he broke his s5 mini sitting on it lol.
Best wishes
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
PlutoDelic said:
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
Click to expand...
Click to collapse
Hi,
I tried downgrading to lollipop without success, as it would stay on samsung logo.
So i had to use smart switch to re-install marshmellow.
Tripping knox is no issue, Therefore as supersu not been updated it would leave me with only option to go back to lollipop?
If so, is there a tut i could follow as doing usal way with odin etc did simply not work.
The A3 is on 02 network
Best wishes
Go for the 4 file package then, it is the only thing that keeps saving peoples phones around here.
Use SamFirm for to download them (make sure you tick binary update)
Who would be kind enough to try the C.F. Auto root on their device not sure the outcome but it is available for firmware QD9.
If it works we can flash stock QD9 Odin firmware and have a rooted phone. Let's get the ball rolling on this.
Won't work because of the bootloader being locked. Others have tested, no go.
i would try any time why not right lol
I remember when he had a temp root that would temporarily work to flash mods and such but retain stock
Very new to rooting. and trying to learn and tinker.
Purchased Samsung Galaxy Tab A 8.0/SM-T350NZAAXAR wifi only.
Performed updates and am on 6.01
Rooted it by following these instructions (http://www.droidviews.com/root-galaxy-tab-a-8-0-and-install-twrp-sm-t350-t355-sm-p350-p355/)
Downloaded and then removed an app to confirm that tablet is rooted.
Did not realize that I had Knox --- did not even know about Knox and when I reboot. I get a yellow message in left corner
Set Warranty Bit - Kernel --- not a big deal since it is not under warranty anyhow. Are there ways to reset this?
Questions/need explanation and/or links to explain
? How do I use the TWRP recovery to make a backup ---
? How do I use the TWRP recovery to go back to the stock version I had ---can that be done?
? Is it safe to use the unroot in SU Superuser ---not that I want to ---just learning and want to know.
? I can no longer update via normal channels because it now says custom ----so to update is it always via flashing using Odin?
? Where do I find custom ROM's for my device and do I flash using Odin?
? What is the difference between Odin and Kies?
? Is there a list somewhere of what system apps are safe to delete?
Hi,
I will buy tomorrow a Galaxy S8 SM-G950F and I want to modify some part of my bootloader image after I discovered an interesting thing in it.
Is it possible or there is some hardware protection to avoid us to flash a custom bootloader with odin? (I don't talk about knox warranty bit)
Also, since it's mostly reverse engineering and I will modify opcodes, if I flash a corrupted bootloader, is it still possible to go to download mode and flash another one again? My initial guess would be yes, since in the past, with my s6 edge, s4 and s2, when the flash froze at flashing the bootloader, I always successfully flashed it again.
Thanks,