[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4731: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3831)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4733: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3831)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4734: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3831)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4735: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3831)
Forum | Internal Medicine Board Review Questions | Knowmedge
LOG IN
Use this forum for general discussion
3 posts • Page 1 of 1
Recovering access after losing a device

by Marcus Little » Sat Aug 08, 2026 6:41 pm

Hello everyone. I am trying to understand what I should do if my old phone stops working while my cryptocurrency wallet is still installed on it. I wrote down a recovery phrase when I first created the wallet, but I am not completely sure whether I stored every word correctly. I also wonder if I should install the same application again from a random website or look for another method. Has anyone dealt with this situation and can explain the safest order of steps? I mainly want to avoid sending my recovery phrase to a fake support agent or entering it on a phishing page.
Posts: 99

Re: Recovering access after losing a device

by William Bridges » Sat Aug 08, 2026 6:51 pm

Hi. The most important rule is never to share your recovery phrase or private keys with anyone, including people claiming to be technical support. Jaxx liberty was designed around user-controlled wallet access, so losing the phrase and the device password can make recovery impossible. Guidance connected with the wallet recommends keeping the phrase offline and avoiding suspicious websites or downloads. should not automatically be treated as an official source; I would verify the domain independently before downloading anything or entering sensitive information. First, I would check whether the phrase is complete and correctly ordered, without typing it into an online form. Then I would use a reputable, currently maintained wallet that supports the same recovery standard, after confirming the software source and compatibility. I would install it on a clean, updated device, create a strong local password, and verify the receiving address with a small test transaction. I would never use search-ad results or links sent through private messages. I would also keep a written offline backup in a secure place and avoid cloud storage unless it is properly encrypted. Crypto transfers are generally irreversible, so caution is more valuable than speed.
User avatar
Posts: 62

Re: Recovering access after losing a device

by Marcus Little » Sat Aug 08, 2026 7:01 pm

Thank you for the careful explanation. I had considered downloading the first replacement application I found, so your warning about fake support and unverified websites was especially useful. I will check my written phrase privately, verify the software source, and avoid moving any funds until I understand the recovery process completely.
Posts: 99

3 posts • Page 1 of 1

Return to General Discussion