yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 General] mark1316:
Am I right in thinking that if I root and need to send back for service I need to flash the original Rom back to the phone through odin and then return ? They cant tell its been rooted as long as I dont trip know ? Sorry for being stupid but im a convert from HTC
[Galaxy S 5 General] wajiman:
if you have read the OP carefully, it says this won't trip knox. If you want to send it back for service, just uninsured root and done or flash stock firmware
[Galaxy S 5 General] nfribeiro:
Did you read the OP of this thread?

Sent from SM-G900FD S5 Duos using Tapatalk
[Galaxy S 5 General] georgemircea:
i apreciate little help, simply yes or no,or use this metod :) i ask because don't see my firmware, and i don't wanna brick the "precious". thank's
[Galaxy S 5 General] wajiman:
btw if you read the OP you will not require to see your firmware. But since you were negligent in reading the OP, the answer to your question is YES use this method to root, it will NOT trip your KNOX
[Galaxy S 5 General] Neo-ST:
Hi, I've read the OP but not the rest. I just bought the S5 and if someone could answer a few questions I'd be grateful.

1. If I do the procedure described in the OP, will it wipe my phone (data, pics, apps, etc.) ?

2. If not, is it advisable to do the factory reset anyway ?

3. Will it void my warranty?

4. Will I keep getting the official updates from Samsung or it "breaks" it ?

5. What's the difference between this method and "CF Auto root" one?

Thanks
[Galaxy S 5 General] rederik75:
1. No

2. Not necessary

3. It won't trip Knox, so it's reversible, so it won't void your warranty

4. You should disable OTA updates by Samsung, using mobile Odin pro instead. You'll find how going a bit further from the OP

5. This method won't trip Knox and won't void your warranty, CF autoroot will trip Knox and void warranty. The latter opens the way to the world of custom recoveries, roms and kernels, at the cost of the warranty..

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] yukou:
without rooting, it's fine for me now

But when warranty expired, I'll root it :)
[Galaxy S 5 General] jaskof1:
I have g900f on 4.4.2 AGN2. I get ota update for new firmware about 170mb. Will this method work after update??
[Galaxy S 5 General] rederik75:
Yes, but you have to download the correct kernel for the updated firmware.

It happened the same to me. I bought this phone a week ago and it suddenly had an update, that I applied. Then, to root, I downloaded the kernel corresponding to my firmware and everything went the right way...

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] jaskof1:
Thx for replay. I updated my phone to FXXU1ANG8 4.4.2. Whera I can find kernel for ng8? Or I need to create kernel?
[Galaxy S 5 General] mauriicio21:
i have 900M in NI1, so, i need to download ANI1 firmware and NE3 and follow tuto changing NG3 to my actually? right?

sorry my bad english :/
[Galaxy S 5 General] rederik75:
In settings, phone info, you may find a couple of strings, under "baseband" and "build version". In mine, for example (see screenshot), I have ANG8 baseband and ANG9 build. So I downloaded the kernel for ANG9 from the link in the OP, and it works fine..

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] jaskof1:
I see. My is NI3. And there are dont egsist link for download. I try to download rom from sammobile germany (vodafone) buth sometnhing wrong with sammobile. Cant dowload any rom..
[Galaxy S 5 General] Gibblets:
So I have stock NI2 Verizon S5, tried Misterxtc's root for NI2 where I copy towelroot, busy box, and safestrap to the SD card of my phone, flash to NCG and install and run towelroot but when I get done odin flash to NCG I install towelroot and try getting root access but it says it does not support my phone. I got to my build and it still says NI2...but it said NCG passed? I don't get it. Any help?

I dont really care about tripping knox, if I do then I do if not then thats awesome. I know Safestrap will probably or definitely trip knox, I just want to be able to root honestly and thats all. I don't understand why towelroot says my phone isn't supported other than that the kernel and build say NI2 even though I flashed to NCG through odin and it says it passes.
[Galaxy S 5 General] kevded:
Merci

Merci pour le tutoriel, G900F ANG9 rooté knox 0x0.
[Galaxy S 5 General] wajiman:
If you dont care about KNOX, use CF-Root
[Galaxy S 5 General] jaskof1:
I finaly root my s5 g900f with this metod. If somebody have some quastion ask me. I will help you.

Thanks for this method rooting s5 without triping knox. Everithing works good. I installed titanium backup and rostore some apps from my earlier phone note 3, install greenfy, xposed module, wanam xposed...
[Galaxy S 5 General] ChelseaHansa:
Did your s-health work after you installed Xposed?
[Galaxy S 5 General] jaskof1:
I think it work. I never used s healt.. Now i updadet and opened and it seems to work..
[Galaxy S 5 General] iDontbreak:
Worked like a charm. Thought though I had MTP/MTB whatever its called, driver failures but noticed once you go in download mode it all fixes and u can connect the device to PC without an issue.

