Complete noob: Need some clarifications regarding dash update

abhichoco

Junior Member
Jan 22, 2014
15
0
Hello there guys, my first post!
First of all thanks to team-xecuter for the awesome program, Jrunner.

I own a Xbox S 4gb Trinity.
My current dash version is 14699.
I'm updating to 16537, but its my first time and I'm scared Ill brick the thing. Ypu see there isn't much support for Xboxs if things go wrong here in India.

Although I have read many tutorials and watched videos, I have some doubts.

The guy I bought the xbox from had given me a nand dump, so I just loaded it up in jrunner, it automatically selected trinity and RGH2(yay!).
Entered the CPU key and then just went ahead and created a new nand dump. It went about successfully.

That's all I did, have I missed any important steps?
I mean, I don't know whether my xbox has cygnos, demon or none.
And I don't use FSD at all, so will I have to configure launch.ini options?

I know the next step is to copy it into flash 360 folder and plug into the xbox...

I know these are stupid questions, please bear with me..=p

Thanks!
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
You don't need to do any of this. Dashlaunch installer combined with xebuild/J-Runner will update the console for you over the network automatically. The latest dash is 16547, which is now supported by J-Runner.
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Thank you for the quick reply!

And the problem I have is, I don't have a network cable lying around to connect the xbox and to be honest, I don't really know to connect it to the network..:frown:
 

abhichoco

Junior Member
Jan 22, 2014
15
0
I do have a wireless network.

Could you please point me to an article/video which explains the update process?
I have never used either dashlaunch or FSD. All I use is XeXMenu with an ext. HDD.

Thanks.
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Hey..
One more thing.

I have now connected my xbox to my wireless network, now what?
When I try scanning IP on Jrunner, it says no xbox detected.

Please help.
Thanks.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Hey..
One more thing.

I have now connected my xbox to my wireless network, now what?
When I try scanning IP on Jrunner, it says no xbox detected.

