Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple minor fixes #3

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

Conversation

Morlok8k
Copy link

@Morlok8k Morlok8k commented Aug 7, 2013

Yes, its not 4.3 compatible, but it still fixes a bunch of little issues i've noticed

@supercurio
Copy link
Member

Hey hello Morlok8k, thanks very much for those changes I'll review them
quickly and merge.

I'm sad the app cannot work anymore for it's main purpose on 4.3 and I
think before publishing an update something should be done about addressing
this, like a fat warning to people in 4.2.x explaining them that if they
update and their boot-loader is locked, possibly preventing firmware
downgrade it's possible they will lose root forever.

On Wed, Aug 7, 2013 at 3:06 AM, Morlok8k [email protected] wrote:

Yes, its not 4.3 compatible, but it still fixes a bunch of little issues

i've noticed

You can merge this Pull Request by running

git pull https://github.com/Morlok8k/ota-rootkeeper-app master

Or view, comment on, or merge it at:

#3
Commit Summary

  • Update AndroidManifest.xml
  • Merge remote-tracking branch 'mattlgroff/master'
  • updated android:targetSdkVersion
  • fixed mispelled word
  • fixed a bunch of warnings
  • updated to target android 4.2.2
  • added more checks to check for alternate superuser apps.
  • updated .gitignore to add more generated files
  • version bump

File Changes

Patch Links:

François Simond
Android developer, open source enthusiast.

http://twitter.com/supercurio
http://project-voodoo.org/

@Morlok8k
Copy link
Author

Morlok8k commented Aug 7, 2013

Yes, you should put a nice big warning on the app saying it doesn't work on 4.3.

I actually made these changes months ago, but forgot to submit a pull request.

maybe with some research, people can find a way to securely protect root. 4.3 is really new.

@supercurio
Copy link
Member

Yep. I studied the question right away but the security model is really
different, enough to break the previous paradigms.
And on the Nexuses, attempts to keep root make the OTA fail as it cannot
rewrite or delete some immutable files.

On some other devices, it might be possible to keep root thanks to the fact
they use different OTA mechanisms tho.

On Wed, Aug 7, 2013 at 3:23 AM, Morlok8k [email protected] wrote:

Yes, you should put a nice big warning on the app saying it doesn't work
on 4.3.

I actually made these changes months ago, but forgot to submit a pull
request.

maybe with some research, people can find a way to securely protect root.
4.3 is really new.


Reply to this email directly or view it on GitHubhttps://github.com//pull/3#issuecomment-22223947
.

François Simond
Android developer, open source enthusiast.

http://twitter.com/supercurio
http://project-voodoo.org/

Copy link

@Rwadxvv Rwadxvv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

8wui

@@ -118,7 +118,16 @@ private void ensureAttributeUtilsAvailability() {

public void analyzeSu() {
isRooted = detectValidSuBinaryInPath();
isSuperuserAppInstalled = isSuperUserApkinstalled();
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I

android:targetSdkVersion="15" />

android:targetSdkVersion="17" />
<uses-permission android:name="android.permission.ACCESS_SUPERUSER" />
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<uses-permission android:name="android.permission.ACCESS_SUPERUSER" />
<uses-permission android:name="android.permission.ACCESS_- SUPERUSER"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants