[App]XSecureStorage - Bypass secure storage checks on SHealth and Private mode

Search This thread
By:
Advanced…
wanam

wanam

Recognized Developer / Inactive RC
Jan 26, 2011
6,209
30,012
Toulouse
wanam.net
OnePlus 7T
Sony Xperia 5 III
Hi guys,

I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.

One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs

This module bypass the secure storage checks on SHealth and Private mode services, and will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.

I did just the basic tests for SHealth because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket :D .

Download

Note:

  • You may need to clear SHealth and Health service data (you will loose your Pedometer data).
  • Clearing Personal pages service will break Private mode.
Troubleshooting:
If you can't get Private mode to work after switching to Xposed, you need to go back to a stock FW and backup your private files, after that you can install Xposed and enable my module then remove "/data/system/users/privatemode_edk_1000" as advised by @invano.

Changelog:
1.0.1:
- Add Private mode support.
- App renamed from XHealth to XSecureStorage


Thanks to:
  • Rovo89 for his awesome work on Xposed framework and Mods.
  • Tungstwenty for contribution on Xposed framework and his many Mods
 

Attachments

  • Screenshot_2014-09-16-11-52-09.png
    Screenshot_2014-09-16-11-52-09.png
    33.4 KB · Views: 11,891
  • Screenshot_2014-09-16-11-52-27.png
    Screenshot_2014-09-16-11-52-27.png
    250.7 KB · Views: 11,922
  • Screenshot_2014-09-17-09-52-58.png
    Screenshot_2014-09-17-09-52-58.png
    103.6 KB · Views: 5,237
  • Desktop.PNG
    Desktop.PNG
    46.3 KB · Views: 5,039
Last edited:
  • Like
Reactions: khoailang2500, Foo Bar, DeadCode1 and 32 others
O

Orka82

Senior Member
Aug 26, 2008
427
57
Stockholm
Working good! I had the secure storage disabled but I enabled it now and tried your module. S Health works! Thank you!
 
U

ulsa

Senior Member
Aug 26, 2008
213
54
Not working for me. Getting “Health service has stopped working” about every other second. Much more frequent than before…
Maybe I am doing something wrong.
It also seems to reset everything saved in the Health Service app, or? Maybe you should have mentioned that.
 
U

ulsa

Senior Member
Aug 26, 2008
213
54
wanam said:
Can you post your xposed logs?
Click to expand...
Click to collapse

16 sep 2014 11:46:32 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
-----------------
16 sep 2014 11:50:23 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
Loading modules from /data/app/ma.wanam.xshealth-1.apk
Loading class ma.wanam.xshealth.Xposed
Loading modules from /data/app/com.oasisfeng.greenify-4.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading class com.oasisfeng.greenify.pro.SettingsPatch
Loading modules from /data/app/com.bubblesoft.android.bubbleupnp-6.apk
Loading class com.bubblesoft.android.bubbleupnp.xmod.BubbleUPnPXMod
logging enabled: false
created audio cast fifo: /data/data/com.bubblesoft.android.bubbleupnp/audiocast
 
wanam

wanam

Recognized Developer / Inactive RC
Jan 26, 2011
6,209
30,012
Toulouse
wanam.net
OnePlus 7T
Sony Xperia 5 III
ulsa said:
16 sep 2014 11:46:32 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
-----------------
16 sep 2014 11:50:23 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
Loading modules from /data/app/ma.wanam.xshealth-1.apk
Loading class ma.wanam.xshealth.Xposed
Loading modules from /data/app/com.oasisfeng.greenify-4.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading class com.oasisfeng.greenify.pro.SettingsPatch
Loading modules from /data/app/com.bubblesoft.android.bubbleupnp-6.apk
Loading class com.bubblesoft.android.bubbleupnp.xmod.BubbleUPnPXMod
logging enabled: false
created audio cast fifo: /data/data/com.bubblesoft.android.bubbleupnp/audiocast
Click to expand...
Click to collapse

No issues on the logs, which means it should be working fine, are you using the latest SHealth update? were you using any other mod to get it working before?

About the App data, i got a popup to restore my data through SHealth App and it was restored with no issues!
 
U

ulsa

Senior Member
Aug 26, 2008
213
54
S health says it's the latest update.

I have not done any other mods.
I did not get a restore popup. The data was automatically restored when I uninstalled xsposed.

Skickat från min SM-G900F via Tapatalk
 
wanam

wanam

