Database Info

[Q] Root CAT b10

Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.

cabrerachaparro said:
Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.
Click to expand...
Click to collapse
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.

ninr said:
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.
Click to expand...
Click to collapse
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.

cabrerachaparro said:
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.
Click to expand...
Click to collapse
OK, that's no problem.
Attached package contains few another packages....(update.zip is the same like I uploaded here before)
1. Try to use "Superuser-3.1.3-arm-signed.zip" (this should be enough but I don't know why it isn't)
2. Reboot
3. Look at Superuser app
4. If Superuser app doesn't work then use "update.zip" once again
5. Reboot
6. Look at Superuser app
7. Now it should be working if not you can update Superuser app from market and try above procedure once again
Root this phone is really long term job. But never give up!! This phone is useless without root. I have been rooting this phone more then week.
Good luck and post if will you be successful.

just wondering since you have some experience with the phone.is there a custom rom for this phone or just the original one?

[Q] Tf700 Root/Superuser stopped working??

All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge

iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.

iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and

Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.

buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.

iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.

iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.

buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.

You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.

Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!

buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?

iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.

buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge

I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?

IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .

buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...

IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.

I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.

IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?

sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...

Problems with installation of Marshmallow on a Tab 2 5113 with 4.1.1

I hired someone not super familiar with flashing a custom rom, but who knew more than me. We got MM installed but I am having some problems. First, the only reason, I updated the rom was to get mirroring. However: 1. there is no mirroring, but there is cast. I have a Tab 4 and mirroring works perfectly with it and KitKat. I tried about 5 mirroring apps from the Play Store and they all require that the Smart TVs I have (Samsung and LG) be connected to the Internet because using the TV's internet connection is a major nuisance for me. That is not required with my KK Mirroring, and I am wondering whether I should get rid of MM and flash KK. Or, is there an app that will work without mirroring. 2. My SD card is now invisible. When I link my Tab to my windows 7 computer, my SD card doesn't show. (Additionally, come to think of it, none of my files show. All I get is an image of 5100, but when I click on it nothing shows on my windows 7 computer.) 3. Probably related to No. 2 -- Some apps seem to install, but I have no way to access them because no shortcut is placed on the screen and I have no tree of files. (Titanium Backup for instance, can't be accessed. However, when I downloaded ai-keyboard, it mostly worked)
Hate to ask so many questions, but this is what I now have. Would call the person who did the flash, but his wife is due any day, and for all I know, gave birth yesterday.

which M Rom did you installed? kindly mention Rom and recovery build number as well.
are you using any other home launcher than the default? how did you installed titanium backup? normal or copy pasted apk to the system partition?
have you checked the luncher setting? for instance I can hide some apps from the nova launcher but can find it with it's search bar.
check with the default launcher or any other.
did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?
I haven't tested screen mirroring with this device. although I checked briefly with a Samsung S, S4 and a G3 on a LG smart tv with webOS 3 using LG TV plus app, I had to be on a same network with wifi hotspot enabled from my device (didn't required a working internet) and selecting LG tv plus option from the TV.
I still haven't been used to with screen mirroring and cast. so others can help.

Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.

decijp said:
Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
Device specific builds are too outdated. Kindly flash these depending on your model
Espresso3g - P3100 & P5100
EspressoWifi - P3113, P5113, P3110, P5110
For more info, visit this thread http://forum.xda-developers.com/gal...fied/rom-cyanogenmod-13-cm13-0-t3303798/page1
And flash it with the latest TWRP recovery found on andi34.github.io under recoveries
Sent from my espresso3g using XDA Labs

Root is enabled through developer options. Go settings, about tablet. Tab build number 7 times. Back out and open dev options. Scroll down a bit and enable roo & adb. You should be good to roll then
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.

decijp said:
Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.
Click to expand...
Click to collapse
if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery.

decijp said:
Hi Billys,
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well

billysam said:
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well
Click to expand...
Click to collapse
Billys,
There was no CM logo, but went to settings and USB and you were right. Now I can view the files of my tablet on my PC. Thanks a lot.

Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?

decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
It won't automatically get the zip file because you select the zip you flash. Just navigate to whet you put the zip and flash that
Sent from my espresso3g using XDA Labs

decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
install the latest twrp by using cwm. after install reboot back into recovery. you shuold see the graphical differences between twrp and cwm.

To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.

decijp said:
To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.
Click to expand...
Click to collapse
If you installed CM13, is actually pre rooted. Just enable it from the developer settings
Sent from my espresso3g using XDA Labs

Finally figured out that I could transfer SuperSu zip file to my Tab and then install it from TWRP. Did so and also wiped clean the cache and now SuperSu is functional and I can get rid of the bloatware and speed up the Tab. Thanks for everyone's help.

Help with Samsung s5 root!

Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be!
Thank you in advance!

CloeNi said:
Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be! Thank you in advance!
Click to expand...
Click to collapse
Since you can flash custom recovery then your bootloader is already unlocked so....
Do a search for "flashing SuperSU.zip Galaxy S5" or you might need to search for "flashing SuperSU.zip in systemless mode galaxy s5". Flashing one of those should give you root and su binaries, after flashing, boot the device and open the SuperSU app and update the su binaries then reboot the device. Then after rebooting, you need to go to system settings>developer options>root access and set it to "apps and adb", then install a file manager that has a root explorer such as ES File Explorer, then open it, tap the menu button, go to the "TOOLS" tab, find "Root Explorer" and turn it on, then when you see the next menu, tap "Mount R/W", then set all listed partitions to "rw".
If you can access your SELinux profile, make sure it's set to "permissive" mode.
If you can get all of that set then you'll have access to modify and control pretty much anything you want about the device.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

thank you!!!
i wont be able to try it for a few days but i'll try it as soon as i can and give you feedback on this!

So i'm trying to follow your instructions right now. I guess it's ok if i install recovery upon recovery and SU upon SU without first removing the "faulty" one?
Cause i have done the first steps a lot these days
edit: i flashed again aaaaaand nothing new happened. The SU binary is nowhere to be found :/
some say it could be a problem of the cable or the computer?
Should i try from a different pc and cable? I do not really understand it but i'll give it a try later
edit 2: i retried from another pc and another usb cable, the same happens. Does not install the SU through the recovery
I installed the SuperSU (actually enebled it again and updated it) from playstore and opened it and it says the sme thing again. Can't find su binaries and stuff.
What should i do? Is format a solution or can avoid it?

Trying to Root phone using SuperSu - need help.

Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.

a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing

Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.

tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!

@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.

tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..

@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.

tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.

@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “

tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?

@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.

tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.

tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.

tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.

Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.

tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs