A tool for analysing GrapheneOS ADB logs.
git clone https://github.com/HappenedByProxy/graphene-analyser
python code/oxidize.py
ADB must be on path.
- The phone must be unlocked. This is a standard for all forensic tools.
- The owner profile must be the unlocked profile. It does not matter if you have no access to other profiles.
- Developer options must be active, and USB debugging to be enabled.
- The commands can be ran in any profile as long as the computer was authorized in the owner profile and the cable does not get disconnected.
- Unlock the device and connect it to the computer with USB.
- Open a cmd prompt and enter
adb devices -l
. - Look at the phone and authorize the computer.
- Check
adb devices -l
again. If the device is shown as anything but "unauthorized", it's probably ready.
- account
- notification
- package
- user
- List of all installed applications.
- Accounts connected to apps. Known examples include Twitter, Gmail, Reddit, OneDrive, Pixiv, YouTube.
- Media. We are analysing logfiles, we do not extract any media from the device.
- Browser history.
- SMS.
- If the phone has rebooted, then information on deleted profiles will be incredibly limited, along with other data possibly.
- Deleted apps are able to be found, but are unpredictable in format.
- Recent app history.
- WiFi history.
- Windows: adb tcpip 5555
- WSL: adb connect :5555