Hi all, i had a 250gb slim version like 3 years (or more) turn down, i remember some guy installed a RGH (i guess) chip
Today i turn on again and try to just play a new game, i must update from the disc to run the game so i start to learn how update it , i follow some pretty easy tutorials to update with dashlaunch 3.16 and xenbuild, my dash ver is 14699 and i get this error when i try to update with xebuild update -f 17489 trought updsvr
Ok, read somewhere that the command "xebuild.exe client -p" should fix the problem, i get a new error:
So now, i0m totally lost, i don't know what to do 
By other hand I tried to make nand dump, and seems there is not cpukey and that... the console has some backup in the hdd and works perfect with XeXMenu 1.1
I would appreciate some tips
Today i turn on again and try to just play a new game, i must update from the disc to run the game so i start to learn how update it , i follow some pretty easy tutorials to update with dashlaunch 3.16 and xenbuild, my dash ver is 14699 and i get this error when i try to update with xebuild update -f 17489 trought updsvr
Code:
*****ERROR: console hv patches are not recent enough to support update mode! update console patches and reboot before trying again.
Ok, read somewhere that the command "xebuild.exe client -p" should fix the problem, i get a new error:
Code:
connected to Trinity with updsvr version 2 (peek version 0)Updating patches in auto mode: 14699\bin\patches_g2Trinity.bin
***** ERROR: could not load 14699\bin\patches_g2Trinity.bin, aborting
By other hand I tried to make nand dump, and seems there is not cpukey and that... the console has some backup in the hdd and works perfect with XeXMenu 1.1
Code:
xeBuild v1.12.659---------------------------------------------------------------
---- { Client Mode } ----
started, watching network for xbox...success, found xbox beacon at 192.168.1.40
attempting to connect...success!
Getting console info...success!
connected to Trinity with updsvr version 1 (peek version 0)
NAND image size: 0x1080000 Block size: 0x4200 Spare Data: Yes
------ parsing console info response ------
Console Current Info:
running kernel : 2.0.14699.0
bootstrap type : Trinity
hardware type : Trinity
hardware flags : 0x40000227
internal HDD : present
Image Type : Trinity (Glitch2)
1BL key : 00000000000000000000000000000000 (bad)
Virtual Fuses : not present
1BL RSA pub : bad
PIRS RSA pub : bad
MASTER RSA pub : bad
Xell Reason : console eject button
CF LDV : 0
Pairing Value : 0x000000
dumping console flash to \Users\MaTi\Desktop\nanddump.bin
reading flash image from console...received 0x1080000 bytes data OK, writing to file \Users\MaTi\Desktop\nanddump.bin...success!
Completed in 2s
success!