I have rooted my phone so my flag goes 1x0,0x1etc. When i closed xposed i can use privacy mode. I need to use both privacy mode and xposes at the same time.
Xposed on S5
- Thread starter carbonize
- Start date
Closed? Xposed installer 'app' doesn't make the privacy mode or any KNOX related things because it is just one of user apps.
If privacy mode blocks xposed framework and anything like xposed framework, there's no way neither.
I have a strange bug, I guess Gravity Box it's causing it. When GB is active and I plug microUSB to charge my phone, Samsung music start to play over and over. It's like Samsung demo music or something. It's loudness depends on calls volume. I was updating GB yesterday plus make some changes in developer options. Any suggestions?
I'm running ALEXNDR ANG7 rom.
I'm running ALEXNDR ANG7 rom.
Last edited:
wanam
Recognized Developer / Inactive RC
Hello there.
I have S5 dula sim (international version) G900FD.
I rooted the phone and installed Wanam Xposed Framework.
After that, as all of you, I started experiencing problems on Shealt (crash and lag) and on private mode accessibility.
Then I edited the build.prop file in System folder ("false" instead "true" in ro.securestorage line) and cleared data in Shealt app setting: following this procedure Shealt it's working again. By the way Private Mode is still unaccessible.
Reading the forum I found out the existence in Xposed Framework of the XSecureStorage module which (in some case) solved the problem: I installed it but without succeeding because private mode still won't work!
Then I tought that the problem should be the edited build.prop file so I edited it back to "true" after unistalled xposed framework and all modules.
Rebooting the device (therefore without Framework) private mode was finally accessible and I noticed that all my pics in there were safe (...that sound good to me because when I need them I "only" have to uninstall xposed framework with modules and reboot).
Thereafter I tryed to install again Xposed framework and all modules (obviously included XSecureStorage) and rebooted again but as a result private mode does not work again (...WTF...).
I'm going mad: why somebody has been able in dealing the problem through XSecureStorage and on my phone this won't works??? '
Am I wrong in any step? Anybody can suggest me something to try?
I really think that a solution is pretty close... probably it depends by some setting in wanam xposed?
Please, lend a hand!!
I have S5 dula sim (international version) G900FD.
I rooted the phone and installed Wanam Xposed Framework.
After that, as all of you, I started experiencing problems on Shealt (crash and lag) and on private mode accessibility.
Then I edited the build.prop file in System folder ("false" instead "true" in ro.securestorage line) and cleared data in Shealt app setting: following this procedure Shealt it's working again. By the way Private Mode is still unaccessible.
Reading the forum I found out the existence in Xposed Framework of the XSecureStorage module which (in some case) solved the problem: I installed it but without succeeding because private mode still won't work!
Then I tought that the problem should be the edited build.prop file so I edited it back to "true" after unistalled xposed framework and all modules.
Rebooting the device (therefore without Framework) private mode was finally accessible and I noticed that all my pics in there were safe (...that sound good to me because when I need them I "only" have to uninstall xposed framework with modules and reboot).
Thereafter I tryed to install again Xposed framework and all modules (obviously included XSecureStorage) and rebooted again but as a result private mode does not work again (...WTF...).
I'm going mad: why somebody has been able in dealing the problem through XSecureStorage and on my phone this won't works??? '
Am I wrong in any step? Anybody can suggest me something to try?
I really think that a solution is pretty close... probably it depends by some setting in wanam xposed?
Please, lend a hand!!
I imagine you are having this problem: http://xdaforums.com/xposed/modules...re-storage-t2878708/post55643613#post55643613Hello there.
I have S5 dula sim (international version) G900FD.
I rooted the phone and installed Wanam Xposed Framework.
After that, as all of you, I started experiencing problems on Shealt (crash and lag) and on private mode accessibility.
Then I edited the build.prop file in System folder ("false" instead "true" in ro.securestorage line) and cleared data in Shealt app setting: following this procedure Shealt it's working again. By the way Private Mode is still unaccessible.
Reading the forum I found out the existence in Xposed Framework of the XSecureStorage module which (in some case) solved the problem: I installed it but without succeeding because private mode still won't work!
Then I tought that the problem should be the edited build.prop file so I edited it back to "true" after unistalled xposed framework and all modules.
Rebooting the device (therefore without Framework) private mode was finally accessible and I noticed that all my pics in there were safe (...that sound good to me because when I need them I "only" have to uninstall xposed framework with modules and reboot).
Thereafter I tryed to install again Xposed framework and all modules (obviously included XSecureStorage) and rebooted again but as a result private mode does not work again (...WTF...).
I'm going mad: why somebody has been able in dealing the problem through XSecureStorage and on my phone this won't works??? '
Am I wrong in any step? Anybody can suggest me something to try?
I really think that a solution is pretty close... probably it depends by some setting in wanam xposed?
Please, lend a hand!!
I would start reading from that post and backwards for about 1-2 pages to understand the issue and then proceed to do what he says in that post. He is the author of the module by the way. Carefully read his posts though before you go ahead and do or clear anything, backup, etc.
thanks but i have a g900i, i dont think there are any custom roms that support it yet
---------- Post added at 10:34 AM ---------- Previous post was at 10:24 AM ----------
Thanks Dude! Just trying right now with this process:
1) Titaniun Backup (app + system files)
2) Wipe data and cache partition from Recovery (Pilz_touch CWM)
3) Restore TB backup...
...crossed fingers...
I hope taht this will finally works! ; )
Last edited:
Similar threads
- Locked
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
3Look, I'm going to be blunt here.
"We must let this thing work!!!" is about as useful as "I want it now", i.e. not at all.
Rovo89 has posted about problems on Samsung stock ROMs using Lollipop, the exact reasons he doesn't have time to explain personally to each and every person, and even if he did, I doubt you would be able to understand them since they are probably too technical.
The fix will take time. If you want a working version of Xposed for Lollipop YOU WILL HAVE TO WAIT, simple as that . If you aren't satisfied with waiting until news of a fix for Samsung devices, you might as well not be here at all.3
I made a small module that let you bypass those Secure storage checks.
Try it and let me know if it works.3
Well, pardon me for suggesting a change that I was wondering if was the cause of S-Health and Private mode not actually working
Xposed currently uses a different context for the app_process than the original one (I believe rovo is working to change that), and while that is indeed needed for most ROMs, apparently for S5 the "correct" context can be used and Xposed keeps working.
Unfortunately it doesn't fix your problems. Too bad.
(personally ATM I don't have any other ideas about what could be the cause)1
@ex-28 provided a logcat for this, which I missed to reply to so far: https://dl.dropboxusercontent.com/u/34800164/S5.G900W.Shealth.crash.txt
I think this is the relevant part:
Code:I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2 I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2 I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2 E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2 I/SQLiteSecureOpenHelper( 7245): getWritableDatabase(pwd) I/SQLiteSecureOpenHelper( 7245): getDatabaseLocked(b,b,pwd)... I/SQLiteSecureOpenHelper( 7245): Open platform.db in secure mode E/SQLiteLog( 7245): (26) statement aborts at 0: [PRAGMA user_version;] file is encrypted or is not a database E/DefaultSecureDatabaseErrorHandler( 7245): Corruption reported by sqlite on database: /data/user/0/com.sec.android.service.health/databases/platform.db E/DefaultSecureDatabaseErrorHandler( 7245): backup the database file: /data/user/0/com.sec.android.service.health/databases/platform.db D/SQLiteSecureOpenHelper( 7245): ...getDatabaseLocked(b,b,pwd) E/JavaBinder( 7245): *** Uncaught remote exception! (Exceptions are not yet supported across processes.) E/JavaBinder( 7245): java.lang.RuntimeException: android.database.sqlite.SQLiteDatabaseCorruptException: file is encrypted or is not a database (code 26) E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:164) E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:100) E/JavaBinder( 7245): at com.sec.android.service.health.cp.HealthContentProvider.query(HealthContentProvider.java:534) E/JavaBinder( 7245): at android.content.ContentProvider.query(ContentProvider.java:857) E/JavaBinder( 7245): at android.content.ContentProvider$Transport.query(ContentProvider.java:200) E/JavaBinder( 7245): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112) E/JavaBinder( 7245): at android.os.Binder.execTransact(Binder.java:404) E/JavaBinder( 7245): at dalvik.system.NativeStart.run(Native Method) E/JavaBinder( 7245): Caused by: android.database.sqlite.SQLiteDatabaseCorruptException: file is encrypted or is not a database (code 26) E/JavaBinder( 7245): at android.database.sqlite.SQLiteConnection.nativeExecuteForLong(Native Method) E/JavaBinder( 7245): at android.database.sqlite.SQLiteConnection.executeForLong(SQLiteConnection.java:788) E/JavaBinder( 7245): at android.database.sqlite.SQLiteSession.executeForLong(SQLiteSession.java:652) E/JavaBinder( 7245): at android.database.sqlite.SQLiteStatement.simpleQueryForLong(SQLiteStatement.java:107) E/JavaBinder( 7245): at android.database.DatabaseUtils.longForQuery(DatabaseUtils.java:825) E/JavaBinder( 7245): at android.database.DatabaseUtils.longForQuery(DatabaseUtils.java:813) E/JavaBinder( 7245): at android.database.sqlite.SQLiteDatabase.getVersion(SQLiteDatabase.java:996) E/JavaBinder( 7245): at android.database.sqlite.SQLiteSecureOpenHelper.getDatabaseLocked(SQLiteSecureOpenHelper.java:366) E/JavaBinder( 7245): at android.database.sqlite.SQLiteSecureOpenHelper.getWritableDatabase(SQLiteSecureOpenHelper.java:275) E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:153) E/JavaBinder( 7245): ... 7 more
It somehow can't decrypt the database. I don't know why. The only indication I have is the part about libdvm.so. Maybe it doesn't like some changes I have done to the file in the memory. If yes, I think I might have accidently fixed this for the upcoming version. I will send you a link for a pre-alpha version. If that doesn't help, I don't know what else to check...
