#21. Posted:
Rodent
  • Blind Gifter
Status: Offline
Joined: Jan 21, 201212Year Member
Posts: 9,958
Reputation Power: 11632
Status: Offline
Joined: Jan 21, 201212Year Member
Posts: 9,958
Reputation Power: 11632
Proof this works
#22. Posted:
-Sparks
  • Winter 2020
Status: Offline
Joined: Oct 26, 20149Year Member
Posts: 462
Reputation Power: 2042
Status: Offline
Joined: Oct 26, 20149Year Member
Posts: 462
Reputation Power: 2042
Works for me, Thanks!
#23. Posted:
Nicholasbroo
  • Prospect
Status: Offline
Joined: Feb 20, 201014Year Member
Posts: 670
Reputation Power: 35
Status: Offline
Joined: Feb 20, 201014Year Member
Posts: 670
Reputation Power: 35
Important: Do make sure you have a NAND-X / JR-Programmer before ever flashing your nand to ensure you can get right back into it.
Testing is such a marvelous thing, but things can go wrong during a flash examples are below. Each console is different, and patches vary between each console type.

I've noticed a few bugs that were never patched or the offsets were not on my trinity nand

[TRINITY CRITICAL BUGS]
1. The dashboard can crash a lot, and go into dump mode before reboot.
2. Sometimes the console turns into a test kit, and you cannot debug the console at all
3. HVPeekxPoke is not patched, you can peek, but you cannot poke any data
4. Return To XShell does not patch the hudstring's correctly and therefore doesn't work.
5. Various Kernel hard crashes in dump mode [Requires 2 consecutive reboots] Dash.xex is buggy...
6. Watson spams annoying network errors as it's not patched..
Error: [DISCARD] IP-level unicast via link-level multicast or vice versa
7. Still looking around...


Note: This is with and without using a CPUKey to build your nand.
Which means some patches could be wrong; But, instead of assuming, I'm looking around to see if that's entirely true. Also, thanks OP for the release!

Notes: This doesn't support any patches at all. I've been looking around, and no patches are enabled on this build. Possibly due to the fact there isn't any patches in the patches folder.
So if you'd want to fully debug, you have two options.
1. Switch to 17150 and spoof to 17559
or
2. Wait for an official build which I hope should be soon....

I'll add more data as I go along...

My Speculation has been confirmed from patching from 17150 / v510 build of RGLoader vs. This build.
When you build your nand, you're supposed to see the following from options.ini.
Compiling KHV Patches for 17150-dev...
--- SHADOWBOOT DISABLED ---
--- SYSTEM ROOT MAPPED TO HDD ---
--- KD retries patched to 1 ---
--- Adding HvxPeekPoke ---
--- Disabling Mem Protection ---
KHV Patch build completed! <= we require these patches.


Image of this:
https://cdn.discordapp.com/attachments/776772247980867585/796104805218779196/17150A.PNG


When you build your nand with this and many other versions even with the patches etc, set up, you only see
*** KHV Patch build completed!


Image of this:
https://media.discordapp.net/attachments/776772247980867585/796104854765305886/17489NOPATCHES.PNG


Therefore, no patches are enabled except the original spoof patches in flash/filesystems. I.E rglXam.rglp file. Nothing will be patched at least on Trinity. Didn't test others.
Users browsing this topic: None
Jump to:


RECENT POSTS

HOT TOPICS