Cannot install Dashlaunch

[godreborn]

try to power cycle. I don't know if it's required, but I always do it. unplug the power, push the power button for about a minute to flush the memory, then plug the console back in.

 

[brickmii82]

If you safe flashed it, it should have a dump of the original nand. You'll need a hardware programmer if it is indeed bricked. The program that builds the dashboard is called Xebuild, and it is incorporated into Jrunner which is a user friendly interface for the RGH/Jtag procedures. Dash launch does not have a dash builder afaik.

 

[E1ite007]

Well, yeah it's bricked. Before, the console would boot slowly, but in around 2 minutes, now it just shows nothing and the power LED is on, and I cannot connect any controller neither access 360 Usb Auto-Dumper, not even after 20 minutes of waiting.
Fortunately, I did dumped the original NAND beforehand (as @brickmii82 suggests), so I just need to reflash it... but before I need to get the hardware... and also I need to learn to solder.
Shit.

 

[brickmii82]

Something isn't right here, Simple nand flasher will only flash a updflash.bin file which would only come from a legitimate build. When it dumps it goes to flashdmp.bin, and you would have to make a build. What did you use to build a dashboard?

 

[E1ite007]

Something isn't right here, Simple nand flasher will only flash a updflash.bin file which would only come from a legitimate build. When it dumps it goes to flashdmp.bin, and you would have to make a build. What did you use to build a dashboard?

J-Runner.
The console is weird. Before I brick it, system wouldn't update the avatars since those were gray. It just wouldn't recognize the update in the USB drive.
OG owner I guess never used anykind of capabilities other than playing disk backups, since he didn't used Aurora, neither any kind of homebrew since he selled me the console with burned DVDs.

 

[brickmii82]

J-Runner.
The console is weird. Before I brick it, system wouldn't update the avatars since those were gray. It just wouldn't recognize the update in the USB drive.
OG owner I guess never used anykind of capabilities other than playing disk backups, since he didn't used Aurora, neither any kind of homebrew since he selled me the console with burned DVDs.

Ok you are experienced and know RGH stuff enough to do an avatar update, I don't understand what could be wrong here either. Jrunner would still build a proper dashboard. Unfortunately, yes it sounds like you will need to solder to troubleshoot this problem further. Does Jrunner still have its logs for the build?

 

[godreborn]

J-Runner.
The console is weird. Before I brick it, system wouldn't update the avatars since those were gray. It just wouldn't recognize the update in the USB drive.
OG owner I guess never used anykind of capabilities other than playing disk backups, since he didn't used Aurora, neither any kind of homebrew since he selled me the console with burned DVDs.

You need an hdd for the avatars update.

 

[E1ite007]

You need an hdd for the avatars update.

That answers that question in that case.

Ok you are experienced and know RGH stuff enough to do an avatar update, I don't understand what could be wrong here either. Jrunner would still build a proper dashboard. Unfortunately, yes it sounds like you will need to solder to troubleshoot this problem further. Does Jrunner still have its logs for the build?

I got an XeBuild log:

Spoiler: Log

==================================
Swizzy's xeBuild GUI version 2.098
Log Started: Friday 24/09/2021 09:53:42 p. m.
==================================

*** Some console information ***
CB Version: 9188
Serial number: 123456789012
Console region: PAL/Europe (0x02FE)
DVDKey: 12345678901234567890123456789012
Console ID: 064B566441
MFR-Date: 23-06-09
OSIG String: PLDS DG-16D2S 7485
FCRT.bin Required: False

Using xell-reloaded for Glitch hack
Including dashlaunch... Done!
Including custom dashlaunch settings (launch.ini)... Done!
Copying nand to data directory, this may take a while... Done!
Checking if SMC is Glitch or Retail...
Dumping current SMC... Done!
Checking SMC...
SMC is Glitch patched! it will be used the way it is...

Parameters sent to xeBuild:

-noenter -t glitch -c trinity -d data -f 17559 -b DD88AD0C9ED669E7B56794FB68563EFA -p C9CBEC7F04E1C63E27E8581569982320 output.bin

