Database Users

[Q] CMW success, SU fail :(

Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.

jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used

leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.

jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.

leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager

actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.

No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card

scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice

jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!

Do I need to flash TWRP first to flash PhilZ touch? G900F UK

Thanks for reading. When I received my phone a week ago, I was burnt twice before when flashing CF Autoroot and then PhilZ via Odin and wouldn't get past the logo, so I flashed TWRP and it was a nightmare just to get into recovery. I gave up and used KIES to go back to stock.
So, in as simple an explanation as possible, please can you tell me how to install a root kernel onto stock 5.0 build BOD3 so I don't lose anything?
Thank you very much?

aRc. said:
Thanks for reading. When I received my phone a week ago, I was burnt twice before when flashing CF Autoroot and then PhilZ via Odin and wouldn't get past the logo, so I flashed TWRP and it was a nightmare just to get into recovery. I gave up and used KIES to go back to stock.
So, in as simple an explanation as possible, please can you tell me how to install a root kernel onto stock 5.0 build BOD3 so I don't lose anything?
Thank you very much?
Click to expand...
Click to collapse
i suggest you read the dev sction in depth

-PiLoT- said:
i suggest you read the dev sction in depth
Click to expand...
Click to collapse
Thanks for that condescending reply. The dev section is such a mess, there's no organisation whatsoever and if I wanted to flash an entire new ROM, I would, but I don't.
Hence my request.

Which Device?
Sent From Nexus 6

Galaxy S5 SM-G900F
Lollipop 5.0
Build LRX21T.G900FXXU1BOD3

Have you tried installing the custom recovery using the TWRP MANAGER app? Worked for me!
It on PlayStore

aRc. said:
Thanks for that condescending reply. The dev section is such a mess, there's no organisation whatsoever and if I wanted to flash an entire new ROM, I would, but I don't.
Hence my request.
Click to expand...
Click to collapse
it wasn't a condescending reply, it just seemed that way.
firstly, if you can concentrate the dev sections aren't that bad, secondly no one mentioned rom flashing at all. ever. in fact you never even explained what you needed to flash recovery for.
i was offering you the chance to hunt for the answer like we had to but since you need the help ill give it
this thread for twrp
TWRp is what i use to flash stuff if i want to and it works fine but if you want philz then all you have to do is go here go to klte and download the odin version, then flash via a pc
the problem you had was because the odin chainfire root is slightly ****y an you need the recovery flashable version. so you put philz or twrp in the phone and flash the chainfire root via the recovery,
now i apologies if you thought that i was being condescending but i got all that info from the place i pointed you to earlier, theres no reason you couldnt have done it aswell. i was trying to help by pointing you in a direction, but no ones here to spoon feed. you dont learn anything from it.

Apologies, as it seemed that way, but you have been helpful in your reply.
So I can flash this TWRP > https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar.html. Does flashing TWRP give me SuperSu or is that something separate I need to install?
I don't expect to be spoon-fed, I like to learn things, but this stuff is so delicate that I want to make sure I'm using the right files.
Thanks in advance.

aRc. said:
Apologies, as it seemed that way, but you have been helpful in your reply.
So I can flash this TWRP > https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar.html. Does flashing TWRP give me SuperSu or is that something separate I need to install?
I don't expect to be spoon-fed, I like to learn things, but this stuff is so delicate that I want to make sure I'm using the right files.
Thanks in advance.
Click to expand...
Click to collapse
no twrp is a recovery, a custom recovery which makes it easier to flash non official firmwares. install twrp via odin, then flash the chainfire root via twrp flashing, the chainfire flash root will gove you super su

As it happens, TWRP installed SuperSU automatically.

Looking for Testers with the T817 model to test new root hack.(tested and working)

NOTE: NOW CONFIRMED TESTED AND WORKING FOR THE T817T/W AND T817P MODELS.
Looking for testers with the T817 model (no ATT or Verizon models) to test a new hack to get root on Samsung stock SElinux Enforcing kernels running Android 5.11 or Android 6.0.
This means the kernel will be stock, so LTE will be unaffected.
Basically what this is about:
Chainfire has released new beta's of Supersu, the latest is 2.52. This new release can root Samsung 5.1.1 roms and Android 6.0 Marshmallow roms.
However to accomplish this a patch needs to be applied to the kernel Ramdisk to allow root with stock kernels.
What does this mean? This means if you have a T817 running Lollipop 5.1.1 then you can gain root and retain LTE connectivity as it uses the stock kernel instead of having to flash a permissive T810 wifi only kernel.
I need someone willing to test the patched Ramdisk and kernel on their device which has 5.1.1 installed.
The procedure is fairly simple all that is required is to flash the new boot.img, then root with Supersu v2.52.

Here is the patched boot.img for anyone that wants to test it.
*It goes without saying make a back up with TWRP first! *
FOR SM-T817T/T817W
Extract the boot.img from the zip then Install with TWRP:
Tab_S2_t817_boot.zip
FOR SM-T817P
Extract the boot.img from the zip then Install with TWRP:
Tab_S2_T817P_boot.zip
Then root with BETA-SuperSU-v2.52 using TWRP

I have a t817p I would be happy to test, how do I install twrp without root though?
Sent from my SM-T817P using Tapatalk

saramon said:
I have a t817p I would be happy to test, how do I install twrp without root though?
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
If you have an SM-T817P I will upload a specific boot.img for you.
You dont need root to install TWRP, just install with ODIN.
Install with TWRP: Tab_S2_T817P_boot.zip
Stock Recovery if required: T817PVPU1AOH6_recovery

Flashed it, and I'm getting LTE

saramon said:
And I eagerly await the upload, I got TWRP installed
Click to expand...
Click to collapse
Important: make a full back up with TWRP first!

saramon said:
Flashed it, and I'm getting LTE
Click to expand...
Click to collapse
Do you have root?

Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk

saramon said:
Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
So we can say we have success?
You are the first one to have root and LTE on a 5.1.1 S2 tablet!

Just to be sure, this does work with the Tmobile T817T, correct?
Edit: found answer.

graysooner said:
Just to be sure, this does work with the Tmobile T817T, correct?
Edit: found answer.
Click to expand...
Click to collapse
No idea. Nobody has tested it yet and come back with the answer.
Still waiting...

ashyx said:
So we can say we have success?
You are the first one to have root and LTE on a 5.1.1 S2 tablet!
Click to expand...
Click to collapse
I'd say so, great job!

Willing to try, but a question. If I flash with Odin, is TWRP installed also?

graysooner said:
Willing to try, but a question. If I flash with Odin, is TWRP installed also?
Click to expand...
Click to collapse
You have to flash twrp first. You will find my builds of TWRP in the development section.
Flash the 5.1.1 t810 version.

can't get into twrp
ashyx said:
If you have an SM-T817P I will upload a specific boot.img for you.
You dont need root to install TWRP, just install with ODIN.
[/URL]
Click to expand...
Click to collapse
i flashed the boot patched file odin is successful it says but kernel is not seandroid enforcing and will not boot into twrp, boots into stock recovery still

Aikavaras2015 said:
i flashed the boot patched file odin is successful it says but kernel is not seandroid enforcing and will not boot into twrp, boots into stock recovery still
Click to expand...
Click to collapse
That message is normal.
What you have to do is after flashing twrp you need to directly boot into twrp to prevent the stock recovery overwriting it.
Flash twrp again but disable auto reboot in Odin.
After flashing reboot by holding POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.

i did that, still booted into system not twrp
ashyx said:
That message is normal.
What you have to do is after flashing twrp you need to directly boot into twrp to prevent the stock recovery overwriting it.
Flash twrp again but disable auto reboot in Odin.
After flashing reboot by holding POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Click to expand...
Click to collapse
still no twrp. just goes to stock. I have tried both times with autoreboot off, once with f reset checked and another with f reset unchecked.

Aikavaras2015 said:
still no twrp. just goes to stock. I have tried both times with autoreboot off, once with f reset checked and another with f reset unchecked.
Click to expand...
Click to collapse
Don't mess with f.reset
Honestly this is purely about timing. Plenty have already done it with the same device as you.
As long as you are flashing the correct twrp file then you should be good after following the advice above.
Can you flash twrp then post me a screenshot of odin?

How did you get xposed working?
[/U]
saramon said:
Yup, sure do, got xposed installed too
Sent from my SM-T817P using Tapatalk
Click to expand...
Click to collapse
I have the T715 but can't get xposed to work

LeeLongLang said:
[/U]
I have the T715 but can't get xposed to work
Click to expand...
Click to collapse
Please, this thread is only for testing the above kernels.

Do I need to unlock the bootloader?

Hello!
I want to finally install a custom rom for my phone (GT-I9301I) but to do that I want to install TWRP. Every tutorial on how to install TWRP just use odin and phone in download mode despite the fact that in a lot of places it is said that you need to have an unlocked bootloader to flash a custom recovery. (Also in CF-auto root webpage it is stated that bootloader needs to be unlocked). But do I really need to unlock the bootloader (yes, I am new to this) to flash a custom recovery when using Odin? And after the TWRP is installed I can just use CF auto root and then install the ROM, right?
I would greatly appreciate your help !
Thanks in advance,
TheKiloOhm

I'm pretty sure, that S3Neo+ has an unlocked bootloader.

There is a way to flash a recovery without a PC. Use Flashify just from the Play Store.
Sent from my GT-I9301I using Tapatalk

sasd123 said:
There is a way to flash a recovery without a PC. Use Flashify just from the Play Store.
Sent from my GT-I9301I using Tapatalk
Click to expand...
Click to collapse
But I need root access which I can get by flashing CF auto root.
Is Towelroot considered as a common rooting tool?
RometVinnal said:
I'm pretty sure, that S3Neo+ has an unlocked bootloader.
Click to expand...
Click to collapse
Is there a way I can check it? When I boot into recovery it doesn't show anything about lock/unlock state.

TheKiloOhm said:
Is there a way I can check it? When I boot into recovery it doesn't show anything about lock/unlock state.
Click to expand...
Click to collapse
Well.. Try booting to download mode. (Vol. and center button down on boot). If you want to root you should download custom recovery. I recommend TWRP.

Ok, first of all..
I AM REALLY HAPPY SOMEONE MENTIONED THIS AT LAAAAAAAAAAAAAAST
Now.. I have this device.. and mine is bootloader locked
our s3ve3g is definitely locked...
and I tried to flash TWRP using ODIN and I ended up looping (Read)
So Take Care ...
Been trying to find a way to unlock this thing for a while now... will post my findings here or on my blog if I ever find anything
Edit: Did I mention that some variants of our specific device are locked and some are not !!
and I can't figure out the difference...

Found this
and it pointed me to this
but I don't have time to test now...

OK... I think I found the answer...
According to IanWorthington
http://forum.xda-developers.com/showthread.php?p=66377330#post66377330
FIXED: This TWRP requires 4.4.4. It does NOT work on 4.3.

Samsug bidn't lock bootloader for s3 neo i have a i9301i and i can do anything with it recoevry root vustom rom kernel flashing. ANYITHING. So i think it deneds on serial nunber or something

Help with root on an uncommon S5 build

Hi guys, I'm tired of searching for a safe root method for my G900F, but I can't find any solution which considers my build number:
MMB29M.G900FXXU1CPEM
Although my baseband shows:
G900FXXU1CPC9
Can you guys help me to understand what I need to root my S5?
Thanks in advance for your time.

Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537

6Maverick6 said:
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
Thanks man. That thread warns about using roms which aren't exactly our model number and that seems to be my problem.
Although I have a S5 G900F (kltexx) my build ends in ...XXU1CPEM and chainfire's auto-root doesn't have it listed.
For what it's worth, sammobile lists my rom as having PDA G900FXXU1CPEM and CSC G900FTPH1CPE2
Also, chainfire's thread where we're supposed to point to new published stock roms doesn't allow me to comment, so I guess it's a dead end.
Is there anywhere where I can search?
Thanks again mate.

All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find

*Detection* said:
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
Click to expand...
Click to collapse
Thanks for your reply.
Although I also usually lecture people, in my own field of expertise, on how they shouldn't come to me with a problem without trying everything to fix it, I also try to be helpful in showing them the path that may enable them to help themselves.
Your answer does nothing for me, but thanks. I'm also aware that it shouldn't do anything for me, because of (insert jibber jabber about how these foruns are for developers and how rooting and custom roms will never be mainstream because the casual user isn't smart enough to press all the buttons in the correct sequence and developers need their time to be developing and not answering programming-illiterate people).
Anyway, if anyone else could point me, tip me, give me an innuendo in the right direction, I would be thankful. I'm not an expert, but since I've rooted my S4 (i9505) with chainfire's auto-root and loved CM12.1 and now CM13 roms, I was expecting to find a way to root my S5 (G900F) with these uncommon baseband and build numbers I've printed.
By the way: a search in xda-developers with my baseband shows 7 results, none of which concerns a rooted rom or specific method to root it. I know, because I've checked it before I bother everybody on this forum.
Thanks in advance guys.

You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP

*Detection* said:
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
Click to expand...
Click to collapse
Thanks man. Could you just answer me one last question? From your pointer and what I've read so far, this is what I think I understood already, could you let me know if this is by any chance a misinterpretation or am I in the correct path?
1) Since there's not an auto-root package with my baseband and build number I should resort to conventional root: installing a custom recovery, superuser and a custom rom like CM13.
2) Also, I now understand that, CF-Auto-Root would never help me to install CM13, because it just provides root access, nothing else, like CF's says.
3) Rooting with Supersu after installing a custom recovery isn't build or baseband dependent. Auto-root is, because it's basically your ROM rooted. Rooting with TWRP/SuperSu is just model dependent, so I would be fine with klte specific TWRP at https://dl.twrp.me/klte/ and a compatible SuperSu build.
My last question if you have the time, because I've searched for it and cannot find a clue: is it possible that my SIM-free G900F variant, has a locked bootloader? How can I check it?
Thanks again for your patience.
EDIT: dumb numbering.

