Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Bootloop on 3.6.16 and Kit Kat 4.4.2 #2209

Closed
OrpheeGT opened this issue May 27, 2015 · 9 comments
Closed

Bootloop on 3.6.16 and Kit Kat 4.4.2 #2209

OrpheeGT opened this issue May 27, 2015 · 9 comments
Labels

Comments

@OrpheeGT
Copy link

Hello,

As discussed on XDA, I have a bootloop when I update to 3.6.16 on my Samsung Galaxy Tab S.

I don't know how to attach log on github, so there are here : http://d-h.st/gXdg

Thank you

@M66B M66B added the bug label May 27, 2015
M66B added a commit that referenced this issue May 27, 2015
@M66B
Copy link
Owner

M66B commented May 27, 2015

Could you please try this version:
https://crowd.xprivacy.eu/XPrivacy_3.6.16-1.apk

@OrpheeGT
Copy link
Author

it boot, but it says xprivacy need to reboot... And Of course I rebooted, twice
I uninstalled and retried, but same

@an0n981
Copy link
Contributor

an0n981 commented May 27, 2015

Same issue here, privacy version mismatch. Restrictions were working

M66B added a commit that referenced this issue May 27, 2015
@M66B
Copy link
Owner

M66B commented May 27, 2015

Since @an0n981 didn't have the reported problem (as far as I know), I like to know from @OrpheeGT if this version is working now:
https://crowd.xprivacy.eu/XPrivacy_3.6.16-2.apk

@OrpheeGT
Copy link
Author

It boots, and Xprivacy is starting, but I had an error at start, mail sent as asked by the app.

XPrivacy: 3.6.16
Android: 4.4.2 (SDK 19)

Brand: samsung
Manufacturer: samsung
Model: SM-T805
Product: chagallltexx
Device: chagalllte
Host: SWDD3918
Display: KOT49H.T805XXU1ANH1
Id: KOT49H

com.android.server.am.ActivityManagerService.mContext not found
com.android.server.am.ActivityManagerService.mContext not found
com.android.server.am.ActivityManagerService.mContext not found
com.android.server.am.ActivityManagerService.mContext not found

@M66B
Copy link
Owner

M66B commented May 27, 2015

@OrpheeGT you can ignore this message, it will be gone in the next release.

M66B added a commit that referenced this issue May 27, 2015
@M66B M66B closed this as completed in 8413a53 May 27, 2015
@M66B
Copy link
Owner

M66B commented May 28, 2015

@an0n981 is your problem solved?

Version mismatch means that the Xposed part is a different version than the application part.
Try to disable and enable XPrivacy in Xposed and reboot after this.

@an0n981
Copy link
Contributor

an0n981 commented May 28, 2015

As you previously mentioned, I didn't have the original problem. I only tested the 6-1 update, where the version mismatch happened. If you think it might benefit, I can test the -2 update.

@M66B
Copy link
Owner

M66B commented May 28, 2015

I am preparing a new release right now, so better try that.

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

No branches or pull requests

3 participants