Definatley Appears to be something not quite right with Slims and recent dash

[seanr28]

nothing connected at the minute, just AV lead.

Anyway heres my log file for the new dash currently running on it.

there is an error, clearly not a major one, and is worked I was not worried about but should I be concerned?

--------------------------------------------------------------
xeBuild v1.00.356
---------------------------------------------------------------
building glitch image
data directory overridden from command line to '14699'
per build directory overridden from command line to 'mydata'
file name overridden from command line to 'trinityout.bin'
------ parsing user ini at '.\mydata\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x173 bytes in memory
loading cpukey.txt from .\mydata\cpukey.txt
CPU Key set to: 0x
loading 1blkey.txt from 1blkey.txt
1BL Key set to: 0x sum: 0x983 (expects: 0x983)
xex Key set to: 0x2 sum: 0x800 (expects: 0x800)
------ parsing ini at '.\14699\_glitch.ini' ------
ini version 14699
ini: label [trinitybl] found
found (1) 'cba_9188.bin' crc: 0x5a76752d
found (2) 'cbb_9188.bin' crc: 0xfebb1074
found (3) 'cd_9452.bin' crc: 0x455fa02c
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_14699.bin' crc: 0x6fb4d90e
found (6) 'cg_14699.bin' crc: 0xbccc9fe1
ini dictates dual CB for this model
ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0x36790e61
found (2) 'bootanim.xex' crc: 0x187ede71
found (3) 'createprofile.xex' crc: 0x81d7a946
found (4) 'dash.xex' crc: 0x3957764c
found (5) 'deviceselector.xex' crc: 0x6246b4c0
found (6) 'gamerprofile.xex' crc: 0xb7add96a
found (7) 'hud.xex' crc: 0x202eb5c8
found (8) 'huduiskin.xex' crc: 0x4c80fbe9
found (9) 'mfgbootlauncher.xex' crc: 0x254ad664
found (10) 'minimediaplayer.xex' crc: 0xd8d21cfc
found (11) 'nomni.xexp' crc: 0xbf36fdf7
found (12) 'nomnifwk.xexp' crc: 0xa837ae53
found (13) 'nomnifwm.xexp' crc: 0x93246a8a
found (14) 'SegoeXbox-Light.xtt' crc: 0x086eb344
found (15) 'signin.xex' crc: 0xecd9cab1
found (16) 'updater.xex' crc: 0x125cdb94
found (17) 'vk.xex' crc: 0x9c744d4c
found (18) 'xam.xex' crc: 0x0b764b88
found (19) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (20) 'xenonclatin.xttp' crc: 0x7a507ad1
found (21) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (22) 'xenonjklatin.xttp' crc: 0x945b7092
found (23) 'ximecore.xex' crc: 0x8d45ea14
found (24) 'ximedic.xex' crc: 0x1d992bfb
found (25) 'ximedic.xexp' crc: 0xc90a651a
found (26) '..\launch.xex' crc: 0x00000000
found (27) '..\lhelper.xex' crc: 0x00000000
ini: label [security] found
found (1) 'crl.bin' crc: 0x00000000
found (2) 'dae.bin' crc: 0x00000000
found (3) 'extended.bin' crc: 0x00000000
found (4) 'fcrt.bin' crc: 0x00000000
found (5) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------
output name overridden to: trinityout.bin