5/5 for tutorial.

Wonder how you can unlock your sim card now though for free
[Galaxy S 5 General] Gibblets:
I cannot seem to find anywhere how to use CF root or CF auto root for Galaxy S5 or especially the VZW S5.

autoroot.chainfire(DOT)eu/#fastboot

There is a list of supported devices there and not one says SM-G900V.

How come when I flash to NCG odin tells me it passes but the build still says NI2 and why does towelroot say its not supported if it really is flashed to NCG?
[Galaxy S 5 General] 2ndcarpenter:
You may be able to get more support in the Verizon S5 thread or the CF-root thread. Also Chainfire has a google+ account you may even be able get a response from him there.
[Galaxy S 5 General] JacobCob:
I have the ang2 and it currently isnt supported by the towel root? shall i downgrade or? the kernel is from July....

---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------

I have the ang2 and it currently isnt supported by the towel root? shall i downgrade or? the kernel is from July....
[Galaxy S 5 General] wajiman:
Did you read the OP?? Your questions are already answered over there exactly
[Galaxy S 5 General] jaskof1:
You need to flash NE2 kernel, because towel root doesnt suport newer kernel. You flash ne2 kernel, root phone with towel root, update super su, disable knox and flash back your kernel.. With ne2 kernel you will get some force closes buth when you flash back to your kernel everithing will work grate :)
[Galaxy S 5 General] jaskof1:
I promise to "darkdead4" to make step by step tut to help him and other to root s5 with towelroot without trip knox.

1. Download super su from market and towel root apk from https://towelroot.com and istall it.

