Homebrew RELEASE Noexs Remote Debugger

phonz · Nov 6, 2019

Smoker1 said:
Question - Under the Pointer Search, what is the Threads amount for? Amount of CPU Processing Threads to make the Searches faster?

In a sense.
It's kind of like the amount of instructions to run in parallel.
So the more threads the more it can spread out the task and complete the instructions quicker.
Though it wouldn't benefit you to use more than your logical core count.

Kirby567fan · Nov 6, 2019

So Ive been using noexes lately and it worked quite well.But today i tried to attach a game to the process and i just doesnt work. It either tell me that its alreday attached even if it isnt or it gives me this error:
Attach failed. Reason: Module:1 Desc:122.
Can someone help me please.

wiitendo84 · Nov 6, 2019

Kirby567fan said:
So Ive been using noexes lately and it worked quite well.But today i tried to attach a game to the process and i just doesnt work. It either tell me that its alreday attached even if it isnt or it gives me this error:
Attach failed. Reason: Module:1 Desc:122.
Can someone help me please.

Either hold down L as you boot the game or disable dmntcheat in your ini file. Usually works for me

Kirby567fan · Nov 6, 2019

wiitendo84 said:
Either hold down L as you boot the game or disable dmntcheat in your ini file. Usually works for me

Thanks its fixed now.

Esppiral · Nov 8, 2019

The download links are dead

phonz · Nov 8, 2019

Esppiral said:
The download links are dead

the download links for what?

Esppiral · Nov 8, 2019

phonz said:
the download links for what?

For the releases here

https://github.com/mdbell/Noexes

phonz · Nov 8, 2019

Esppiral said:
For the releases here

https://github.com/mdbell/Noexes

Thats a github link, you can find the downloads in the release Tab at the top of the project page.
Heres a quick link though for you.
https://github.com/mdbell/Noexes/releases/download/v1.1.2-hotfix/noexs-1.1.2-hotfix.zip

Kirby567fan · Nov 8, 2019

Does anyone here know how to create cheats with pointers?

TaiTai · Nov 8, 2019

Alright so I got this working it connected and even attached but i boot again a few day later and now it says attach failed module tcpGecko already attached. Any help would be appreciated .

designgears · Nov 8, 2019

phonz said:
Thats a github link, you can find the downloads in the release Tab at the top of the project page.
Heres a quick link though for you.
https://github.com/mdbell/Noexes/releases/download/v1.1.2-hotfix/noexs-1.1.2-hotfix.zip

Should use the sysmodule version
https://github.com/KranKRival/Noexes/releases

masagrator · Nov 8, 2019

TaiTai said:
Alright so I got this working it connected and even attached but i boot again a few day later and now it says attach failed module tcpGecko already attached. Any help would be appreciated .

You have updated FW in the meantime?

TaiTai · Nov 8, 2019

designgears said:
Should use the sysmodule version
https://github.com/KranKRival/Noexes/releases

I am using sys module thats how i got it working.

masagrator said:
You have updated FW in the meantime?

also which firmware i have 7.0.1 and ams 9.4 oh yes I by mistake so I followed the guide to restore my sysnand back to 7.0.1

wiitendo84 · Nov 8, 2019

TaiTai said:
Alright so I got this working it connected and even attached but i boot again a few day later and now it says attach failed module tcpGecko already attached. Any help would be appreciated .

Sometimes you have to hold the L button while loading the game. That should deactivate the cheat system and then you connect to it.

TaiTai · Nov 8, 2019

wiitendo84 said:
Sometimes you have to hold the L button while loading the game. That should deactivate the cheat system and then you connect to it.

Thank your idea fixed it.

--------------------- MERGED ---------------------------

phonz · Nov 9, 2019

designgears said:
Should use the sysmodule version
https://github.com/KranKRival/Noexes/releases

Agreed.

Kirby567fan · Nov 11, 2019

Does anyone know how to fix this problem:

Code:

