Hi everyone,
I stumbled upon this issue after fully encrypting my Honor 6 [H60-L04] running Marshmallow 6.0 and EMUI 4.0 (C432B860).
I've installed Keepass2Android and enabled its Accessibilty Sevice to use the AutoFill feature on my device.
Now, when I boot the phone, it no longer asks for a PIN at boot, instead it boots straight to the lock screen.
Googled this and found following "trick" to re-enable the boot prompt: "Reset your Pattern/PIN/Password, check the "Require ... to start device" option."
Okay, sounds good, but there is no "Require ... to start device" option in the dialogues when setting a new Pattern/PIN/Password?!
What can I do now?
Is there anything I can do to get the PIN at boot prompt back without having to wipe the phone? ADB maybe?
Any help is much appreciated!
Bump
136 reads and nobody knows a solution?
Update:
Uninstalled Keepass2Android in the meantime, but still no luck in getting back a securely encrypted android without a full wipe, which is a big downside in my eyes.
Makes no sense to encrypt a device when enabling an app-service disables the encryption so the device will boot without asking for the disk encryption password at boot.
This is a major design flaw.
Related
I was messing with my galaxy core prime (android 4.4.4) using a app to remove system apps that you can't with the stock app manager.. (no reason for crap like smartcard manager, bluetooth, wifi sharing..etc to be running when i haven't authorized such things, seems like security risk imo)
Was also editing the autorun list and messing with Norton applock and phone encryption settings to try to further secure it.
Welp, I f'ed things up because phone crashed and now can't do anything.. can't access home screen, settings, call/txt, nothing. So I booted into the stock bootloader and tried formatting the entire thing including cache..
Didn't fix the problem, can't finish the setup wizard without it crashing, get message saying setup, hangouts, and keyguard stopped working and then my phone bricks and can't do absolutely anything. No backup either.
I have been googling and googling for solutions but everything I read says to either:
-Reformat from bootloader (tried a 100 times)
-Wipe with TWRP or CWM (don't have either and can't access play store)
-Use Kies (won't detect my device since I can't enable MTP)
-ADB sideload twrp or cyanogen (cant, usb debugging probably not enabled since I formatted and no way to enable it since setup of android fails)
Odin can't detect anything either.. probably due to same reason. (Cant enable MTP or usb debugging)
So am I totally screwed? What are my options here?
I noticed the stock bootloader has a option to install from external storage.. can I put my sd card in a phone that does work and download twrp, cyanogenmod, (or ANYTHING else to fix this) to that, then put it back in my bricked phone and re flash it that way? That way I wouldn't need mtp or usb debugging... or won't that work?
Wasted so much time trying to fix this guys, googling and even formatted my pc removing Linux and reinstalling Windows hoping suddenly my pc would detect it.. atleast on linux when I used "adb devices" command it detected my device (trying to sideload anything didn't appear to work though, phone says error about verifying it and tries again and says completed and reboots but no sign of the rom I just supposedly sideloaded anywhere)
removing Linux and installing Window seems to have been a mistake because on windows using "adb devices" returns a blank list.. Tried different cords, ports, kies 2 and 3, reinstalling drivers, disabling firewall..etc but like I said even if I do get adb to detect it, what can I do from there without mtp or debugging?
Sorry for wall of txt, just want to be descriptive as possible so I don't get all replies telling me to try stuff that I've tried 100 times or just flat out won't work for my particular problem because of the above reasons..
will be sincerely grateful to anyone that took the time to read this and try to help me.
I have an encrypted device. Until recently it didn't have any lock screen protection, but I added a pin. I just rebooted the phone but at the usual password screen it asks me for the pin and only gives me a numeric keyboard. Obviously I can't get past this since my encryption password has letters in it.
I can access the device via the recovery with the old encryption password and it works fine over ADB. The question is, what do I do to set the keyboard back to the right type via the command line? Editing settings.db doesn't help - probably not accessible until disk is unlocked.
Any help is appreciated.
OS: Cyanogenmod 13
hello_world2 said:
I have an encrypted device. Until recently it didn't have any lock screen protection, but I added a pin. I just rebooted the phone but at the usual password screen it asks me for the pin and only gives me a numeric keyboard. Obviously I can't get past this since my encryption password has letters in it.
I can access the device via the recovery with the old encryption password and it works fine over ADB. The question is, what do I do to set the keyboard back to the right type via the command line? Editing settings.db doesn't help - probably not accessible until disk is unlocked.
Any help is appreciated.
OS: Cyanogenmod 13
Click to expand...
Click to collapse
Greetings and welcome to assist. A factory reset will fix the issue but I'm pretty sure your issue is rom related so I'd try asking in the rom thread
Good Luck
Sawdoctor
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
ravensfan8448 said:
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
Click to expand...
Click to collapse
So you're sending the phone back to Google....why? Because it came without the stock OS? It's hard to believe that the phone came with AOSP already installed...that's awesome if it did since AOSP is usually something that you have to load yourself.
So I'm sure you understand that your bootloader has to be unlocked in order to boot TWRP yes? Because typically when the bootloader is not unlocked the phone will reject the recover and shut down. So make sure your bootloader is unlocked in developer settings since you have a Google verison.
Sounds like your partitions are being weird when plugged in to the PC and its only seeing some of the partition. I would try to reinstall the driver and see where that gets you.
If you're concerned about your APKs, I would just use Titanium Backup and backup all the APKs to storage and then pull that from the phone using PC.
Hope this helps.
Dear all,
I do have a tricky question and I know already that this could be suspicious.
Allow me describe the issue.
I have Realme 5 where the user set password (not pin or gesture), but is unable to remember.
Now when phone starts (even before Android boot) it asks for password (not gesture or pin) which the user is unable to repeat.
Easy solution is factory reset, which is fine to be done.
But there is number of photos he wants to safe.
And I'd like to ask if there is a way to do so.
USB Debug is not allowed, therefore my thinking to use ADB is no possible as phone is not visible.
Is there any way to achieve the goal to safe the photos?
Can I make a backup, do factory reset and restore from backup?
Or is there any other chance? Via recovery/custom ROM? I guess not, since USB Debug is not allowed, right?
Thank you for hints or send me PM if you do not wish to discuss it here.
Jindrich
thanks all who checked this out.
I know how "silly" the request is, as this would be solution for any stolen device.
On the other hand, I was thinking about approaches and seems to me there is no way
Since I do not know pwd, I can't use recovery either, although there is sdcard slot, since I'll be asked for pwd before entering recovery (or before installing something via recovery).
I can't use ADB either, due to USB debug not enabled, this is also a dead end...
So I do not see a way how to get access DCIM folder..
J.
hello everyone ..
I'm trying to access my phone with correct password but i found that work profile is enabled with different lock screen password i didn't set any work profiles before when i searched for that problem i found that using cloned apps make work profile to be enabled automatically
Now my phone is locked with an important data on it So, I really do hope there is a way to get access to those data. And I'd be extremely grateful if someone could help me out with this.
There are many tools for this purpose available for windows and the most common way is by adb tools
Busybox with su might be an option?
can you explain the method i have no experience with that
hello everyone..
when trying to remove the screenlock the phone suddenly crach and restarted when the phone opens again it tells me to enter the pattern which i already removed with a notification on lockscreen says ''some functionality may be limited tap to unlock work profile'' now i can't access my phone and factory reset is not an option.
need help please
factory reset is your only option