Related
i am thinking to get the s6 and i dont think i can give up on root so i heard there is a root method pingpong does not trip knox if i do it
can i install custom recovery on it without tripping knox or anything else on download mode
if i restore to stock will everything stays the same?
thank you in advance
You can root without tripping the KNOX with Ping Pong Root , but if you flash unsigned software like custom recovery or custom ROM the knox will trip and you will loose the warranty.
Vixa said:
You can root without tripping the KNOX with Ping Pong Root , but if you flash unsigned software like custom recovery or custom ROM the knox will trip and you will loose the warranty.
Click to expand...
Click to collapse
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
Your answer is in post number 2
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
I am talking about using flashify to flash twrp not odin
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
Xposed does not work on 64bit
Sent from my SM-G920F using Tapatalk
There is something strange about knox. I flashed BTU(UK) stock ROM on my XXV(vietnam) SM-920F brand new phone using odin 3.10.6. And hell, knox is tripped now. Strange? Anybody any clues?
sstiwari said:
There is something strange about knox. I flashed BTU(UK) stock ROM on my XXV(vietnam) SM-920F brand new phone using odin 3.10.6. And hell, knox is tripped now. Strange? Anybody any clues?
Click to expand...
Click to collapse
I'm so glad i saw this, i was about to do the same. Got all my backups ready to flash and wipe to change the CSC to BTU (from EVR). So your KNOX has tripped, how was this confirmed?
Were you able to do anything since tripping it?
Thanks
sohail_ahmad said:
I'm so glad i saw this, i was about to do the same. Got all my backups ready to flash and wipe to change the CSC to BTU (from EVR). So your KNOX has tripped, how was this confirmed?
Were you able to do anything since tripping it?
Thanks
Click to expand...
Click to collapse
Nothing much. Once knox is tripped. Its tripped. There is nothing one can do about it.
Can I Update S6 via Odin
I have S6 (SN-G92F)
Made in Vietnam
Original CSC code "ECT"
Active CSC code "ECT"
Knox Warranty void 0*0
CSC Country Nigeria/NG
CSC version
G920FOJV1AODE
Android version 5.0.2
When I tried to OTA update, it shows "already latest OS installed"
I have tried to update it through smart switch, but it updated to the same version.
I have checked in sammobile that 5.1.1 stock available for the same CSC of Nigeria.
Can I update my mobile to 5.1 through odin with out Knox trip.
Knox tripping is very important for me.
any one can help me
Hello all,
I am receiving tomorrow my new Samsung S6 and i want to know some things.
- Unlocking bootloader (how to and link?) - have searched a bit and you need ODIN. but what is the best version etc
- Installing TWRP3.0 (how-to) - where to find the latest TWRP for samsung s6
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
forumber2 said:
3- Boot up to TWRP and backup your unmodified stock ROM before do anything on TWRP;
4- flash this ZIP
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Also, here are the threads for TWRP and SuperSU for the S6 on XDA:
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
http://forum.xda-developers.com/galaxy-s6/orig-development/cf-auto-root-t3056630
djbosanac said:
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Click to expand...
Click to collapse
No, and there probably won't be any for a long time, but there are lots of TouchWiz-based custom ROMs.
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
djbosanac said:
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
Click to expand...
Click to collapse
Correct. The only custom ROMs availability now and the foreseeable future are based on TouchWiz, not AOSP Android or CyanogenMod.
CafeKampuchia said:
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Click to expand...
Click to collapse
He need dm-verity disabled boot image for working TWRP backups. That's why I suggest him to install this ZIP.
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
djbosanac said:
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
Click to expand...
Click to collapse
As I said before, there's no bootloader unlock because bootloader is factory-unlocked on Samsung devices.
If you want root, you should to use TWRP for install the latest SuperSU.
Yes, there's no CM ROM for Exynos 7420 right now. Maybe in future? Who knows...
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
djbosanac said:
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
Click to expand...
Click to collapse
It is not an issue, it is just a warning. I wrote what you need to do at first reply;
forumber2 said:
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
i tried to install it, used the AP method in Odin.
But when i want to go in TWRP recovery i get the stock recovery! How to solve this issue
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
SuddenGun007 said:
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
Click to expand...
Click to collapse
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
piotrus22 said:
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
Click to expand...
Click to collapse
I did figure this out, check this post for how I did it.
Just got this phone new from cricket. I'm having issues making calls. I downloaded the update. But am wondering should I use it. I'm wanting to do custom roms exc. I have not unlocked boot loader or anything yet. If I do the update will I still be able to unlock the boot loader and root custom roms exc? 6045o is the type
First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.
thanks
plumbe0 said:
First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.
Click to expand...
Click to collapse
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.
Luckeyleo said:
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.
Click to expand...
Click to collapse
First of all make sure you never mount /system as rw when using TWRP.
Then just do a systemless root (download SuperSU from chainfire website on your phone, launch TWRP's terminal and type "echo SYSTEMLESS=true>>/data/.supersu", then flash SuperSU as usual), systemless root won't be detected by apps/os. Will probably be detected by SafetyNet but i'm not sure PoGo uses it. In case you have problems with root detection you can try suhide by Chainfire.
Also note that systemless Xposed (rootcloak, etc) and V4A are possible via Magisk (just search it on XDA).
Hello, I currently have a G920T that had been working alright for quite some time. The problem is that yesterday while using it normally, it suddenly froze. Thought it was the app, but saw it was the phone itself. Thus, I decide to turn it on again. When I do that, the phone does not continue after the logo and has the LED light white, while blinking on an off. When I manage to enter the Android Recovery menu it gives me the error shown in the title. The phone's rooted and was unlocked, so I could use it with AT&T.
I attempted doing a full reset, upgraded it to Nougat, and I am still stuck. Any help's appreciated in advanced.
Would like to say, when I installed the official Nougat Upgrade for my phone, upon starting, it began installing some things and then preceded to start Deleting. Afterwards, it just froze again. Did I do something wrong?
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Starnel said:
To get past this issue you have to Root with SuperSU, this will patch the Kernel to disable DM-Verity and will allow you to boot normally.
If you don't want to get rooted then reflash stock firmware via odin. never do OTA updates as i have always say the come "Dirty"
EDIT: Sorry didn't read you were rooted, just re-root again with SuperSU (To get your Kernel patched again) for DM-Verity
Click to expand...
Click to collapse
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
Root with TWRP and superSU zip, i don't recommend CF-AutoRoot
Before flashing the Zip do the following on a Terminal in TWRP
Mount o- bind /dev/urandom /dev/random
Junito72 said:
So I use (what I previously used) cf-autoroot again? I ask this, since it seems their website have the recovery for marshmallow version and not for nougat (if I am not able to downgrade to 6).
Click to expand...
Click to collapse
You can use CF-AutoRoot for 6.0.1 and 7.0.
forumber2 said:
You can use CF-AutoRoot for 6.0.1 and 7.0.
Click to expand...
Click to collapse
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Junito72 said:
When I use CF-Autoroot and attempt to boot it into recovery I get the following message, "recovery is not seandroid enforcing".
So I'd take I try installing a custom ROM first before attempting to start it in recovery?
Click to expand...
Click to collapse
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
forumber2 said:
Oh, that means CF-AutoRoot has not updated to work on 6.0 & 7.0 bootloader for G920T (It is updated and working on 6.0.1 & 7.0 for G920F)
Flash the stock ROM again. After that, flash TWRP and than flash latest SuperSU zip via TWRP.
Click to expand...
Click to collapse
I tried doing that, but wouldn't get past the main ROM's screen. I tried a custom ROM then (I think nemesis or such) and lasted longer, but again froze and loops with the white LED light on.
Any suggestions?
hi
bit of a noob question but ill give some context first...
My s7 (g930f) is on android 7.0, ive successfully installed twrp , magisk and samsung anti root removal via odin.
Knox counter has not been activated as far i can tell .
Snapchat still works. Knox app says warranty is still valid
so far so good
Now i wish to back up my phone in its current state
Now to my question , with my phone rooted, twrp installed with knox still intact ..
Could i make a backup with twrp , then later recover with twrp and STILL have knox with a counter of 0?
I'm not sure how you have managed to flash custom without tripping KNOX
But KNOX is not part of anything that TWRP backs up, so if you somehow have not tripped it, back up, then trip it and restore, it will remain tripped, it is a permanent hardware change
magisk hides the true state of the knox.
Actually his knox is not 0x0
guillefs said:
magisk hides the true state of the knox.
Actually his knox is not 0x0
Click to expand...
Click to collapse
Yea, thought something like that was happening, no-one has managed custom flashing without tripping KNOX yet
Before flashing the supersu, my knox is 0x0 (magisk installed) via download mode.