me.mdbell.noexs.core.ConnectionException: Result{mod=1, desc=106}
        at me.mdbell.noexs.core.Debugger.readmem(Debugger.java:274)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:373)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.refineSearch(MemorySearchService.java:211)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:187)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
        at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

Code:

java.io.IOException: Not enough free space for dump!
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:335)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
        at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
        at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

After the first error, everytime I try ro search it gives me the second error.

irNuu · Nov 20, 2019

I need help. I've spent hours for 2 days now and I can't make it connect. I am using Atmosphere 0.9.4 and Hekate 5.0.2. FW 9.0.1.

BCT
Debugmode = 1

I couldn't figure out where to put the noexs.kip1 so I add it in /atmosphere/kips.

I used Kip_select to check if it is enabled, and it seems to be enabled. Basically both debugmode and noexs.kip1 is enabled but it is still not connecting. Please, can anyone provide me with some help? I appreciate if anyone can point me to the correct direction.

Thanks!

--------------------- MERGED ---------------------------

phonz said:
have you tried using the alternative sysmodule instead?

OMG!!! After working on how to make it work... Finally!!! that is 2 days of time lost (including slacking at work). Now I can study pointer search.

--------------------- MERGED ---------------------------

irNuu said:
I need help. I've spent hours for 2 days now and I can't make it connect. I am using Atmosphere 0.9.4 and Hekate 5.0.2. FW 9.0.1.

BCT
Debugmode = 1

I couldn't figure out where to put the noexs.kip1 so I add it in /atmosphere/kips.

I used Kip_select to check if it is enabled, and it seems to be enabled. Basically both debugmode and noexs.kip1 is enabled but it is still not connecting. Please, can anyone provide me with some help? I appreciate if anyone can point me to the correct direction.

Thanks!

--------------------- MERGED ---------------------------

OMG!!! After working on how to make it work... Finally!!! that is 2 days of time lost (including slacking at work). Now I can study pointer search.

I got another error now.... :'(

me.mdbell.noexs.core.ConnectionException: Result{mod=349, desc=9}
at me.mdbell.noexs.core.Debugger.readInfo(Debugger.java:525)
at me.mdbell.noexs.core.Debugger.query(Debugger.java:375)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.init(DumpRegionSupplier.java:82)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.getSize(DumpRegionSupplier.java:73)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:334)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

irNuu · Nov 20, 2019

irNuu said:
I need help. I've spent hours for 2 days now and I can't make it connect. I am using Atmosphere 0.9.4 and Hekate 5.0.2. FW 9.0.1.

BCT
Debugmode = 1

I couldn't figure out where to put the noexs.kip1 so I add it in /atmosphere/kips.

I used Kip_select to check if it is enabled, and it seems to be enabled. Basically both debugmode and noexs.kip1 is enabled but it is still not connecting. Please, can anyone provide me with some help? I appreciate if anyone can point me to the correct direction.

Thanks!

--------------------- MERGED ---------------------------

OMG!!! After working on how to make it work... Finally!!! that is 2 days of time lost (including slacking at work). Now I can study pointer search.

--------------------- MERGED ---------------------------

I got another error now.... :'(

me.mdbell.noexs.core.ConnectionException: Result{mod=349, desc=9}
at me.mdbell.noexs.core.Debugger.readInfo(Debugger.java:525)
at me.mdbell.noexs.core.Debugger.query(Debugger.java:375)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.init(DumpRegionSupplier.java:82)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.getSize(DumpRegionSupplier.java:73)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:334)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

OK! After reading from page 1 - 29. I am ablee to make it work now. Phew!! Thank you all!! I still get some errors but I'll figure it out for now. haha~~

Smoker1 · Nov 20, 2019

Might have already covered this, but why does the Battery get drained like crazy, even when connected to Power?

Homebrew RELEASE Noexs Remote Debugger

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

The patches guy

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

New Member

Well-Known Member

Similar threads

Popular threads in this forum