Related
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
try flashing su in recovery http://androidsu.com/superuser/
yeah thats exactly what i did...
I rooted my phone long ago and just got the new update so had to reroot it after installation... which seemed to work fine (with the older su-2.6.3.1) but sadly now that i got this nonworking superuser 3.0.7 (elf).zip in my phone none of my apps that need root access work
At this point im trying to figure how to go back to the older version (unless i can get this one working). Was just hoping i dont have to start all over as i cant even seem to reflash the older version - as it now gives me errors. Might just have to wipe the phone and start all over with the update.
But yeah so I updated the latest htc update and had to reroot my phone, I was able to flash the su-2.6.3.1 via CMR and this worked fine. It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Did you make regular Nandroid backups?
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1. I take it this isn't the case, because that backup would mean you could perform a factory restore, reflash CWM, and restore the backup. Any time you are making changes to your phone, backup before and along the way, just in case something like this happens. Titanium has its uses, but if your phone environment gets borked and you can't use it, it kind of defeats the purpose. Nandroid backups are more reliable in my book, and aren't app-dependent.
Sounds like you will have to start from scratch, although I'm unsure as to why Superuser 3.0.7 didn't work as expected. Possibly there was a conflict in moving from 2.6.3.1 to the newer version. I don't know of any specific problems 3.0.7 has with the MT4GS, and I'm running it on my phone with the latest binary without any problems. I do get an error message for one app, Quick Boot, when I use it to boot into recovery, but that doesn't stop the app from functioning as expected. I think that difficulty is related to the app itself and not Superuser.
Hopefully someone with a little more Superuser experience will chime in here. I'm afraid I don't have any ideas beyond the above.
Good luck --
--
KingCheetah
steve_77 said:
It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Click to expand...
Click to collapse
I had a similar problem before with SU after switching ROMs. Don't know if it might help but with Titanium Backup it showed that I had no busybox so I dl'ed busybox then SU wouldn't allow the apps to gain root access. Couldn't figure out what the problem was at all. Then I went to the SU app then saw that under the apps that were allowed or disallowed root access, the SU app itself was there. Once I deleted it from the list all the other apps that needed access worked fine. Hope that helps...
KingCheetah said:
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1.
Click to expand...
Click to collapse
Yeah i know - as fate would have it this is the one time i did not make a backup yet as i was hoping to gut out all the crap apps before doing a backup. Guess ill need to get more religious with the backups.
manimmal
Yeah i had Titanium Backup running with busy box before i had the "bright" idea to upgrade to 3.0.7 - but i guess i could try that but likely i might have to start-over from scratch (and forget about the 3.0.7 version) - unless anyone has any other ideas.
The only thing I can think of is perhaps the first su was flashed using one version of CMR and the second another version of CMR (updated after i installed rom manager perhaps)?
Even more interesting is the "su-2.3.6.1-ef-signed" with su having a datestamp of 8/17/2010; while the "Superuser-3.0.7-efghi-signed2" su version has a datestamp of 2/29/2008 - which seems a bit weird....
steve_77 said:
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
Click to expand...
Click to collapse
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Fuzi0719 said:
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Click to expand...
Click to collapse
do you still have the exact same zip file you used to install 3.0.7 ? (perhaps you have a slightly different one then whats available on the website)
I have no doubt that it works on some peoples devices, but i just dont know why it doesn't work on my device. I am pretty much running stock rom with the latest htc update, CMR 5.0.2.7 , rom manager 5.0.0.6 , superuser 2.3.6.1, su binary 2.3.1-ef - this works ( i have root) but if i boot into recovery and install the latest su for froyo 3.0.7 I loose root. (made nandroid backup this time)
I was thinking of trying to use chainsdd "su update fixer" in the market - but dont know how to use this app.. if it helps in debug i am also having a hard time installing busybox. i use "partitions info lite" to check status of my partitions, root access, and that i have busybox installed... i tried installing it via "busybox" [Stephen (Stericson)], which didnt seem to be recognized so uninstalled and tried "busybox installer" [JRummy16] - they are probably separate issues but who knows...
steve_77 said:
... and install the latest su for froyo 3.0.7 I loose root. ...
Click to expand...
Click to collapse
You answered your own question.
Froyo was the version of Android that predates Gingerbread.
The only official release of software for this device is on Gingerbread.
We are moving forward into Ice Cream Sandwich, but not officially.
You are basically trying to install a Windows 7 Program on Windows 95, to craft an analogy.
Stick with the gingerbread release of superuser.
The reason why the version is higher is because for the Froyo version of Android it went through more iterations.
Shame I didn't see this thread sooner, someone else had this same issue a while ago and I gave the same answer, should be around here somewhere. Would have saved you some trouble.
Some confusion here, I think...
Here's what is at ChainsDD's official site, http://androidsu.com/superuser/
Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)
md5: fc462fa0630379edbe10006b1d19d9b1
Superuser-3.0.7-efghi-signed.zip | mirror | RM Web Connect
binary only
md5: 26d08a253f1883c13561d173094d70b9
su-bin-3.0.3.2-efghi-signed.zip | mirror | RM Web Connect​
The lines after the md5 codes are links for the zip files. Superuser 3.0.7, according to the dev, is applicable to all flavors of Android as listed. This is also the exact file that I flashed and am using on my phone. There is a separate file for Donut 1.6, and it also is designated 3.0.7, but with a slightly different filename: Superuser-3.0.7-d-signed.zip.
I still think updating from 2.3.6.1 is part of the problem. If you go straight to 3.0.7 after your reformatting, it should work properly.
Also, Manimal's suggestion to check that Superuser isn't disallowed within the app itself is a great idea. It's weird, but an easy fix if this is the case.
I believe the update fixer Chains has available is to correct problems with the Superuser app updating new binaries. I don't think this would be of benefit to your situation.
Chains would be the best source for help, I think; an e-mail couldn't hurt --
--
KingCheetah
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
So why not install the working version, and then just update the binary from within the app?
That would be one way.
Sent from a digital distance.
steve_77 said:
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
Click to expand...
Click to collapse
Android 2.3.X is Gingerbread. Froyo is 2.2.X. Anyway, the SU you have SHOULD work, it is the same as I used. Have you tried flashing it via fastboot? I simply flashed the 3.0.7 version via recovery when I installed my ROM (stock 1.63.531.2).
Good day!
What is the purpose in updating BusyBox?
And what's with the custom version?
Is it really essential to update this for all user or best only for developers and modifiers?
UPDATE:
I asked before I modify this post if the "Auto Update BusyBox" above the BusyBox Pro works without Google Play in my device. I have busybox v1.22.1-stericson installed and found it to be the latest. So I can figure it out on my own soon whenever an update is released.
Hey Guys -
Today, I upgraded my Shield Portable to 103 / Lollipop from the last public update. As I have all my Android devices rooted, I am needing to do so, but have a question. I much prefer manual rooting over apps (like Kings) where i don't know what's going on behind the scenes.
After reading through posts, I read that TWRP (which I usually use) wasn't installing SuperSU, but that CWM was working properly. I went to CWM's site, but they didn't have a download specifically for the Shield so I searched everywhere for whatever the latest working version would be. I ended up downloading and flashing two separate recovery images, but they didn't work. For both, when attempting to enter recovery from the Bootloader menu it just quickly reloaded the Bootloader menu and when fully booted into OS and running "adb reboot recovery", it would boot to an error screen.
Which version of CWM should I be using with Update 103 / Lollipop for the Shield portable? If you have a link or if steps beyond flashing it using above methods are needed, what are they? Finally, I read in one post what seemed to say that SuperSU was integrated in CWM therefore there wasn't need to download a separate zip for it. If that's the case, great. If not, which version should i use - the latest Beta 2.49?
Thanks Guys!
You can install SuperSU (No Custom Recovery Required)
Actually you don't need any custom recovery to install SuperSU, All you need to do is the following :
-Install KingUser App to install root.
-Download any "Control Rotation App" (at Google Play Store) and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps) {This step for the next App to get it work}
-Install "Super-Sume" (at Google Play Store) , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day
Thanks for the reply...
Well, the only reason I was trying to use this method was so that I wouldn't have to use KingUser since I didn't know what it would do on the system. Since I haven't gotten any other replies yet, it may be my only option currently. I'll probably go with it over manual root (using CWM) tomorrow morning unless I get another reply by morning.
Thanks
Newer TWRP builds install supersu fine. Use the TWRP in the multirom thread, not the one in the 2.8.5.0. In my recent development, I've installed supersu 2.49 several times without issue.
Thanks, I actually just found this out right before checking this post. I used "twrp-multirom-20150801-UNOFFICIAL-roth.img" which worked great.
Thanks!
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Fixed the broken link, and clarified that this is only tested on the latest supersu.
SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer
SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?
drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.
Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse
Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!
Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.
drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk
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.