Recovering InnoDB database from backed up “data” folder in XAMP in Windows 10

I copied the data directory from mysql folder and uninstalled the XAMPP as the MariaDB was not starting. I installed XAMPP same version and backed up the data folder into mysql data directory. At first only copied the required database folder named production inside the mysql data directory. PhpMyAdmin showed the tables correctly though no record/row was there and it showed "Table doesn’t exist in engine". Then I copied all the contents from the DATA folder to the mysql data folder and now it does not start. Now the problem is MariaDB is not starting. I tried setting the innodb_force_recovery but it failed to start the mysql.

The error log is given below:

2021-06-11  0:08:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2021-06-11  0:08:23 0 [Note] InnoDB: Uses event mutexes 2021-06-11  0:08:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-06-11  0:08:23 0 [Note] InnoDB: Number of pools: 1 2021-06-11  0:08:23 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-06-11  0:08:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M 2021-06-11  0:08:23 0 [Note] InnoDB: Completed initialization of buffer pool 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\applied.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`applied``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`applied` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education_list.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education_list``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education_list` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\industry.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`industry``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`industry` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\jobs.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`jobs``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`jobs` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_admini.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_admini``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_admini` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\resume.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`resume``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`resume` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\selected.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`selected``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`selected` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\entries.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`entries``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`entries` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geoname.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geoname``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geoname` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geonamebackup.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geonamebackup``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geonamebackup` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\pincodes.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`pincodes``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`pincodes` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\specifier.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`specifier``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`specifier` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\users.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`users``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`users` because it could not be opened. 2021-06-11  0:08:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-06-11  0:08:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-06-11  0:08:23 0 [Note] InnoDB: Setting file 'D:\Program Files\XAMP\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-06-11  0:08:23 0 [Note] InnoDB: File 'D:\Program Files\XAMP\mysql\data\ibtmp1' size is now 12 MB. 2021-06-11  0:08:23 0 [Note] InnoDB: Waiting for purge to start 2021-06-11  0:08:23 0 [Note] InnoDB: 10.4.19 started; log sequence number 1515509790; transaction id 611499 2021-06-11  0:08:23 0 [Note] InnoDB: Loading buffer pool(s) from D:\Program Files\XAMP\mysql\data\ib_buffer_pool 2021-06-11  0:08:23 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-06-11  0:08:23 0 [Note] Server socket created on IP: '::'. 

Does Chill Touch Prevent Druid’s Wild Shape from Recovering Hit Points?

Does the Chill Touch cantrip’s secondary effect prevent a Druid from regaining hit points via Wild Shape?

Chill Touch reads:

… On a hit, the target takes 1d8 necrotic damage, and it can’t regain hit points until the start of your next turn.

Wild Shape:

… When you transform, you assume the beast’s hit points and Hit Dice.

RAW: Is "assume" the same as "regain"?

trouble recovering rotation and translation from essential matrix

I am having trouble recovering rotation and translation from an essential matrix. I am constructing this matrix using the following equation: \begin{equation} E = R \left[t\right]_x \end{equation}

which is the equation listed on Wikipedia. With my calculated Essential matrix I am able to show the following relation holds: \begin{equation} \left( \hat x \right) E x = 0 \end{equation}

for the forty or so points I am randomly generating and projecting into coordinate frames. I decompose $ E$ using SVD then compute the 2 possible translations and the two possible rotations. These solutions differ significantly from the components I’m starting with.

I have pasted a simplified version of the problem I am struggling with below. Is there anything wrong with how I am recovering the these components?

import numpy as np   t = np.array([-0.08519122, -0.34015967, -0.93650086])  R = np.array([[ 0.5499506 , 0.28125727, -0.78641508],     [-0.6855271 , 0.68986729, -0.23267083],     [ 0.47708168, 0.66706632, 0.57220241]])  def cross(t):     return np.array([     [0, -t[2], t[1]],     [t[2], 0, -t[0]],     [-t[1], t[0], 0]])   E = R.dot(cross(t))   u, _, vh = np.linalg.svd(E, full_matrices=True)  W = np.array([ [ 0,-1, 0], [ 1, 0, 0], [ 0, 0, 1]])  Rs = [u.dot(W.dot(vh.T)), u.dot(W.T.dot(vh.T))] Ts = [u[:,2], -u[:,2]] 

What counts as being “wounded” for the purpose of the rules on recovering a point of Hope?

In The One Ring game, players are allowed to recover a point of Hope if their Fellowship focus is not wounded during the session. The issue is that the rules don’t seem to state if they mean the Wounded condition (which involves a successful edge hit with armor failing to overcome injury), or simply having taken damage.

Recovering files after switch_root

So, I have an embedded system running a Linux distro. It has a key (RSA) in an intermediate stage and then calls switch_root. switch_root recursively deletes the files on the host filesystem, but I don’t think this is a secure delete, so it seems to me that the new filesystem should be able to recover files from the precursor including that RSA key. I am verifying the security of this system, and don’t think it is secure because of this flaw, but I am unable to prove it.

Halp? Pls?

Recovering my data in sim card [closed]

Is there a tool, a device or an app that could restore my calls history from the sim card itself? is it possible in any way?

(My phone isn’t available, and the google contacts back up messed up my contacts, as it’s known to do)

When I imported my contacts from Gmail, they got back but some of them were recorded as just names, including the contact I’m looking for, there was a sim card icon next to it, so it’s recorded in my sim. However, someone told me it’s due to that number being in a whattsgroup, so I might need to restore my whattsup data in order to view it. Others told me it might only got recorded as a name without a number, but I know it didn’t, cause that number kept calling not so far from two years. It’s indeed stored in that deleted data, I was wondering if I could restore all my call history from the sim card itself.

I have contacted the service provider company and they don’t keep more than 6 months of data. I also thought of hiring a professional hacker specialized in telecommunications so they can infiltrate the company’s database and restore all my automatically deleted data, but this is a bit far solution for now.

(Yeah and the Gmail account, No one remembers what it’s exactly was, so I think google customer support won’t be of aid (cause I thought of contacting them about the horrible backup issue, thought I could restore that contact properly. And the recovery email too)

Can I safely sell a used keyboard without risk of new owner recovering previous inputs?

As far as of my knowledge goes, keyboard don’t store keystrokes in their memory by default (excluding those bundled with keyloggers). The thing that comes to my mind though is that some keyboards do have some built-in memory for storing user’s preferences (e.g. gaming keyboards). Can this be somehow reprogrammed to store other data than just LEDs color combo?

Can I sell my keyboard without worrying that new owner might recover previous input in some way?

Cheers, Dominic

Recovering local chrome passwords from dead pc [migrated]

recently my PC died and will not power on. The motherboard had a complete failure. My HDD survived. I have it set up as an external to pull my photos and such. My question comes down to transferring the local passwords I had stored on chrome. I didn’t have a google account sync. But the profiles are still accessible on the old HDD. I want to view my passwords or at least transfer them to my new pc. The older HDD belonged to a win 8.1 pc. I pulled up the Login data sqlite file but when I view it in sql server it says the password value is stored in a blob. Any advice on recovering them would be helpful,a majority of my lifes on there.

Recovering log in information

we are running two websites on WP. We had an external person managing both of them but unfortunately he passed away recently. We had the password and username for one of them but for the other website we never got the info to log on etc. It is a fairly new website and he didn’t get the time to give us the info before he passed. Was wondering if theres anyway of recovering the account or the log in details?

Any help would be appreciated, thank you in advance!

Alex