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] TWRP replaced with stock recovery[t805]

I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for
Android 4.4 KitKat: Google Making Root Without Unlocked Bootloader Difficult?
Click to expand...
Click to collapse
(sry can't link)

JoeRifle said:
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for (sry can't link)
Click to expand...
Click to collapse
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?

The question would be why you didn't use the recommended way of using Flashify to flash twrp?

Eddie Hicks said:
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
Click to expand...
Click to collapse
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
kenkiller said:
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Click to expand...
Click to collapse
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?

JoeRifle said:
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
Click to expand...
Click to collapse
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.

kenkiller said:
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
Click to expand...
Click to collapse
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:

JoeRifle said:
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
Click to expand...
Click to collapse
You don't get by in XDA by being cautious in everything. There's enough reports to tell otherwise.
Yes, using Flashify to flash TWRP replaces stock recovery. TOTALLY.

Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.

JoeRifle said:
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
Click to expand...
Click to collapse
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.

kenkiller said:
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
Click to expand...
Click to collapse
I just need to get the hang of these appy lil spy thingy thing things...god knows what g**gle has in store for you. out of curiosity, so you are saying there is no hash check in the bootloader keeping me/us from doing our evil deeds? how about the article up there I quoted, and what the heck happened when i odined TWRP?
just asking...will flash the CF. so lets cross thumbs and make tha knox trip count

Hi Guys. As following the instructions to flash openrecovery-twrp-2.8.0.1-chagallwifi.tar using Odin3 v3.09, my T805 reboots into recovery, the TWRP boot screen is blurred, and after the Menu appears, my device locks up and there is no way to reboot it. Force reboot by holding down the Power button doesn't work. I've been trying for nearly an hour and nothing works. The Task Menu and Return buttons are lit, but the screen is blank. Any suggestions on how to get my T805 to reboot normally?
Thanks.
UPDATE:
I found that 2.8.0.1 appears out of alignment on the screen, and I had to poke around until I found where the Reboot button was located. By chance I got it to go into Bootloader and the system rebooted. Once online I installed Flashify and installed TWRP 2.7.1.1 and SUCCESS!! Now my T805 is working normally. WHEW!!

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

[Q] [IMPORTANT] Is there any way I can root htc one m8 Lolipop 5.0?

Someone if you know and tested it, can I root my htc one m8 device having the new firmware updated 5.0.1 lolipop??
Please anwser and if there is a way please send a link
THANKS A LOTTT!!

It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a rom , likely rooted already.
?

Darth said:
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a room, likely rooted already.
Click to expand...
Click to collapse
thanks for that but when I did it in my phone it says su binary out of date! what can I do now?

Can you explain everything you did, beginning to end. And exactly when/where you get that message?

I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing

Koukosftw said:
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Click to expand...
Click to collapse
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.

i did that too nothing happened :/

xunholyx said:
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
Click to expand...
Click to collapse
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.

Darth said:
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Click to expand...
Click to collapse
I tried the normal it didnt work, how I do the second, I pressed it but nothing happened!

I don't think you have twrp installed anymore, or not properly. You've flashed it with fastboot, since updating to lollipop? How did you update to lollipop?

Normal, I never had root before. Upgraded my phone to 5.0 and then i tried to root it

Rooted fine here with normal method. Just had to update super su.

OK, can you please walk us through exactly what steps to Root you took. From the beginning. And we'll see what happened.
?

i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know

chinkyarmour said:
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
Click to expand...
Click to collapse
Settings > Power > Fast boot

xunholyx said:
Settings > Power > Fast boot
Click to expand...
Click to collapse
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem

chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
They must have taken the option out. It didn't boot any faster for me anyways. Not since 4.4.2

chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
SO GUYS, ITS ME THAT I CREATED THIS THREAD! PROBLEM SOLVED. I ALREADY HAD TWRP AND DOWNLOADED THE Update-supersu file from the above youtube video (links) and I did it with recovery mode. I DONT KNOW BUT THE PREVIOUS supersu I installed couldnt update the su binary. This one did it. PROBLEM SOLVED AND I ROOTED MY 5.0.1 LOLIPOP DEVICE.
THANKS GUYS FOR EVERYTHING REALLY HELPFUL!!!

recovery is not seandroid enforcing

I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.

Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?

audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.

Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.

Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html

So you twrp 3.1.1 and it will work right
I having the same issue
Thank you

so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran

timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself

Trwp
What version of twrp I need to use
Thank you

timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1

Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran

timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.

Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks

timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way

I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you

timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4

Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran