WARNING: THIS IS NOT A FLASHABLE ZIP
This is a modified kernel for Android 5.0 that allows root to work.
This kernel alone will not grant root access.
Flash this in custom recovery to obtain root: http://download.chainfire.eu/591/SuperSU/BETA-SuperSU-v2.17.zip
The kernel boot.img can be flashed using fastboot.
Credit goes to Chainfire. After seeing this post: https://plus.google.com/+Chainfire/posts/VxjfYJnZAXP ,
I took it upon myself to decompile, edit, then recompile the stock manta LPX13D kernel since he had only done so for the Nexus5/7.
Link: https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Keep in mind this kernel allows root to work, but most apps that require root will need to be updated in order to fully work on Android 5.0.
Chainfire explains this in greater detail in the first G+ post i linked.
Damn, titanium backup is a no go.
great! works perfect, thanks a lot
newellj79 said:
Damn, titanium backup is a no go.
Click to expand...
Click to collapse
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
Thanks I'll give it a shot.
phrix626 said:
TiBu Works on 5.0!!!
Link: Experimental Version of TiBu that works on Andriod 5.0
Click to expand...
Click to collapse
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!
anoneemooz said:
What has your experience been with this so far? Does it delete system apps too? Thanks for the link!
Click to expand...
Click to collapse
So far I've only restored a previous backup of flappybird from tibu on 5.0, I'm restoring a twrp backup of kitkat now so i can run a new backup in tibu, then restore lollipop, then test all the things!
It force closes when trying to sync with my Google cloud backup.
So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)
phrix626 said:
So far I've found that the experimental version of TiBu fails to uninstall system apps claiming "Cannot remove system app, failed to locate the apk file."
But... It does restore backups (app + data)
Click to expand...
Click to collapse
Aw man. That's all I really want right now. I'm about to give rooting this a shot now. Hopefully to try out some ad removing stuff like adaway! Thanks for the updates on TiBu!
I can't seem to get this to work. I flashed the boot.img via fastboot using "fastboot erase boot" followed by "fastboot flash boot boot.img" and then I reboot into recovery to flash the superuser zip in this thread..and I still get the same error with SuperSU about missing stuff and all root apps I've tried say I'm not rooted. I'm using the latest TWRP. Anything I'm missing?
Off topic: if you only need root to restore TiBu backup - create update zip from your backup, then flash the update zip in recovery. No root needed.
On topic: since you followed Chainfires' method, this won't set the whole system to permissive, right?
edit: I believe not, if TiBu is not working with this boot image. TiBu has not adopted to the new 5.0 SELinux environment yet.
Thanks for this kernel. İs there anybody tried this kernel ? I havent got much experience about android.
Thanks, this gave me root. Just need to wait for the various apps to be updated in due course. First one I tried, rashr, gained root access but said device not supported.
as an aside, anyone looking to block ads with or without root you can always flash this from recovery http://forum.xda-developers.com/showthread.php?t=1916098
Keep up to date with the latest versions of TiBu. Check out their Twitter feed.
https://mobile.twitter.com/TitaniumBackup/status/524487475738443776
The first test version I linked was older. I haven't had a chance to test this one yet.
Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!
Ti2 said:
Flashed the modified boot image & flashed SuperSu 2.17
SuperSU app won't let me update the binaries - so no root. SuperSU 2.16 doesn't work for me either.
Where to look? Can't find flashable SU binaries either.
Thanks!
Click to expand...
Click to collapse
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.
Latest tibu test version working ok here for backup and restore :good:
phrix626 said:
If you flashed the boot.img and the SuperSU zip, root access should work.
The SuperSU zip includes the SuperSu app and the su binaries. It won't let you update the binaries because 2.16 is the latest stable release.
To test root:
Download and open Terminal Emulator > type "su" > you should get a SuperSU promt > grant access to Terminal Emulator.
The $ should now be a # , this confirms you are using the shell as root user.
Click to expand...
Click to collapse
No # for me... not even the prompt (duh..)
I flashed the boot.img and the SuperSU zip. I just don't have root.
What build of Lollipop are you running?
I flashed the images from this post :http://forum.xda-developers.com/showpost.php?p=56505625&postcount=99
Edit: that build is android-5.0.0_r2 (LRX21M)
Related
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Are you s-off? If so not sure what the problem is. If you're not s-off, that's your problem
Sent from my HTC Desire using XDA App
pspuser007 said:
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Click to expand...
Click to collapse
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this zip
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
pspuser007 said:
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
Click to expand...
Click to collapse
If u updated super user through the market, uninstall the update..after that flash the zip in recovery
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
pspuser007 said:
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
Click to expand...
Click to collapse
u never looked in settings/applications?
super user i guess is a system app (like gmails, gmaps, gtalk, etc)..so u can't uninstall those applications..but u can uninstall updates for those applications..mean for system apps u can only uninstall updates
so go in settings/applications, select super user app and u should see uninstall updates, if yes do uninstall updates, if not then its ok and flash the zip
do a nandroid backup in recovery before touch something, just to be sure
I hadn't checked system applications so far.
Unistalled the update, did a nandroid backup and flashed the zip!
Everything OK now!
Thanks a lot for your help!
Many many thanks!!!
what does the zip need to be named?
Does the zip need to be named update or does it stayed named like it is?
Name it whatever makes you happy. Remember its whats on the inside that counts.
Sent from my PG86100 using XDA Premium App
I'm getting the same warning message with my market updated su, when I open Titanium Backup but it hasn't affected anything. I just ignore the message and everything still seems to work. Am I missing something?
Problem Updating
andQlimax said:
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this "goo-inside.me/superuser/su-3.0-efgh-signed.zip"
Click to expand...
Click to collapse
I have uninstalled SU and installed the super user update and I get the following error when I update the binary updater:
"Failed to find currently installed su binary. Update cannot continue"
UPDATE:
I downloaded and installed the binary file (su-3.0-bin-efgh-signed.zip) from androidsu.com and now get FC error "The application Superuser has stopped unexpectedly. Please try again"
Thanks for your help.
When this issue occurred for I found that just by simply reflashing the SU zip in recovery and then running the update fix it seemed to fix it. I think for me it may have had to do with using an outdated version though.
su binary update failed..
Hi, I'm using CyanogenMod 7.1.0 RLS3 for Kaiser.. Today I got a "su binary outdated" I try to update it.. Going ok until "Moving su to it's final location - Fail" how to solve this? guide me please.. I'm newbie..
Hi, I had rooted my Garmin-Asus A50 about a year ago with help from these fora. Also installed Titanium backup and other related apps.
My question: upon waking thisr morning and waking the phone, a message said "SU binary outdated - tap to update" I let it update without thinking -but immediately had doubts about some trojan doing this to gain access.
So I switched off the phone and am trying to gather some info here and on WP. From your post I see that this 'update' message may be legit - or am I wrong?
Thanks ffor any further tips.
.-.
Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.
Hey all,
Just installed the Official Cyanogenmod on my N1 and lo and behold, root has run away.
ROM here: cyanogenmod(dot)org/hardware/oppo-n1/#images
I installed the TWRP Recovery and tried to let it install Root and it appears that it sort of does with the SuperSU app, but other root checkers and Titanium fail hard on this.
Anybody got any ideas on how to root Cyanogenmod? (Just sounds weird to say that)
Thanks
Tal
I had to flash SuperSU in recovery. I encountered the same issue. TWRP didn't root, even though it said that it did. Updating SuperSU within android didn't help. So I flashed it manually.
Sent from my N1 using Tapatalk
When you say flashed it manually. Was that through fastboot? ADB? or from the recovery.
Also, are we talking about UPDATE-SuperSU-v1.86.zip from download.chainfire(dot)eu/supersu
I tried that through recovery and still get /system/xbin/su command missing in Titanium.
Thanks
Talung said:
When you say flashed it manually. Was that through fastboot? ADB? or from the recovery.
Also, are we talking about UPDATE-SuperSU-v1.86.zip from download.chainfire(dot)eu/supersu
I tried that through recovery and still get /system/xbin/su command missing in Titanium.
Thanks
Click to expand...
Click to collapse
Ok good News, what I mentioned above through recovery works just fine.
Issues:
Remove all previous instances of it from OS (from inside the SuperSU app, select Switch superuser app or Unroot)
WIPE DALVIK CACHE!!!
Hope this helps others.
Thanks
So question is, when we ill we be able to successfully root Android M?
Have tired with TWRP. get stuck on HTC One boot screen.
Had to flash stock ROM via stock recovery...
***
TWRP 2.8.7.0
SupersU 2.46 (also tried beta version 2.52 zip
You need to use latest SuperSU 2.65. Download
When TWRP want to install SuperSU check "Do not install" and reboot.
Hmm, I've done the above and it seemed to install correctly, but the SuperSU app which I installed from the zip is saying "no SU binary installed".
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Click to expand...
Click to collapse
Thanks, I've also tried the app store app, it says "no SU binary installed".
For me, I can't install SuperSU as system app. (not currently available in system-less root mode). And Twrp says I'm not rooted, asks to install
Try 2.64.zip no problems for me
Running 2.65
2.64 didn't work either, still get the same problem. Think I'll just try to install it the system way.
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
It worked well for me too:
http://forum.xda-developers.com/showpost.php?p=64493553&postcount=296:bien:
Gandalforce said:
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
Click to expand...
Click to collapse
MegaGalan said:
It worked well for me too[/url]
Click to expand...
Click to collapse
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
BenPope said:
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
Click to expand...
Click to collapse
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
sssssbarn said:
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
Click to expand...
Click to collapse
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
BenPope said:
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
sssssbarn said:
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
Click to expand...
Click to collapse
thanks for the files... fyi you transposed the numbers in the version of twrp. it is 2.8.7.1.
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Gandalforce said:
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Click to expand...
Click to collapse
I had problems with 2.66 as well. I reported it with a logcat and sticking with 2.65 for now
Same
Gandalforce said:
Same
Click to expand...
Click to collapse
Yeah same here.
Had to install TWRP twrp-2.8.7.1_CPTB-B1-hima and BETA-SuperSU-v2.65-20151226141550. then finally booted in to the OS.
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
You ALREADY HAVE root with CM-SU. To enable it, just go to developer option and give root permissions to app. Some SuperSU's versions are incompatible afaik. CM-SU preinstalled is just fine.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Meneldur said:
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Click to expand...
Click to collapse
Have you try this method http://forum.xda-developers.com/lg-g2/general/bump-supersu-t3273251
CustomPatcherScript_Bump.zip + UPDATE-SuperSU-v2.65-20151226141550.zip
But it's also can cause reboot loop
Do backup before doing flash that script
That worked fine with my D855 32Gb + CM13