All,
Please find the attached Windows RT native binaries for Process Hacker (v 2.30). See the project homepage for more details:
http://processhacker.sourceforge.net/
I'm currently labeling this as a [[beta]] release because I've disabled some functionality to get this building clean for Windows RT. The kernel component is not yet ported. I'm going to continue working on this tool in my spare time to add any missing functionality. Its not quite ProcessExplorer.. but its pretty darn close
I haven't had a whole lot of time to test everything.. so if anyone finds any other functionality that is missing or appears broken please report it here so I can investigate fixing it.
Cheers!
EDIT: I forgot to include the plugins in the original zip package.. all fixed now. Sorry.
EDIT2: It looks like someone else actually worked on this a few weeks ago but failed to share it with anyone -> http://processhacker.sourceforge.net/forums/viewtopic.php?f=5&t=926
EDIT3: Stack walking and proper CPU identification should now work. I've also renamed the zip files to avoid confusion. This is the 3rd release.
EDIT4: Posted a test signed kernel driver. It has been built without the WDK/DDK and in debug mode. I've also included the pdb file for those who might need/want it. Drop this in the root folder and restart processhacker. Its been very stable for me, but please use at your own risk. *updated - 31-03-2013*
Thx
That is great. Aspecialy because my Task manager is not running anymore.
But it is running at 50% CPU usage. quit a lot i think.
Update
Original post has been updated with new binaries. Stack walking and CPU identification issues now fixed.
Is it possible that porting kernel driver for ARM platform?
I only know that there is no DDK for ARM platform.
I've been looking for it, but still cannot find it yet.
kkw620 said:
Is it possible that porting kernel driver for ARM platform?
I only know that there is no DDK for ARM platform.
I've been looking for it, but still cannot find it yet.
Click to expand...
Click to collapse
I haven't tried it yet.. but I'm not expecting it to be too difficult. There really isn't a "DDK" anymore.. and the driver kit has been merged into the Windows SDK. All that I can see missing from the SDK is the kernel libraries. For simple software drivers you don't need that many libs.
Anyway.. I'll post an update here once (and if) I get it building. The biggest problem will be testing it.. because I won't be able to do any kernel debugging
Cheers!
kkw620 said:
Is it possible that porting kernel driver for ARM platform?
I only know that there is no DDK for ARM platform.
I've been looking for it, but still cannot find it yet.
Click to expand...
Click to collapse
You'll need ARM WDK that is not public (I really believe that soon it would be leaked, similar to IFS and HAL DDKs in old days).
You can compile simple drivers without it by taking the headers from x86 WDK and recreating the import libraries yourself - some persons succeeded in that. But even if you have ARM WDK - not all drivers can be ported by a simple recompilation. For example I've tried to recompile an OpenVPN driver - and failed, as it is based on NDIS 5.0 when minimal supported NDIS version in RT is 6.3. Someone familiar with NDIS is needed to update its sources first.
Compiled the driver for RT. Driver is unsigned - sign it yourself. And driver is not tested by me. The only thing I've modified except for project settings - commented the "_asm"s.
Binaries attached.
Edited: attached modified sources too.
mamaich said:
Compiled the driver for RT. Driver is unsigned - sign it yourself. And driver is not tested by me. The only thing I've modified except for project settings - commented the "_asm"s.
Binaries attached.
Edited: attached modified sources too.
Click to expand...
Click to collapse
See .. I figured it would be easy . As I said, you really don't _need_ the DDK/WDK, but it would certainly make most drivers much easier to work with. As much as I appreciate the binaries the biggest problem is testing without having a kernel debugger. Testing and debugging via crash dumps is not what I would call fun
Cheers!
Thanks! Seems that it is working fine
mamaich said:
Compiled the driver for RT. Driver is unsigned - sign it yourself. And driver is not tested by me. The only thing I've modified except for project settings - commented the "_asm"s.
Binaries attached.
Edited: attached modified sources too.
Click to expand...
Click to collapse
I did jailbreak 1.20 on my Surface RT. I saw that it contains kernel code execution hack, (means that Test Mode for test signing driver)
And I signed the driver with test signature, put the driver file in same folder with Process Hacker main binary.
After that, I opened up Process Hacker with Administrator right.
You know, without the kernel driver, when I wanna see the stack trace of threads which are on "System" process, it isn't possible.
But now it works!
It seems that it is working fine. I try to test more.
kernel driver
Post updated to include my own built version of the kernel driver.
unstable
All,
Since the most recent update I've noticed some instability with the driver. I'll try to resolve the issue and repost an updated driver soon. Right now, use with caution.
Cheers!
driver updated
Fixed a BSOD issue with the driver. Please try the new one if you're experiencing issues.
Related
Hey everyone,
I've been trying to connect my wiimote in debian. Im new to linux, im kinda putting all the pieces together as i go. wminput and all its corresponding packages seemed to install just fine with 'apt-get install wminput'.
But when I run wminput I get the error "unable to open uinput"
so googled, and managed to find uinput.ko and some general instructions on installing it.
I loaded it into /lib/modules/2.6.29.6-cm41/ and ran 'insmod uinput.ko' and i get the error 'Invalid module format' which im assuming is because it was compiled for an x86 system. modprobe displays a similar error.
I also dont understand the "cm41" in the path /lib/modules/2.6.29.6-cm41/, is that short for CyanogenMod, am I placing this module in my android Filesystem?
Are there any linux guru's around that could compile uinput.c for the g1 debian build? Or simply tell me that im way off track and there are bigger problems involved with getting this to work.
Also, if wminput did function. Does anyone know if it would send button presses to android while running in the background?
uinput.c
http://abstrakraft.org/cwiid/browser/trunk/wminput/uinput.c?format=txt
wminput
http://packages.debian.org/lenny/wminput
wmgui which i believe uses the same library as wminput has been made to work through ssh
http://www.lukedupin.com/projects/show?project=g1_wii -
There is also WMD for connecting to wiimotes but it requires uinput as well (i think).
http://www.circuitdb.com/articles/7/3 -
Ive been reading http://www.saurik.com/id/10 and it seems that this modules really needs to be installed to Android? And then I will be able to access this module from debian which is running on top on android? Can anyone confirm that?
I extracted the config file from my phone at /proc/config.gz and it has the line # CONFIG_INPUT_UINPUT is not set. some googling brings me here http://lxr.linux.no/#linux+v2.6.31/drivers/input/misc/Kconfig
206 config INPUT_UINPUT
207 tristate "User level driver support"
208 help
209 Say Y here if you want to support user level drivers for input
210 subsystem accessible under char device 10:223 - /dev/input/uinput.
211
212 To compile this driver as a module, choose M here: the
213 module will be called uinput.
This all leads me to believe that this module will work on the G1. Will Any Devs PLEASE compile this for me. If you think it would work properly that is.
I just dont have the skills to compile it myself yet. Ive been reading alot on how to compile the kernel and kernel modules for the G1, I setup Ubuntu, and setup my environment and installed the android source code. I was working off this link http://andblogs.net/2008/12/compiling-your-own-g1-kernel-modules/ but i dont understand how i get the kernel source . I have sooo much reading todo before I get all this. Any recommended links?
I just went to the android kitchen thread to see if there have been any updates to accommodate java 7 and the dev has closed the thread
Any one know how to get the kitchen to recognize java 7, it still is looking for java in the jre6 folder and that isn't there anymore. I have even done a fresh install of cygwin after installing java 7 and it still didn't automatically recognize the new version.
Hopefully dsixda doesn't take too long a break but I am sure it is well deserved, it is a priceless tool.
You can have more than one version of java installed on your system you know. Java 7 isn't going to just magically improve anything for you really unless you're a developer.
True but didn't know if it was an fairly easy change to a script or something to get it to check/recognize the new location. Before it would let me get to the "building a rom from working folder" portion before it would give me a message about java, now it won't even start the kitchen saying it can't find java version.
I wouldn't consider myself a dev by any means but I build roms for my own use and to just try different things out to see how things work/change things, basically to learn what does what.
Between this issue and fact that I can't get pc to recognize my phone as a storage device anymore...I am lost.
Symlink java7 to the old location for java6.
adrynalyne said:
Symlink java7 to the old location for java6.
Click to expand...
Click to collapse
Just to add to what adrynalyne said (since it's the easiest way), that would be using the "ln" command on linux/unix/cygwin or mklink on windows.
Thanks for idea, tried mklink but in process realized I had x86 version of java6 and x64 of java7. So I tried just installing x86 version of java7 and opened up kitchen and was able to create output .zip from my current working folder
Now if I could just get pc to recognize phone properly... then maybe I think I will avoid updates of software for awhile.
Hi everyone!
I have this question in mind for a long time now. It gets confirmed every time a company decides to make a new mobile OS. Why is it so damn difficult to first install a mobile OS, but even more, why only people with some special knowledge and dedication can port an OS to a new mobile device?
I mean, on a computer we just have to select if we want i386/x86 or AMD/x86_64 installer what ever computer brand or other hardware we do have while on mobile, we need to have a very specific image for our device. We end up with hundreds if not thousands of images of the same version of the OS.
So my question is, why don't we have this work flow to install a mobile OS:
- Flash a generic image on the device
- Run it
- Auto compile a new kernel on the device itself
- Load generic drivers
- If generic drivers don't work, download specific ones
- Continue with installing other regular software
Technical answers are welcomed.
Thanks,
Dragnucs.
Because.
Building the kernel on the device would take a lot of time and most phones do not have the resources to do so (memory and CPU).
Adding a development environment (compiler, libs, etc.) to the install image would make the install image quite large.
Most manufacturers release incomplete code for their drivers. This makes a complete re-creation of them from source nearly impossible.
There is no repository for 3rd party binary device drivers (probably not "legal" to do so). Mobile phones often have a proprietary system UI framework which is never released as source code. The best you can do is either re-create your own (AOSP, CM, AOKP) or borrow the one from the stock firmware release (Touchwiz, Sense).
If your phone needs a "special" network driver, how are you going to transfer one over during your install if you don't already have one. (classic chicken vs egg scenario)
It is much easier to setup one generic build (on a PC or server), then have custom compile scripts for each device you intend to support. Also a lot easier to debug build issues on a full computer than trying to do so on a phone.
In the PC world, you have manufacturer's that have to release binary drivers to Apple/Microsoft for validation and make binary or source drivers available for Linux. In the mobile world, those processes do not exist.
-Mike
Dragnucs said:
Hi everyone!
I have this question in mind for a long time now. It gets confirmed every time a company decides to make a new mobile OS. Why is it so damn difficult to first install a mobile OS, but even more, why only people with some special knowledge and dedication can port an OS to a new mobile device?
I mean, on a computer we just have to select if we want i386/x86 or AMD/x86_64 installer what ever computer brand or other hardware we do have while on mobile, we need to have a very specific image for our device. We end up with hundreds if not thousands of images of the same version of the OS.
So my question is, why don't we have this work flow to install a mobile OS:
- Flash a generic image on the device
- Run it
- Auto compile a new kernel on the device itself
- Load generic drivers
- If generic drivers don't work, download specific ones
- Continue with installing other regular software
Technical answers are welcomed.
Thanks,
Dragnucs.
Click to expand...
Click to collapse
Thanks buddy. :good:
Hello Everyone,
I've written a small tool that allows you to sign a single file or a complete folder. See attachments. It is quick and dirty. If someone wants to improve it, there is the source attached also.
Please note that this tool will sign every exe and dll files in all sub folders if you select "Sign folder"!
Best of all: It also runs on Windows RT directly
Have fun!
[Removed]
Hmm it seems to have some issues with signing some binary exe files that had been previously compiled and worked on RT 8.0. I'm guessing this has to do with Release vs Debug ARM binaries?
hi guys can some one help i cant find how to jailbreak my surface Windows 8.1 rt
hatekiller said:
hi guys can some one help i cant find how to jailbreak my surface Windows 8.1 rt
Click to expand...
Click to collapse
Follow the guide here: https://forum.xda-developers.com/wi...ent/windows-8-1-rt-jailbreak-exploit-t3226835
Hello, I know it's been a long time since this tool was made but would it be possible to add some kind of handler of errors to the signTool? It's becoming harder to use since programs are having more and more files and we have to close a little error message for every file otherwise the process is paused.
Even though this is pretty old post, thank you so much for this tool!
It took hours of trying to get .exes to work. The signtool.exe also didn't really work for me.
FINNAL IT WORKS!
There is an issue with this tool prompting you after every single file. I fixed it and also added some other minor things such as .sys file support. here it is
H, can anyone help me, I'm total noob, what is this signing? how do I sign this? I'm trying to have some apps works on the RT
starfrost013 said:
There is an issue with this tool prompting you after every single file. I fixed it and also added some other minor things such as .sys file support. here it is
Click to expand...
Click to collapse
Oh whoa thanks, this would help alot since this was updated recently
Trying to build my own AOSP ROM and I keep getting stuck on emulator unable to find the kernel version, though the file is there.
I am using Hyper-V VM with Ubuntu V20 installed and the VHD is exactly that, a .vhd file extension for the virtual hard drive.
I just can not seem to resolve the problem on the missing kernel, also have supplied a pic showing exactly what it says after the build is finished and then I try and run emulator.
Any help or info, links on the matter would be much appreciated and thank you for taking the time to help out.
I have also noticed I can not use "emulator -list-avds" nothing happens. Just exits and terminal is ready for user input again.
So far I did a repo sync again and then a m -checkbuild and just waiting for it to finish to try emulator again
Update: Decided to start from scratch
Changes that I have made.
Using Ubuntu 18.04 for O.S
Switched from M.S Hyper-V to Oracle Virtual-Box (V.B has more features then Hyper-V and is better in performance because of it.).
Virtual HDD is set to .VHD but is on Sata and not IDE now (Virtual-Box only allows it).
Made the VHD a fixed drive instead of dynamic for better performance (Max size of 512GB)
Dedicated 32GB of ram to VM.
Allowed up to 6 cores on a 12 core processor.
might experiment getting Oracle JDK installed instead of using openjdk, due to having issues with it.
UPDATE_1
Fresh build on 18.04 same issues as old build. emulator, avd and android. all not working.
I might have missed a package to download or something or maybe java still is not working. Using openjdk 11 at the moment. I am running out of ideas as to why i can not get it working.
Update_2
Looks like the reason emulator is not working is due to me not installing SDK, I am not using the IDE so I think I need the command-line & Platform tools installed. got to work out how to install it now.
UPDATE_3
SDK from what I know is installed. Now I am getting an output file is missing, but build completed with no issues. Please help, new image also supplied.