black screen whit jasper BB

x23are

Senior Member
Nov 4, 2011
145
0
krj
if it stopped booting xell after installing the cap then there is your problem - your issue now is down to that one specific change - did you wire it correctly? if so, then it must be down to 1 of 3 things...soldering...wire routing....or installed 'extra' components....
1.I desoldered.no problem in soldering
2.wire routing :(i am sorry for very low qualitiy but is show wire routing)

3.there isnt any extra component.
but just black screen and no xell booting.
what is(are) my problem(s)?
 
Last edited:

x23are

Senior Member
Nov 4, 2011
145
0
krj
how do i found my soldering is correct?can i use a LED?(if yes) i did this work before.if this method is correct i will send the result.
i am noob.please help me.
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
my problem back again.
i try to solder a cap for solve freezing problem but console not booting xell now.
i flashed the ecc image again but no result.
check wirring .everything is good.
test coolrunner whit impact there isnt any problem.
what do i do?
i checked everything sevsral times but no booting?when i try solder a cap this problem appeared(before that system booted correctly and instantly).
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
when i connected my fans i saw they werent 5v and they were 12v.
what is problem?this is first time i see this problem.(my not booting still exist)
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
i checked everything sevsral times but no booting?when i try solder a cap this problem appeared(before that system booted correctly and instantly).
What capacitor are you using? Seams to a wrong value
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
i use 683-680-104 but no result.may my CR or its component is damaged ?(it flashed whit impact.)
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
i use 683-680-104 but no result.may my CR or its component is damaged ?(it flashed whit impact.)
You could try with a higher value cap. I have been using 150nF caps with good results.
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
no.i whitout cap rghed my console.(boot 2-6 sec).
if you read page 1&2 of my thread).
but i dont know what is this problem?
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
please tell me:
how to check and find:
1.my motherboard components is damaged?
2.my CR is damaged?
what INSTRUMENT is needed?
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
please tell me:
how to check and find:
1.my motherboard components is damaged?
2.my CR is damaged?
what INSTRUMENT is needed?
Okay

Dont think your CR is at fault. You could boot to Xell in the first place.

Maybe your final image.bin is the problem. You're saying your fans are spinning with 12v. Did that happen AFTER flashing final image file?
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
Okay

Dont think your CR is at fault. You could boot to Xell in the first place.

Maybe your final image.bin is the problem. You're saying your fans are spinning with 12v. Did that happen AFTER flashing final image file?
yes.i could boot to xell and freeboot in the first place.
i think.but after the problem i erase my nand and write it again but fans are 12v still.
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
yes.i could boot to xell and freeboot in the first place.
i think.but after the problem i erase my nand and write it again but fans are 12v still.
Did you have any bad blocks in your original nand?

Are you using QSB for reading nand?
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
Did you have any bad blocks in your original nand?

Are you using QSB for reading nand?
no.i dumped my nand 10 times whotout any bad block.(i use a homemade flasher).
no.i dont use qsb for reading or writing my nand.
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
no.i dumped my nand 10 times whotout any bad block.(i use a homemade flasher).
no.i dont use qsb for reading or writing my nand.
No bad blocks ehh...

Then you should revert back to your original nand.

Remove power from CR

See what happens.

Could also post Multibuilder log-file from creating freeBoot file
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
No bad blocks ehh...

Then you should revert back to your original nand.

Remove power from CR

See what happens.

Could also post Multibuilder log-file from creating freeBoot file
I remove Cr and all wires but no...
Code:
---------------------------------------------------------------
     ggBuild v0.33.273
