Just sharing if nobody have heard of it yet.
An app was released recently to fix the security vulnerability on our Android phones. In case you're bothered by that vulnerability, and you happen to have Xposed framework already installed, you may install this app http://forum.xda-developers.com/showthread.php?t=2365294 then activate it in Xposed. Many thanks to dev @Tungstwenty. His app is actually available also in Play Store -> https://play.google.com/store/apps/details?id=tungstwenty.xposed.masterkeydualfix
Before and after when checked by SRT app scanner.
http://db.tt/ZdOonmqi
Tapatalked from my bricked TX
I already patched, without using this
XD
Confirmed by using Bluebox
Using 9.1.B.1.67
And no malicious app or firmware too, using SRT
XD
How about you ?
Yenkazu said:
I already patched, without using this
XD
Confirmed by using Bluebox
Using 9.1.B.1.67
And no malicious app or firmware too, using SRT
XD
How about you ?
Click to expand...
Click to collapse
That's my actual one on screenshot in the OP.
Tapatalked from my bricked TX
Rycon33 said:
That's my actual one on screenshot in the OP.
Tapatalked from my bricked TX
Click to expand...
Click to collapse
Are you using this patch Rycon ?
Yes, I can see TiB is malicious app ?
I'm sorry, but I can't enlarge your pic from DropBox
XD
Yenkazu said:
Are you using this patch Rycon ?
Yes, I can see TiB is malicious app ?
I'm sorry, but I can't enlarge your pic from DropBox
XD
Click to expand...
Click to collapse
Yes I'm using it, the patch is for the master key and the two mentioned bugs. Then the SRT scanner I used only to confirm if the patch works, and it does really work. I don't mind what other apps the scanner is declaring as malicious or not.
Tapatalked from my bricked TX
Rycon33 said:
Yes I'm using it, the patch is for the master key and the two mentioned bugs. Then the SRT scanner I used only to confirm if the patch works, and it does really work. I don't mind what other apps the scanner is declaring as malicious or not.
Tapatalked from my bricked TX
Click to expand...
Click to collapse
Sorry Rycon, I have already see your screenshot
Actually, TiB not malicious app, since you have paid app, that cannot scanning correctly
SRT already said that
XD
Yenkazu said:
Sorry Rycon, I have already see your screenshot
Actually, TiB not malicious app, since you have paid app, that cannot scanning correctly
SRT already said that
XD
Click to expand...
Click to collapse
Ofc tibu is not malicious, it only cannot be read by scanner.
And we're not concern with that, the important thing is the patch works in containing the two mentioned bugs. Look at the before and after screenshot, before - vulnerable, after - secure for the two bugs(with number names)
Again, the patch is the "dual master key fix" app and then you can use any scanner to determine if the patch worked.
Tapatalked from my bricked TX
Related
Is our XZ being patched from Android Master Key vulnerability & Bug 9695860? Althoough Google had issue the pacth, but does anyone have any ideas/news from Sony?
if u have 4.2.2 installed then no worries. vulnerability has been fixed in that. download the Bluebox Security Scanner app and get a scan
Yes, patch, not sure on 4.1.2 but confirmed patch in 4.2.2
But there are two exploits.
Sent from my Xperia Z using XDA premium.
Dreiundachzig said:
But there are two exploits.
Sent from my Xperia Z using XDA premium.
Click to expand...
Click to collapse
master key vulnerability: patched
Bug 9695860: NOT patched (confirmed with SRT AppScanner)
Solution:http://forum.xda-developers.com/showthread.php?t=2365294
A big thank you to everyone on these information/updates. :good:
Feel more secure now when use my Z, at least 50% sure!
kennethso168 said:
master key vulnerability: patched
Bug 9695860: NOT patched (confirmed with SRT AppScanner)
Solution:http://forum.xda-developers.com/showthread.php?t=2365294
Click to expand...
Click to collapse
kennethso168 said:
master key vulnerability: patched
Bug 9695860: NOT patched (confirmed with SRT AppScanner)
Solution:http://forum.xda-developers.com/showthread.php?t=2365294
Click to expand...
Click to collapse
BOTH patched in coming 10.3.1.A.0.xxx versions
gbil said:
BOTH patched in coming 10.3.1.A.0.xxx versions
Click to expand...
Click to collapse
gbil someone on other topic received a 10.3.1.A.0.236 update and I saw that you are on .244!
Did you received the .236 update before? Is it going to be the official release?
Unofficial, no warranty, express or implied. Not final, nothing to do with the CM people, not backed by them, not made by them, may cause corruption of innocent kittens if used irresponsibly. I am posting this only because the main CM sources are not perfect right now for building for Qualcomm devices just yet, and need some tweaks in new branches.
CM 10.2 Android 4.3 built for, and working on C6603 International Xperia Z, once again thanks to Sony using such nice, open-source-friendly devices.
Working:
WiFi
Compass + sensors
Sound
Bluetooth
Front + Rear Camera
External SD
Not Working:
???
This is for the International C6603. Other devices at your risk. Build is for yuga, if that tells you whether it will work or not
http://goo.im/devs/pulser/XperiaZ/CM10.2/cm-10.2-20130807-UNOFFICIAL-yuga.zip
Awesome
Btw, can you provide me the device + vendor tree u used? Thanks sir
OT: (Sorry for that)
Is it compulsory to be a RC/RD to get a XDA Build Server? Sorry for OT Again
nolinuxnoparty said:
Awesome
Btw, can you provide me the device + vendor tree u used? Thanks sir
OT: (Sorry for that)
Is it compulsory to be a RC/RD to get a XDA Build Server? Sorry for OT Again
Click to expand...
Click to collapse
Yes, that is for RD/ERD/RC
I just used regular device and vendor tree for yuga, but used the "next" and "next-wip" branches of
frameworks/av
frameworks/native
hardware/qcom/media-caf
hardware/qcom/display-caf
hardware/libhardware
hardware/libhardware_legacy
Are you sure this is for the Yuga? Link name is Pollux_Windy. Thats the Tablet Z. Im gonna download it and check build.prop (maybe the filename is incorrect)
Taylor_Swift said:
Are you sure this is for the Yuga? Link name is Pollux_Windy. Thats the Tablet Z. Im gonna download it and check build.prop (maybe the filename is incorrect)
Click to expand...
Click to collapse
I guess you need to use the text in the link. It's linked wrong I believe.
I haven't seen any 4.3 gapps. Will try the 4.2.2 I have and report back
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 04:35 PM ---------- Previous post was at 04:20 PM ----------
pulser_g2 said:
Unofficial, no warranty, express or implied. Not final, nothing to do with the CM people, not backed by them, not made by them, may cause corruption of innocent kittens if used irresponsibly. I am posting this only because the main CM sources are not perfect right now for building for Qualcomm devices just yet, and need some tweaks in new branches.
CM 10.2 Android 4.3 built for, and working on C6603 International Xperia Z, once again thanks to Sony using such nice, open-source-friendly devices.
Working:
WiFi
Compass + sensors
Sound
Bluetooth
Front + Rear Camera
External SD
Not Working:
???
This is for the International C6603. Other devices at your risk. Build is for yuga, if that tells you whether it will work or not
http://goo.im/devs/pulser/XperiaZ/CM10.2/cm-10.2-20130729-UNOFFICIAL-yuga.zip
Click to expand...
Click to collapse
Quoted with correct link
Sent from my Nexus 7 using Tapatalk HD
pulser_g2 said:
Yes, that is for RD/ERD/RC
I just used regular device and vendor tree for yuga, but used the "next" and "next-wip" branches of
frameworks/av
frameworks/native
hardware/qcom/media-caf
hardware/qcom/display-caf
hardware/libhardware
hardware/libhardware_legacy
Click to expand...
Click to collapse
I built using the original sources. Seems like it's building correctly now. It boots
alnikki25k said:
I built using the original sources. Seems like it's building correctly now. It boots
Click to expand...
Click to collapse
can you upload build please?
eranda84 said:
can you upload build please?
Click to expand...
Click to collapse
Sure. Just let me finish up a few things.
You can flash this Gapps guys CLICK thx to banks
Anyone having issues with SMS with 10.2? I installed it on my ZL and me and another user are unable to send SMS. Want to figure out if it's ZL related or the Z is also affected.
Thanks!
havanahjoe said:
Anyone having issues with SMS with 10.2? I installed it on my ZL and me and another user are unable to send SMS. Want to figure out if it's ZL related or the Z is also affected.
Thanks!
Click to expand...
Click to collapse
There was this issue with HTC one as well not sure if codeworx fixed it
Sent from my C6603 using xda app-developers app
havanahjoe said:
Anyone having issues with SMS with 10.2? I installed it on my ZL and me and another user are unable to send SMS. Want to figure out if it's ZL related or the Z is also affected.
Thanks!
Click to expand...
Click to collapse
Nope. Nothing here. I could send messages. Put up the logcat when you send a message.
I can't get root to work, is it normal or should I flash again?
saibz said:
I can't get root to work, is it normal or should I flash again?
Click to expand...
Click to collapse
try flashing Chainfire's latest flashable SuperSU and let say if it's work.
gandou63 said:
try flashing Chainfire's latest flashable SuperSU and let say if it's work.
Click to expand...
Click to collapse
Thanks, although it's working now. I'm not exactly sure how, but I think messing around in "Developer options" somehow fixed it.
Nice work :thumbup:
Sent from my C6603 using xda app-developers app
Not sure if this is just a one-time release ROM but I've been using it for roughly a week and have no major issues, except for the occasional freeze. Oh sometimes the browser flickers too while typing characters in the "omnibar".
saibz said:
Thanks, although it's working now. I'm not exactly sure how, but I think messing around in "Developer options" somehow fixed it.
Click to expand...
Click to collapse
Yes. You need to first change the Root Access option under Developer options to Apps and ADB. Seems to reset Superuser permissions.
New build posted.
Hate being spied on and possible monitored,don't like your device telling you what you can do with it..Me too,so I fixed that.I have made this as Samsung Universal as possible.Some devices have different knox items/locations. I have tried to locate and remove as much as possible.If you see or know of an item I missed please post location and file/apk name.Removal of item's did not trip knox counter.Enjoy.
Does not remove knox from bootloader.
See removed item's below
View code here
ui_print("Removing Knox in System");
delete("/system/app/KNOXAgent.apk");
delete("/system/app/KNOXAgent.odex");
delete("/system/app/KLMSAgent.apk");
delete("/system/app/KLMSAgent.odex");
delete("/system/app/KnoxAttestationAgent.apk");
delete("/system/app/KnoxAttestationAgent.odex");
delete("/system/app/KNOXStore.apk");
delete("/system/app/KNOXStore.odex");
delete("/system/app/KnoxSetupWizardClient.apk");
delete("/system/app/KnoxSetupWizardClient.odex");
delete("/system/app/KNOXStub.apk");
delete("/system/app/KNOXStub.odex");
delete("/system/app/KLMSAgent.apk");
delete("/system/app/KLMSAgent.odex");
delete("/system/app/ContainerEventsRelayManager.apk");
delete("/system/app/ContainerEventsRelayManager.odex");
delete("/system/app/ContainerAgent.apk");
delete("/system/app/ContainerAgent.odex");
delete("/system/app/KnoxVpnServices.apk");
delete("/system/app/KnoxVpnServices.odex");
delete("/system/app/SecurityManagerService.apk");
delete("/system/app/SecurityProviderSEC.apk")
delete("/system/containers/framework/KNOXModeSwitcher.apk");
delete("/system/containers/framework/sec_container_1.zzzKnoxLauncher.apk");
delete("/system/priv-app/KNOXAgent.apk");
delete("/system/priv-app/KNOXAgent.odex");
delete("/system/priv-app/KLMSAgent.apk");
delete("/system/priv-app/KLMSAgent.odex");
delete("/system/priv-app/KnoxAttestationAgent.apk");
delete("/system/priv-app/KnoxAttestationAgent.odex");
delete("/system/priv-app/KNOXStore.apk");
delete("/system/priv-app/KNOXStore.odex");
delete("/system/priv-app/KnoxSetupWizardClient.apk");
delete("/system/priv-app/KnoxSetupWizardClient.odex");
delete("/system/priv-app/KNOXStub.apk");
delete("/system/priv-app/KNOXStub.odex");
delete("/system/priv-app/KLMSAgent.apk");
delete("/system/priv-app/KLMSAgent.odex");
delete("/system/priv-app/containereventsrelaymanager.apk");
delete("/system/priv-app/containereventsrelaymanager.odex");
delete("/system/priv-app/ContainerAgent.apk");
delete("/system/priv-app/ContainerAgent.odex");
delete("/system/priv-app/KnoxVpnServices.apk");
delete("/system/priv-app/KnoxVpnServices.odex");
delete("/system/priv-app/SecurityManagerService.apk");
delete("/system/priv-app/SecurityProviderSEC.apk")
delete("/system/etc/secure_storage/com.sec.knox.store");
delete("/system/etc/secure_storage/com.sec.knox.seandroid");
ui_print("Removing Knox in Libs");
delete("/system/lib/libknoxdrawglfunction.so");
delete("/system/lib/libknox_encryption.so");
ui_print("Removing Knox in Data");
delete("/data/data/com.sec.knox.containeragent");
delete("/data/data/com.sec.eventsmanager");
delete("/data/data/com.sec.enterprise.knox.attestation");
delete("/data/data/com.sec.knox.app.container");
delete("/data/data/com.sec.knox.seandroid");
delete("/data/data/com.sec.knox.store");
delete("/data/data/com.samsung.klmsagent");
delete("/data/data/com.samsung.knox.rcp.components");
delete("/data/data/com.sec.enterprise.knox.cloudmdm.smdms");
delete("/data/data/com.sec.knox.bridge");
delete("/data/data/com.sec.knox.knoxsetupwizardclient");
delete("/data/data/com.sec.knox.setupwizardstub");
ui_print("Knox Removed");
Changelog: 7/7/14
Updated uninstaller
7-17/14: Added removal of annoying security policy updater
i used on my i537 only thing left was
(com.sec.knox.eventsmanager) /system/app/containereventsrelaymanager.apk and /system/app/containereventsrelaymanager.odex
(com.sec.knox.containeragent) /system/app/ContainerAgent.apk and /system/app/ContainerAgent.odex
(com.sec.enterprise.app.knoxvpn) /system/app/KnoxVpnServices.apk and /system/app/KnoxVpnServices.odex
(com.sec.knox.app.container) /system/containers/framework/KNOXModeSwitcher.apk
(com.sec.android.app.knoxlauncher) /system/containers/framework/sec_container_1.zzzknoxlauncher.apk
will edit if i find more
Thank you very much. I will add ASAP.
blaz1nr said:
Thank you very much. I will add ASAP.
Click to expand...
Click to collapse
how do I use this ie install it please
Flash in recovery
updated
can this be flashed through stock recovery or do i need to have safe strap running?
Safestrap
blaz1nr said:
Safestrap
Click to expand...
Click to collapse
hello my gf is flashing it on her phone and she is still getting the security policy update message does this remove it?
wolf45801 said:
hello my gf is flashing it on her phone and she is still getting the security policy update message does this remove it?
Click to expand...
Click to collapse
I uploaded wrong version. I have one that stops that. will update soon.
Delete SecurityProviderSEC.apk from the script. It's an Android app. You NEED this if you want to use the Android Keychain.
You want a more KNOX and Sammy's root protection-free /system partition? Add this to script:
/system/bin/tima_dump_log
/system/bin/containersetup
/system/tima_measurement_info
/system/preloadedkiosk/
/system/preloadedsso/
/system/app/Bridge.apk
/system/app/EdmSimPinService.apk
/system/app/EdmSysScopeService.apk
/system/app/EdmVpnServices.apk
/system/app/KnoxMigrationAgent.apk
/system/app/KnoxSetupWizardClient.apk
/system/app/KnoxSetupWizardStub.apk
/system/app/RCPComponents.apk
/system/app/MDMApp.apk
/system/app/UniversalMDMClient.apk
/system/app/SysScope.apk
/system/priv-app/SPDClient.apk
/system/framework/com.policydm.features.jar
/system/framework/ContainerProxies.jar
/system/app/Bridge.odex
/system/app/EdmSimPinService.odex
/system/app/EdmSysScopeService.odex
/system/app/EdmVpnServices.odex
/system/app/KnoxMigrationAgent.odex
/system/app/KnoxSetupWizardClient.odex
/system/app/KnoxSetupWizardStub.odex
/system/app/RCPComponents.odex
/system/app/MDMApp.odex
/system/app/UniversalMDMClient.odex
/system/priv-app/SPDClient.odex
/system/framework/com.policydm.features.odex
/system/framework/ContainerProxies.odex
/system/lib/libcordon.so
/system/lib/libmealy.so
/system/lib/libspdkeygen.so
/system/lib/libtyrfingr.so
/system/lib/libtwifingr.so
/system/etc/permissions/com.policydm.feature.xml
/system/etc/permissions/mycontainerbadge.png
/system/etc/permissions/sec_mdm.xml
/system/etc/secure_storage/com.sec.knox.seandroid/
/system/etc/secure_storage/com.sec.knox.store/
Also, delete this lines from build.prop:
ro.config.knox
ro.config.tima
ro.config.timaversion
ro.security.mdpp.ux
security.mdpp
ro.security.mdpp.ver
ro.security.mdpp.release
security.mdpp.result
If you also want to save some of your privacy without breaking any functionality, delete this:
/system/app/TcpdumpService.apk
/system/app/SilentLog.apk
very very fine exelent ....thanks
this has only effect on tw based roms?
Success
Tried it on i537 and worked. After install and reboot it showed a screen "Android is Upgrading, optimizing apps x of 133". After that, checked the phone and it appears that it's working properly. Thanks!!
pinyata said:
can this be flashed through stock recovery or do i need to have safe strap running?
Click to expand...
Click to collapse
blaz1nr said:
Safestrap
Click to expand...
Click to collapse
Sorry guys, but what this mean?
I have stock 4.4.2 on S4 LTE 9506 Europe.
No idea what Safestrap is
So, can I simply run the script or I need to do something else first?
Thanks
J
blaz1nr said:
I uploaded wrong version. I have one that stops that. will update soon.
Click to expand...
Click to collapse
Was the updated version posted? Im also receiving these messages
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Well I updated the script with the changes/additions iJo09 posted with the exception of the build.prop since I've modified mine beyond what iJo09 mentioned and doubt many other people would want the changes. It flashed alright and my phone booted, but I haven't tested beyond that yet since it's late.
-edit-
So far my phone's working as expected with no issues or errors.
Kyuta Syuko said:
Well I updated the script with the changes/additions iJo09 posted with the exception of the build.prop since I've modified mine beyond what iJo09 mentioned and doubt many other people would want the changes. It flashed alright and my phone booted, but I haven't tested beyond that yet since it's late.
-edit-
So far my phone's working as expected with no issues or errors.
Click to expand...
Click to collapse
Has anyone tested this version? Results?
Does it rid of the annoying security update messages?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
pvchip3 said:
Has anyone tested this version? Results?
Does it rid of the annoying security update messages?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't received any security update messages and as I stated in my edit no issues so far phone's running as expected.
Kyuta Syuko said:
I haven't received any security update messages and as I stated in my edit no issues so far phone's running as expected.
Click to expand...
Click to collapse
Im still receiving the security updates after flashing your zip...any suggestions?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Hey all!
just received my z3 compact after years of being sammy boy
first i must say this device rock..
is there anyway to change the hardware buttons layout ? to be more like the galaxy buttons ? back on the right and last apps on the left ?
or its possible only on custom roms ?
Those aren't hardware keys but soft keys (the navigation bar) AFAIA the order can only changed when the phone is rooted, with Xposed for example.
Iruwen said:
Those aren't hardware keys but soft keys (the navigation bar) AFAIA the order can only changed when the phone is rooted, with Xposed for example.
Click to expand...
Click to collapse
lol yeah, i meant the NavBar keys
guess we'll have to wait for a proper root method
spyvsspy said:
lol yeah, i meant the NavBar keys
guess we'll have to wait for a proper root method
Click to expand...
Click to collapse
I came from the world of Samsung too, and Blackberry before that, so yeah...I think the back key belongs on the right as well.
But yeah, you do have to root to change it. To me, this and the other options Xposed gives me are more than worth the slight loss in camera quality from the bootloader unlock. I mean, look how nice this is....
damn... Now that you lost those drm ****ties, you think you will be able to restore them ? i think im gonna root my device aswell (b)
It looks great btw!!!
Sent from my D5833 using XDA Premium 4 mobile app
mattdm said:
I came from the world of Samsung too, and Blackberry before that, so yeah...I think the back key belongs on the right as well.
But yeah, you do have to root to change it. To me, this and the other options Xposed gives me are more than worth the slight loss in camera quality from the bootloader unlock. I mean, look how nice this is....
Click to expand...
Click to collapse
it looks ****ing fantastic!
did you use the root method posted here on xda ?
and did you find any luck with camera alternative who gave somewhat of a nice results out of this 21megacrap camera ? if not, you're not worrying with those lost drm keys ?
i'm probably gonna root this device in the next hour
spyvsspy said:
damn... Now that you lost those drm ****ties, you think you will be able to restore them ? i think im gonna root my device aswell (b)
It looks great btw!!!
Sent from my D5833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
spyvsspy said:
it looks ****ing fantastic!
did you use the root method posted here on xda ?
and did you find any luck with camera alternative who gave somewhat of a nice results out of this 21megacrap camera ? if not, you're not worrying with those lost drm keys ?
i'm probably gonna root this device in the next hour
Click to expand...
Click to collapse
Yeah, I used the root method in DooMLoRD's bootloader unlock thread.
I haven't tried every camera app on the market, but I haven't found any yet that can match the stock Sony camera, even crippled. To be honest, it still takes fantastic pictures most of the time. It's only crippled when you're shooting in low light without flash, which I don't really do that often.
But even more important than that, I can't live without Xposed modules. So no, I'm not worrying about the DRM keys.
(And no, there will be no way to restore them.)
mattdm said:
Yeah, I used the root method in DooMLoRD's bootloader unlock thread.
I haven't tried every camera app on the market, but I haven't found any yet that can match the stock Sony camera, even crippled. To be honest, it still takes fantastic pictures most of the time. It's only crippled when you're shooting in low light without flash, which I don't really do that often.
But even more important than that, I can't live without Xposed modules. So no, I'm not worrying about the DRM keys.
(And no, there will be no way to restore them.)
Click to expand...
Click to collapse
so.. i looked at the root howto, and it seems my rom version is 23.0.A.2.93 , which is not compatible with the root method..
i haven't received OTA update.. ever experienced update from 3rd parties?
spyvsspy said:
so.. i looked at the root howto, and it seems my rom version is 23.0.A.2.93 , which is not compatible with the root method..
i haven't received OTA update.. ever experienced update from 3rd parties?
Click to expand...
Click to collapse
Have you tried to manually check for an update?
mattdm said:
Have you tried to manually check for an update?
Click to expand...
Click to collapse
yeah... only got movies/album apps update.. nothing major.
spyvsspy said:
yeah... only got movies/album apps update.. nothing major.
Click to expand...
Click to collapse
Well, you could download the 23.0.A.2.105 firmware on your computer and use Flashtool to install it.
spyvsspy said:
so.. i looked at the root howto, and it seems my rom version is 23.0.A.2.93 , which is not compatible with the root method..
i haven't received OTA update.. ever experienced update from 3rd parties?
Click to expand...
Click to collapse
Actually, it seems you can actually used DooMLoRD's method with 23.0.A.2.93.
Due to the Xperia E1 having only 512MB RAM, Sony added a line inside build.prop that disables some features in Android so that the phone won't be running slow. If we change the value of the line from true to false, it will re-enable the disabled features and lockscreen widgets will come back.
Steps:
1. Download an advanced file manager from Play Store (Root Browser)
2. Go to /system and open build.prop with the text editor.
3. Search for the line
Code:
ro.config.low_ram=true
4. Change the value 'true' to 'false'
Code:
ro.config.low_ram=false
5. Reboot
xezrunner said:
Due to the Xperia E1 having only 512MB RAM, Sony added a line inside build.prop that disables some features in Android so that the phone won't be running slow. If we change the value of the line from true to false, it will re-enable the disabled features and lockscreen widgets will come back.
Steps:
1. Download Root Browser from Play Store (Root Explorer is not gonna work)
Click me
2. Go to /system and open build.prop with the text editor.
3. Search for the line
Code:
ro.config.low_ram=true
4. Change the value 'true' to 'false'
Code:
ro.config.low_ram=false
5. Reboot
Click to expand...
Click to collapse
The swipe lockscreen is software bug, or It can be solved with tinkering with build.prop?
Can't work in my xperia e1 dual
If I Help You Then Say Thanks
Kizoky said:
The swipe lockscreen is software bug, or It can be solved with tinkering with build.prop?
Click to expand...
Click to collapse
I tried to set stuff in build.prop, but it still did not work, so I believe it is some kind of software bug, or Sony added something else ( a security certificate thing or something ) that disable the options.
Vicky7999 said:
Can't work in my xperia e1 dual
If I Help You Then Say Thanks
Click to expand...
Click to collapse
That's very unfortunate to hear. Did you do it with Root Browser, or were you using something else? I myself have tried editing build.prop with Root Explorer but it did not work. Root Browser seems to work correctly, or you can also do it using adb push\pull.
xezrunner said:
That's very unfortunate to hear. Did you do it with Root Browser, or were you using something else? I myself have tried editing build.prop with Root Explorer but it did not work. Root Browser seems to work correctly, or you can also do it using adb push\pull.
Click to expand...
Click to collapse
OK I will try
Sent from my D2105 using XDA Free mobile app
xezrunner said:
I tried to set stuff in build.prop, but it still did not work, so I believe it is some kind of software bug, or Sony added something else ( a security certificate thing or something ) that disable the options.
Click to expand...
Click to collapse
No there is no security certificate or software bug. do you use the the single sim (D2005, D2004) or dual sim (D2105, D2104) variant of the e1?
for me it's working
7Zero3 said:
No there is no security certificate or software bug. do you use the the single sim (D2005, D2004) or dual sim (D2105, D2104) variant of the e1?
for me it's working
Click to expand...
Click to collapse
I have a D2005 with 20.0.A.1.21 right now (reinstalled JB for reasons) but this was working last time on 20.1.A.2.13.
xezrunner said:
I have a D2005 with 20.0.A.1.21 right now (reinstalled JB for reasons) but this was working last time on 20.1.A.2.13.
Click to expand...
Click to collapse
Okay then it can be a bug on jelly bean. I can not test now because I can not make a backup of my KitKat firmware. otherwise I would now switch to the Jelly Bean firmware
7Zero3 said:
Okay then it can be a bug on jelly bean. I can not test now because I can not make a backup of my KitKat firmware. otherwise I would now switch to the Jelly Bean firmware
Click to expand...
Click to collapse
The Lockscreen bug only occurs in KitKat, JB is fine. They rushed KK fast on this phone. I regret that day when I bought this phone.
VPN does not work either. Sony does not release Device tree, nor add AOSP support for this phone, so we can't fix it ourselves.
How many devices are affected by this bug please? My E3 on the new 4.4.4 version does not have this issue for example.
image45 said:
How many devices are affected by this bug please? My E3 on the new 4.4.4 version does not have this issue for example.
Click to expand...
Click to collapse
Only the Xperia E1 with KitKat has this issue. They decided to just quickly make the KK for the E1 and didn't care about the bugs (most likely).
xezrunner said:
Only the Xperia E1 with KitKat has this issue. They decided to just quickly make the KK for the E1 and didn't care about the bugs (most likely).
Click to expand...
Click to collapse
There was an updated 4.4.2 build the .14 that states to improve camera stability in a members post. Does anyone know if the screen lock bug is still present. Sony developer world Emma is only flashing the 20.1.A.2.13 build number on unlocked bootloader devices at the moment, however it's advising that the first 4.4.2 .47 build is the latest available version whenever it checks for new updates. I have not seen a 20.1.A.2.14 ftf file for xperia flasher yet.
image45 said:
There was an updated 4.4.2 build the .14 that states to improve camera stability in a members post. Does anyone know if the screen lock bug is still present. Sony developer world Emma is only flashing the 20.1.A.2.13 build number on unlocked bootloader devices at the moment, however it's advising that the first 4.4.2 .47 build is the latest available version whenever it checks for new updates. I have not seen a 20.1.A.2.14 ftf file for xperia flasher yet.
Click to expand...
Click to collapse
Using XperiFirm you can get any of the firmwares you wish. And no, all the firmwares are buggy. Even the Dual versions. Also it's not just the lockscreen bug, it's VPN and overall system stability that's broken.
xezrunner said:
Using XperiFirm you can get any of the firmwares you wish.
Click to expand...
Click to collapse
I have not seen that normally a link to Google drive is posted for example that allows you to download an ftf file of the new build. Not many appear to use Sony Emma, or discussions are low on using this tool.
I was trialing a Z3 style unlock screen and got stuck without been able to get the swipe to Unlock option back. I had to use the philz recovery that K4sh provided for forum E1 users to get back to normal.
image45 said:
I have not seen that normally a link to Google drive is posted for example that allows you to download an ftf file of the new build. Not many appear to use Sony Emma, or discussions are low on using this tool.
I was trialing a Z3 style unlock screen and got stuck without been able to get the swipe to Unlock option back. I had to use the philz recovery that K4sh provided for forum E1 users to get back to normal.
Click to expand...
Click to collapse
If you want to get Swipe to unlock back, you can just simply sync your phone with your Google account (gmail), set up a pattern, go to lockscreen, type in pattern wrong 5 times, select Forgot pattern, type in your creditnals, then exit out from the thing that appears. Then lock the device and see for yourself.
xezrunner said:
If you want to get Swipe to unlock back, you can just simply sync your phone with your Google account (gmail), set up a pattern, go to lockscreen, type in pattern wrong 5 times, select Forgot pattern, type in your creditnals, then exit out from the thing that appears. Then lock the device and see for yourself.
Click to expand...
Click to collapse
So there are workarounds but no current fix.
Is XperiaFirm another program tool or a site? I have visited the sony developer world site, however it does not seem to have any ftf files for the Xperia flasher.
image45 said:
So there are workarounds but no current fix.
Is XperiaFirm another program tool or a site? I have visited the sony developer world site, however it does not seem to have any ftf files for the Xperia flasher.
Click to expand...
Click to collapse
XperiFirm is a tool for downloading Xperia phones' firmwares, even from different countries. It downloads FILESETS or if unpacked by the tool, ftf contents which can be put together in Flashtool to an ftf file, then flashed to your device.
I sent an email regarding issues with the KitKat build to Sony, though I don't think they will care.
I tried but ist it's not working
Aryan Chaurasiya said:
I tried but ist it's not working
Click to expand...
Click to collapse
Try writing ro.config.low_ram=false to the bottom of the file, then reboot and check Settings.
What tool did you use to edit the file?