------ Checking .\mydata\nanddump.bin ------
Loading NAND dump (0x22ee70 bytes)...done!
NAND dump is from a small block machine
NAND dump uses big block controller
parsing dump into user and spare...
done!
decrypting KeyVault at address 0x4000 of size 0x4000
keyvault decrypted OK, will use if no kv.bin is provided
decrypting SMC at address 0x1000 of size 0x3000
SMC decrypted OK, will use if no external smc.bin is provided
seeking smc config in dump...found at offset 0xf7c000! Using if no smc config is provided.
CF slot 0 decrypted ok LDV 0x03 Pairing: 0x8c6e9a
CF slot 1 decrypted ok LDV 0x02 Pairing: 0x8c6e9a
setting pairing data from image to 0x8c6e9a
LDV was previously set to 3
MobileB.dat found at page 0x8c0, size 2048 (0x800) bytes
MobileC.dat found at page 0x4d40, size 512 (0x200) bytes
MobileE.dat found at page 0x42c0, size 2048 (0x800) bytes
seeking security files...fsroot found at page 0x42a0 raw offset 0x896a00
crl.bin found in sector 0x356 size 0xa00...verified! Will use if external file not found.
dae.bin found in sector 0x60 size 0xad30...verified! Will use if external file not found.
extended.bin found in sector 0x35b size 0x4000...verified! Will use if external file not found.
fcrt.bin found in sector 0x353 size 0x4000...verified! Will use if external file not found.
secdata.bin found in sector 0x32b size 0x400...verified! Will use if external file not found.
Writing initial header to flash image
------ Loading bootloaders and required security files ------
reading .\mydata\smc.bin failed, using smc.bin from nand dump
reading .\mydata\kv.bin failed, using kv.bin from nand dump
reading .\14699\cba_9188.bin (0x1ac0 bytes)
reading .\14699\cbb_9188.bin (0x7800 bytes)
reading .\14699\cd_9452.bin (0x4f20 bytes)
reading .\14699\ce_1888.bin (0x5606a b pad 0x56070 b)
xell not found in perbuild directory, checking firmware /bin folder
xell not found in firmware /bin folder, checking base path
reading xell-gggggg.bin (0x40000 bytes)
reading .\14699\cf_14699.bin (0x4450 bytes)
reading .\14699\cg_14699.bin (0x67168 b pad 0x67170 b)
reading .\14699\bin\patches_trinity.bin (0x6f8 bytes)
reading .\mydata\smc_config.bin failed, using smc_config.bin from nand dump
-------------------
checking smc_config
-------------------
extracting config
------------------
SMC config info:
------------------
Target temps: Cpu: 82øC Gpu: 78øC Edram: 76øC
Max temps : Cpu: 89øC Gpu: 82øC Edram: 82øC
Cpu Fan : (auto)
Gpu Fan : (auto)
MAC Address : 00:25:ae:80:a4:da
AVRegion : 0x00000300 (PAL50)
GameRegion : 0x02fe (NTSC/EU)
DVDRegion : 2
resetKey : AADR
---------------------
Checking for smc config data patches
smc config was not patched
---------------------
done!
------ Encrypting and finalizing bootloaders ------
SMC checksum: f9c96639
known clean SMC found, type: Trinity v5.1(3.01)
******* ERROR: clean SMC found? you should use a hacked smc for glitch images.
done!
------ Adding bootloaders to flash image ------
adding smc.bin to 0x00001000 len 0x3000
adding kv.bin to 0x00004000 len 0x4000
adding cba_9188.bin to 0x00008000 len 0x1ac0
adding cbb_9188.bin to 0x00009ac0 len 0x7800
adding cd_9452.bin to 0x000112c0 len 0x5200
adding ce_1888.bin to 0x000164c0 len 0x56070
adding xell-gggggg.bin to 0x00070000 len 0x40000
adding cf_14699.bin to 0x000b0000 len 0x4450
adding cg_14699.bin to 0x000b4450 len 0x67170
adding patches_trinity.bin to 0x000c0010 len 0x3e8
Fixing up FS table...done!
Writing CG patch slot overflow data to sysupdate.xexp1...done!
------ adding 27 firmware files ------
reading .\14699\aac.xexp (0x14000 bytes) (crc32: 0x36790e61 ini: 0x36790e61)
adding as aac.xexp1 at raw offset 0x12b5c0
reading .\14699\bootanim.xex (0x61000 bytes) (crc32: 0x187ede71 ini: 0x187ede71)
adding as bootanim.xex at raw offset 0x140000
reading .\14699\createprofile.xex (0xc000 bytes) (crc32: 0x81d7a946 ini: 0x81d7a946)
adding as createprofile.xex at raw offset 0x1a1000
reading .\14699\dash.xex (0x63a000 bytes) (crc32: 0x3957764c ini: 0x3957764c)
adding as dash.xex at raw offset 0x1b0000
reading .\14699\deviceselector.xex (0x9000 bytes) (crc32: 0x6246b4c0 ini: 0x6246b4c0)
adding as deviceselector.xex at raw offset 0x7ea000
reading .\14699\gamerprofile.xex (0x1b000 bytes) (crc32: 0xb7add96a ini: 0xb7add96a)
adding as gamerprofile.xex at raw offset 0x7f5000
reading .\14699\hud.xex (0x1e000 bytes) (crc32: 0x202eb5c8 ini: 0x202eb5c8)
adding as hud.xex at raw offset 0x813000
reading .\14699\huduiskin.xex (0x13000 bytes) (crc32: 0x4c80fbe9 ini: 0x4c80fbe9)
adding as huduiskin.xex at raw offset 0x832000
reading .\14699\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0x254ad664 ini: 0x254ad664)
adding as mfgbootlauncher.xex at raw offset 0x847000
reading .\14699\minimediaplayer.xex (0xc000 bytes) (crc32: 0xd8d21cfc ini: 0xd8d21cfc)
adding as minimediaplayer.xex at raw offset 0x850000
reading .\14699\nomni.xexp (0xe000 bytes) (crc32: 0xbf36fdf7 ini: 0xbf36fdf7)
adding as nomni.xexp1 at raw offset 0x85c000
reading .\14699\nomnifwk.xexp (0x2000 bytes) (crc32: 0xa837ae53 ini: 0xa837ae53)
adding as nomnifwk.xexp1 at raw offset 0x86a000
reading .\14699\nomnifwm.xexp (0x5000 bytes) (crc32: 0x93246a8a ini: 0x93246a8a)
adding as nomnifwm.xexp1 at raw offset 0x86e000
reading .\14699\SegoeXbox-Light.xtt (0x6000 bytes) (crc32: 0x086eb344 ini: 0x086eb344)
adding as SegoeXbox-Light.xtt at raw offset 0x875000
reading .\14699\signin.xex (0x16000 bytes) (crc32: 0xecd9cab1 ini: 0xecd9cab1)
adding as signin.xex at raw offset 0x87e000
reading .\14699\updater.xex (0x7000 bytes) (crc32: 0x125cdb94 ini: 0x125cdb94)
adding as updater.xex at raw offset 0x896000
reading .\14699\vk.xex (0x9000 bytes) (crc32: 0x9c744d4c ini: 0x9c744d4c)
adding as vk.xex at raw offset 0x89f000
reading .\14699\xam.xex (0x236000 bytes) (crc32: 0x0b764b88 ini: 0x0b764b88)
adding as xam.xex at raw offset 0x8a9000
reading .\14699\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
adding as xenonclatin.xtt at raw offset 0xae2000
reading .\14699\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
adding as xenonclatin.xttp1 at raw offset 0xbff000
reading .\14699\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
adding as xenonjklatin.xtt at raw offset 0xc18000
reading .\14699\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
adding as xenonjklatin.xttp1 at raw offset 0xdc0000
reading .\14699\ximecore.xex (0x15000 bytes) (crc32: 0x8d45ea14 ini: 0x8d45ea14)
adding as ximecore.xex at raw offset 0xdc7000
reading .\14699\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
adding as ximedic.xex at raw offset 0xddd000
reading .\14699\ximedic.xexp (0x2800 bytes) (crc32: 0xc90a651a ini: 0xc90a651a)
adding as ximedic.xexp1 at raw offset 0xe70000
***** could not read .\14699\..\launch.xex, skipping *****
***** could not read .\14699\..\lhelper.xex, skipping *****
------ adding 5 security files ------
reading .\mydata\crl.bin (0xa00 bytes)
writing as crl.bin to flash
crl appears crypted, attempting to decrypt with CPU key...failed! Trying alternate key...success!
reading .\mydata\dae.bin (0xad30 bytes)
writing as dae.bin to flash
dae appears encrypted, attempting to decrypt with CPU key...failed! Attempting to decrypt with alternate key...
success!
reading .\mydata\extended.bin (0x4000 bytes)
writing as extended.bin to flash
could not read fcrt.bin, using data from nanddump.bin...writing as fcrt.bin to flash
reading .\mydata\secdata.bin (0x400 bytes)
writing as secdata.bin to flash
------ checking for Mobile*.dat ------
MobileB.dat was found in dump, 0x800 bytes, adding type 0x31
MobileC.dat was found in dump, 0x200 bytes, adding type 0x32
MobileE.dat was found in dump, 0x800 bytes, adding type 0x34
------ adding smc_config.bin ------
adding smc config to offset 0x00f7c000, len 0x400
------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
fixing up big block controller on small block NAND LBA numbers...done!
calculating ECD bytes and assembling raw image...done!
writing file 'trinityout.bin' to disk...done!
trinityout.bin written OK
---------------------------------------------------------------
trinityout.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size: 16MiB
Build : Glitch
Xell : power on console with console eject button
CPU Key :
1BL Key :
CF LDV : 3
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

