Develop Bugs

Flashing Recovery Problem!

RESOLVED SEE POST #6
Hey guys,
I am having trouble flashing a custom recovery (TWRP) to be specific on my brothers Note 2. I was able to easily do it with my phone but I didnt update OTA to the latest ATT software.
I have the latest samsung drivers installed too.
So in general.
1. My brother updated OTA
2. I use odin to try to flash TWRP via PDA
3. It says success but when I reboot into recovery it goes into the stock android recovery instead of the custom one
4. ??? perplexed

is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.

cortez.i said:
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
Click to expand...
Click to collapse
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"

mc704 said:
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
Click to expand...
Click to collapse
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.

cortez.i said:
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
Click to expand...
Click to collapse
what about ODIN doesn't it root the phone when you flash a custom recovery?
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused

mc704 said:
what about ODIN doesn't it root the phone when you flash a custom recovery?
Click to expand...
Click to collapse
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
mc704 said:
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
Click to expand...
Click to collapse
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.

cortez.i said:
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
Click to expand...
Click to collapse
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:

mc704 said:
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
Click to expand...
Click to collapse
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.

cortez.i said:
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
Click to expand...
Click to collapse
just a quick update.
I flashed CF-autoroot, TWRP, and a custom rom! Everything works great!
Thanks for the help!

[Q] which recovery after root?

Howdy, I plan on rooting my tablet in a few days. The instructions say to root, then, flash stock recovery. Is flashing the stock recovery necessary if i plan on using goo to install twrp recovery prior to flashing cleanrom on my device?
Also, the cleanrom thread says to flash the appropriate version of twrp. Am I to assume the latest version on goo is the ticket for that?
Also, while the dev has indicated there will be further versions after 1.2, can I expect to simply download updates, or expect to flash new versions every time? I guess this particular question doesn't really matter I'm just interested.
And finally, has anybody used heimdall with any success with the p600? Google says no...
I would have posted this on the clean rom thread but was not allowed since I have not had enough posts yet. moving this to there would not hurt my feelings.
I appreciate any and all help and of course feel appreciation and give thanks to the developers who have put in such great effort. Thank you.

sleekmason said:
Howdy, I plan on rooting my tablet in a few days. The instructions say to root, then, flash stock recovery. Is flashing the stock recovery necessary if i plan on using goo to install twrp recovery prior to flashing cleanrom on my device?
Also, the cleanrom thread says to flash the appropriate version of twrp. Am I to assume the latest version on goo is the ticket for that?
Also, while the dev has indicated there will be further versions after 1.2, can I expect to simply download updates, or expect to flash new versions every time? I guess this particular question doesn't really matter I'm just interested.
And finally, has anybody used heimdall with any success with the p600? Google says no...
I would have posted this on the clean rom thread but was not allowed since I have not had enough posts yet. moving this to there would not hurt my feelings.
I appreciate any and all help and of course feel appreciation and give thanks to the developers who have put in such great effort. Thank you.
Click to expand...
Click to collapse
That's a lot questions! Lol.... here's two answers:
If you want to flash CleanRom, then you don't need to root your stock rom, just use Odin to flash TWRP and that will either let you install CleanRom or let you install SuperSU (root). You can the recovery from their website.
I'm on the P600 and the goomanager didn't install the recovery correctly, so I had to flash with odin.
I don't know about Heimdal. Good luck on your ten posts
Sent from my SM-P600

Odin eh?
grmcrkrs said:
That's a lot questions! Lol.... here's two answers:
If you want to flash CleanRom, then you don't need to root your stock rom, just use Odin to flash TWRP and that will either let you install CleanRom or let you install SuperSU (root). You can the recovery from their website.
I'm on the P600 and the goomanager didn't install the recovery correctly, so I had to flash with odin.
I don't know about Heimdal. Good luck on your ten posts
Sent from my SM-P600
Click to expand...
Click to collapse
My understanding is that root is neccesary to flash twrp. If that is not the case, they why use Odin at all?
Heimdall is a program reverse engineered to work on Samsung devices. Potentially more stable than odin. Open source. I use a linux box but will have access to a windows box in a week or so.

supersu
Furthermore, for verification, super su does not root your device, it only manages the permissions of those programs that need root access. Can somebody else chime in for verification?

sleekmason said:
Furthermore, for verification, super su does not root your device, it only manages the permissions of those programs that need root access. Can somebody else chime in for verification?
Click to expand...
Click to collapse
No, you CAN flash recovery without rooting, and if your not rooted then TWRP asks if you'd like to install SuperSU and root that way. I guess you don't have to believe me though
Sent from my SM-P600