Building nand using xeBuild (this may take a while):

---------------------------------------------------------------
xeBuild v1.21.810
---------------------------------------------------------------
base path changed to F:\Xbox 360 Trinity\xeBuild\files
---- { Image Build Mode } ----
building glitch image

done! fsroot found ok!
---------------------------------------------------------------
output.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17559.0
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 123456789012
ConsoleId : 016896097961
MoboSerial: 7029729100079265
Mfg Date : 06/23/2009
CPU Key : C9CBEC7F04E1C63E27E8581569982320
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 12345678901234567890123456789012
CF LDV : 7
KV type : type1 (no hash)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------


Moving output to your destination directory... Done!
Cleaning data and temporary directories... Done!


****** The app has now finished! ******


==================================
Swizzy's xeBuild GUI version 2.098
Log Started: Friday 24/09/2021 09:49:10 p. m.
==================================

*** Some console information ***
CB Version: 9188
Serial number: 123456789012
Console region: PAL/Europe (0x02FE)
DVDKey: 12345678901234567890123456789012
Console ID: 064B566441
MFR-Date: 23-06-09
OSIG String: PLDS DG-16D2S 7485
FCRT.bin Required: False

Using xell-reloaded for Glitch hack
Including dashlaunch... Done!
Including custom dashlaunch settings (launch.ini)... Done!
Copying nand to data directory, this may take a while... Done!
Checking if SMC is Glitch or Retail...
Dumping current SMC... Done!
Checking SMC...
SMC is Glitch patched! it will be used the way it is...

Parameters sent to xeBuild:

-noenter -t glitch -c trinity -d data -f 17559 -b DD88AD0C9ED669E7B56794FB68563EFA -p C9CBEC7F04E1C63E27E8581569982320 output.bin

Building nand using xeBuild (this may take a while):

---------------------------------------------------------------
xeBuild v1.21.810
---------------------------------------------------------------
base path changed to F:\Xbox 360 Trinity\xeBuild\files
---- { Image Build Mode } ----
building glitch image

done! fsroot found ok!
---------------------------------------------------------------
output.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17559.0
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 123456789012
ConsoleId : 016896097961
MoboSerial: 7029729100079265
Mfg Date : 06/23/2009
CPU Key : C9CBEC7F04E1C63E27E8581569982320
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 12345678901234567890123456789012
CF LDV : 7
KV type : type1 (no hash)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------


Moving output to your destination directory... Done!
Cleaning data and temporary directories... Done!


****** The app has now finished! ******

And... no, I'm not experienced at all. This is the first time I use a RGH or a modded Xbox 360 in that regard.
I'm just experienced in other console's troubleshooting as OG Xbox, Wii U, 3DS and others, and that's why I kinda did my own research before asking here. When answers were leading me to nowhere, that's when I came asking for help.

EDIT: Too bad almost no console has anykind of brick protection as the Wii with Priiloader or 3DS with Magnethax.

 

[godreborn]

Something looks weird with your DVD key, which could indicate an issue with the kv.

 

[E1ite007]

Something looks weird with your DVD key, which could indicate an issue with the kv.

Yeah, I noticed too.
360 Usb Auto-whatever showed error when trying to get the data, and it's just a string of secuential numbers (dunno why).
I don't have any idea why the OG modder modify it. The DVD works... but maybe just because he changed it ghetto style or something, and when trying to flash the NAND with that data, it cannot work with it.

EDIT: When checking on XeBuild, it shows the serial number to be the same: a string of secuential numbers, so Idk what the hell they did to this console when they modded it in the past. Thank God I still have my original 360 for playing.

 

[brickmii82]

*** Some console information ***
CB Version: 9188
Serial number: 123456789012
Console region: PAL/Europe (0x02FE)
DVDKey: 12345678901234567890123456789012

This looks like the nand was built from donors originally. This console looks like a Frankenstein situation.

 

[godreborn]

Try dumping the kv from the nand dump. Then use kv modder to check DVD key. It can be encrypted or decrypted, just need cpu key.

 

