Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
jruivo said:
Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
Click to expand...
Click to collapse
Hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from the Vol down to the Vol up button. This should put you back into TWRP where you can reflash and start over. You have to be quick shifting from Vol down to Vol up or the tablet will boot to download mode instead of TWRP. If it does, then do the same thing again but switch faster.
jruivo said:
Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
Click to expand...
Click to collapse
If you have twrp installed its pretty easy to remove the pattern lock.
https://forum.xda-developers.com/redmi-note-4/themes/tool-remove-lockscreen-password-pin-t3692411
Thank you everyone, I was able to use the TWRP and restored a backup. I thought it was some app incompatibility but apparently none of the secure lock-screens work with SuperSU, they all mess it up and I end up restoring the tablet.
Related
Okay, I finally had time to update my A500 to ICS I was at 3.1 and was rooted. I went through several updates to get to ICS. 3.2, 3.2.1, a small patch, then 4.0.3. After the update finished, saying it was successful, my tab will reboot itself no longer than 30 seconds after it gets to the lock screen I don't have time to uninstall any apps that might be interfering with startup, not that i could tell whats doing it, and i don't have time to do the factory reset through the system menus Not sure why but the recovery (power&vol boot) only displays a red triangle over a dead droid so, guess my actual question is, how could i go about correcting this issue? I have ADB if needed, but I don't know were to start. any help would be appreciated. THANKS.
[Edit]
Okay, so I managed to turn off the wifi on my tab and it seems to stop restarting. When I do turn on the wifi, several apps give an error that they have stopped. after the second one pops up the tab then restarts unless the wifi is shut off. Any ideas as to what this may be would be appreciated.
Hi, sorry to say that i have the exact same problem.
Updated today from 3.2 to 4.0.3 and after first boot started the reboot sequence that only stopped after I managed to switch off the wifi...
I investigated a little but it seems this is quite an isolated issue... and all ways are leading to the factory reset...
StarCruiser said:
Hi, sorry to say that i have the exact same problem.
Updated today from 3.2 to 4.0.3 and after first boot started the reboot sequence that only stopped after I managed to switch off the wifi...
I investigated a little but it seems this is quite an isolated issue... and all ways are leading to the factory reset...
Click to expand...
Click to collapse
guess i'll give that a shot, i dont have much installed anyway...
Hi,
Got that problem too. Did a factory reset and it works fine now.
Sent from my HTC Desire HD using XDA
Here's on direct from Acer Support:
(of course us old dogs already know this trick)
Note: Clean boot will erase all the data/information which is saved on your tablet. Recommend you to back up the data before performing a clean boot. (yeah, like you can get in there to save it
1. Shutdown the power (press the power button for long time to shutdown).
2. Press and hold volume up key (the key next to rotation lock) until you finish step 4.
3. Press power button for 3 seconds until you feel device vibrates then release power button.
4. Once you feel device vibrates, very quick to switch on/off "rotation key" many times (this activity has to be done very fast, otherwise it will not success). To ensure you success, switch on/off rotation key when Acer logo appears on screen.
5. Wait for a while (you will see Erase Userdata and Erase Cache on top-left corner on screen), device will reboot and start from OOBE screen.
Managed to get it to work. Appreciate the help. Runs like a champ now.
Sent from my A500 using xda premium
Hi guys,
Recently i installed the ROMs Phoenix 9.4 and Imperium 10.0, both with S5 style. Both works fine, but one thing not. I configured a PIN Password in my phone, but after reboot the system, the unlock mode is set to Slide Unlock (without password), if i wait the screen turn off or lock the system and try unlock, then the PIN Password is required.
This happened in the two ROMs.
Have a way to fix it?
I would like the password was required at first, immediately after the system becomes available.
Sorry for my english, i wrote with some help of Google Translate.
Thanks!
Did you find a solution?
I have the same issue. It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result, basically the PIN lock does not activate untill 30 seconds or so after the phone boots up.
scott2ride said:
Did you find a solution?
I have the same issue. It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result, basically the PIN lock does not activate untill 30 seconds or so after the phone boots up.
Click to expand...
Click to collapse
No, I have not found a solution. A partial solution was to activate a Pattern Unlock.
I have just wiped and upgraded my Galaxy s4 to 4.4.2. I would like to fully encrypt my phone and use pattern unlock so I followed this article:
(just google pattern-unlock-an-encrypted-android-phone, I can't post URL)
But even though I have tried this multiple times and unplugged the USB cable (as mentioned in the article) as soon as I hit enter to start the encryption command the screen goes black on the phone and then after about 10min the phone reboots to the unlock screen and it is still unencrypted. I have tried following other articles too but they are all the same in terms of the command you run to encrypt the phone.
Any ideas? How can I get pattern unlock to work with an encrypted Android phone? Yes I know you can't do this via the GUI but then you need to enter a silly long password every single time you want to unlock the phone which is not an option for me. I don't mind entering a long password when turning on the phone but when it comes to unlocking the phones lock screen I would like to use the pattern unlock.
Any one else had any success with this on 4.4.2? Thanks!
BB007BB said:
I have just wiped and upgraded my Galaxy s4 to 4.4.2. I would like to fully encrypt my phone and use pattern unlock so I followed this article:
(just google pattern-unlock-an-encrypted-android-phone, I can't post URL)
But even though I have tried this multiple times and unplugged the USB cable (as mentioned in the article) as soon as I hit enter to start the encryption command the screen goes black on the phone and then after about 10min the phone reboots to the unlock screen and it is still unencrypted. I have tried following other articles too but they are all the same in terms of the command you run to encrypt the phone.
Any ideas? How can I get pattern unlock to work with an encrypted Android phone? Yes I know you can't do this via the GUI but then you need to enter a silly long password every single time you want to unlock the phone which is not an option for me. I don't mind entering a long password when turning on the phone but when it comes to unlocking the phones lock screen I would like to use the pattern unlock.
Any one else had any success with this on 4.4.2? Thanks!
Click to expand...
Click to collapse
Flash a different stock 4.4.2 . maybe its missing some files.
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube
when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?
WARKRIME said:
when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?
Click to expand...
Click to collapse
I have exactly the same problem, I installed thirdparty launcher like lawchair 2, and set it to default.
Don't know if it had something to do with this.
Now I flashed back to stock ROM.
Any one have a solution on this?
Not just your phone, I am experiencing this as well as of this moment. I have Galaxy S10, bootloader unlocked, rooted with Magisk and installed hades ROM.
After todays reboot, I cannot use my phone - on lockscreen, I draw a pattern and it just goes back to lock screen. It doesn't matter whether I boot the phone in root mode (Power + Bixby + Vol Up) or normal mode (just start with Power button).
I don't know how to fix it and I want to avoid reflashing the whole phone as I just finished setting it up from scratch.
Well... interesting thing... when this happens to you next time, try to boot into recovery (TWRP) and then back to system.
This has helped me twice now. After such reboot, I can get past the lock screen loop.
Still trying to figure out how to fix this.
zoomsk said:
Well... interesting thing... when this happens to you next time, try to boot into recovery (TWRP) and then back to system.
This has helped me twice now. After such reboot, I can get past the lock screen loop.
Still trying to figure out how to fix this.
Click to expand...
Click to collapse
When you do that, you boot in the non Rooted System. There it works for me too. But when i try booting into rooted System i have a Lockscreen loop as described of you.
btw Galaxy s10 SM-G973F
I ve been there once. In my case it was the SoundAssistant app causing this. Somehow. Luckily I had my PC authorized so I was able to use adb to uninstall the app and reboot. Then reinstall.
A little more details on this fyi, it isnt bootloop because its still in the lock screen. Just the app (with "appear on top" permissions) somehow isnt able to load properly so it keeps opening and closing.
If you happen to have SoundAssistant installed, try above. If not, you can go to safemode see if it still happens. After that you might need to take some time to figure out which app is causing.
I dont think this has anything to do with Magisk or root, at all.
alex.do said:
I ve been there once. In my case it was the SoundAssistant app causing this. Somehow. Luckily I had my PC authorized so I was able to use adb to uninstall the app and reboot. Then reinstall.
A little more details on this fyi, it isnt bootloop because its still in the lock screen. Just the app (with "appear on top" permissions) somehow isnt able to load properly so it keeps opening and closing.
If you happen to have SoundAssistant installed, try above. If not, you can go to safemode see if it still happens. After that you might need to take some time to figure out which app is causing.
I dont think this has anything to do with Magisk or root, at all.
Click to expand...
Click to collapse
I think do too. Had it solved by renaming every item with "keypass" in /vendor/lib/hw
which disabled my pin, so everything worked fine.
WARKRIME said:
when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?
Click to expand...
Click to collapse
Same problem