RGH Falcon wont boot to xell

jmiko58

Full Member
Dec 2, 2011
35
0
Hey, today i just got a Falcon mobo from a customer who "Attempted" the RGH...

So here's my problem,
-He lost his orig nand dump (not sure how people do this lol)
-He tore the CPU_PLL_BYPASS, so i did the same alt method that i have done on four other consoles that worked perfect for them.
-Console will not boot at all, and worst part is i have no origanal nand dump to start over with or cpu key to build a new one with

Where should i start guys? this is the first console out of the huge amount that ive RGH and jtagged thats like this...hope the pics are okay, let me know if you need more or better ones!

The console tries to glitch, fans make there sound, cool runner flashes every 6 seconds, i've tried hdmi, vga, and component, dvd drive plugged in and unplugged, so now im 90% sure its the nand thats the problem, the kid tried to build in multibuilder...

Here's some pics,
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Whilst I don't think the issue is soldering, without the NAND to prove it either way you could be in for a long slog.

If you didn't have the original NAND, where did the ECC come from?

Try ensuring the CPU_PLL_BYPASS wire runs along the length of the heatsinks. Any repairs I've done using the topside point have needed this to be the case.
 

jmiko58

Full Member
Dec 2, 2011
35
0
The ecc was apparently created by jrunner by the kid that gave me the console, i just emailed him asking for more info on what happened and his story was that he dumped the nand on a pc that had deep freeze installed and he accidentally shut it off without thinking lol, so ya im pretty sure that the ecc exists because if i try to create another with jrunner it gives me the "could not create ecc" error but who knows, and the CPU_PLL_BYPASS wire was across the heat sinks but i just though id give this a try when it didn't glitch that way
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
It still might be a CPU_PLL_BYPASS wiring issue. I fix the trace from the via itself on the underside then solder it topside. The wire you have running from bottom to top may be picking up interference.
 

jmiko58

Full Member
Dec 2, 2011
35
0
nothing still...does exact same thing still
Also just for the heck of it i just tried a new coolrunner, re-soldering every point on the board and now im out of idea's because without the orig nand dump it just seems impossible to diagnose other possible problems
heres the pics if my small repair...
 
Last edited:

jmiko58

Full Member
Dec 2, 2011
35
0
Woooooohooooo!!
Look at this pic lol...

Looks like my young customer soldered to the wrong point! im not sure how i missed that but w/e

Thanks for all the support Martin! :D
 

jmiko58

Full Member
Dec 2, 2011
35
0
well, just ran into another problem!
So i've been seaching for hours but im having trouble creating my new glitch nand from the dump that i made after finally getting the console to boot to xell, heres my log


---------------------------------------------------------------
xeBuild v1.01.421
---------------------------------------------------------------
building glitch image
data directory overridden from command line to 'xeBuild\14699'
per build directory overridden from command line to 'xeBuild\data'
file name overridden from command line to 'C:\J-Runner\066416582207\nandflash.bin'

------ parsing user ini at '.\xeBuild\data\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x150 bytes in memory
loading cpukey.txt from C:\J-Runner\xeBuild\.\xeBuild\data\cpukey.txt
CPU Key set to: 0x6E134B2D936E3A008F7F40F96E60389A
setting 1blkey from ini: 0xDD88AD0C9ED669E7B56794FB68563EFA
1BL Key set to: 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
xex Key set to: 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)
Using patchsmc option (ini file)

------ parsing ini at '.\xeBuild\14699\_glitch.ini' ------
ini version 14699

ini: label [falconbl] found
found (1) 'cb_5771.bin' crc: 0x859140f0
found (2) 'none' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_14699.bin' crc: 0x6fb4d90e
found (6) 'cg_14699.bin' crc: 0xbccc9fe1

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
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 ------

output name overridden to: C:\J-Runner\066416582207\nandflash.bin


------ Checking C:\J-Runner\xeBuild\.\xeBuild\data\nanddump.bin ------
Loading NAND dump (0x28ee70 bytes)...done!
Detecting NAND controller type from dump data...
NAND dump is from a small block machine
NAND dump uses big block controller
parsing dump into user and spare...
block 0x4f was remapped to block 0x50, entering remap instance 1
block 0x0 was remapped to block 0x51, entering remap instance 2
block 0x0 was remapped to block 0x52, entering remap instance 3
block 0x0 was remapped to block 0x53, entering remap instance 4
block 0x0 was remapped to block 0x54, entering remap instance 5
block 0x0 was remapped to block 0x55, entering remap instance 6
block 0x0 was remapped to block 0x56, entering remap instance 7
block 0x0 was remapped to block 0x57, entering remap instance 8
block 0x0 was remapped to block 0x58, entering remap instance 9
block 0x0 was remapped to block 0x59, entering remap instance 10
block 0x0 was remapped to block 0x5a, entering remap instance 11
block 0x0 was remapped to block 0x5b, entering remap instance 12
block 0x0 was remapped to block 0x5c, entering remap instance 13
block 0x0 was remapped to block 0x5d, entering remap instance 14
block 0x0 was remapped to block 0x5e, entering remap instance 15
block 0x0 was remapped to block 0x5f, entering remap instance 16
block 0x0 was remapped to block 0x60, entering remap instance 17
block 0x0 was remapped to block 0x61, entering remap instance 18
block 0x0 was remapped to block 0x62, entering remap instance 19
block 0x0 was remapped to block 0x63, entering remap instance 20
block 0x0 was remapped to block 0x64, entering remap instance 21
block 0x0 was remapped to block 0x65, entering remap instance 22
block 0x0 was remapped to block 0x66, entering remap instance 23
block 0x0 was remapped to block 0x67, entering remap instance 24
block 0x0 was remapped to block 0x68, entering remap instance 25
block 0x0 was remapped to block 0x69, entering remap instance 26
block 0x0 was remapped to block 0x6a, entering remap instance 27
block 0x0 was remapped to block 0x6b, entering remap instance 28
block 0x0 was remapped to block 0x6c, entering remap instance 29
block 0x0 was remapped to block 0x6d, entering remap instance 30
block 0x0 was remapped to block 0x6e, entering remap instance 31
block 0x0 was remapped to block 0x6f, entering remap instance 32
MAX REMAPS of 32 exceeded, remapping disabled and image rejected as faulty!
Writing initial header to flash image

------ Loading bootloaders and required security files ------


**** could not read smc.bin (-1) ****

******* ERROR: critical bootloader files are missing, cannot proceed!



***** FATAL BUILD ERROR: -1 unable to complete NAND image

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


Detecting NAND controller type from dump data...
NAND dump is from a small block machine
NAND dump uses big block controller

Is that my problem?
 
Last edited:

TilVl

VIP Member
May 11, 2011
1,383
0
Going to need a donor and leave it a rgh box. Or if you have a valid kv you can inject it into a donor nand.

Sent from my SGH-T839 using Tapatalk
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
No idea what you've done here. I'm assuming J-Runner wasn't used at the start.

You will need a donor NAND and then build from there, but I think you knew that already.
 

jmiko58

Full Member
Dec 2, 2011
35
0
Ya the kid said he used Multi builder... Well thanks for all the help guys! :) just finished making my donor NAND now all is good! Console boots and runs flawless,

man it's getting annoying, this is the 3rd console this week that someone has brought to me after an "attempted rgh" but whatever I love repairing them haha


---
I am here: http://tapatalk.com/map.php?1snpll