Conor Richard
Conor Richard
I changed the call to: `` Native.NtFreeVirtualMemory((IntPtr)(-1), ref pImage, ref RegionSize, Execute.Win32.Kernel32.AllocationType.Release); `` After reviewing the documentation for NtFreeVirtualMemory, it seems like the incorrect value was entered here. Valid values...
Similar experience with the new BOOX Note 5, with the same CPU. I know next to nothing but am willing to learn and test.
Does not work for the Note 5 either. Tried a few variations without luck.
Still unable to pull the boot image from the BOOX Note 5 using --memory=ufs. I can open a new issue since it's a different device. I've tried from a couple...
> Ok, so: > > onyx boox note air2 has 0x0014d0e100000000, which is SDM662. > > What msmid does boox note 5 show ? The msmid is the only reliable...
@b1gcat this should be fixed in the newer versions of the code. The solution was to introduce RIP relative addressing. I have also found that in some cases, it's necessary...
@cnotin did you have a preference for how this would be done? I can think of two ways, for Windows based systems, that could accomplish this without doing more intrusive...
@wietze, I added a step in the linting workflow to validate our YML-Template.yml file to make sure it's valid in addition to adding the .gitattributes file.
Thank you @akat12 for your contribution to the LOLBas!
Thank you @elliotkillick for your addition to the LOLBas!