grmcrkrs said:
No, you CAN flash recovery without rooting, and if your not rooted then TWRP asks if you'd like to install SuperSU and root that way. I guess you don't have to believe me though
Sent from my SM-P600
Click to expand...
Click to collapse
that sounds great but doesn't TWRP need root in order to be installed? my understanding is yes. If not I should be able to install it using Goo manager. from what I've read the developers for GooManager are very serious and would not allow a non working application to remain in their program.

sleekmason said:
Howdy, I plan on rooting my tablet in a few days. The instructions say to root, then, flash stock recovery. Is flashing the stock recovery necessary if i plan on using goo to install twrp recovery prior to flashing cleanrom on my device?
Also, the cleanrom thread says to flash the appropriate version of twrp. Am I to assume the latest version on goo is the ticket for that?
Also, while the dev has indicated there will be further versions after 1.2, can I expect to simply download updates, or expect to flash new versions every time? I guess this particular question doesn't really matter I'm just interested.
And finally, has anybody used heimdall with any success with the p600? Google says no...
I would have posted this on the clean rom thread but was not allowed since I have not had enough posts yet. moving this to there would not hurt my feelings.
I appreciate any and all help and of course feel appreciation and give thanks to the developers who have put in such great effort. Thank you.
Click to expand...
Click to collapse
You wont need to root if your intent is to just flash my ROM.
Appropriate version would be 2.6.3.3
As far as updates / patches... Depends on the issue. Mostly do full updates if something changes. If its a bug fix then I would just do a patch.
Hemidall? No, never tried it.
Basically to flash a custom ROM you just need to flash TWRP using Odin then flash the ROM using TWRP.
You dont techincally need to root unless you want to stay stock and have root. But that is no fun!
Also, the goo.im app does not work with this device so you have to use Odin manually (for simplicity).
Hope this helps!

sleekmason said:
that sounds great but doesn't TWRP need root in order to be installed? my understanding is yes. If not I should be able to install it using Goo manager. from what I've read the developers for GooManager are very serious and would not allow a non working application to remain in their program.
Click to expand...
Click to collapse
I read the TWRP thread, and others are having problems installing through goomanager. I also wanted to install it that way, but it wouldn't work. But it didnt work. It also wouldn't flash through the stock recovery. Hence, odin.
Sent from my SM-P600

thank you for the clarification! in order to flash TWRP in Odin do I simply use the AP slot as you would to flash autoroot by their directions?
one of the things thats tripped me up is that on the TWR P site as well as in Google Play it says you must have a rooted device. This would suggest that in order to get TWRP on your device it would already have to be rooted. it seems strange to me that the tablet will allow odin to install it on a non rooted device.
hoops I guess. So being a non Windows user, that is not familiar with the Windows operating system,( bet you don't hear that everyday) ,I would suppose the order would go something like this.
1 download Samsung drivers from kies.1
2. Download TWRP from site for odin.
3. Open odin.
4. go to download mode on device.
5. Plugin device and wait for it to be recognized.
6. Drag the Twrp zip for odin to the AP slot, enter,
7. Wait for it to .......?
8. Reboot.
9 download the cleanrom rom.
10. Reboot into recovery
11. Installcleanrom
12 enjoy.
a couple of other questions concerning the SD card. Should I leave it in during any or all of these processes? I've seen where other people have had problems with their SD card not being read is this due to it not being installed when they install clean rom? I really do appreciate all the help.
not breaking my device by doing something stupid is paramount. Lol! as I will be using my daughters computer any other information regarding the installation of the Samsung drivers or Odin would be much appreciated I do not want to hurt her computer.

I kept my SD card installed while flashing TWRP in Odin and had no problems. If you're worried then take it out. As far as Odin goes... run it as an admin and after connecting your Note (in DL mode) just click on "AP" and navigate to the directory where you saved the TWRP file. From there just hit "start" and your good to go. Odin isn't gonna mess anything up on your daughters pc and if you have a copy of the stock recovery just reflash it if you run into problems with TWRP. Also, read through all the different threads/watch YouTube videos. Most of this has been covered many times over and you can see what success or problems others have had.

SuperSU Error after cf-auto

Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.

Try the flashable version in this post after you install a custom recovery with odin.
ramjet73

ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?

mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73

ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.

I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73

OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?

mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73

ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X

You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®

done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.

Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73

there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root

hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.

mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.

mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73

How to remove Root from Galaxy Tab S?

I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks

There is no update. 5.0.2 is the latest.

ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!

MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?

MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck

3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:

If you want to go back to stock just flash the latest firmware with odin.

Have to flash SU systemless

It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!

No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.

nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.

StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.

@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su

nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.

tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.

nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.

tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su

nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.

No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe

otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.