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
Hello friends
I am using the N7100. I flashed the CM12 Unofficial Build and was extremely happy with it. I recently updated it to the 05.01.14 build and found out I had lost all root privileges. I do not understand how that happened considering I was rooted all along till flashing that update. I would like to know what I should do now to get back root.
Thank you so much.
arorakar97 said:
Hello friends
I am using the N7100. I flashed the CM12 Unofficial Build and was extremely happy with it. I recently updated it to the 05.01.14 build and found out I had lost all root privileges. I do not understand how that happened considering I was rooted all along till flashing that update. I would like to know what I should do now to get back root.
Thank you so much.
Click to expand...
Click to collapse
I believe that root is disabled by default in CM12. Go to the Developer Settings and find Root Access. Click on it and select Apps Only.
If it doesn't work, download SuperSU and flash it via ur recovery.
Irwenzhao said:
I believe that root is disabled by default in CM12. Go to the Developer Settings and find Root Access. Click on it and select Apps Only.
If it doesn't work, download SuperSU and flash it via ur recovery.
Click to expand...
Click to collapse
Aha! Thank You So Much! :good:
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!!!
What happened:
1. Used TWRP to flash an earlier System backup
2. Boots but two system apps force close and phone reboots
3. This goes on indefinitely
4. Can no longer go to either recovery
I'm thinking I should use FlashTool and flash a default System for 14.5.A.0.270 but I can't seem to find any firmware image for it. Does anybody have this/better idea to get me out of the boot loop?
Edit: found the file, will report back.
another complication: I can't go into flashmode
ctap001 said:
another complication: I can't go into flashmode
Click to expand...
Click to collapse
Bl locked or unlocked?
levone1 said:
Bl locked or unlocked?
Click to expand...
Click to collapse
locked. Am I SOTL?
ctap001 said:
locked. Am I SOTL?
Click to expand...
Click to collapse
Probably not. Are you wanting to save data, etc?
levone1 said:
Probably not. Are you wanting to save data, etc?
Click to expand...
Click to collapse
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.
ctap001 said:
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.
Click to expand...
Click to collapse
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.
levone1 said:
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.
Click to expand...
Click to collapse
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)
ctap001 said:
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)
Click to expand...
Click to collapse
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.
levone1 said:
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.
Click to expand...
Click to collapse
I have flashed System from an unrooted FTF. Still can't access recovery though
ctap001 said:
I have flashed System from an unrooted FTF. Still can't access recovery though
Click to expand...
Click to collapse
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.
levone1 said:
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.
Click to expand...
Click to collapse
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work
ctap001 said:
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work
Click to expand...
Click to collapse
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....
levone1 said:
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....
Click to expand...
Click to collapse
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.
ctap001 said:
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.
Click to expand...
Click to collapse
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others
levone1 said:
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others
Click to expand...
Click to collapse
> .216
The latest I tried was .380
King root
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.
wwwjunkboywww said:
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.
Click to expand...
Click to collapse
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.
Thanks
levone1 said:
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.
Click to expand...
Click to collapse
Yeah i had tried that. The BAT right? I ended up flashing multi twrp and then using that to get NUT's, he's made a sweet recovery.
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.