Recognized Developer / Inactive RC
Jan 26, 2011
6,209
30,012
Toulouse
wanam.net
OnePlus 7T
Sony Xperia 5 III
ulsa said:
S health says it's the latest update.

I have not done any other mods.
I did not get a restore popup. The data was automatically restored when I uninstalled xsposed.

Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse

Okay, if you have time to try the module again, PM me your logcat.

If don't get the same bellow errors, then it should be other thing:

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
 
  • Like
Reactions: ulsa
S

Sock12345

Senior Member
Jun 22, 2014
851
251
Works perfect!!!
Using Neatrom v2.2 odexed
Set false back to true and works without a fc :) @ulsa try fc and wipe data of shealth make a backup first if you dont want to lose progress.
Reboot and try again might work for you.

Verstuurd vanaf mijn SM-G900F met Tapatalk
 
  • Like
Reactions: ulsa
U

ulsa

Senior Member
Aug 26, 2008
213
54
Sock12345 said:
Works perfect!!!
Using Neatrom v2.2 odexed
Set false back to true and works without a fc :) @ulsa try fc and wipe data of shealth make a backup first if you dont want to lose progress.
Reboot and try again might work for you.

Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse

FC and wiping data worked perfectly. Thanks to you both!
 
  • Like
Reactions: wanam
DirkStorck

DirkStorck

Senior Member
Sep 5, 2009
3,702
814
Samsung Galaxy S20 / S20+ / S20 Ultra
Samsung Galaxy S24 Ultra
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.

---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
DirkStorck said:
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.
Click to expand...
Click to collapse
OK. I am running your wanam Xposed module. If that makes a difference ☺
 
JohnKuczek

JohnKuczek

Senior Member
Oct 19, 2010
374
57
Central Ohio
Google Pixel 4 XL
Google Pixel 6 Pro
DirkStorck said:
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.

---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------


OK. I am running your wanam Xposed module. If that makes a difference ☺
Click to expand...
Click to collapse

wanam said:
Yes my latest update include this fix.
Click to expand...
Click to collapse

I was running both modules and SHealth did not work. Uninstalled this module, and now SHealth is working. Having 2 modules doing the same thing must cancel out the thing...
 
trevagreene

trevagreene

Senior Member
Jan 8, 2011
352
36
Melbourne
clearing data on both shealth and health service resolved the FC's . Thanks heaps.

---------- Post added at 07:44 AM ---------- Previous post was at 07:27 AM ----------

I have noticed that the latest update to Wanam Xposed has a check box for disabled secure storage check for shealth. So can I uninstall this module and just check that box in the wanam xposed ?
 
wanam

wanam

Recognized Developer / Inactive RC
Jan 26, 2011
6,209
30,012
Toulouse
wanam.net
OnePlus 7T
Sony Xperia 5 III
trevagreene said:
clearing data on both shealth and health service resolved the FC's . Thanks heaps.

---------- Post added at 07:44 AM ---------- Previous post was at 07:27 AM ----------

I have noticed that the latest update to Wanam Xposed has a check box for disabled secure storage check for shealth. So can I uninstall this module and just check that box in the wanam xposed ?
Click to expand...
Click to collapse
Yes, you do NOT need this module if you are using Wanam xposed.
 
  • Like
Reactions: trevagreene
G

GastonC

Senior Member
Jun 27, 2014
195
11
Nvidia Shield TV & TV Pro (2019)
Samsung Galaxy S23 Ultra
wanam said:
Hi guys,

I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.

One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs

This module will let you bypass the secure storage checks on SHealth services, and load SHealth App with no hangs on Rooted devices running Xposed framework.

I did just the basic tests because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket :D .

attachment.php
attachment.php



Download

Note: You may need to clear SHealth and Health service data.


Thanks to:
  • Rovo89 for his awesome work on Xposed framework and Mods.
  • Tungstwenty for contribution on Xposed framework and his many Mods
Click to expand...
Click to collapse

I have a question about your module. I am still learning about all the stuff on android. So I fixed my S Health with the Buildprop editor. Yet I am unable to get Secure Storage to work, but S HEALTH DOES. So will you app solution work? Do I have to change what I did in build.prop?

---------- Post added at 04:44 AM ---------- Previous post was at 04:36 AM ----------
wanam said:
Hi guys,

I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.

One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs

This module will let you bypass the secure storage checks on SHealth services, and load SHealth App with no hangs on Rooted devices running Xposed framework.