---------- Post added at 22:30 ---------- Previous post was at 22:27 ----------

in the options should the patchsmc = false - should I have changed this to true?

---------- Post added at 22:37 ---------- Previous post was at 22:30 ----------

just tried the patched SMC option, no error on the log now, re-flashed it but still red lights

 

[faz2k2000]

LDV issues ?

 

[ball00]

LDV issues ?

Definitely not as he gets it to boot albeit occasionally

 

[TimboZero]

As it says in the tuts the LDV must be set correctly and the patchsmc (on a slim) must be set to true. After flashing (and they say use 360nandflasher but i found it caused the error in this thread and so used rawflash instead to avoid the erase) you must pull the psu for 30secs as the smc has been changed and needs to 'reset'.
I had the same issue as in this thread until I changed to rawflash and pulled the psu. I had already the correct settings in the ini but for some reason a few slims dont seem to like 360nandflasher.

 

[garageinc]

thats odd mate as the second slim i done i was wondering if my switches were working too. the issue i had was on slim no green light but on phat green light but no glitch. you did help a bit on it if you remember. anyway i tried various lengths of wire before settling on one fairly short but the console went with very erratic boot times between 5 seconds and 1min 30 seconds on slim setting but no glitch ever on phat. now the console was glitching fine and fully built up the night before with boot times on slim of between instant and 15 seconds on the full 50cm wire, but when i tested with the customer it didn't even flash green on the CR. funny thing here is the last thing i did with it the night before was see if it booted better on phat which it didn't so switched back to slim and put the outer casing back on. makes me wonder if it was still stuck on phat when the customer arrived. like i said i finally got it going to a degree after trimming and off it went but during the trimming process i was trying both slim and phat so it could also have switched back to slim properly. its possible i could ask this console to be returned if there is a way to check this out, i'm sure it would be simple enough to bypasss the switch or remove it and solder the correct connection in place.

on a side note i just had outstanding results from wrapping the cpu-rst round the xclamps insead of coiling or snaking. boot times of instant to 10 seconds virtually every time andthis slim was being stubborn as ever coiled or snaked at full length. i also trimmed 1cm of the wire also snaked and coiled it and was no good but wrap it round the xclamps and it loves it trying to hunt doown the thread i found someone discover this on to report it and thank them.

 

[esbmaepo]

I have just updated 2 SLIMS to the new dashboard. Did this:

1) Using Nand Flasher 360. Dumped Nand.

2) Created new image file with XeBuild. Did NOT select Dashlaunch.

3) Using Nand Flasher 360. Flashed new image file.

4) Booted up. Workes fine. Installed Dashlaunch.

Both consoles working fine

 

[bongtoker]

Nothing stands out in the log. Wouldn't explain why it started now, but are there any wires that could be shorting something? How is CPU_RST routed?

 

[seanr28]

ok, looks like i have resolved it, switch was still sticky,but I have since re-made the image, and made sure that SMC Patch = true, was set to false before. I have tried it several times now and so far so good.