search

MercuryWorkshop / fakemurk

[UNMAINTAINED] fakemurk - a set of scripts for spoofing verified on an enrolled chromebook
Other
56 stars 19 forks source link

file exists #51

Closed Lord-Funion closed 8 months ago

Lord-Funion commented 8 months ago

ISSUE DESCRIPTION

i just ran it and it gave me an error

TERMINAL OUTPUT (if any)

/dev/fd/63: line 1198: /dev/sdap2: No such file or directory mkdir: cannot create directory '/tmp/rootmnt': File exists "echo "----- stage 2: patching target rootfs -----"" command failed with exit code 1. THIS IS A BUG, REPORT IT HERE https://github.com/MercuryWorkshop/fakemurk

ADDITIONAL NOTES

e9x commented 8 months ago

mkdir: cannot create directory '/tmp/rootmnt': File exists

You ran the script twice. You need to either unmount /tmp/rootmnt or just restart your chromebook before running it again.

umount /tmp/rootmnt

or just reboot.

/dev/fd/63: line 1198: /dev/sdap2: No such file or directory

An issue that I found in the get_largest_nvme_namespace function is that if you have a USB plugged in and it just happens to be larger than the rootfs partition, the script will think it's the rootfs and will try to treat it like it's an eMMC even tho it's a usb. A workaround for this is to just unplug your USB before running fakemurk.

To prevent this in the future, instructions to remove any USBs before running fakemurk can be added to the README or get_largest_nvme_namespace can be updated to only pick eMMC devices or ignore USB devices.

e9x commented 8 months ago

Cryptosmite has an implementation of get_largest_nvme_namespace that will not only check if the device is chromeOS, but if it's removable too, which would fix the USB problem. It might be worth taking a similar approach.

https://github.com/FWSmasher/CryptoSmite/blob/39a235386957207185af844b0521e8a2d90c4440/cryptosmite.sh#L30