---------------------------------------------------------------
data directory overridden from command line to '13604'
per build directory overridden from command line to 'my360'
file name overridden from command line to 'nandflash.bin'
------ parsing user ini at '.\my360\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0xe6 bytes in memory
loading cpukey.txt from .\my360\cpukey.txt
CPU Key set to: 0xBD3A3F63142E20CAEB746E233AF4939F
setting 1blkey from ini: 0xDD88AD0C9ED669E7B56794FB68563EFA
1BL Key set to: 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
Using nonandmu option (ini file)
Using patchsmc option (ini file)
------ Checking .\my360\nanddump.bin ------
Loading NAND dump...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 0x05 Pairing: 0x8c714e
CF slot 1 decrypted ok LDV 0x04 Pairing: 0x8c714e
setting LDV from image to 5
setting pairing data from image to 0x8c714e
MobileB.dat found at page 0x7530, size 2048 (0x800) bytes
MobileC.dat found at page 0x4e0, size 512 (0x200) bytes
MobileD.dat found at page 0x3c40, size 2048 (0x800) bytes
MobileE.dat found at page 0x3c94, size 2048 (0x800) bytes
------ parsing ini at '.\13604\filelist.ini' ------
ini version 13604
ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
found (2) 'cb_bnone.bin' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_13604.bin' crc: 0x639a4cd7
found (6) 'cg_13604.bin' crc: 0x7e9f5364
ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0xdaed8bc7
found (2) 'bootanim.xex' crc: 0x8a7ab1b4
found (3) 'createprofile.xex' crc: 0xe19ca8c4
found (4) 'dash.xex' crc: 0xecdaf6c0
found (5) 'deviceselector.xex' crc: 0xaa4579d1
found (6) 'gamerprofile.xex' crc: 0xebc5fec3
found (7) 'hud.xex' crc: 0xe2410ee1
found (8) 'huduiskin.xex' crc: 0x390eac39
found (9) 'mfgbootlauncher.xex' crc: 0xf3637ed9
found (10) 'minimediaplayer.xex' crc: 0x23d28bb8
found (11) 'nomni.xexp' crc: 0xed7cd3f5
found (12) 'nomnifwk.xexp' crc: 0x2c6fd7e8
found (13) 'nomnifwm.xexp' crc: 0xaa978831
found (14) 'signin.xex' crc: 0xf7436a62
found (15) 'updater.xex' crc: 0xd0cd6753
found (16) 'vk.xex' crc: 0x65f4eec0
found (17) 'xam.xex' crc: 0x2a74ee0f
found (18) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (19) 'xenonclatin.xttp' crc: 0x7a507ad1
found (20) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (21) 'xenonjklatin.xttp' crc: 0x945b7092
found (22) 'ximecore.xex' crc: 0xccb87938
found (23) 'ximedic.xex' crc: 0x1d992bfb
found (24) 'ximedic.xexp' crc: 0x47a55af9
found (25) 'launch.xex' crc: 0x00000000
found (26) '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: nandflash.bin
Writing initial header to flash image
------ Loading bootloaders and required security files ------
reading .\my360\smc.bin failed, using smc.bin from nand dump
reading .\my360\kv.bin failed, using kv.bin from nand dump
reading .\13604\cb_6750.bin (0x9a40 bytes) (crc32: 0xf7afa8cc ini: 0xf7afa8cc)
reading .\13604\cd_8453.bin (0x5780 bytes) (crc32: 0x25e0acd0 ini: 0x25e0acd0)
reading .\13604\ce_1888.bin (0x5606a b pad 0x56070 b) (crc32: 0xff9b60df ini: 0xff9b60df)
reading .\my360\xell-gggggg.bin (0x40000 bytes)
reading .\13604\cf_13604.bin (0x4450 bytes) (crc32: 0x639a4cd7 ini: 0x639a4cd7)
reading .\13604\cg_13604.bin (0x659e0 bytes) (crc32: 0x7e9f5364 ini: 0x7e9f5364)
reading .\13604\bin\patches_fat.bin (0x6dc bytes)
reading .\my360\smc_config.bin failed, using smc_config.bin from nand dump
-------------------
checking smc_config
-------------------
extracting config
------------------
SMC config info:
------------------
Target temps: Cpu:  80ّC Gpu:  75ّC Edram:  77ّC
Max temps   : Cpu:  95ّC Gpu:  90ّC Edram:  92ّC
Cpu Fan     : (auto)
Gpu Fan     : (auto)
MAC Address : 00:25:ae:25:84:cb
AVRegion    : 0x00000300 (PAL50)
GameRegion  : 0x02fe (NTSC/EU)
DVDRegion   : 2
resetKey    : XAUD
---------------------
Checking ini for smc config data patches
smc was not patched
---------------------
done!
------ Encrypting and finalizing bootloaders ------
SMC checksum: 5b3aed00
clean SMC found, type: Jasper 2.3
patching clean smc, type: Jasper 2.3 offset: 0x12ba
clean SMC hacked successfully
done!
------ Adding bootloaders to flash image ------
adding smc.bin to 0x00001000 len 0x3000
adding kv.bin to 0x00004000 len 0x4000
adding cb_6750.bin to 0x00008000 len 0x9a40
adding cb_bnone.bin to 0x00011a40 len 0x0
adding cd_8453.bin to 0x00011a40 len 0x5a40
adding ce_1888.bin to 0x00017480 len 0x56070
adding xell-gggggg.bin to 0x00070000 len 0x40000
adding cf_13604.bin to 0x000b0000 len 0x4450
adding cg_13604.bin to 0x000b4450 len 0x659e0
adding patches_fat.bin to 0x000c0010 len 0x3e8
Fixing up FS table...done!
Writing CG patch slot overflow data to sysupdate.xexp1...done!
------ adding 26 firmware files ------
reading .\13604\aac.xexp (0x4800 bytes) (crc32: 0xdaed8bc7 ini: 0xdaed8bc7)
reading .\13604\bootanim.xex (0x55000 bytes) (crc32: 0x8a7ab1b4 ini: 0x8a7ab1b4)
reading .\13604\createprofile.xex (0xc000 bytes) (crc32: 0xe19ca8c4 ini: 0xe19ca8c4)
reading .\13604\dash.xex (0x5e7000 bytes) (crc32: 0xecdaf6c0 ini: 0xecdaf6c0)
reading .\13604\deviceselector.xex (0x9000 bytes) (crc32: 0xaa4579d1 ini: 0xaa4579d1)
reading .\13604\gamerprofile.xex (0x1a000 bytes) (crc32: 0xebc5fec3 ini: 0xebc5fec3)
reading .\13604\hud.xex (0x1f000 bytes) (crc32: 0xe2410ee1 ini: 0xe2410ee1)
reading .\13604\huduiskin.xex (0x11000 bytes) (crc32: 0x390eac39 ini: 0x390eac39)
reading .\13604\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0xf3637ed9 ini: 0xf3637ed9)
reading .\13604\minimediaplayer.xex (0xc000 bytes) (crc32: 0x23d28bb8 ini: 0x23d28bb8)
reading .\13604\nomni.xexp (0xd000 bytes) (crc32: 0xed7cd3f5 ini: 0xed7cd3f5)
reading .\13604\nomnifwk.xexp (0x2000 bytes) (crc32: 0x2c6fd7e8 ini: 0x2c6fd7e8)
reading .\13604\nomnifwm.xexp (0x5000 bytes) (crc32: 0xaa978831 ini: 0xaa978831)
reading .\13604\signin.xex (0x12000 bytes) (crc32: 0xf7436a62 ini: 0xf7436a62)
reading .\13604\updater.xex (0x8000 bytes) (crc32: 0xd0cd6753 ini: 0xd0cd6753)
reading .\13604\vk.xex (0x9000 bytes) (crc32: 0x65f4eec0 ini: 0x65f4eec0)
reading .\13604\xam.xex (0x218000 bytes) (crc32: 0x2a74ee0f ini: 0x2a74ee0f)
reading .\13604\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
reading .\13604\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
reading .\13604\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
reading .\13604\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
reading .\13604\ximecore.xex (0x15000 bytes) (crc32: 0xccb87938 ini: 0xccb87938)
reading .\13604\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
reading .\13604\ximedic.xexp (0x2800 bytes) (crc32: 0x47a55af9 ini: 0x47a55af9)
reading .\13604\launch.xex (0x9000 bytes)
reading .\13604\lhelper.xex (0x6000 bytes)
------ adding 5 security files ------
reading .\my360\crl.bin (0x9e0 bytes)
writing as crl.bin to flash
reading .\my360\dae.bin (0xad30 bytes)
writing as dae.bin to flash
reading .\my360\extended.bin (0x4000 bytes)
writing as extended.bin to flash
***** could not read fcrt.bin, skipping *****
reading .\my360\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
MobileD.dat was found in dump, 0x800 bytes, adding type 0x33
MobileE.dat was found in dump, 0x800 bytes, adding type 0x34
------ adding smc_config.bin ------
------ 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 'nandflash.bin' to disk...done!
nandflash.bin written OK
---------------------------------------------------------------
nandflash.bin glitch image built, info:
---------------------------------------------------------------
console  : jasper
NAND size: 16MiB
CPU Key  : BD3A3F63142E20CAEB746E233AF4939F
1BL Key  : DD88AD0C9ED669E7B56794FB68563EFA
CF LDV   : 5
---------------------------------------------------------------
    ggBuild Finished. Have a nice day.
---------------------------------------------------------------
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
how do i find what is damaged?
i said before everything was good and i try several cap but freezing didnt fix but console booted and finally when i test 683 cap again system didnt boot.(i dont remember but maybe i used a cap when console was power on)
whit this in mind what is damaged?
 

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
how do i find what is damaged?
i said before everything was good and i try several cap but freezing didnt fix but console booted and finally when i test 683 cap again system didnt boot.(i dont remember but maybe i used a cap when console was power on)
whit this in mind what is damaged?
Can you please confirm that you have removed CR and wires completely, AND have flashed your original nand back...!

What exactly happens now when you boot up?

Do you get red rings?
 

x23are

Senior Member
Nov 4, 2011
145
0
krj
yes.0022.(but when xell and freeboot booted the orig nand got 0022)