Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
My RGH'd (Reset Glitch Hack) console can vary in how long it takes to boot. On average, it's not very long, but I've waited upwards of around 30-40 seconds to get to the splash screen. The RGH chip on my console does the glitch every boot, so it's considered persistent (there are non-persistent software exploits such as BadUpdate, with further projects like XeUnshackle to get your system closer in state with exploited consoles that have been JTAG'd or RGH'd). As for what what you do with exploit: my (simplified) understanding is roughly that glitching the chip causes some registers to get zero'd, which is very convenient when code performing memcmp is being evaluated (for comparing, say, hashes). So, you want to patch the hypervisor (which has been dumped and reverse engineered from various sources) and then do whatever you want. In practice, the downstream effect of this technical trickery was that kids would be infecting each other with mod menus on Call of Duty.
obehongHack - Custom Bad Update Payload (dumps CPU key, DVD key, 1BL) Made a custom payload for Bad Update on dashboard 17559. Uses an improved exploit version that's faster and more reliable than normal Bad Update. I also made an ABadAvatar version (no game needed, triggers from the profile select screen) but it's not on GitHub. What it shows: - Console type - Kernel version - CPU key - DVD key - Blown fuse count Buttons: - X = Save all info to USB - Y = Dump 1BL to USB - A = Backup MAC address - BACK = Exit to dashboard Video: youtube.com GitHub: Nija6600/NobehongHack2 Credits: - Bad Update exploit by grimdoomer: grimdoomer/Xbox360BadUpdate - ABadAvatar by shutterbug2000: shutterbug2000/ABadAvatar - HV patching by XeUnshackle (Byrom90): Byrom90/XeUnshackle
obehongHack - Custom Bad Update Payload (dumps CPU key, DVD key, 1BL) Made a custom payload for Bad Update on dashboard 17559. Uses an improved exploit version that's faster and more reliable than normal Bad Update. I also made an ABadAvatar version (no game needed, triggers from the profile select screen) but it's not on GitHub. What it shows: - Console type - Kernel version - CPU key - DVD key - Blown fuse count Buttons: - X = Save all info to USB - Y = Dump 1BL to USB - A = Backup MAC address - BACK = Exit to dashboard Video: youtube.com GitHub: Nija6600/NobehongHack2 Credits: - Bad Update exploit by grimdoomer: grimdoomer/Xbox360BadUpdate - ABadAvatar by shutterbug2000: shutterbug2000/ABadAvatar - HV patching by XeUnshackle (Byrom90): Byrom90/XeUnshackle