G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM

*Detection* said:
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
Click to expand...
Click to collapse
Thank you so much man. The fact that you took the time to include the version numbers is awesome. I'll use TWRP because that's what I had in my S4 and worked really great. I believe I'll encounter small issues, but after your push I'll search for them in the forum. You're right, I was forgetting that CM13 has a built-in superuser manager. Thanks again.
The really scary part for me is the custom recovery install, because of bootloops or bricks.. but from what I've read so far I just need to be careful with checking and unchecking the right stuff in Odin and removing the battery after the green pass and before the device reboots. In some threads it's said that one should uncheck "auto-reboot", others say it should be checked, which is a bit confusing. I've seen in this thread http://forum.xda-developers.com/galaxy-s5/help/g900f-stuck-odin-mode-t3378907 that you advise to "uncheck it". Is it always the case?
Ok. This was really the last question.
Thanks again mate. You were really helpful and I'm sorry if I came across as annoying.

Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it

*Detection* said:
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
Click to expand...
Click to collapse
Hey man, just to let you know that everything went smooth like you said it would. Thanks again.

No probs, glad to hear it

lol
i was searching for a theard like this.
After 5 years i found it. I have the same baseband and build number. I have android 6.0.1.
will it still work? Im so much afraid of bricking my phone :crying:
Edit: Rooted succesfully.
Thanks a lot