Hacking JGecko U Setup Guide

  • Thread starter Thread starter BullyWiiPlaza
  • Start date Start date
  • Views Views 416,120
  • Replies Replies 1,143
  • Likes Likes 27
You mean the memory usage? It uses a lot for unknown value searches unfortunately but I'm improving it a bit in the next update...
Is there a limit on the amount of memory you can search through at a time because I did a specific value search of the range 30000000-49000000
and near 100% I got an error about the java heap
 
How did you determine that? Because that does work. Makes wii u freeze and errors on computer
the 32-bit value starts at 3E873234. So the first byte is at 3E873234 as well. The second one is at 3E873235, the third one at 3E873236 and the last one, the 0x63 at 3E873237. This is where the byte of lives is stored at.
The freeze was probably caused because during a loading time the value was something less than 0x63 as well.
You could try this:
03000000 3E873237
00000062 00000000
00000000 3E873237
00000063 00000000
D0000000 DEADCAFE

It checks if the value is 98. If this is the case it will increase it to 99. This should work since there's a change of 1/256 that this byte is 98 during a loading sequenz
 
@BullyWiiPlaza :DThe unknown search is working very well since the last update, but I have been having some issues and I discovered why......Take a look at the pictures, you will notice that my search is between 37000000 - 38000000. The exact value I searched is found but linked to the wrong address in the 10000000-11000000 range. (the txt shows the correct address that should be listed)

If I poke it nothing happens because in memory view it also shows the address found in my search, that was not even in my search range.....:wtf:

I checked other games with already know addresses and the same thing....JGecko U finds the value but gives the wrong address.....oops :huh:
 

Attachments

  • Wrong address.PNG
    Wrong address.PNG
    37.1 KB · Views: 209
  • Wrong address2.PNG
    Wrong address2.PNG
    42.7 KB · Views: 176
Last edited by JingleBells,
@BullyWiiPlaza :DThe unknown search is working very well since the last update, but I have been having some issues and I discovered why......Take a look at the pictures, you will notice that my search is between 37000000 - 38000000. The exact value I searched is found but linked to the wrong address in the 10000000-11000000 range. (the txt shows the correct address that should be listed)

If I poke it nothing happens because in memory view it also shows the address found in my search, that was not even in my search range.....:wtf:

I checked other games with already know addresses and the same thing....JGecko U finds the value but gives the wrong address.....oops :huh:
Okay. Since I remade the search almost completely, this is apparently an issue that slipped through xD

EDIT:
I fixed it now but I couldn't test if it worked.
 
Last edited by BullyWiiPlaza,
Hello. The new Jgecko U work, but for me, the memory viewer is broken... at least there are 00000000 everywhere after the address 20000000... I do not think it is Jgecko U that doesn't work... Is it possible that TCPgecko.elf does not work properly ?
 
Does memory dumping at too big a range stop the file creation? I dumped from 30000000-49000000 and the file wasn't created.
No. I already dumped 1GB just fine. I don't know why people even say that, it never happened to me. It is created when the dump is done but only if there was no error (message).
Hello. The new Jgecko U work, but for me, the memory viewer is broken... at least there are 00000000 everywhere after the address 20000000... I do not think it is Jgecko U that doesn't work... Is it possible that TCPgecko.elf does not work properly ?
Why do you think seeing some zeros is wrong? Look at address 10000000 and it won't be like that
 
Last edited by BullyWiiPlaza,
No. I already dumped 1GB just fine. I don't know why people even say that, it never happened to me. It is created when the dump is done.
Huh. Weird... I'll try from 40000000-49000000 on friday. Searching 30000000-49000000 was too big for the java heap for me, so I might not have the RAM to dump that much. I only have 4GB
 
Last edited by HackingNewbie,
Huh. Weird... I'll try from 40000000-49000000 on friday. Searching 30000000-49000000 was too big for the java heap for me, so I might not have the RAM to dump that much. I only have 4GB
Dumping memory needs far less memory than the search because it doesn't need to remember search results nor compare anything.

I could make it write the file during dumping so low RAM users will never run into problems but then the dumping would be a bit slower for everyone :(
 
Last edited by BullyWiiPlaza,
Dumping memory needs far less memory than the search because it needs to remember search results and compare.
Maybe it's still not enough since I usually have LOADS of processes in the background while using JGecko U. Sometimes my computer slows to a halt:rofl2:
 
Last edited by HackingNewbie,
  • Like
Reactions: BullyWiiPlaza
It works now.....You definitely fixed that unknown refine search also.:ph34r: Running very well. Hope to see the ability to replace files someday:rolleyes:
What? There's a version that fixes unknown values values? Wow.. I really am the last person to know everything xD!
I was working on that, I just need to see if it works or ask some other developers...
Happy to test anything!
 
Last edited by HackingNewbie,

Site & Scene News

Popular threads in this forum