Hey everyone, like an idiot I was disabling some bloatware via ADB (through ADB App Control) and was not careful enough...I'm now facing a serious problem.
For my lock screen, I am still using the old school method of a pattern and after rebooting the lock screen comes up. The problem lies with the fact there is no area in order to enter in the pattern and am locked out of my phone.
Some of the packages I got rid of are overlays which I'm guessing is where the problem came from. Does anyone know exactly what packages I need to restore to get the lock screen back up and running again? Thanks in advance
I'd just undo everything you did, then you'll be sure to get it back.
otherwise just flash the firmware over itself to restore all those system packages that you disabled.
This is why I never debloat. it's just not worth it, and it more often than not causes problems.
I never made a note of the actual packages I disabled because I just did it though ADB App Control. You can easily restore them back but only if the phone is unlocked which I can't do now because of this issue.
Is there a list of all of OnePlus8T's preinstalled packages? Can't find one online anywhere....
Though I know flashing the firmware is the sure way to fix this, I'm looking to only do this as a last resort with all the work to setup the phone would take me again.
Is there a way to flash firmware over the top without wiping data on OnePlus? I know there is for most other OEMs.
Related
This app: Ultimate Rotation Control
has now claimed a second victim. A long time ago, I installed URC on my Motorola Atrix, as a way to force screen rotation in certain apps. Once I uninstalled URC, my Atrix could no longer use the system's auto rotate feature, until I completely wiped it and installed a new ROM.
Well I was hoping that it was just a fluke, a one-time incompatibility with the Atrix. Because I needed it on my new phone, a Samsung Galaxy S3, because it was the only way to get Tasker to rotate my screen.
Well sure enough, the moment I uninstalled it from my S3, I could no longer use the system's built-in auto rotate feature, AGAIN.
I have tried rebooting, reinstalling the app, uninstalling the app with different settings (like uninstalling it while in force-rotate mode), toggling system rotate in different conditions... NOTHING I've tried gets it working again!
I've contacted the developer, but in the mean time, does anyone have any suggestions to get my phone's auto-rotate working again? Perhaps there's some hidden system file that URC messed with, that I can go edit to fix all of this? I really don't want to have to do a factory reset again!
moeburn said:
This app: Ultimate Rotation Control
has now claimed a second victim. A long time ago, I installed URC on my Motorola Atrix, as a way to force screen rotation in certain apps. Once I uninstalled URC, my Atrix could no longer use the system's auto rotate feature, until I completely wiped it and installed a new ROM.
Well I was hoping that it was just a fluke, a one-time incompatibility with the Atrix. Because I needed it on my new phone, a Samsung Galaxy S3, because it was the only way to get Tasker to rotate my screen.
Well sure enough, the moment I uninstalled it from my S3, I could no longer use the system's built-in auto rotate feature, AGAIN.
I have tried rebooting, reinstalling the app, uninstalling the app with different settings (like uninstalling it while in force-rotate mode), toggling system rotate in different conditions... NOTHING I've tried gets it working again!
I've contacted the developer, but in the mean time, does anyone have any suggestions to get my phone's auto-rotate working again? Perhaps there's some hidden system file that URC messed with, that I can go edit to fix all of this? I really don't want to have to do a factory reset again!
Click to expand...
Click to collapse
Flash your ROM again. If your phone isnt unlocked then... i dont know.
jason.hamilton said:
Flash your ROM again. If your phone isnt unlocked then... i dont know.
Click to expand...
Click to collapse
Flash what ROM? I'm running stock, rooted. My phone is unlocked.
But of course wiping the entire phone would fix it. I'm asking if there is any way to fix it without wiping everything.
Right now it seems like the only way I can get it working is to have the app installed and running at all times. Strange that I'm the only reviewer that has noticed this behaviour, maybe no one else has ever tried to uninstall it before?
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?
Hi there, your comments would be greatly appreciated.
To keep data, I flash the whole 8.0 stock firmware after removing -w.
After using days, the phone can't be easily unlocked, even by power key or by FPR. Sometimes, I need to wait a more long time for the phone waking up.
Sometimes the incoming call can't even wake it up, I can't answer the call.
Have reflashed the firmware with -w available then restore all my app via titanium backup. the issue persists.
Please help! How to tell which app prevent the phone from waking
Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk
Thanks. have tried clean install. everything is fine before restoring data with titanium.
So there must be some app which prevent phone from waking. Is there any chance of find this app.
PunishedSnake said:
Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I'd say just start over....
I'd say it's titanium backup restore itself
Sent from my Pixel using Tapatalk
thank you dude, will take a try.
If the issue persists you could give a list of the apps you install if you don't mind.. maybe we can figure out which one affects the unlocking. :highfive:
Sent from my Pixel using XDA Labs
I'm having a similar issue, but in my case I'm having trouble waking up the phone after it's been unplugged from the charger. If I use my phone all day after a full charge (and after rebooting), it's silky smooth, but the second I plug it in, the issue starts until I reboot again.
It might be extreme, but I've done this multiple times on previous phones. I restore half my apps, say the ones starting with A through M. If there's no problem, then I install half of what's left, say N through S, etc. Keep doing this as a process of elimination. Yes it's tedious but eventually you can narrow down the problem app and/or app data. You could also try restoring all of your apps without data, and if there's no problem then restore the data for half of the apps, etc.
Otherwise, as @PunishedSnake said, don't restore data (or even apps) at all with Titanium Backup. It sucks but we all occasionally have to do that.
I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).
Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
boojay said:
I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).
Click to expand...
Click to collapse
bush911 said:
Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
Click to expand...
Click to collapse
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).
Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
boojay said:
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Click to expand...
Click to collapse
bush911 said:
Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
Click to expand...
Click to collapse
Glad to hear you were able to resolve your problem. In my case, I actually don't want immersive mode activated all the time so I may still have to root in order to selectively choose which apps I apply this command to.
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).
Let me tell you a story (you can skip if you want to):
Once upon a time I ****ed up the back layer of the touch screen during repair and desperately tried to use my phone with my PC, found some tools online that let me simulate my phone's screen via ADB. Didn't got that working, ADB was unable to recognize my phone. Ok. Then i taped together the touchscreen (one of the absurdest things i ever did), reconnected it to the phone and guess what. It worked. I booted into recovery mode first and it worked flawlessly. No issues whatsoever. "Wonderful" i thought to myself, booting into system mode eagerly. The boot animation went by without any crashes, graphical issues or anything one could think off, and i even was able to enter my pin. When i did that i was full of enthuisasm. But that didn't last long. The SystemUI began to crash constantly, the lockscreen hasn't even finished building and it crashed again. I was absolutely unable to use the device and utterly devasted. Then i absolutely knew: i. ****ed. up.
But that didn't keep my from trying things out and eventually i was able to get past the lockscreen (without a SIM card so no PIN required) without any crashes and back up at least Whatsapp and a few other apps. But then i made the mistake of turning the screen off which set me back to square one: constant SystemUI crashes. I tried again and again and again and finally, after hours of work i got in a second time. This time, i thought to myself, i gonna make things differently. I backed up everything with Titanium, thought of myself to be safe. Which i technically was, i got backups of everything now. Then i decided to re-flash the rom without a factory reset which didn't do anything. Luckily there is an unofficial build of the ROM i'm using (Resurrection Remix) and i clean flashed it. It worked. Flawlessly. I was thrilled. The phone i was ready to toss into the trash finally worked again. I set everything up, thought myself to be safe but boy was i wrong. Google made regular (i think daily) backups of my apps and contacts and all so i wanted to restore that first. But it required a Pattern which i don't have because i always had a 5x5 pattern and it gave me a 3x3 pattern. I didn't know what to do with it!
I continued setting up my phone after failing to restore that backup and then instantly continued to restore the backup i made with Titanium, It installed all the missing apps, apparently restored the data. Nice. But there are a few apps that don't like that restored data so they just didn't use it and started from scratch again (like SwiftKey). Also, some of my contacts are missing and i'm lowkey too lazy to like the existing ones to Whatsapp again.
Tl;dr: ****ed up phone, got it working again, some apps didn't accept the Titanium backup and now i want to restore the Google backup which requires a 3x3 pattern which i don't have because i always used a 5x5 pattern.
Well, the question is simply: Is there a way to unlock the Google Drive backup without that pattern or do i need to try my luck again accessing the old Data (made a TWRP backup before flashing the new ROM)? If i do need to try again, how do i disable the lock on my backups? Do i only need to change my pattern to a 3x3 one?
I can't unlock my phone with the Pattern I assigned it. I always use the same Pattern, so I was pretty sure it's not an error. When I draw the pattern, it says "incorrect pattern" and makes me wait 30 seconds before trying again (from the first try).
Luckily, I have access to Samsung's Find my Mobile, I unlocked the device, removed the lock. But every time I restart the device, the bugged lock screen would come back, and I would have to unlock the device again with Find my Mobile.
please note that I can't set a new lock after unlocking the device, it will revert back to no lock after setting a new pattern/pin/password. definitely a bug.
if there is any method to fix this, or to reset Samsung's lock screen app, please let me know!
my device is Samsung Galaxy A8+ in case anyone was curious.
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
blackhawk said:
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
Click to expand...
Click to collapse
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
majdcomp said:
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
Click to expand...
Click to collapse
Oh my bad, it locks no matter what. That's not good.
Boot menu>clear system cache (don't hit factory reset by accident).
Google for the button sequence to hit for that model. Timing is critical, you might need to try more then once.
That might get it.
Try clearing the Dynamic Lock Screen data.
I would backup all critical data now if you haven't. Do not use Smart Switch to transfer settings if you do factory reset, ha-ha.
Someone here probably has a better solution as I know little about this system.
As always do a Google search, you can probably use solutions from other Samsung models going back a few years.
Erratic and strange behavior can also be a sign of a virus, rootkit etc.
When in doubt, factory reset especially if you can't track down the root cause.
Finding the root cause and correcting it is always preferable to a factory reset but not always possible. If the OS load is older then a year a factory reset be a good plan anyway... nothing like a clean, fresh OS.
Delete your Google account before you factory reset so that doesn't password pester you. I'm told if you reset from settings vs the boot menu that doesn't happen. Not sure haven't tried a factory reset that way.
sammiev said:
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
Click to expand...
Click to collapse
Can you do that on a stock Android that's not rooted?
blackhawk said:
Can you do that on a stock Android that's not rooted?
Click to expand...
Click to collapse
You would need to be rooted.
sammiev said:
You would need to be rooted.
Click to expand...
Click to collapse
I read if you load TWRP you'll lose things like Samsung Pay.
Seems risky at least to me. I like to play with it but don't have a phone to burn.
A factory reset for me at this point is fairly painless ie no data loss and takes under a couple hours.
If it's of any interest here:
On Android the pattern lock data (SHA-encrypted) is kept in a file named gesture.key and stored in the /data/system folder.
If phone's Android is rooted you simply delete that file to bypass the pattern lock. Using ADB you would run command sequence
Code:
adb devices
adb shell "rm -f /data/system/gesture.key"
to achieve this.
The phone should be now accessible with no pattern lock applied.