2. if your kernel is newer then ANG2 kernel (newer then 03.june) you need to flash old kernel NE2 (download from : https://www.dropbox.com/s/cun1uainm2h07em/KERNEL_G900FXXU1ANE2.tar.md5 ) and flash with odin 3.09.

4. When you flash old kernel ANG2 and turn on phone you get some force closes. It normal and dont wory. Also wi fi dont work with ANG2 kernel and you need to have mobile data for this step. Its very important.

5. Open towlroot and klik make it ra1n. Your phone is rooted.

6. Now, open super su and update binary. If That take long time you can see in scrol bar some atention, like unauthorised operations. Open and just ignore. Open again super su and you get massage to disable knox, disabble knox exit super su. Open again and super su and update binary.

7. Now you need to flash kernel for your rom.

8. Download from( https://www.androidfilehost.com/?w=files&flid=18027 )

9. Flash kernel :)
[Galaxy S 5 General] jaskof1:
You see on picture my kernel is NI3. On this site ( https://www.androidfilehost.com/?w=files&flid=18027[/url] ) there are not link for kernel. And i kreate it my self.
[Galaxy S 5 General] ckatlanta:
Anyone verify my instructions for sprint G900PVPU1ANE5?

never mind, figured out towelroot works just fine on Sprint G900PVPU1ANE5
[Galaxy S 5 General] monemhamid:
Confirmed I was able to do this on sm-g900fd
[Galaxy S 5 General] jaskof1:
This is link how to create own kenrel ( https://www.youtube.com/watch?v=-3j7lyI_DuU )
[Galaxy S 5 General] yeahman45:
with this I can install custom roms? how to make backups or restore backup if something goes wrong if there is no CWM?
[Galaxy S 5 General] annson08:
This method only gives root without triggering knox. But it doesn't mean that flashing custom recoveries and rom wont trigger it.
[Galaxy S 5 General] wajiman:
AFAIK you can only flash alendr's and NeatRom without tripping knox
[Galaxy S 5 General] yeahman45:
ok thx... if something goes wrong.. can i still recover to original rom?
[Galaxy S 5 General] ckatlanta:
anyone able to answer my previous post about sprint S5?

never mind, figured out towelroot works just fine on Sprint G900PVPU1ANE5
[Galaxy S 5 General] bunder9999:
Hi, just bought an Bell S5 last week and I was wondering about the root procedure...

The phone came with ANF3 (June 16), and it looks like my choices of kernel to (ab)use is just AND1 from April?

Is the procedure the same as other providers firmwares (split kernel from firmware, downgrade kernel, root, disable knox, update supersu, restore original kernel, fix s-health)?

Thanks

edit: Nope... ANF3 works just fine. No downgrading needed.
[Galaxy S 5 General] bett3rthan:
If I update my firmware with odin, and I mean an original firmware from sammobile, would this trigger knox on my S5? I am on ang9 and i want to go to anj1
[Galaxy S 5 General] wajiman:
Can you tell me which kernel did you flash to root?

Flashing any samsung branded firmware WILL NOT TRIP Knox. Only customs recoveries, kernal and custom roms that contain custom kernel WILL TRIGGER KNOX
[Galaxy S 5 General] monemhamid:
I was at j1, flashed f6 and then reverted
[Galaxy S 5 General] Kriomag:
i tripped knox just by flashing older firmware in my S4, official firmware... thats why im always afraid of this method, to flash older kernel to root, i wonder when samsung will make it trigger knox...
[Galaxy S 5 General] wajiman:
The reason you tripped knox is due to flashing 4.3 on 4.4. that will trigger knox but thats not gonna happen in s5 as it does not have 4.3 but cant say anything for lolipop 5 whether it will have same protection like in s4. but i think flashing the kernel and doing it should be fine
[Galaxy S 5 General] rederik75:
So the key is the custom kernels and recoveries? Would it be possible to build an aosp ROM without Samsung framework and system, just keeping the untouched kernel and the original recovery? Just wondering....

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] chainbr3ak:
No
[Galaxy S 5 General] wajiman:
Nope AFAIK the reason, samsung firmware pack, as a whole comes with a signature detected as valid by the KNOX. Any custom modified rom will not have that signature and will blow your KNOX.

there is a way to create and flash custom roms without triggering KNOX. Like _alexndr and Neatrom. Both are available in s5 android development zone. I have personally flashed _alexndr's custom rom without tripping knox.
[Galaxy S 5 General] the_pinkfloyd:
Hi, received new OTA update this morning ( 95 Mb size ) does someone have any information on it ? Can we do it without scarry about loosing root ? Thanks !

EDIT : Disabled the problem ^^

Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear.

Step 2. Disable Otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak

Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/

Step 4. Reboot

PS : FotaClient.apk not found on my device but all the rest is ok, and no more notification
[Galaxy S 5 General] Dakloos88:
No more updates?

I have succesfully rooted my S5 thanks to this tutorial, all is well it seems.

The only thing I noticed is that when I now check for updates on the phone (through ''about phone''), it says my device is altered in a way not allowed. It tells me to use Kies for software updates.

Is that supposed to happen with this method?
[Galaxy S 5 General] wajiman:
it happens on every device you root
[Galaxy S 5 General] Dakloos88:
Thanks for your answer. So I understand I will have to use Kies to update, however I will of course lose the root should I install one.
[Galaxy S 5 General] the_pinkfloyd:
hum, if you check my previous post, my s5 rooted, downloaded and asked me to install OTA update this morning... ( i doesn't try to install it, so don't know if it will success )
[Galaxy S 5 General] wajiman:
no i meant to say, whenever you update using OTA, root will be lost
[Galaxy S 5 General] LinoX:
Are you sure??

Doesn't Mobile Odin Pro use a custom (unsigned by samsung) kernel (named "FlashKernel") to flash firmwares?

I thought the procedure went like

flash custom kernel

reboot in custom kernel

flash from custom kernel the system (rooting it)

flash back again standard kernel

reboot.

If the procedure is this Mobile Odin WILL trip knox (in step 1)
[Galaxy S 5 General] the_pinkfloyd:
ah yes, agreed ^^
[Galaxy S 5 General] Dakloos88:
So, something must have gone wrong, since I can't update from the device itself no more?
[Galaxy S 5 General] gee2012:
Flashing stock firmware with Mobile Odin Pro and keep root will NOT trip KNOX ;)

---------- Post added at 06:36 PM ---------- Previous post was at 06:21 PM ----------

If you are rooted you can`t flash OTA`s anymore. You could try Kies but you`ll loose root. Best way is to flash the latest stock rom with Mobile Odin Pro and keep root.

If a device is rooted users should forget about OTA`s and Kies anyway ;)
[Galaxy S 5 General] villa_bryan:
thank god.

After tons of reading, I found out that all I had to do was flash the old kernel, unroot, and flash the new kernel. The problem was that I could not find a way to get the kernel out without doing things that seemed too complicated and gave me a lot of chances to mess it up.

Anyways I will be giving this a shot on the G-900J (aka scl23)
[Galaxy S 5 General] LinoX:
Because you tried it?

Someone here doesn't agree. And I honestly am somewhat dubious too.

