Hi!
I have a rooted Sony Xperia Z, Jellybean 4.3. I am having trouble setting a security lock for my screen. The problem started after I uninstalled the Cyanogen mod on my phone and reverted it back to stock firmware. I re-rooted my device afterwards, using the exact same method I had used before installing the Cyanogen mod (following instructions from Doomlords CWM-based recovery and rooting thread). Now the root works just fine, every other aspect of my phone is working like a dream except for the security lock.
Here is what I do:
Settings > Security > Screen lock > Pattern
I have tried all other locks including PIN and Password but every time I press enter after putting in my pattern/PIN/password, the screen lock does not change from 'Swipe'. My screen lock was working fine on my rooted phone before I installed Cyanogen mod and while it was installed. However, now it seems to be broken.
Is there anything I can do or try to fix this? Thanks a lot for reading and I look forward to your replies!
P.S. I don't really want to install any apps that have a third-party locking system, I would just like to be able to lock my phone as I have usually done it
Do a backup of necessary apps and everithing what is for you necessary, next step is to do factory reset and then fresh install of your rom
Hmm, is that my only option? Is there root application (or any application) I can install that locks my phone in a similar way? That would be more convenient!
Related
Hi all,
I turned on my rooted nook color (which was running fine for a month) and suddenly, instead of the way I had customized the NC, I got the android logo on the screen, and was prompted to set up my google account again. It was similar to what you see as soon as you root the device for the first time. If I go to the 'extras' screen, all my downloaded apps are gone other than the default ones that came with the device. Superuser and NookColorTools are still there though. Anything I got from the market as well as all my custom settings are gone.
I have no idea what caused it. The process I used originally for stock rooting is here (using autorooter) and the device has 1.0.1. It was loaded to the internal memory.
nookdevs.com/NookColor_Rooting
Anyone know how I can return it to the way it was without losing my apps or data?
Sorry for my lack of correct terminology but I'm still new to this. I am afraid that if I try re-rooting I'll lose my settings and data. Thanks
EDIT: Just discovered something. I plugged in the NC to charge it, and it automatically installed an update bumping the firmware up to 1.1.0. I never manually did this update. And now I'm back to the default 8 apps under the extras screen, no NookColorTools or Superuser anymore. Seems it's back to factory defaults. Any way to at least salvage my angry birds data?
If you want to disable auto updates, you will need to follow these steps:
1. Re-root your NC
2. Download ADB or Root Explorer
3. Rename a file that is located in /etc/security. Change otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Thanks. It's odd that it was able to update the firmware at all, because it was always my understanding you needed to have the device back at stock (like new) before installing those, and this happened while it was still in a rooted state.
So you think there's no way to get it to the way it was without rooting again?
A question for any intellectual Android/Nook-addicts out there...
Basically, I've rooted my Nook HD+ (Numberous times now) and have experience rooting android devices in the past and have had no problems. I used the CWM method - installed universal root on factory stock (And afterwards, 2.1.0 stock just to see if it fixed the problem... it didn't) and extras (Tried not installing extras twice also, didn't make a difference)
Basically, I've learnt the hard way that eight resets on boot and the device hard-resets to factory stock. The first Root Bootup is fine (The bootup after removing the CWM sdc) and, after turning it off and on again, so is the second bootup... But the third one is where the problem occurs. I power on as normal, and the standard 'Nook' screen appears as it begins to boot...
It then proceeds to resetting itself eight times - never getting past the 'Nook' screen that appears at the start of every bootup, therefore causing a hard factory reset.
I've tried using the CWM recover method to the OS I used before rooting the nook originally, and there doesn't seem to be any problems if the device isn't rooted. I've also just let it update itself from factory version to current version - and it works fine with that also.
Perhaps this is common and I'm just a plain idiot. I honestly can't find any answers - so if it is common, sorry for wasting your time!
Thanks for your time!
- P
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
P Complex said:
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
Click to expand...
Click to collapse
Why are you installing superuser? It is already installed with the universal root. That may be it too.
Edit: And some of the apps I put on there are old on purpose. Like Root Browser. I have it set so that the free version is ad free. If you update it, the ad free goes away.
Sent from my Nook HD+ running CM10.1 on emmc.
I am VERY sorry it's taken me so long to reply! Even though I've only just joined, I should have done it long before now.
I found the problem - it was 'Pimp my Android' app. I was experiencing something called 'boot loop' - so much for my research skills for such a common problem. I fiddled about with my usual settings - and found some that cause it to get stuck like that, even when they're set not to activate on startup!
Tis' all working now. Everything else seems to be just peachy! You were right, thanks for your help
I don't know how this happen but it was previously on JB (slimbean) and I flashed Slimkat. It said it couldn't installation had failed a couple of times, so I did a factory reset and stuff and wiped the phone completely and tried again. The phone flashed correctly this time and I was able to boot into Kitkat, everything was working fine.
But when I tried to install Greenify etc. I found out that I had lost root. I'm not sure how this happened because obviously I was previously rooted otherwise none of this could have worked. I tried flashing another kernel (Mackay) nothing changed. I tried installing SuperSU etc. nothing.
Any ideas why? I just want to be rooted so that I can use the Galaxy S Unlock app to unlock the phone which is my main concern (need it for new sim). If there is any other method to unlock the phone without having to root it would be fine as well as long as I can unlock the phone.
Any ideas?
Thanks
utsmaster18 said:
I don't know how this happen but it was previously on JB (slimbean) and I flashed Slimkat. It said it couldn't installation had failed a couple of times, so I did a factory reset and stuff and wiped the phone completely and tried again. The phone flashed correctly this time and I was able to boot into Kitkat, everything was working fine.
But when I tried to install Greenify etc. I found out that I had lost root. I'm not sure how this happened because obviously I was previously rooted otherwise none of this could have worked. I tried flashing another kernel (Mackay) nothing changed. I tried installing SuperSU etc. nothing.
Any ideas why? I just want to be rooted so that I can use the Galaxy S Unlock app to unlock the phone which is my main concern (need it for new sim). If there is any other method to unlock the phone without having to root it would be fine as well as long as I can unlock the phone.
Any ideas?
Thanks
Click to expand...
Click to collapse
When you flash most of these KitKat ROMs it seems you lose the superuser facility in so doing. Go to Settings>About Phone>Build number .... and press it like 7 times until it says you have developer options. Then go to Developer options and allow root access to apps or apps and ADB depending on your preference.
Then try Galaxy S unlock.
If the unlock doesnt work (and I know some people who say it hasnt) go back to GB 2.3.6 stock, root it with cf-root as usual, and then try unlock there. Then move back up to your kitkat after its unlocked.
Incidentally when moving up to Kitkat be sure to flash fist Cyanogenmod ROM, CM10.2 (or above) to get the new CWM recovery and the correct partition so that the rom works well.
Let us know
Thanks for the response. What I did was flashed semaphore for KitKat using Odin. That did the trick for giving root. Used galaxsim unlock and everything succeeded except for one thing (network lock) but I think that may have been due to there being no Sim in the phone currently.
Sent from my Nexus 4 using Tapatalk
Root permission
joedom1 said:
Go to Settings>About Phone>Build number .... and press it like 7 times until it says you have developer options. Then go to Developer options and allow root access to apps or apps and ADB depending on your preference.
Click to expand...
Click to collapse
Thanks man!! I was also worried abt this. Installed SlimKat on my GT-N7000, everything worked ok (still testing) until I wanted root access, I installed SuperSU but it didnt get any response, I even reinstalled the CWM, which screwed my firmware (had to reinstall that too! :silly: )
After pressing "build number" as u said repeatedly, I got the developer options enabled, where I activated root permission. Then SuperSU installed n updated with proper root permission! :good:
Stallione said:
Thanks man!! I was also worried abt this. Installed SlimKat on my GT-N7000, everything worked ok (still testing) until I wanted root access, I installed SuperSU but it didnt get any response, I even reinstalled the CWM, which screwed my firmware (had to reinstall that too! :silly: )
After pressing "build number" as u said repeatedly, I got the developer options enabled, where I activated root permission. Then SuperSU installed n updated with proper root permission! :good:
Click to expand...
Click to collapse
Pleasure mate, not the first time its happened,
_________________
Hit the Thanks button if you think it helped
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
I don't get notifications working. Tried just about everything. Different stock roms, unlocked or locked bootloader, with or without twrp, with or without SuperSU/Magisk root...
In SafeCenter, and in later 3.5 Roms 'Security' app I disable all auto accelerate, anti spam, antivirus, auto cleanup. I white listed all apps/associated apps in autostart.
Enabled/disabled USB debugging.
Disabled all apps in Battery optimization
Sync on in account settings
In notifications settings everything enabled.
And still I don't get no freaking notifications! Only if open the app the notification appears..
Anything else I could try, and please don't tell me to use custom ROM! I want to get this fixed, it should be possible right?!
Edit;
Currently running 3.5.344ST/unlocked/twrp/supersu root
did u use a backup to restore apps or did u fresh install from store?
move app for /system/priv-app
Was it solved by moving into system/priv-app?
Did you get to the bottom of this ?
It makes a difference if you upgrade from very old ROM versions, or newer versions.
E.g. I started with ZUI 1.9xx (QFIL) and then OTA all the way up to the newest version (3.4xx)
Everything basically worked, but I had battery issues and some notification issues which I couldn't fix.
Then I tried to encrypt my device and it critically failed, so I had to switch to a new ROM anyway.
Then I took the newest possible full ROM for QFIL, I think it was ZUI 3.1xx and then OTA the short way up to the newest version.
Now Everything works, also encryption and with good battery life and notifications. But I feel the ROM is a little less snappy then before, maybe because of encryption.
Besides it still has 2 turn-downs:
- Some apps like Amazon Prime Video complain about an "uncompatible device ID" thus won't start
- Language is english and I can't manage to change the language permanently (not even with morelocale and ADB commands)
So our ZUK2 Pro's always have some funny behaviour... But I really feel the device is at its best now after ~1 Year in my pocket.
€dit: All with locked bootloader and without root