The new alphanumeric password is not yet really usable as it is not accepted in hybris-recovery, I’d say.
I had the “Ahoj boot loop syndrom”.
No way to recover my data as I could not enter recovery mode. (no probs tho, as I had a good backup)
PRECONDITIONS:
Having an alphanumeric password set
STEPS TO REPRODUCE:
Set an alphanumeric password
Try to enter recovery mode with fastboot
EXPECTED RESULTS:
Password accepted,
Enter in the phone’s recovery shell
ACTUAL RESULTS:
Password refused
MODIFICATIONS:
Patchmanager: yes
OpenRepos: yes
Chum: yes
Other: none specified
ADDITIONAL INFORMATION:
I tried with e.g ‘bbbbb’ password. Even that simple is not working whereas ‘12345’ is working.
edit:
My error somewhere. things like ‘bbbbb’ are working in recovery.
But other passphrases with numbers and some special signs are not.
Device Owner User: defaultuser + secondary user, same password
Home Encryption: enabled
the initial version of this bug report was created using Bugger 0.9.9+git3
I flashed another XA2.
My mistake/typo by testing on simple alpha passwords. They are working in recovery too.
But a more complex passphrase with a number and a special sign is not working in recovery whereas it is working to unlock the phone/partition in normal conditions.
E.g.:
“A b:1” (without quotes)
Thank you for the idea, @nephros
Alas, unfortunately no.
I tried with the english-US keyboard enabled, finding and hitting the correct keys to make the “A b:1” test code. But no.
Bug still of actuality.
My first guess is that the space character is not accepted at the gate of the recovery mode.
Namely, while “ A b:1 ” fails (XA2 with 4.5.0.24), the code “ Ab:123 ” lets me through.
The valid characters for the security code (in normal phone functions) are listed here:
It seems that we should add a remark for the space character (if fixing the code checker happens to be hard).
Also the security code “ ,.!?;:&%#()=+- ” is valid, i.e., all the special characters on the 3rd row (but not ‘space’) of the valid characters in that document ^.
Please note: the asterisk (*) does not belong to the valid characters.