Related
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
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.
Well, guys I would apreciate some help.
I have FRD-L09C432B381 with TWRP & Root, but I have same weird experience:
1) after instaling SuperSU update, the binaries couldn't get to install and I have found no other way. It seemmed to work anyway but I always had to revert back to SuperSU v2.79 EMUI 5.0 version for being stopped bullied by SuperSU demanding to update binaries,
2) for example GSM Battery Monitor has it's own Root Companion app, which requires to be instlled as system priv app, but even when it's allowed by SuperSU it won't,
3) in TWRP I can't get into internal memory, or I am just way far from finding it, but when OS is on, it says that the internal memory is mounted as /storage/emulated, but I don't see it in TWRP.
I am not sure if this is just a coincidence or it has some more poetic explanation but I believe that something goes wrong with ROOT on Android N version of Honor.
Thanks for any more funded opinions.
I did managed to do step 2)... it was almost as hard as uninstalling some system apps... through Solid File Explorer and changing permissions of files. The rest is still a mystery.
I have found topic for SuperSU on EMUI 5.0. Question 1) is thereby solved there.
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've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
iBreakStuff said:
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
Click to expand...
Click to collapse
It may be having a conflict with cached data from the version that you installed, removing the cached data might allow you to install the version you want.
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Click to expand...
Click to collapse
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
iBreakStuff said:
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
Click to expand...
Click to collapse
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So I tried what you suggested, I got the same result. Maps uninstalls but still lives in the root directory. Not being an ADB expert I went into adb shell super user mode and tried the the rm command to delete the folder, also the remount system command. Neither of those worked. Trying to install the older APK results in "App not installed"
And yes I have Magisk manager. It installed the latest version automatically. I use RootExplorer and it has superuser permissions.
Would something like this work? I'm not completely clear on how this works.
https://www.isrgrajan.com/how-to-copy-and-delete-files-in-android-using-recovery-mode.html