Related
I obtained root via Odin as superoneclick didn't work. Then i flashed the latest version on MIUI and I lost root access. A couple of forums said superuser needs to be enabled in the settings. However when I opened superuser and looked under preferences there was no toggle to enable it.
Sent from my SGH-I997 using XDA App
Download rom manager. Go to download rom in rom mannager. Select superuser. Download superuser 2.3.6.3 efg. Install through cwm by reboot into recovery and select install zip from sd card. You dont need to wipe anything just install zip from sd card. To find it in cmw its under clockworkmod, then download, then downloads.androidsu.com, then superuser, then the zip. Reboot and you will have root. I had this problem also this worked for me.
Click thanks if this helped you.
Use GTGs ultimate unbricker and revert to stock with superuser rights and 3e recovery
Or...
Just try to use superoneclick
Sent from a CRABThinker running Infused GB
Sent from a CRABThinker running Infused GB
Same problem
Carlrobling said:
Download rom manager. Go to download rom in rom mannager. Select superuser. Download superuser 2.3.6.3 efg. Install through cwm by reboot into recovery and select install zip from sd card. You dont need to wipe anything just install zip from sd card. To find it in cmw its under clockworkmod, then download, then downloads.androidsu.com, then superuser, then the zip. Reboot and you will have root. I had this problem also this worked for me.
Click thanks if this helped you.
Click to expand...
Click to collapse
u mean 2.3.6.3 efgh?? miui is not listed as supported in the description and the one you say to DL doesn't exist in ROM manager.
invizo said:
Same problem
u mean 2.3.6.3 efgh?? miui is not listed as supported in the description and the one you say to DL doesn't exist in ROM manager.
Click to expand...
Click to collapse
Carlrobling said:
Download rom manager. Go to download rom in rom mannager. Select superuser. Download superuser 2.3.6.3 efg. Install through cwm by reboot into recovery and select install zip from sd card. You dont need to wipe anything just install zip from sd card. To find it in cmw its under clockworkmod, then download, then downloads.androidsu.com, then superuser, then the zip. Reboot and you will have root. I had this problem also this worked for me.
Click thanks if this helped you.
Click to expand...
Click to collapse
Yes that's what I was referring to. It supports the os not the rom. So its for the version of android not the rom you are using. I followed these steps and it worked flawlessly for me. I just checked in rom manager its in there. Make sure that you installed rom manager properly. I found these instructions in the miui thread in the android dev section.
I can confirm that this is working. There is no toggle though. Just open your programs that require root again and it will ask you whether to allow or deny root access.
Worked for me. FINALLY got Superuser access again. Thrilled
Thanks going to you!
Hi guys android newbie here! My friend rooted my Nexus 5 and it was working fine for a couple of weeks. Yesterday I tried to open SuperSU and it didn't work! Other apps that required root didn't work either.
I have been looking around and it seems OTA updates may have screwed up my root. Every time I try to open SuperSU it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" If you just upgraded to Android 4.3 (I have 4.4), you need to manual re-root. Consult the relevant forums for your device!" I have used root checker by joeykrim and it says "Sorry! this device does not have proper root access" (to confirm my root is busted).
My question is, is there any way to fix this without re-rooting? If I have to re-root, can I just directly re-root it again using something like Wugs rootkit?
Thank you very much in advance!
Just flash the newest version of supersu and you'll be good to go..... http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
simms22 said:
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
Click to expand...
Click to collapse
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
seyba said:
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
Click to expand...
Click to collapse
cant even get into it?
Yea it says there is no SU binary installed. I think I've lost root access
seyba said:
Yea it says there is no SU binary installed. I think I've lost root access
Click to expand...
Click to collapse
flash this with your custom recovery, its the latest supersu http://download.chainfire.eu/supersu
bodooo said:
Just flash the newest version of supersu and you'll be good to go.....
Click to expand...
Click to collapse
I can install/update to v1.8! I just can't open it. Gives me a "SU binary not installed" when I do!
Did you install/update from the playstore or flashed the new update?
simms22 said:
flash this with your custom recovery, its the latest supersu
Click to expand...
Click to collapse
Sorry if this is a stupid question .. but how/ do I flash this or what program do i use?
My friend helped me root it so i have no idea on how to do this @@ Very sorry.
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
bodooo said:
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
Click to expand...
Click to collapse
Ok so I can't open flashify either. It also says I have lost root access and my superuser is busted. I have attached a screenshot!
http://i42.tinypic.com/2mgw0v6.png
Of course, you don't have root access, silly me lol Well guess we'll have to do it the hard way (it's not really that complicated) ok read carefully. Power off your phone, afterward hold the power and volume down buttons which should get you into the bootloader, cycle trough the options with the volume buttons and when you see recovery mode select it with the power button, now depending on which Recovery you have you'll have to choose the option that says install or install from sd card, again, depending on which one you have this will be slightly different. After doing i believe the paths will be the same, chose 0/ then look for the download/ folder which you should have that supersu.zip file, if you're using twrp recover it should be touch screen and you simply select it and swipe to install, if you're using cwm (which i do) you'' have to scroll with the volume buttons and select the file with the power button to install. I hope I was as clear as i could be, good luck
after going into recovery mode, there is just a android robot with his chest open and an exclamation mark! can't proceed after that.
Ouhhh you don't have a recovery then, do you have adb or any kind of toolkit?
I have wugs toolkit. but every time i try to do anything at all on it. It says ADB device not found? That seems to be preventing me from doing anything as well.
Do you have the adb drivers installed or/and usb debug turned on in developer settings?
how/where do i install adb drivers? I have not done so, and i doubt my friend did it when he rooted.
I do turn on usb debugging when i tried to unroot/root on wugs toolkit
In wugs toolkit it has a walk-through on how to do so, i suggest you use the RAW drivers option
I must be blind to not have seen this before. Thank you very much for your help I'll let you know how it goes!
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.
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
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me
Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse
Prompt dialog not working in amazon fire devices.
erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269