Please help.
Thanks.
Why are you pressing the Scan IP button?
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Alright..
Thanks for your patience guys, I'm catching up.
Now after I download the latest official $systemupdate, I load up the standalone dashlaunch in a USB(since my xbox doesn't have dashlaunch installed) and connect it to the xbox and then just press update and everything will magically take place over the LAN? Great!

One more question,
What will happen if I check the option 'Use Dashlaunch' when there is no dashlaunch installed in my xbox?

Thanks!
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Dashlaunch should be installed on all RGH consoles. It's there for a reason. The update will build with dashlaunch fine.

Provided you put the $SystemUpdate in the xebuild/16547 folder, it'll do the avatars for you.

Once you run the dashlaunch installer, open the configurator and enable updserv. Then you can run the Update option in J-Runner.
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Hello guys,
I tried updating, but im getting the following errors.

---------------------------------------------------------------
xeBuild v1.07.632
---------------------------------------------------------------
---- { Update Mode } ----
started, watching network for xbox...success, found xbox beacon at 192.168.0.222

connected to Trinity with updsvr version 2 (peek version 0)

*****ERROR: console hv patches are not recent enough to support update mode!

update console patches and reboot before trying again.


***** FATAL UPDATE ERROR: unable to parse info reply from console!

---------------------------------------------------------------
xeBuild Finished. Have a nice day.


### NOTE ###

I tried to follow suggestions given in a post of this thread for the same error.
Follows what I got:
C:\Users\Administrator\Desktop\FSD\xeBuild_1.08>xeBuild.exe client -p
---------------------------------------------------------------
xeBuild v1.07.632
---------------------------------------------------------------
---- { Client Mode } ----
started, watching network for xbox...success, found xbox beacon at 192.168.0.222

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

disconnecting from server...OK
---------------------------------------------------------------
xeBuild Finished. Have a nice day.

Please Help!
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Alright Guys..

Apparently, if your dash is at 14699, it is too outdated to be updated via the lan technique and it will even brick some consoles if your try.
So its best advised you do it manually if you are on older dashes.

I updated mine manually to 16202(just to be safe) and then use the simple lan technique to update to 16547.

But I wasn't able to update the avatars, JRunner threw an exception 'File not Found', even though the $systemupdate folder was downloaded and placed in the correct destination. If someone can enlighten me on this, I'd appreciate that.

Hope this information proves useful to someone.

Thanks guys.
 
Last edited:

abhichoco

Junior Member
Jan 22, 2014
15
0
I have placed it inside the xebuild/16547 folder.
I downloaded it from JRunner and it is named $systemupdate and not $SystemUpdate as you mention it.
Could that be the problem?

And can I "update" to the same firmware again just for the avatars via JRunner?

Thanks.
 
Last edited:

abhichoco

Junior Member
Jan 22, 2014
15
0
Here it is..

base path changed to G:\Softwares\xeBuild
---- { Update Mode } ----
<enter> key on completion suppressed
data directory set from command line to '16547\'
dump directory set to 'G:\Softwares\output\'
***** WARNING: reusing folder G:\Softwares\output\!
started, watching network for xbox...success, found xbox beacon at 192.168.1.104
attempting to connect...success!
Getting console info...success!
connected to Trinity with updsvr version 2 (peek version 2)
NAND image size: 0x1080000 Block size: 0x4200 Spare Data: Yes
------ parsing console info response ------
Console Current Info:
running kernel : 2.0.16202.0
bootstrap type : Trinity
hardware type : Trinity
hardware flags : 0x40000207
internal HDD : not present
Image Type : Trinity (Glitch2)
CPU key : 415EDD6E1353903CC7C275FA01230503 (weight:0x35 valid; ecd: valid)
DVD key : 5564D44F9145177E0D6855D2872375B8
1BL key : DD88AD0C9ED669E7B56794FB68563EFA (good)
Virtual Fuses : not present
1BL RSA pub : good
PIRS RSA pub : good
MASTER RSA pub : good
CPU Key set to : 415EDD6E1353903CC7C275FA01230503 (weight:0x35 valid; ecd: valid)
1BL Key set to : 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
xex Key set to : 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)
Xell Reason : console eject button
CF LDV : 1
Pairing Value : 0x29ad6c pairing set to: 29 ad 6c
------ parsing ini at '16547\_glitch2.ini' ------
ini version 16547
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_16547.bin' crc: 0xa54f9efc
found (6) 'cg_16547.bin' crc: 0xc34c06ed
ini dictates dual CB for this model
ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0xf2808dc5
found (2) 'bootanim.xex' crc: 0xd5c63122
found (3) 'createprofile.xex' crc: 0xf7e474ef
found (4) 'dash.xex' crc: 0x2a153493
found (5) 'deviceselector.xex' crc: 0x09e04596
found (6) 'gamerprofile.xex' crc: 0x4647565d
found (7) 'hud.xex' crc: 0xa6f9c197
found (8) 'huduiskin.xex' crc: 0x1d296f10
found (9) 'mfgbootlauncher.xex' crc: 0x33d5771b
found (10) 'minimediaplayer.xex' crc: 0x4de56d9c
found (11) 'nomni.xexp' crc: 0x97cadcec
found (12) 'nomnifwk.xexp' crc: 0xc7ab2e5b
found (13) 'nomnifwm.xexp' crc: 0x22253a42
found (14) 'SegoeXbox-Light.xtt' crc: 0xe0ee6049
found (15) 'signin.xex' crc: 0xaffe7f78
found (16) 'updater.xex' crc: 0xf6e1cdd5
found (17) 'vk.xex' crc: 0xb916846b
found (18) 'xam.xex' crc: 0x027463e8
found (19) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (20) 'xenonclatin.xttp' crc: 0x7a507ad1
found (21) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (22) 'xenonjklatin.xttp' crc: 0xe2adddfb
found (23) 'ximecore.xex' crc: 0xa86f3ef4
found (24) 'ximedic.xex' crc: 0x1d992bfb
found (25) 'ximedic.xexp' crc: 0x186d8df9
found (26) '..\launch.xex' crc: 0x00000000
found (27) '..\lhelper.xex' crc: 0x00000000
found (28) '..\launch.ini' 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 ------