I did just the basic tests because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket :D .

attachment.php
attachment.php



Download

Note: You may need to clear SHealth and Health service data.


Thanks to:
  • Rovo89 for his awesome work on Xposed framework and Mods.
  • Tungstwenty for contribution on Xposed framework and his many Mods
Click to expand...
Click to collapse

Does this also fix Private Mode?
 
You must log in or register to reply here.

Similar threads

GermainZ
  • Sticky
[INDEX] Xposed Modules Collection | Post Modules' Requests Here!
Replies
12K
Views
4M
russanandres
russanandres
C
[Mod][Xposed] Amplify - Battery Extender - Control alarms, services, and wakelocks
Replies
8K
Views
2M
A
amn1987
M
[APP][Xposed][1.6.5]Snapprefs - The ultimate Snapchat-utility [9.21.1.0] [JB-M]
Replies
14K
Views
3M
S
Scoobapigeon
C3C076
[APP][KK][XPOSED] GravityBox v3.6.2 - tweak box for Android 4.4 [23/04/2017]
Replies
14K
Views
3M
S
SiperX
C3C076
[APP][JB][XPOSED] GravityBox v3.7.2 - tweak box for Android 4.1/4.2/4.3 [30/04/2017]
Replies
9K
Views
3M
B
Borchuck

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 35
    wanam
    wanam
    Hi guys,

    I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.

    One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs

    This module bypass the secure storage checks on SHealth and Private mode services, and will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.

    I did just the basic tests for SHealth because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket :D .

    Download

    Note:

    • You may need to clear SHealth and Health service data (you will loose your Pedometer data).
    • Clearing Personal pages service will break Private mode.
    Troubleshooting:
    If you can't get Private mode to work after switching to Xposed, you need to go back to a stock FW and backup your private files, after that you can install Xposed and enable my module then remove "/data/system/users/privatemode_edk_1000" as advised by @invano.

    Changelog:
    1.0.1:
    - Add Private mode support.
    - App renamed from XHealth to XSecureStorage


    Thanks to:
    • Rovo89 for his awesome work on Xposed framework and Mods.
    • Tungstwenty for contribution on Xposed framework and his many Mods
    View
    3
    wanam
    wanam
    RS050377 said:
    Will you add private mode support also to Wanam Xposed?
    Click to expand...
    Click to collapse
    Yes, on my next update.
    View
    3
    wanam
    wanam
    I think i have some great news about Private mode too :D .
    View
    2
    I
    invano
    wanam said:
    I managed to reproduce this issue after clearing my "Personal pages service" data, it resets the private key on the service level only, and somehow the password stay incorrect while calling "mount_privatemode 1000 /mnt/shell/privatemode /storage/Private" even if i force the regeneration of the private and backup key!

    Disabling secure storage let you bypass its checks but it fails now on the Knox container level "com.sec.knox.container.util.EnterprisePartitionManager.mountPrivateMode", there no way to reset the password, obviously it requires the old one, so i don't see what we can do at this level :confused: .
    Click to expand...
    Click to collapse

    Hi,
    I also had this issue until some minutes ago.
    Honestly I don't know why but before rooting and installing xposed, I think I cleared the PersonalPage service data...I ended up in an unusable PrivateMode like other users on this thread but even worse, for me, the impossibility of removing my fingerprint reading since I was using the fingerprint unlock method with PrivateMode.

    I am investigating from 1hour and, as you said, there is something strange with the FsKeyBackup string. The 'getPrivateFsKeyBackup()' method always return null and the entire management of this second key seems to be left to com.sec.knox.container.

    BUT

    I found 'privatemode_edk_1000' under '/data/system/users' and guess what. By deleting this file (to force its creation again) the backup key is handled correctly, getPrivateFsKeyBackup() does not return null anymore and PrivateMode works again.

    *For users which have some files in PrivateMode: this procedure will reinitialize PrivateMode thus all your private data will be destroyed.

    I am testing all this stuff on a Note4 N910F
    View
    1
    wanam
    wanam
    ulsa said:
    S health says it's the latest update.

    I have not done any other mods.
    I did not get a restore popup. The data was automatically restored when I uninstalled xsposed.

    Skickat från min SM-G900F via Tapatalk
    Click to expand...
    Click to collapse

    Okay, if you have time to try the module again, PM me your logcat.

    If don't get the same bellow errors, then it should be other thing:

    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
    View

New posts