[E1ite007]

*** Some console information ***
CB Version: 9188
Serial number: 123456789012
Console region: PAL/Europe (0x02FE)
DVDKey: 12345678901234567890123456789012

This looks like the nand was built from donors originally. This console looks like a Frankenstein situation.

Sounds logical.
The console on the shell says it was built in 2010, but the NAND data says that it was built in 2009.
The serial number and DVD key is just secuential numbers.
And the region is PAL, although I'm from Mexico.

Try dumping the kv from the nand dump. Then use kv modder to check DVD key. It can be encrypted or decrypted, just need cpu key.

Well, it shows this:

The DVD drive info, serial number and manufacturing date is weird, but definitely the DVD key is not the one XeBuild is displaying.

 

[E1ite007]

Now I'm just curious.
May this be salvageable at all? Did I just wasted $75 USD (around $1,500 MXN) for a piece of crap that would work correctly anyway?

 

[brickmii82]

Sounds logical.
The console on the shell says it was built in 2010, but the NAND data says that it was built in 2009.
The serial number and DVD key is just secuential numbers.
And the region is PAL, although I'm from Mexico.


Well, it shows this:

View attachment 276953

The DVD drive info, serial number and manufacturing date is weird, but definitely the DVD key is not the one XeBuild is displaying.

This is totally repairable, but yeah it's going to need hardware flashing. Normally, Xell would be your "Priiloader" but it never worked so something was off about this to start.

 

[E1ite007]

This is totally repairable, but yeah it's going to need hardware flashing. Normally, Xell would be your "Priiloader" but it never worked so something was off about this to start.

OK.
Tbh, I'm not planning on getting the hardware... at least not now. NAND flashers are expensive for some reason (although it sounds logical), and taking this to someone who makes a living by modding consoles sounds cheaper.
What data should I scavenge for this person? And what info should I give to him?

 

[brickmii82]

OK.
Tbh, I'm not planning on getting the hardware... at least not now. NAND flashers are expensive for some reason (although it sounds logical), and taking this to someone who makes a living by modding consoles sounds cheaper.
What data should I scavenge for this person? And what info should I give to him?

Make sure they have that USB you used with the flashdmp.bin file and if you want to copy that xebuild log into a text file and show them, that might help also.

 

[E1ite007]

Make sure they have that USB you used with the flashdmp.bin file and if you want to copy that xebuild log into a text file and show them, that might help also.

Perfect.
Then I will recolect the files, and... maybe tomorrow I will gonna check if someone can help me.
If I get any updates on this, whether some modder fixes my console, or I find something new, I will post it here. I don't like to let threads with no ending.

 

[E1ite007]

OK. I did it.
I got someone to repair the NAND of the console and it works now. The only issue (possibly related to the KV) is that I don't have any connection to Live, it's stuck in 17511 (the modder told me that I shouldn't update the console since he couldn't do it at all, and this is the only kernel that worked correctly), and according to the modder, the x360run chip is soldered like shit and it can be flimsy.
He couldn't fix the DVDkey, neither the serial number, and the drive only reads burned DVDs and cannot copy DVDs (neither burned or legit) to the HDD, so... yeah. Kinda OK so far, but some limitations given how the mod is done is somewhat disappointing, but at least it works for now.

 

[brickmii82]

OK. I did it.
I got someone to repair the NAND of the console and it works now. The only issue (possibly related to the KV) is that I don't have any connection to Live, it's stuck in 17511 (the modder told me that I shouldn't update the console since he couldn't do it at all, and this is the only kernel that worked correctly), and according to the modder, the x360run chip is soldered like shit and it can be flimsy.
He couldn't fix the DVDkey, neither the serial number, and the drive only reads burned DVDs and cannot copy DVDs (neither burned or legit) to the HDD, so... yeah. Kinda OK so far, but some limitations given how the mod is done is somewhat disappointing, but at least it works for now.

Im glad you got it working again. This sounds like it is in rough shape though, which sucks.