The only way Mobile Odin Pro can avoid tripping knox is putting the custom (flash)kernel in a data page (instead of temporarily flashing it to the partition) and jump to execute it...but as far as I know data pages are protected from execution of code (the magic thing that in "x86" world is called NX bit)
[Galaxy S 5 General] gee2012:
You are mixing up Mobile Odin Pro and CF Auto Root which does flash a insecure kernel to install root files. I used MOP a lot of times and it simply works well without tripping KNOX if you flash a stock rom.
[Galaxy S 5 General] LinoX:
I'm not mixing. :eek: Mobile Odin Pro installs a custom flash kernel (that flashes according to the instructions given to the program from the user). That's not CF Auto Root. Proof of what I'm saying is that, for reasons I won't explain here, I once got stuck in "Flash kernel" bootloop on my note 10.1.

Turning it off did absolutely nothing because, at boot, the flashkernel was loaded instead of the "normal one".

So this custom kernel

IS

permanently flashed (at least on Note 10.1), the device is rebooted, the custom kernel kicks in, executes the instructions, flashes whatever you have chosen in the UI (at least it tries), eventually injects in /system the su/superuser.apk, replaces itself with default kernel after the flashing completes (not if it fails) and the device is rebooted.

Unless Chainfire gives us details on the way he managed to not trip KNOX on the S5 I can assume that what you say must be wrong to the extent that if I need to keep knox to 0x0 I won't try it. :p
[Galaxy S 5 General] wajiman:
although i am not a technical person but the way i understood is that MOP does flash kernel but it does it after the phone boots and KNOX checks the signature on kernel and it does not blow as it is original.

After which MOP flashes kernel temporarily and flashes the zip file after which it uninstalls itself. Retaining the original kernels integrity.

This is the only way that makes sense as to why KNOX does not blow as i have flashed custom Rom using MOP without triggering KNOX.

I hope you understand what i am trying to say.

delivered via DHL from S5
[Galaxy S 5 General] rederik75:
I don't know how he did the magic, but I can confirm that flashing a stock or stock-derivative rom with MOP doesn't trigger Knox. Today I flashed alexndr's NJ1 based rom with MOP and Knox didn't trigger. I was on NG9 rooted stock rom.

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] tisazalay:
It's been explained before, KNOX "as a service" is called from the bootloader and it checks the integrity of the recovery & kernel (the stock ones are -signed-) and if they are fine, then the "Knox flag" won't be tripped. Stock ROMs include at least a stock kernel (signed), maybe a recovery (signed) so everything is fine according to Knox. MOP does all the flashing before the bootloader kicks in (reboot) so Knox is not running. If you flash a non stock rom from MOP, when the bootloader calls the routines to check integrity, knox will be tripped.
[Galaxy S 5 General] Bauamt:
Thanks

I had to use the script to get a md5 file myself, but it worked on my g900f and knox is still 0x0, thank you!
[Galaxy S 5 General] rederik75:
Once tripped the flag can't be reverted back, right? For example flashing a whole stock rom with Odin PC...
[Galaxy S 5 General] tisazalay:
That's correct, so far, there's no proof on any s5, Snapdragon or exynos, that it can be reverted, some people call it an e-fuse.

The problem with the H (exynos ) is that there's no way to gain write access to system from within the rom, there's no exploitable back door in the kernel to let that happen.

I wonder if a system app can be hacked or patched to write the supersu binaries in the right place, from "userland"....
[Galaxy S 5 General] gee2012:
Dude get your facts straight next time before posting stuff which is not correct ;)
[Galaxy S 5 General] yeahman45:
guys what happens if I do a bad/corrupted rom flash? will still be able to recover without cwm? (via odin maybe??)
[Galaxy S 5 General] gee2012:
You mean a corrupted custom or stock rom flash? If custom reboot into recovery and sideload a rom from the pc or flash a stock rom with Odin. Thats why you need to make a nandroid backup for a working rom to fall back too ;)
[Galaxy S 5 General] rederik75:
You should always be able to flash back a stock rom, but if you trigger Knox it won't be reversible

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] yeahman45:
Thx that is what i wanted to know
[Galaxy S 5 General] mag1car:
Hi im new with android, so im sorry for for asking these kind of questions but i need to be shure becouse i dont want to trigger KNOX, thanks for understanding,

I have galaxy s5 G900F, android version 4.4.2 Baseband version G900FXXU1ANG8, Kernel 4.3.0, Build number G900FXXU1ANG9

Questions:

1)I saw here (http://xdaforums.com/galaxy-s5/general/tut-root-tripping-knox-t2803951)

sholud i first start towelroot and make it rain, than via supersu disable KNOX and after that start ODIN or its reverse first ODIN and after that towelroot.

2) http://xdaforums.com/galaxy-s5/general/guide-update-to-g900fxxu1ang2-root-knox-t2835315

