[[TOC]]
Q: What Exynos chipsets and Android versions are supported?
| Model | Model # | Android OS | Exynos SoC (chipset) |
| Galaxy S7 | SM-G930F / SM-G930K / SM-G930L / SM-G930S / SM-G930W8 / SM-G930FD | 7.x-9.x | 8 Octa 8890 |
| Galaxy S7 Edge | SM-G935F / SM-G935K / SM-G935L / SM-G935S / SM-G935FD | ||
| Galaxy S8 | SM-G950F / SM-G950N / SM-G950FD | 9 Octa 8895M | |
| Galaxy S8 Plus | SM-G955F / SM-G955N / SM-G955FD | 7.x-9.x | |
| Galaxy Note 8 | SM-N950F / SM-N950N / SM-N950NKPC / SM-N950FD | ||
| Galaxy Note 9 | SM-N960F / SM-N960F/DS / SM-N960N | 8.x-13.x | Octa 9810 |
| Galaxy S9 | SM-G960F / SM-G960F/DS / SM-G960N | ||
| Galaxy S9 Plus | SM-G965F / SM-G965F/DS / SM-G965N | ||
| Galaxy S10E | SM-G970F / SM-G970F/DS / SM-G970N | 9.x-12.x | Octa 9820 |
| Galaxy S10 | SM-G973F / SM-G973F/DS / SM-G973N | ||
| Galaxy S10+ | SM-G975F / SM-G975F/DS / SM-G975N | ||
| Galaxy S10 5G | SM-G977B / SM-G977N | ||
| Galaxy F62 | SM-E625F/DS | ||
| Galaxy M62 | SM-M625F/DS | ||
| Galaxy Note 10 | SM-N970F / SM-N970F/DS | ||
| Galaxy Note 10 5G | SM-N971N | ||
| Galaxy Note 10+ | SM-N975F / SM-N975F/DS | ||
| Galaxy Note 10+ 5G | SM-N976B / SM-N976N | ||
| Galaxy S20 | SM-G980F / SM-G980F/DS | 10.x-13.x | 990 |
| Galaxy S20 5G | SM-G981B / SM-G981B/DS | ||
| Galaxy S20+ | SM-G985F / SM-G985F/DS | ||
| Galaxy S20+ 5G | SM-G986B / SM-G986B/DS | ||
| Galaxy S20 Ultra | SM-G988B / SM-G988B/DS | ||
| Galaxy Note 20 | SM-N980F/DS | ||
| Galaxy Note 20 5G | SM-N981B/DS | ||
| Galaxy Note 20 Ultra | SM-N985F/DS | ||
| Galaxy Note 20 Ultra 5G | SM-N986B/DS | ||
| Galaxy S21 | SM-G991B/DS / SM-G991N | 11.x-14.x |
2100
|
| Galaxy S21+ 5G | SM-G996B/DS / SM-G996N | ||
| Galaxy S21 Ultra 5G | SM-G998B/DS / SM-G998N | ||
| Galaxy A33 5G | SM-A3360 / SM-A336B / SM-A336B/DS / SM-A336B/DSN / SM-A336E / SM-A336E/DS / SM-A336E/DSN / SM-A336M / SM-A336N | 12.x-14.x | 1280 S5E8825 |
| Galaxy A53 5G | SM-A5360 / SM-A536B / SM-A536B/DS / SM-A536D / SM-A536E / SM-A536E/DS / SM-A536J / SM-A536N / SM-A536U / SM-A536U1 / SM-A536V / SM-A536W / SM-S536DL | ||
| Galaxy Jump 2 | SM-M336K | ||
| Galaxy M33 | SM-M336B / SM-M336B/DS / SM-M336BU / SM-M336BU/DS | ||
| Galaxy M34 5G | SM-M346B / SM-M346B/DS / SM-M346B1 / SM-M346B1/DS / SM-M346B2/DS | 13.x-14.x | |
| Galaxy Watch FE | SM-R861 / SM-R866 | Wear OS 4.x-6.x | W920 S5E5515 |
| Galaxy Watch4 | SM-R860 / SM-R865 / SM-R870 / SM-R875 | Wear OS 3.x-6.x | |
| Galaxy Watch4 Classic | SM-R880 / SM-R885 / SM-R890 / SM-R895 | Wear OS 3.x-6.x | |
| Galaxy Watch5 | SM-R900 / SM-R905 / SM-R910 / SM-R915 | Wear OS 3.x-6.x | |
| Galaxy Watch5 Pro | SM-R920 / SM-R925 | Wear OS 3.x-6.x | |
| Galaxy Watch6 | SM-R930 / SM-R935 / SM-R940 / SM-R945 | Wear OS 4.x-6.x | W930 S5E5515 |
Q: How do I put an Exynos-based device into Boot ROM mode?
To enter Boot ROM mode, Samsung devices require short-circuit of the test pins. However, some models have alternative methods:
- Samsung Galaxy Note 9: Hold Vol - and Bixby buttons.
- Samsung Galaxy S9/9+: Hold the two left buttons and the button on the right.
- Samsung Galaxy Watch devices require physical disassembly and direct contact with the USB test pads on the board. A detailed pinout PDF guide is available from the Passware Kit Mobile UI.
Q: What mobile applications are supported for decryption
In addition to the passcode recovery, Passware Kit Mobile detects installed applications and performs instant decryption or initiates password recovery process. Application decryption results are saved as an SQLite database in the “unprotected” folder of the output project folder.
The following applications are supported:
| Application | Recovery Options |
| Wickr Me | Instant decryption |
| Signal | Instant decryption |
| 1Password up to v.7 | Instant decryption / Brute-force |
| Enpass up to v.6 | Instant decryption / Brute-force |
Q: What encryption methods are supported for Exynos-based devices?
The following encryption methods can be used on mobile devices with full-disk or file-based encryption:
-
Secure Startup
Passware TipInstant decryption is available for phones with disabled Secure Startup - PIN, Pattern, Password
Decrypted data format for full-disk encryption is EXT4 (.DD), and DAR or plaintext for file-based encryption.
Q: Can GPU acceleration be used with Exynos-based devices?
For Exynos-based devices with Secure Startup enabled, Passware Kit Mobile performs GPU-accelerated brute-force and distributed password recovery.
Q: I get a "Failed to prepare Samsung device" error (with a dice image). How do I fix it?
The attack is probabilistic and depends on the computer hardware you are using. Connecting Samsung Exynos-based devices may require multiple attempts (up to approximately 10), which is expected behavior.
Click "Retry" and follow these recommendations:
Use a USB 3.0 port when possible. In some cases, however, switching to USB 2.0 has resolved connectivity issues.
- For certain devices, the battery must be connected. If required, connect the battery when the "Extracting hardware keys" stage appears in Passware Kit Mobile. If it does not help, disconnect the battery, connect it again, and retry. The battery should be fully charged.
- Some devices establish a stable connection only with a powered USB hub, while others connect more reliably directly, without a hub.
- Try a different computer and different USB cables.
- Consider using an Intel-based or Apple Silicon Mac, as it may provide better connection stability. Windows Agents can then be used to accelerate password recovery operations.
- If any other forensic software capable of attacking mobile devices is running, close it before switching the device to Boot ROM mode and starting the Passware Kit Mobile attack.
__________________________________
Overview of Passware Kit Mobile
General questions
Exynos test-point gallery
Comments
0 comments
Article is closed for comments.