------ getting bad blocks ------
no bad blocks found on device
mounting \SystemRoot to usv:...success!
------ getting security files ------
retrieving USVR\crl.bin...OK, received 0xa00 bytes
verified! Will use if external file not found.
retrieving USVR\dae.bin...OK, received 0xad30 bytes
verified! Will use if external file not found.
retrieving USVR\extended.bin...OK, received 0x4000 bytes
verified! Will use if external file not found.
retrieving USVR\fcrt.bin...OK, received 0x4000 bytes
verified! Will use if external file not found.
retrieving USVR\secdata.bin...OK, received 0x400 bytes
verified! Will use if external file not found.
retrieving USVR\kv_enc...OK, received 0x4000 bytes
decrypt and verify...keyvault is good!
retrieving USVR\smc_enc...OK, received 0x3000 bytes
decrypt and verify...smc is good!
------ getting mobile settings ------
retrieving USVR\MobileB.dat...OK, received 0x800 bytes
retrieving USVR\MobileC.dat...not available
retrieving USVR\MobileD.dat...OK, received 0x800 bytes
retrieving USVR\MobileE.dat...not available
retrieving USVR\MobileF.dat...not available
retrieving USVR\MobileG.dat...not available
retrieving USVR\MobileH.dat...not available
retrieving USVR\MobileI.dat...not available
retrieving USVR\MobileJ.dat...not available
retrieving USVR\Statistics.settings...OK, received 0x400 bytes
retrieving USVR\Manufacturing.data...OK, received 0x80 bytes
console has no available blmod
console has no available addons
retrieving USVR\Static.settings (smc_config.bin)...OK, received 0x4000 bytes
verifying...smc_config is good!
Writing initial header to flash image
------ loading system update container ------
16547\su20076000_00000000 found, loading...done!
Read 0xb35000 bytes to memory
checking integrity...
header seems valid, version 2.0.16547.0
header hash is OK, checking content hashes...
content hashes seem OK, everything looks good!
extracted SUPD\xboxupd.bin (0x7a010 bytes)
decrypting SUPD\xboxupd.bin\CF_16547.bin (0x4560 bytes)...done!
decrypting SUPD\xboxupd.bin\CG_16547.bin (0x75aac bytes)...done!
------ Loading bootloaders and required security files ------
reading smc.bin failed, using smc.bin from nand dump
reset smc load address to 0x1000 size 0x3000
reading kv.bin failed, using kv.bin from nand dump
reading .\common\cba_9188.bin (0x1ac0 bytes)
loaded cba_9188.bin, signature check passed!
reading .\common\cbb_9188.bin (0x7800 bytes)
reading .\common\cd_9452.bin (0x4f20 bytes)
reading .\common\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)
extracted SUPD\xboxupd.bin\CF_16547.bin (0x4560 bytes)
extracted SUPD\xboxupd.bin\CG_16547.bin (0x75aac bytes)
reading 16547\bin\patches_g2trinity.bin (0x884 bytes)
reading 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 : 7c:ed:8d:57:1b:83
AVRegion : 0x00000300 (PAL50)
GameRegion : 0x02fe (PAL/EU)
DVDRegion : 5
resetKey : LRLA
---------------------
Checking for smc config data patches
smc config was not patched
---------------------
cba_9188.bin signature is good
done!
patch slot offset reset to: 0xb0000
------ Patching BLs and modifying patches ------
Patching BLs...Done!
------ Patching boot reasons and options into flash header ------
Patching header for xell power reason
------ Encrypting and finalizing bootloaders ------
encoding smc.bin size 0x3000
SMC checksum: 87e726b7
unknown SMC found, type: Trinity v5.1(3.01)
glitch hack found in smc.bin!
encoding kv.bin size 0x4000
decrypted keyvault has been set for reference
Keyvault hash is good!
encoding cba_9188.bin size 0x1ac0
encoding cbb_9188.bin size 0x7800
CB 9188 seq 0x03010001 type: 0x03 cseq: 0x01 allow: 0x0001
expected fuses:
fuseset 00: C0FFFFFFFFFFFFFF
fuseset 01: 0F0F0F0F0F0FF0F0
fuseset 02: F000000000000000 (sequence)
fuseset 02: F000000000000000 (allow cseq 1)
**dual CB flag detected!**
encoding cd_9452.bin size 0x5290
encoding ce_1888.bin size 0x56070
encoding xell-gggggg.bin size 0x40000
encoding cf_16547.bin size 0x4560
encoding cg_16547.bin size 0x75ab0
encoding patches_g2trinity.bin size 0x4b8
done!
------ Adding bootloaders to flash image ------
adding smc.bin at raw offset 0x00001000 len 0x3000 (end 0x4000)
adding kv.bin at raw offset 0x00004000 len 0x4000 (end 0x8000)
adding cba_9188.bin at raw offset 0x00008000 len 0x1ac0 (end 0x9ac0)
adding cbb_9188.bin at raw offset 0x00009ac0 len 0x7800 (end 0x112c0)
adding cd_9452.bin at raw offset 0x000112c0 len 0x5290 (end 0x16550)
adding ce_1888.bin at raw offset 0x00016550 len 0x56070 (end 0x6c5c0)
adding xell-gggggg.bin at raw offset 0x00070000 len 0x40000 (end 0xb0000)
adding cf_16547.bin at raw offset 0x000b0000 len 0x4560 (end 0xb4560)
adding cg_16547.bin at raw offset 0x000b4560 len 0x75ab0 (end 0xc0000, rest in fs)
adding patches_g2trinity.bin at raw offset 0x000c0010 len 0x4b8 (end 0xc04c8)
Fixing up FS table...done!
Writing zeropair CG patch slot overflow data to sysupdate.xexp1
at raw offset 0xd0000 len 0x0006a010 (end: 0x0013a010)...done!
------ adding 28 firmware files ------
extracted SUPD\aac.xexp (0x14000 bytes) (crc32: 0xf2808dc5 ini: 0xf2808dc5)
adding as aac.xexp1 at raw offset 0x13a010 len 0x00014000 (end 0x0014e010)
extracted SUPD\bootanim.xex (0x61000 bytes) (crc32: 0xd5c63122 ini: 0xd5c63122)
adding as bootanim.xex at raw offset 0x150000 len 0x00061000 (end 0x001b1000)
extracted SUPD\createprofile.xex (0xc000 bytes) (crc32: 0xf7e474ef ini: 0xf7e474ef)
adding as createprofile.xex at raw offset 0x1b1000 len 0x0000c000 (end 0x001bd000)
extracted SUPD\dash.xex (0x598000 bytes) (crc32: 0x2a153493 ini: 0x2a153493)
adding as dash.xex at raw offset 0x1c0000 len 0x00598000 (end 0x00758000)
extracted SUPD\deviceselector.xex (0xa000 bytes) (crc32: 0x09e04596 ini: 0x09e04596)
adding as deviceselector.xex at raw offset 0x758000 len 0x0000a000 (end 0x00762000)
extracted SUPD\gamerprofile.xex (0x1b000 bytes) (crc32: 0x4647565d ini: 0x4647565d)
adding as gamerprofile.xex at raw offset 0x762000 len 0x0001b000 (end 0x0077d000)
extracted SUPD\hud.xex (0x1d000 bytes) (crc32: 0xa6f9c197 ini: 0xa6f9c197)
adding as hud.xex at raw offset 0x77f000 len 0x0001d000 (end 0x0079c000)
extracted SUPD\huduiskin.xex (0x14000 bytes) (crc32: 0x1d296f10 ini: 0x1d296f10)
adding as huduiskin.xex at raw offset 0x79d000 len 0x00014000 (end 0x007b1000)
extracted SUPD\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0x33d5771b ini: 0x33d5771b)
adding as mfgbootlauncher.xex at raw offset 0x7b4000 len 0x00008000 (end 0x007bc000)
extracted SUPD\minimediaplayer.xex (0xc000 bytes) (crc32: 0x4de56d9c ini: 0x4de56d9c)
adding as minimediaplayer.xex at raw offset 0x7bc000 len 0x0000c000 (end 0x007c8000)
extracted SUPD\nomni.xexp (0xc800 bytes) (crc32: 0x97cadcec ini: 0x97cadcec)
adding as nomni.xexp1 at raw offset 0x7c8000 len 0x0000c800 (end 0x007d4800)
extracted SUPD\nomnifwk.xexp (0x2000 bytes) (crc32: 0xc7ab2e5b ini: 0xc7ab2e5b)
adding as nomnifwk.xexp1 at raw offset 0x7d4800 len 0x00002000 (end 0x007d6800)
extracted SUPD\nomnifwm.xexp (0x5000 bytes) (crc32: 0x22253a42 ini: 0x22253a42)
adding as nomnifwm.xexp1 at raw offset 0x7da000 len 0x00005000 (end 0x007df000)
extracted SUPD\SegoeXbox-Light.xtt (0x6000 bytes) (crc32: 0xe0ee6049 ini: 0xe0ee6049)
adding as SegoeXbox-Light.xtt at raw offset 0x7e1000 len 0x00006000 (end 0x007e7000)
extracted SUPD\signin.xex (0x19000 bytes) (crc32: 0xaffe7f78 ini: 0xaffe7f78)
adding as signin.xex at raw offset 0x7ea000 len 0x00019000 (end 0x00803000)
extracted SUPD\updater.xex (0x7000 bytes) (crc32: 0xf6e1cdd5 ini: 0xf6e1cdd5)
adding as updater.xex at raw offset 0x805000 len 0x00007000 (end 0x0080c000)
extracted SUPD\vk.xex (0xb000 bytes) (crc32: 0xb916846b ini: 0xb916846b)
adding as vk.xex at raw offset 0x80f000 len 0x0000b000 (end 0x0081a000)
extracted SUPD\xam.xex (0x253000 bytes) (crc32: 0x027463e8 ini: 0x027463e8)
adding as xam.xex at raw offset 0x81b000 len 0x00253000 (end 0x00a6e000)
retrieving USVR\xenonclatin.xtt...OK, received 0x11b000 bytes
extracted USVR\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
adding as xenonclatin.xtt at raw offset 0xa6f000 len 0x0011b000 (end 0x00b8a000)
extracted SUPD\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
adding as xenonclatin.xttp1 at raw offset 0xb8b000 len 0x00018000 (end 0x00ba3000)
retrieving USVR\xenonjklatin.xtt...OK, received 0x1a8000 bytes
extracted USVR\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
adding as xenonjklatin.xtt at raw offset 0xba4000 len 0x001a8000 (end 0x00d4c000)
extracted SUPD\xenonjklatin.xttp (0x7000 bytes) (crc32: 0xe2adddfb ini: 0xe2adddfb)
adding as xenonjklatin.xttp1 at raw offset 0xd4c000 len 0x00007000 (end 0x00d53000)
extracted SUPD\ximecore.xex (0x17000 bytes) (crc32: 0xa86f3ef4 ini: 0xa86f3ef4)
adding as ximecore.xex at raw offset 0xd53000 len 0x00017000 (end 0x00d6a000)
retrieving USVR\ximedic.xex...OK, received 0x90000 bytes
extracted USVR\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
adding as ximedic.xex at raw offset 0xd6b000 len 0x00090000 (end 0x00dfb000)
extracted SUPD\ximedic.xexp (0x2800 bytes) (crc32: 0x186d8df9 ini: 0x186d8df9)
adding as ximedic.xexp1 at raw offset 0xdfc000 len 0x00002800 (end 0x00dfe800)
reading 16547\..\launch.xex (0xd000 bytes)
adding as launch.xex at raw offset 0xdfe800 len 0x0000d000 (end 0x00e0b800)
reading 16547\..\lhelper.xex (0x6000 bytes)
adding as lhelper.xex at raw offset 0xe0d000 len 0x00006000 (end 0x00e13000)
retrieving USVR\launch.ini...failed! file not found on console
***** could not read file '..\launch.ini', skipping *****
------ adding 5 security files ------
<- Processing crl.bin ->
could not read crl.bin, using data from SUPD...
crl appears crypted, attempting to decrypt with CPU key...failed! Trying alternate key...success!
adding as crl.bin at raw offset 0xe18000 len 0x00000a00 (end 0x00e18a00)
<- Processing dae.bin ->
could not read dae.bin, using data from SUPD...
dae appears encrypted, attempting to decrypt with CPU key...failed! Attempting to decrypt with alternate key...
success!
adding as dae.bin at raw offset 0xe1c000 len 0x00007090 (end 0x00e23090)
<- Processing extended.bin ->
could not read extended.bin, using data from previous parse...
adding as extended.bin at raw offset 0xe24000 len 0x00004000 (end 0x00e28000)
<- Processing fcrt.bin ->
could not read fcrt.bin, using data from previous parse...
adding as fcrt.bin at raw offset 0xe28000 len 0x00004000 (end 0x00e2c000)
<- Processing secdata.bin ->
could not read secdata.bin, using data from previous parse...
adding as secdata.bin at raw offset 0xe2c000 len 0x00000400 (end 0x00e2c400)
------ checking for Mobile*.dat ------
MobileB.dat found, adding from previous parse
adding MobileB.dat as type 0x31 at raw offset 0xe30000 len 0x800 (end 0xe30800)
MobileD.dat found, adding from previous parse
adding MobileD.dat as type 0x33 at raw offset 0xe34000 len 0x800 (end 0xe34800)
Statistics.settings found, adding from previous parse
adding Statistics.settings at raw offset 0xf78000 len 0x400 (end 0xf78400)
Manufacturing.data found, adding from previous parse
adding Manufacturing.data at raw offset 0xf74000 len 0x80 (end 0xf74080)
------ 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 offset 0xe38000 len 0x4000 (end 0xe3c000)...done!
fixing up big block controller on small block NAND LBA numbers...done!
calculating ECD bytes and assembling raw image...done!
done remapping!
unmounting usv:...success!
------ dumping console flash ------
reading flash image from console...received 0x1080000 bytes data OK, writing to file G:\Softwares\output\nanddump.bin...success!
Completed in 7s
------ flashing console ------
sending flash data to console...
file sent OK, awaiting result...success!
Completed in 9s
------ loading and sending avatar data ------
avatar data skipped, no HDD detected
sending reboot command...OK
------ writing image to disk ------
writing file 'G:\Softwares\output\16547_g2_trinity.bin' to disk...done!
---------------------------------------------------------------
G:\Softwares\output\16547_g2_trinity.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16547.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 003733511208
ConsoleId : 009116783397
MoboSerial: 9256477106661118
Mfg Date : 03/13/2011
CPU Key : 415EDD6E1353903CC7C275FA01230503
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 5564D44F9145177E0D6855D2872375B8
CF LDV : 1
KV type : type2 (hashed - Good! Signature is valid.)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
 

abhichoco

Junior Member
Jan 22, 2014
15
0
Hey guys,

Finally figured it out, the avatars weren't being updated because of a Dash Launch setting, where noupdate was enabled. Disable it and then try,
or else rename the update folder as '$$ystemUpdate'.

Cheers!
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Hey guys,

Finally figured it out, the avatars weren't being updated because of a Dash Launch setting, where noupdate was enabled. Disable it and then try,
or else rename the update folder as '$$ystemUpdate'.

Cheers!
Nope -it had nothing to do with that. Provided you followed the instructions and ensured $SystemUpdate was in the xebuild/16547 folder on your PC BEFORE running the Update feature, it would have applied them for you. How you apply them via USB is different. Totally different.