In odin i saw i need to have two files Bootloader ANG2: BL_G900FXXU1ANG2.tar.md5 and Modem ANG2: CP_G900FXXU1ANG2.tar.md5

My second question is which Kernel should i use, those bootloader and modem ANG2 or should i download other one becouse i have ANG8 and ANG9?

Like i', said im new and don't know lot about rooting and flashing bios so i'm confused becouse i can't find ...ANG8 and ANG9 here https://www.androidfilehost.com/?w=files&flid=18027

Once again thanks for understanding, and for help
[Galaxy S 5 General] rederik75:
1) first towrlroot, then supersu. If supersu gets blocked while disabling Knox, just reboot and supersu again

2) I was in your same situation, you have to download ANG9 kernel

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 General] mag1car:
One more time sorry for those kind of questions

when start make it ra1n it says "this phone isn't currently supported"

I found on google:

Step No 1:- First of all open the TowelRoot application on your device and tap 3 times on the welcome of TowelRoot v3 in order to change the Modstrings.

Step No 2:- You will see the white box make it ra1n.

Step No 3:- Now type the below given codes in the opened white box.

Code 1: 1337 0 1 0 4 0 (Standard code – works on most devices)

Code 2: 1337 0 1 7380 4 0 (For Samsung Galaxy Device)

Code 3: 1337 0 1 0 4 1 (Universal code – gives temporary Root Access)

If it shows a message on your Android device that your “Phone isn’t supported”, then type code 1 and hit the Root button. This Code is standard code and it works on most of the Android Smartphones.

Those who are using the Samsung Galaxy devices, than code 2 is the right code for them. Just hit the root button after entering the code 2.

But this didn't help, is there any other solution ?

Thanks
[Galaxy S 5 General] LinoX:
Signature checking is done at bootloader level, before loading the kernel (obviously). Simplified: bootloader 1 (rom) loads bootloader 2 (from flash) which loads kernel in memory (from flash), verifies signature to see it hasn't been tampered with, if it's not ok sets knox flag, then boots kernel. (more infos here)

Maybe he can just "boot to kernel" without involving the bootloader (something like an "hot boot")

Problem isn't in the rom you flash through MOP, it's in the MOP itself, 'cause to flash roms it uses a custom, not samsung signed, kernel.

Almost right. In exynos phones it can be reset. In qualcomm ones they use an efuse inside the chip itself. Once burnt it's gone forever.
[Galaxy S 5 General] u1988:
[MENTION=3535808]wajiman[/MENTION]

If you have 4.4.4 allready you can try flash NE4 unless Samsung decides to block that option in 4.4.4 (like [MENTION=2743227]gee2012[/MENTION] said)

Same goes to 5.0 Lolipop?

But,what about Note 4 ? there noting to downgreat or to do to prvent the knox from trigger, right?

if you have root right now and you want to upgreate:

Mobile Odin PRO (requires root) so you need to upgreat with root

like in here?

or like in here with pic only flashing the new 4.4.4:

look for "Installation Instructions: If you're coming from NEATROM (KNOX 0x0)"

But -Tick "Everroot" to keep the root unllike in this link Instructions the rast are the same I suppose..

http://xdaforums.com/galaxy-s5/development/rom-neatrom-v1-t2828562
[Galaxy S 5 General] wajiman:
yes but i think the phone will not work correctly on 4.4.4 with a NE4 kernel, so the best choice we have is to update using Mobile Odin Pro to Android lolipop 5 and 4.4.4 to keep root

yes, nothing is there for Note 4 as of now and no downgrade is available

yes you need to upgrade with root using Mobile Odin pro and tick Enable Everroot option

and under this heading "installation Instructions: If you're coming from NEATROM (KNOX 0x0)" in that thread, nowhere it is written "-Tick "Everroot" to keep the root...". Only Un-tick Everroot is written. so i might have not got what you actually meant there:good:
[Galaxy S 5 General] kuraiholy:
I went to sammobile but it didn't seem to have the older NE2 firmware for my G900a. It does seem to have my latest, so i can get that and use the script to get that part in order. But what older kernal do I use for the towelroot to work on that model?
[Galaxy S 5 General] wajiman:
do you know which older firmware supported towelroot for 900a?
[Galaxy S 5 General] kuraiholy:
I sure don't, I upgraded OTA after it pestered me for so long. I was reading on Sammobile but I don't see like a list of previous firmwares for it.
[Galaxy S 5 General] wajiman:
look here for your device:

http://xdaforums.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299