when I click on supersu. I get there is no su binary installed and supersu cannot install it. this is a problem. I did all steps just fine until I click on supersu. =(. help
netsfan549 said:
when I click on supersu. I get there is no su binary installed and supersu cannot install it. this is a problem. I did all steps just fine until I click on supersu. =(. help
Click to expand...
Click to collapse
Totally wrong section, you should search and read before doing anything to your phone. Anyways, download chainfire's latest supersu from the internet, flash it in recovery, and you'll have root.
Kratos90 said:
Totally wrong section, you should search and read before doing anything to your phone. Anyways, download chainfire's latest supersu from the internet, flash it in recovery, and you'll have root.
Click to expand...
Click to collapse
I did that and still get the same thing
Did that and still didn't work. Is it because I'm running 5.0?
netsfan549 said:
Did that and still didn't work. Is it because I'm running 5.0?
Click to expand...
Click to collapse
That isn't the reason. Chainfire's SuperSU has supported Lollipop for some time now. What version did you try?
redpoint73 said:
That isn't the reason. Chainfire's SuperSU has supported Lollipop for some time now. What version did you try?
Click to expand...
Click to collapse
V.2.02.
I go to recovery. I hit install that version..says installed and I restart my phone. It Still doesn't work. Could it be because I didn't delete other zip file from my phone?
netsfan549 said:
V.2.02.
Click to expand...
Click to collapse
Dude, there is your problem right there!
The advice was to flash the latest SuperSU. That would be 2.46 (or even the couple versions before that also work with LP). You are 44 versions behind!
http://forum.xda-developers.com/showthread.php?t=1538053
redpoint73 said:
Dude, there is your problem right there!
The advice was to flash the latest SuperSU. That would be 2.46 (or even the couple versions before that also work with LP). You are 44 versions behind!
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Thank you, I was following a link that I found on Google. Lol. I would post link here but don't have enough post. I really appreciate it.
Related
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Do you have a link to their research or are their findings private?
Regards,
Mr_Bartek said:
Do you have a link to their research or are their findings private?
Regards,
Click to expand...
Click to collapse
saurik - his analysis of the "second master key vuln"
giantpune for his symlnink attack vuln in property space:
Code:
/system/bin/mv /data/property /data/backupprop
/system/bin/mkdir /data/property
/system/bin/ln -s /sys/kernel/uevent_helper /data/property/.temp
/system/bin/setprop persist.sys.fail /data/pwn.sh
jcase said:
I tweeted this a couple week ago before the N1 was publicly out but here you go, nothing fancy, no real ui or output.
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
coolrevi said:
Will this exploit work in any other device. when i try to install the play store warns about the vulnerability. Will this vulnerability be gone after uninstalling oppoown.
Click to expand...
Click to collapse
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
jcase said:
Possibly other oppo devices
No it doesnt fix the vuln, just becareful where you install apps from
Click to expand...
Click to collapse
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
ricky310711 said:
a second mater key vulnurability? hmm, so this could might not be patched in 4.4?
great job by the way, i dont have the device but this is interesting!
Click to expand...
Click to collapse
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
pulser_g2 said:
It should be patched in 4.4.
But some (read most) OEMs still can't manage to patch their devices up to the latest security updates on release.
Anyway, I tested this root method a week or so ago and it works nicely
Click to expand...
Click to collapse
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
ricky310711 said:
so your saying in most devices the master key patch could be a possible vulnurabillity still in 4.3?
interesting...
Click to expand...
Click to collapse
It depends on if OEMs backported it, depends on which build OEMs used and depends on the bug. Four or five different zip parser bugs with similar results. This one I used was patched in 4.3, but other exist.
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
trickraca said:
Im trying to figure out why oppown apk will not install in my n1. everytime i try it just. Says app not installed. But on the install screen it says something about being an update to an already installed program. Any clues as to what the issue is? all ive done is update to the latest ota software and im currently located in indonesia if that makes a difference.
Click to expand...
Click to collapse
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
jcase said:
Possible they patched it by now, if you are on cyanogenmod you are certainly patched
Sent from my HTC Two
Click to expand...
Click to collapse
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
It should not come rooted, if it comes rooted then no way did it pass CTS. I'm guessing unlocking the bootloader and flashing a recovery? I don't know, I dont have one
giuliano rigon said:
So show do you root the cyanogenmod edition n1.. Can you help please.. Does it come rooted or what..
Click to expand...
Click to collapse
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
noobish doubts..
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Please i ne ed a walthrough..
1) download twrp
2) put it in root of the telephone robot
3) flash it in recovery?
4) reboot recovery wipe cache and dalvik flash omnirom..
Please correct me..
Thank you
giuliano rigon said:
1) download twrp Yes
2) put it in root of the telephone Yes
Make sure to copy Omnirom to your phone at some point
3) flash it in recovery? No - Flash TWRP in Fastboot if you haven't flashed the recovery already. Use the official Teamwin site for guidance
4) reboot recovery wipe cache and dalvik flash omnirom.. Wipe Cache, Dalvik, System, and Data
Click to expand...
Click to collapse
Updates in Red
This is off-topic for this thread though. Questions/Info for flashing Omnirom should be addressed in the Omnirom thread.
Harfainx said:
You don't need to root if you aren't staying on stock. There's no lock anywhere on the bootloader or anything.
Simply flash TWRP in fastboot, then flash Omni (or whatever else) through TWRP.
You should be able to just flash a SuperSU zip in TWRP as well if you want to root the stock ColorOS.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
not rooted.. confirm i can flash
nowy57 said:
may you provide to right superSU.zip files
I v got superSU from this link and it doesnt work on first and second CM version
I am not rooted yet ...
thnaks
Click to expand...
Click to collapse
I nave tried my damnedest to root .. Fastboot flashing supersu flashing from recovery Direct install from google play complete unroots and reflash letting recovery do it .. No way..
So now i need a last confirmation.. Can i flash omnirom after wipes even if i am unrooted.. And has anyone rooted omnirom or does it come unrooted.. Thanks for the info .. Another idea.. Flashing color OS footing and then flashing omni.. Or is this a late night bad Dream..
---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------
Harfainx said:
That does work. You're likely not removing root, but rather just uninstalling SuperSU.
I answered you in your Q&A thread on root.
Click to expand...
Click to collapse
Sorry now i got it.. It was in the forums.. Just unchecking the respect cyanogen settings in the super su menu got me roooted and happy.. Sorry for your time.. I flashed super su zip from recovery rebooted and unchecked .. Now i am set..
I were rooted myN1 in yesterday, its really good . thankss
Sent from my N1 using XDA Premium 4 mobile app
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
CNemo7539 said:
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Have you tried updating Supersu from play store
lsherif said:
Have you tried updating Supersu from play store
Click to expand...
Click to collapse
Yes, I did. It says that binaries are not found.
CNemo7539 said:
Yes, I did. It says that binaries are not found.
Click to expand...
Click to collapse
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
22sl22 said:
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Click to expand...
Click to collapse
Thank you! Now I'm rooted again!
Someone if you know and tested it, can I root my htc one m8 device having the new firmware updated 5.0.1 lolipop??
Please anwser and if there is a way please send a link
THANKS A LOTTT!!
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a rom , likely rooted already.
?
Darth said:
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a room, likely rooted already.
Click to expand...
Click to collapse
thanks for that but when I did it in my phone it says su binary out of date! what can I do now?
Can you explain everything you did, beginning to end. And exactly when/where you get that message?
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Koukosftw said:
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Click to expand...
Click to collapse
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
i did that too nothing happened :/
xunholyx said:
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
Click to expand...
Click to collapse
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Darth said:
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Click to expand...
Click to collapse
I tried the normal it didnt work, how I do the second, I pressed it but nothing happened!
I don't think you have twrp installed anymore, or not properly. You've flashed it with fastboot, since updating to lollipop? How did you update to lollipop?
Normal, I never had root before. Upgraded my phone to 5.0 and then i tried to root it
Rooted fine here with normal method. Just had to update super su.
OK, can you please walk us through exactly what steps to Root you took. From the beginning. And we'll see what happened.
?
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
chinkyarmour said:
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
Click to expand...
Click to collapse
Settings > Power > Fast boot
xunholyx said:
Settings > Power > Fast boot
Click to expand...
Click to collapse
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
They must have taken the option out. It didn't boot any faster for me anyways. Not since 4.4.2
chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
SO GUYS, ITS ME THAT I CREATED THIS THREAD! PROBLEM SOLVED. I ALREADY HAD TWRP AND DOWNLOADED THE Update-supersu file from the above youtube video (links) and I did it with recovery mode. I DONT KNOW BUT THE PREVIOUS supersu I installed couldnt update the su binary. This one did it. PROBLEM SOLVED AND I ROOTED MY 5.0.1 LOLIPOP DEVICE.
THANKS GUYS FOR EVERYTHING REALLY HELPFUL!!!
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.
After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?
aalemann said:
After successfully flashing CM12.1 and playing around with it a little bit, I wanted to completely remove root (to get a few apps running). So I was advised to download SuperSU and use it to make a full/complete root removal. After that I de-installed SuperSU and disabled root in the Developer Options.
Well, that worked, I could run the apps that were unhappy with just root disabled in Developer Options. But now I want to have root back and I read in a couple of place that just flashing the latest SuperSU.zip from recovery might be a bad idea.
Any suggestions how to properly re-root my CM12.1 ?
Click to expand...
Click to collapse
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46
levone1 said:
Not sure what would be bad about it. If it's an issue with latest version, just use 2.46
Click to expand...
Click to collapse
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works
aalemann said:
ok, thanks for the prompt answer! I am currently trying to find where I read this..... anyway, will then probably just flash it and see if it works
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/
levone1 said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
this is exactly the version I flashed onto my CM12.1, worked flawlessly