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 guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will I loose root when I flash through Odin? --> Yes
-Is the new firmware rootable, or is there a way to keep root when I upgrade from rooted 4.3?
-->For upgrade yes: If you are rooted on 4.3 you can restore root by flashing a custom recovery and flash superSU manually.
-->chainfire autoroot works but you need to update the superSU app through play store after flashing.
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
-Can I still use flash with KitKat? How?
-->Yes, there is a hacked version see 2nd post for link.
-How is the touchscreen driver? Is the stuttering fixed? Do touch and hold actions still drop after ~23sec?
-->Pretty much fixed. To about the same state as the improved Kernel we had a while ago.
-Are there any apps that are not working (root apps too)?
-Gesture Controls? --> works
-Xposed framework app settings? -->works
-Is Hancom Office included or does it still work? --> not included but does still work.
Thats about what I can think of a the moment.
Hi,
If you are already rooted then all you have to do is re install TWRP and then flash SU zip then you have root.
For flash player, download hacked version here, it works I tested it on new software :
http://forum.xda-developers.com/go...e-how-to-play-flash-video-android-4-t2548001
Also, xposed works. Tested it on new software
Sent from my Note 2014 using Tapatalk
Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP
Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?
starfall42 said:
Here's a question: I'm already rooted. Is flashing the stock KitKat image via Odin and rerooting the only way to upgrade?
Click to expand...
Click to collapse
If you are already rooted, I assume you have TWRP too. Just download this KitKat rom, full wipe and install.
http://forum.xda-developers.com/show....php?t=2720631
Itchiee said:
Chainfire's Auto Root does work, once you flash it thru odin and reboot, go to the Play store and update the app.
- Please update OP
Click to expand...
Click to collapse
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?
itachi30s said:
Not for me I flashed a stock 4.4 kit kat on my tablet coming from root 4.3. I then flashed chainfire autoroot thru odin on the 4.4 and the superuser there only problem is it displays this ' There is no SU binary installed, and SuperSU cannot install this is a problem! I formatted my 4.3 before flashing it maybe thats why?
Click to expand...
Click to collapse
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Do I have to update to kitkat bootloader?
gcrutchr said:
Do I have to update to kitkat bootloader?
Click to expand...
Click to collapse
Not needed. The bootloader is same for 4.3 and 4.4
Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
Thx for the response from what i can see you never fully wipe your data before installing 4.4 KK but i did so i believe i lost my root like that. So when i updated the supersu never carried over from 4.3
Srikar_NBK said:
Not needed. The bootloader is same for 4.3 and 4.4
Click to expand...
Click to collapse
Thanks.
Itchiee said:
Not sure... I installed KK on the tablet via Odin, then rebooted and setup, then rebooted into download mode and flashed auto root thru Odin.
Upon reboot I got an error selecting SuperSU, but once I updated it thru the Play Store its been fine.
Using ES Explorer I removed the items I don't need and removed all of the Knox stuff.
There are a few of us this worked for so I don't know what went wrong for you.
If you don't succeed then try again, and again, and again....Good luck.
Click to expand...
Click to collapse
man you're awesome thx a bunch I saw my mistake, I was using chain fire root except the one I had downloaded from a third party site wasn't exactly for my device. Went to chainfire official site got the autoroot bam im rooted at.
Rep + 1
How do you get hancom office?
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Sorry, but I cant find thread related to the issue .
What do you mean by `fixable through an app`? I`m not rooted and full stock.
Kit Kat SD Card Issue
clouds5 said:
Hi guys I have some questions about the new Firmware and KitKat in general and you may have answers I'll try to update first post with your answers!
-Will KitKat restrict access to my SD card? -->Yes but fixable through an app or editing a file (needs root), there is already a thread about that.
Click to expand...
Click to collapse
Is this the app you are referring to? http://forum.xda-developers.com/showthread.php?t=2684188
Still not out in Germany
I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?
supremekizzle said:
I intend on rooting this tablet. Am I better off rooting 4.3 and then flashing KK update? Or is it possible to update to KK and then root?
Click to expand...
Click to collapse
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.
clouds5 said:
Both ways work equally well I was already rooted with 4.3 but either way has been confirmed working so it doesn't matter.
Click to expand...
Click to collapse
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?
supremekizzle said:
Thank you. So any guide I find on rooting 4.3 should be the same procedure as 4.4?
Click to expand...
Click to collapse
Yes. Refer to this one
http://forum.xda-developers.com/showthread.php?t=2490805
Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®
done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.
Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.
mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73
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:
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