Database Develop

Random Factory Reset (Stock)

Sister says she was driving and phone suddenly factory reset (android recovery icon with text saying erasing, or something along those lines). After the process completes you are greeted with the setup screen to select your language and continue setup. Took a while to get past this since this process somehow also turned on voice assistant. If anyone else experiences this, you need to use two fingers to scroll and tap the item you want, then double tap it to select. (Ex: when you get to a keyboard, to type the letter "a" you need to tap a to highlight it, then double tap "a" to actually send the letter to the textbox. Powered off and jumped into recovery menu which showed a system update progress bar then displayed the following:
LMY47X.G920TUVU3DOJ7
....
(Recovery Menu Options)
....
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I found a post elsewhere about CSC which indicated it had to do with regional codes which will identify the firmware to issue to the device. The post also said after updating the code your device will reset. So, any thoughts on why this would randomly happen? Phone lock screen was secure so accidental taps/presses seems unlikely. I wasn't present at the time of the incident so I cant be certain of each step that took place before it randomly factory reset.
NOTE: Device is fully stock, never rooted or attempted to root. The phone is up an running so this is not a post requesting help for that, just to share experience with others that may run into this issue and possibly find out what caused it.

Messed up with 'vdc cryptfs changepw password' and entered hex values I can't type.

TL;DR I need an answer to one of the four questions at the bottom.
Preferably #1 or #3.
---------------------------------------------------------------
I have a Oneplus 3T running the latest Resurrectionremix (7.1.1) and TWRP recovery (3.0.4-1).
I use a pattern lock and device encryption, but I had separate passwords for the pattern and the encryption.
I tried to change my encryption password back to my pattern combo using 'vdc cryptfs changepw password' and entering numbers that correspond to the dots of the pattern. (E.g. in a 3x3, the dots are labeled 1-9)
Let's say the password I entered was '123456789'
I didn't realize that I needed to enter the HEX values in this command, (313233343536373839) so I just entered the ASCII values (123456789). The password I entered was all numbers so it corresponded to HEX values without giving an error.
Now, when I restart my phone, or boot into TWRP, I cannot enter the password I set. I cannot access adb or a terminal when booting android, and I cannot use 'vdc cryptfs' through TWRP. (I can use adb and terminal through TWRP)
The obvious solution is to convert the HEX values I entered to ASCII values and type them in, but I have two problems:
I use an odd number of dots for my pattern lock, and I entered an odd number of numbers for the HEX password. I don't know how that would break down into ASCII, because you need 2 HEX digits per ASCII character.
No matter how I convert the HEX to ASCII (either by prepending or appending a 0) there are characters that cannot be typed on a keyboard, and cannot be pasted into an adb shell.
---------------------------------------------------------------
I can think of a number of possible solutions to this problem:
How can I input my encryption password in hexadecimal rather than ASCII?
I think this would only be possible through TWRP/adb. It only needs to be temporary; I'll move my data out and format everything.
How can I backup the encrypted '/data' partition to my PC?
This way, I can freely format my phone while I try to decrypt the encrypted blob. Additionally, are there tools to help me decrypt the partition on a PC?
How can I use 'vdc cryptfs' in TWRP?
Right now, the problem is that it cannot find 'cryptd'. If I can get this to work, I can reset the password to something typeable.
How can I use 'vdc cryptfs' in Android without entering a password on boot?
As I said, my phone doesn't turn on adb before I enter the password, and I can't access Terminal or anything... or is there a way?
Or can I solve this any other way, without losing my data?

Change Encryption Password

Hi all,
I have a problem. I made a mistake when changing my encryption password using "vdc cryptfs changepw" command. I tried to change the old password to PIN which apparently only successful in changing the modes of the password. My mistake is that I didn't test the new PIN first and directly reboot. Now, my phone is asking for PIN at decryption screen while the decryption password is still my old password (I checked it in TWRP, it successfully decrypt using my old password). Is there any way to change the keyboard at decryption screen to text mode?
I'm using Sultanxda's CM13
Thanks.
UPDATE:
Solutions I have tried:
1. Using TWRP to change the decryption password again. Doesn't work, it said cannot find cryptfs
2. Using adb to paste text in decryption PIN text field. Doesn't work, adb is not initialised in decryption screen

HELP Again!

I accidentally made my secure boot pin letters instead of numbers. I can enter twrp by typing the corresponding letters to my intended numeric pin. However, on android boot a full keyboard is not present and I can only enter numbers. Therefore the pin fails every time! I already deleted lockscreen.bd and did a full wipe. Ideas?

Each number represents 3 letters. Use the corresponding numbers at secure boot to match your alphabetical pin.

[SOLVED] Can't enter safe mode

The phone doesn't start after installing EdXposed and the Riru Core Magisk module.
I want to enter Safe mode, but it doesn't work. I somehow managed to enter safe mode previously out of pure coincidence (no idea what I did, I pressed some buttons and i got there during a boot sequence, but it was nothing like the tutorial that Google gives you on how to do it properly).
So, I read you can do it like this:
https://support.google.com/pixelphone/answer/2852139?hl=en
However, this doesn't work for me, here's my boot process:
Power on
Unlocked bootloader warning (I skip it)
Google logo shows up
Screen color calibration changes slightly
Google animation starts (i press volume down)
Google animation ends
Normal Google logo stays there for a few seconds
Loading bar appears
Loading bar stayed there overnight (phone doesn't get hot or anything)
Is there any way to:
Enter safe mode properly
Start a terminal in recovery mode (like TWRP) to use the mm module to disable Magisk
Have an on device file manager (like TWRP) to manually delete the app
Delete files using adb
Get a normal adb shell (not sideload)
EDIT 1:
Starting "rescue mode" via fastboot shows the bootloader warning again, then the Google logo and then it's stuck (no color shift, no animation). Same for "recovery mode".
I cannot connect via adb/fastboot while the Logo is showing.
EDIT 2:
I managed to start "rescue mode" by doing the following:
Press power button
Press power button again (Entry selected: "Start")
Press both volume buttons and don't release them (I'm getting desperate here lol)
Bootloader warning (not skipped)
Rescue mode shows up (opened up Android, says "No command")
I can connect via adb, but "adb shell" or any other useful command says "error: closed"
EDIT 3:
Wtf, I got an adb shell by doing the following inside rescue mode:
"adb shell" -> Error
"adb pull /system/" -> Error
"adb pull /etc/hosts" -> Error
Phone restarted
Bootloader warning (skipped it)
Google logo, Animation & loading bar
adb connected
EDIT 4:
I entered the adb shell and used "setprop persist.sys.safemode 1" (source) (which registered correctly), but after rebooting, the phone still loads forever.
EDIT 5:
Turns out Safe mode didn't work because of Magisk/Riru/EdExposed or whatever, so I disabled Magisk by "touch /cache/.disable_magisk" (source) and now I successfully booted into safe mode.

Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!

cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Using this will most likely get you booted up to fix what you need...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557

cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Where are you stuck?