RGH My first RGH job....gone really wrong, need a donor nand and some expert wisdom..

A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
OK, having issues....
Box in question: 13599 Jasper 512MB

Dumped nand with NandPro 2.0e. As it didn't throw errors while dumping (how is this possible?), I neglected to fc /b the two. Bleh.
Used one of the dumps to create ecc file, flashed to CoolRunner.
Booted CoolRunner, have CPU Key.
Now comes the fun....

Used dump in AutoGG and 360_Multi_Builder....360MB balked at content of nand, wouldn't work. AutoGG thought it was OK, rebuilt something for me. Flashed it's output using Xell/rawflash_v4, and consistently get it saying 0x1, 0x6, 0xD blocks seem wrong. As a result, box won't boot into anything but Xell.

Here's the issues, then:
1) Can't get a decent 'stock'/donor NAND to work with. Have CPU key and (apparently crappy) dumps, each of which open and appear normal in 360 Flash Tool v097. I'd try nandpro take1.bin: kv.bin 1 1 and nandpro take1.bin: config.bin ef7 2, and inject to donor if I had one, assuming the EF7 is contained in my FFF (right?) 64MB dump.
2) If I'm rebuilding this nand from donor material using AutoGG, why am I always getting 'seem wrong' blocks at 0x1, 0x6, 0xD during Xell/rawflash_v4 flash? 1 is the keyvault, but I don't know specifically what 6 and D are...they're NOT config blocks, that's for sure.
3) 360 Flash Tool v097 says the dumps are fine, there are no bad blocks. Dumps wouldn't open if key was wrong, so I'm stumped here. Is there a 'rebuild from crap' application that can work with 64MB dumps? NandCompare-v1.3 won't work with Jaspers.

I also have dumps from Xell http interface: keyvault (unenc), fuses (LDV=5, I've checked this during various rebuilds), and 528MB (??) flashdmp.bin. This is unfortunately AFTER my first 64MB flash, so I don't expect these to be of much use.

[Previous links to files removed, problem has been solved]

Do what you will with the key, I will NOT be using it online...not even sure that flies anymore.
I'll subscribe to this thread and respond to questions/comments ASAP.
THANK YOU for any assistance!
 
Last edited:
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
Re: My first RGH job....gone really wrong, need some expert wisdom..

OK, more data...

Grabbed 512MB donor data from this link https://rapidshare.com/files/2593671790/JASPEROriginal512mb.rar , originally located in the depths of 360iso.com.

Pulled kv and config off crappy dumps:
nandpro take1.bin: -r64 kv1.bin 1 1
nandpro take2.bin: -r64 kv2.bin 1 1
nandpro take3.bin: -r64 kv3.bin 1 1

fc /b kv1.bin kv2.bin
fc /b kv2.bin kv3.bin
fc /b kv1.bin kv3.bin
no differences at any point, despite entire 64mb dumps not matching

nandpro take1.bin: -r64 config1.bin ef7 2
nandpro take2.bin: -r64 config2.bin ef7 2
nandpro take3.bin: -r64 config3.bin ef7 2

fc /b config1.bin config2.bin
fc /b config2.bin config3.bin
fc /b config1.bin config3.bin
no differences at any point, despite entire 64mb dumps not matching

Plugged kv and config to this donor listed above. Dash 13599, LDV 7. I selected pair marked 2.

nandpro donor.bin: -w64 kv2.bin 1 1
nandpro donor.bin: -w64 config2.bin ef7 2

Opened with 360 Flash Tool, no problems.

Ran this newly modified "donor.bin" through 360 Multi Builder with LDV set to 5 (matches my original crappy dumps)....

Log:

---------------------------------------------------------------
xeBuild v1.01.421
---------------------------------------------------------------
building glitch image
per build directory overridden from command line to 'my360'
data directory overridden from command line to '14719'
Using PATCHSMC option
file name overridden from command line to 'updflash.bin'

------ parsing user ini at '.\my360\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x151 bytes in memory
loading cpukey.txt from .\my360\cpukey.txt
CPU Key set to: 0xE7CF9C601E2B94F70E089723F0C2C3A7
setting 1blkey from ini: 0xDD88AD0C9ED669E7B56794FB68563EFA
1BL Key set to: 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
xex Key set to: 0x20B185A59D28FDC340583FBB0896BF91 sum: 0x800 (expects: 0x800)

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

ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
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: 0x19cece0a
found (27) 'lhelper.xex' crc: 0xeb581eb5
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) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------

output name overridden to: updflash.bin


------ Checking .\my360\nanddump.bin ------
Loading NAND dump (0x22eea0 bytes)...done!
Detecting NAND controller type from dump data...
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...


**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************

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 0x3be0000! Using if no smc config is provided.
CF slot 0 decrypted ok LDV 0x07 Pairing: 0x22f142
setting pairing data from image to 0x22f142
LDV was already set to 5
MobileB.dat found at page 0x15c00, size 2048 (0x800) bytes
MobileC.dat found at page 0x15c04, size 512 (0x200) bytes
MobileD.dat found at page 0x15c08, size 2048 (0x800) bytes
MobileE.dat found at page 0x15c0c, size 2048 (0x800) bytes
seeking security files...fsroot found at page 0x18820 raw offset 0x5e0c200
crl.bin found in sector 0x363 size 0xa00...verify failed! Discarding data.
dae.bin found in sector 0x14a size 0x7090...
******* ERROR: dae hash incorrect, could not decrypt!
verify failed! Discarding data.
extended.bin found in sector 0x1a9 size 0x4000...verify failed! Discarding data.
secdata.bin found in sector 0x160 size 0x400...verify failed! Discarding data.
Writing initial header to flash image

------ Loading bootloaders and required security files ------
reading .\my360\smc.bin failed, using smc.bin from nand dump
reset smc load address to 0x1000 size 0x3000
reading .\my360\kv.bin failed, using kv.bin from nand dump
reading .\14719\cb_6750.bin (0x9a40 bytes)
reading .\14719\cd_8453.bin (0x5780 bytes)
reading .\14719\ce_1888.bin (0x5606a b pad 0x56070 b)
reading .\my360\xell-gggggg.bin (0x40000 bytes)
reading .\14719\cf_14699.bin (0x4450 bytes)
reading .\14719\cg_14699.bin (0x67168 b pad 0x67170 b)
reading .\14719\bin\patches_fat.bin (0x6f0 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:22:48:d2:ed:1b
AVRegion : 0x00000100 (NTSC-M)
GameRegion : 0x00ff (NTSC/US)
DVDRegion : 1
resetKey : XXUD
---------------------
Checking for smc config data patches
smc config was not patched
---------------------
done!

------ Patching BLs and modifying patches ------
Patching patches...
Patching patches to use 0xd0010 as patch offset in flash
Patching patches for alt power reason
Patches patched!
Patching BLs...Done!

------ Encrypting and finalizing bootloaders ------
encoding smc.bin size 0x3000
SMC checksum: 5b3aed00
known clean SMC found, type: Jasper v4.1(2.03)
patching smc at offset: 0x12ba
SMC hacked successfully
encoding kv.bin size 0x4000
decrypted keyvault has been set for reference
encoding cb_6750.bin size 0x9a40
CB 6750 seq 0x01070050 type: 0x01 cseq: 0x07 allow: 0x0050
expected fuses:
fuseset 00: C0FFFFFFFFFFFFFF
fuseset 01: 0F0F0F0F0F0F0FF0
fuseset 02: 000000F000000000 (sequence)
fuseset 02: 0000F00000000000 (allow cseq 5)
fuseset 02: 000000F000000000 (allow cseq 7)
encoding cd_8453.bin size 0x5a60
encoding ce_1888.bin size 0x56070
encoding xell-gggggg.bin size 0x40000
encoding cf_14699.bin size 0x4450
encoding cg_14699.bin size 0x67170
encoding patches_fat.bin size 0x3e0
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 cb_6750.bin at raw offset 0x00008000 len 0x9a40 (end 0x11a40)
adding cd_8453.bin at raw offset 0x00011a40 len 0x5a60 (end 0x174a0)
adding ce_1888.bin at raw offset 0x000174a0 len 0x56070 (end 0x6d510)
adding xell-gggggg.bin at raw offset 0x00070000 len 0x40000 (end 0xb0000)
adding cf_14699.bin at raw offset 0x000b0000 len 0x4450 (end 0xb4450)
adding cg_14699.bin at raw offset 0x000b4450 len 0x67170 (end 0xd0000, rest in fs)
adding patches_fat.bin at raw offset 0x000d0010 len 0x3e0 (end 0xd03f0)
Writing CG patch slot overflow data to sysupdate.xexp1 at raw offset 0x2b80000...done!

------ adding 28 firmware files ------
reading .\14719\aac.xexp (0x14000 bytes) (crc32: 0x36790e61 ini: 0x36790e61)
adding as aac.xexp1 at raw offset 0x2bcb5c0 len 0x00014000 (end 0x02bdf5c0)
reading .\14719\bootanim.xex (0x61000 bytes) (crc32: 0x187ede71 ini: 0x187ede71)
adding as bootanim.xex at raw offset 0x2be0000 len 0x00061000 (end 0x02c41000)
reading .\14719\createprofile.xex (0xc000 bytes) (crc32: 0x81d7a946 ini: 0x81d7a946)
adding as createprofile.xex at raw offset 0x2c41000 len 0x0000c000 (end 0x02c4d000)
reading .\14719\dash.xex (0x63a000 bytes) (crc32: 0x3957764c ini: 0x3957764c)
adding as dash.xex at raw offset 0x2c50000 len 0x0063a000 (end 0x0328a000)
reading .\14719\deviceselector.xex (0x9000 bytes) (crc32: 0x6246b4c0 ini: 0x6246b4c0)
adding as deviceselector.xex at raw offset 0x328a000 len 0x00009000 (end 0x03293000)
reading .\14719\gamerprofile.xex (0x1b000 bytes) (crc32: 0xb7add96a ini: 0xb7add96a)
adding as gamerprofile.xex at raw offset 0x3295000 len 0x0001b000 (end 0x032b0000)
reading .\14719\hud.xex (0x1e000 bytes) (crc32: 0x202eb5c8 ini: 0x202eb5c8)
adding as hud.xex at raw offset 0x32b3000 len 0x0001e000 (end 0x032d1000)
reading .\14719\huduiskin.xex (0x13000 bytes) (crc32: 0x4c80fbe9 ini: 0x4c80fbe9)
adding as huduiskin.xex at raw offset 0x32d2000 len 0x00013000 (end 0x032e5000)
reading .\14719\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0x254ad664 ini: 0x254ad664)
adding as mfgbootlauncher.xex at raw offset 0x32e7000 len 0x00008000 (end 0x032ef000)
reading .\14719\minimediaplayer.xex (0xc000 bytes) (crc32: 0xd8d21cfc ini: 0xd8d21cfc)
adding as minimediaplayer.xex at raw offset 0x32f0000 len 0x0000c000 (end 0x032fc000)
reading .\14719\nomni.xexp (0xe000 bytes) (crc32: 0xbf36fdf7 ini: 0xbf36fdf7)
adding as nomni.xexp1 at raw offset 0x32fc000 len 0x0000e000 (end 0x0330a000)
reading .\14719\nomnifwk.xexp (0x2000 bytes) (crc32: 0xa837ae53 ini: 0xa837ae53)
adding as nomnifwk.xexp1 at raw offset 0x330a000 len 0x00002000 (end 0x0330c000)
reading .\14719\nomnifwm.xexp (0x5000 bytes) (crc32: 0x93246a8a ini: 0x93246a8a)
adding as nomnifwm.xexp1 at raw offset 0x330e000 len 0x00005000 (end 0x03313000)
reading .\14719\SegoeXbox-Light.xtt (0x6000 bytes) (crc32: 0x086eb344 ini: 0x086eb344)
adding as SegoeXbox-Light.xtt at raw offset 0x3315000 len 0x00006000 (end 0x0331b000)
reading .\14719\signin.xex (0x16000 bytes) (crc32: 0xecd9cab1 ini: 0xecd9cab1)
adding as signin.xex at raw offset 0x331e000 len 0x00016000 (end 0x03334000)
reading .\14719\updater.xex (0x7000 bytes) (crc32: 0x125cdb94 ini: 0x125cdb94)
adding as updater.xex at raw offset 0x3336000 len 0x00007000 (end 0x0333d000)
reading .\14719\vk.xex (0x9000 bytes) (crc32: 0x9c744d4c ini: 0x9c744d4c)
adding as vk.xex at raw offset 0x333f000 len 0x00009000 (end 0x03348000)
reading .\14719\xam.xex (0x236000 bytes) (crc32: 0x0b764b88 ini: 0x0b764b88)
adding as xam.xex at raw offset 0x3349000 len 0x00236000 (end 0x0357f000)
reading .\14719\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
adding as xenonclatin.xtt at raw offset 0x3582000 len 0x0011b000 (end 0x0369d000)
reading .\14719\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
adding as xenonclatin.xttp1 at raw offset 0x369f000 len 0x00018000 (end 0x036b7000)
reading .\14719\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
adding as xenonjklatin.xtt at raw offset 0x36b8000 len 0x001a8000 (end 0x03860000)
reading .\14719\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
adding as xenonjklatin.xttp1 at raw offset 0x3860000 len 0x00007000 (end 0x03867000)
reading .\14719\ximecore.xex (0x15000 bytes) (crc32: 0x8d45ea14 ini: 0x8d45ea14)
adding as ximecore.xex at raw offset 0x3867000 len 0x00015000 (end 0x0387c000)
reading .\14719\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
adding as ximedic.xex at raw offset 0x387d000 len 0x00090000 (end 0x0390d000)
reading .\14719\ximedic.xexp (0x2800 bytes) (crc32: 0xc90a651a ini: 0xc90a651a)
adding as ximedic.xexp1 at raw offset 0x3910000 len 0x00002800 (end 0x03912800)
reading .\14719\launch.xex (0xb000 bytes) (crc32: 0x19cece0a ini: 0x19cece0a)
adding as launch.xex at raw offset 0x3912800 len 0x0000b000 (end 0x0391d800)
reading .\14719\lhelper.xex (0x6000 bytes) (crc32: 0xeb581eb5 ini: 0xeb581eb5)
adding as lhelper.xex at raw offset 0x391f000 len 0x00006000 (end 0x03925000)
reading .\14719\launch.ini (0x294 bytes)
adding as launch.ini at raw offset 0x3926000 len 0x00000294 (end 0x03926294)

------ adding 4 security files ------
<- Processing crl.bin ->
reading .\my360\crl.bin (0xa00 bytes)
crl appears crypted, attempting to decrypt with CPU key...failed! Trying alternate key...success!
adding as crl.bin at raw offset 0x392c000 len 0x00000a00 (end 0x0392ca00)

<- Processing dae.bin ->
reading .\my360\dae.bin (0xad30 bytes)
dae appears encrypted, attempting to decrypt with CPU key...failed! Attempting to decrypt with alternate key...
success!
adding as dae.bin at raw offset 0x3930000 len 0x0000ad30 (end 0x0393ad30)

<- Processing extended.bin ->
reading .\my360\extended.bin (0x4000 bytes)
adding as extended.bin at raw offset 0x393c000 len 0x00004000 (end 0x03940000)

<- Processing secdata.bin ->
reading .\my360\secdata.bin (0x400 bytes)
adding as secdata.bin at raw offset 0x3940000 len 0x00000400 (end 0x03940400)

------ checking for Mobile*.dat ------
MobileB.dat found, adding from nanddump.bin
adding MobileB.dat as type 0x31 at raw offset 0x3960000 len 0x800 (end 0x3960800)
MobileC.dat found, adding from nanddump.bin
adding MobileC.dat as type 0x32 at raw offset 0x3960800 len 0x200 (end 0x3960a00)
MobileD.dat found, adding from nanddump.bin
adding MobileD.dat as type 0x33 at raw offset 0x3961000 len 0x800 (end 0x3961800)
MobileE.dat found, adding from nanddump.bin
adding MobileE.dat as type 0x34 at raw offset 0x3961800 len 0x800 (end 0x3962000)

------ adding smc_config.bin ------
adding smc config to offset 0x03be0000, len 0x400

------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
fixing up big block LBA numbers in spare...done!
calculating ECD bytes and assembling raw image...done!
writing file 'updflash.bin' to disk...done!
updflash.bin written OK

---------------------------------------------------------------
updflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper (big block)
NAND size: 64MiB + NAND MU area
Build : Glitch
Xell : power on console with console eject button
CPU Key : E7CF9C601E2B94F70E089723F0C2C3A7
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 677C4D9F17E9F2594EB8A8AC1A909784
CF LDV : 5
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Comments:
1) Yes, the key is in there....don't care, have fun. Just want this solved.
2) Errors looking at crl and dae. Do I need to extract these files specifically from non-working dumps? Can't say I've seen a location for these, but I suppose I can extract with 360 Flash Tool.

Soooo, I just flashed this using Xell/RawFlash, and am still getting the same errors:
block 0x1 seems bad, status 204
block 0x6 seems bad, status 210
block 0xd seems bad, status 204

Now that I'm flashing with a completely different image, it seems this is NAND related rather than IMAGE related.

I'll try flashing this with the hardware flasher and see what happens. Any comments welcomed...
 
Last edited:
N

nitram

VIP Member
Jan 10, 2012
36
0
UK
Since no one wants to help this guy and just steel his KV, I'm going to take the high ground and help.

Here try this: http://www.mediafire.com/?2bpbn6b74ssr9fk

This might not work because I don't 100% know what your CF LDV is, I just used what your dump had so hopefully it is corrent. If not just post your efuses from Xell.

Flash the nand like this,

Nandpro usb: -w64 jasper512.bin
 
  • Like
Reactions: agt_dale_
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
nitram said:
Here try this: http://www.mediafire.com/?2bpbn6b74ssr9fk

This might not work because I don't 100% know what your CF LDV is, I just used what your dump had so hopefully it is corrent. If not just post your efuses from Xell.

Flash the nand like this,

Nandpro usb: -w64 jasper512.bin
Click to expand...
Thanks for at least looking :)
1) LDV = 5, posted during hilariously large mess above
2) Isn't the command +w64, not -w64? What's the difference? I'll read about this.

afsilver said:
i think flashing with HW flasher will do the trick here, since you had no errors during dump, but they showed once you flashed with RawFlash.
Click to expand...
1) No errors during dump, but dumps don't match and won't work with 360 Multi Builder
2) Currently HW flashing....error 601 too many times to count. I'm going to be BUSY manually programming these.....bleh. [If "+" above sets some sort of hash, I'm screwed.]
 
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
Well, HW flash of course did not go well.
38 error 601 blocks, which I programmed manually.
[Yes, I understand that I've jumped off the cliff and will not be able to get a good, verified dump of this box. At this point, I've spent three days on a 20 minute job, and am willing to recycle the box....]

Now:
Box lights up
Fan sounds like it's been 12Vd...apparently Multi Builder somehow imparts this WITHOUT my consent/knowledge.
CR flashes green per normal
After about 15 minutes of this, box red lights (1, lower right) and gives 1101. This, hilariously enough, seems to be a new code.
Xell still works, shows proper CPU key, DVD key, LDV still = 5 (5 "f"s showing below two CPU key lines...), so I'm not totally screwed yet :)

We can name this code "How NOT to properly dump/flash your NAND". :frown:

BTW, I'm programming this with CR in place/fully soldered. Simply switching it from NOR to PROG, which does NOT allow the unit to have power while AC is plugged in...red light is NOT on.
------------------------------------------------------------------------------------------------------------------
More diagnostic data:
Xell shows MAC address as 002248FFFFFF
FFFFFF should be D2ED18 per 360 Flash Tool data (Tools: Edit Config)
Something is amiss with SMC data, then....

"Take 1.bin" (from first post) is showing SMC = 0.00 in 360 Flash Tool...this is NOT right. If the dump is hosed, how is 360FT even able to open it without complaining?
"Take2.bin" seems the most stable on inspection, hence me using "2" files above.
"Take3.bin" gave ONE read error, now that I think about it...I consider it unstable.

All three dumps given SMC error when opened in 360 Multi Builder.
 
Last edited:
N

nitram

VIP Member
Jan 10, 2012
36
0
UK
+ is for calulating ECC data which xebuild already does so you don't need to do it, what happened when you flashed the nand I gave you ?
 
  • Like
Reactions: agt_dale_
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
nitram said:
+ is for calulating ECC data which xebuild already does so you don't need to do it, what happened when you flashed the nand I gave you ?
Click to expand...
Didn't mention this....did NOT flash NAND you provided:
1) It was 14719....I'm deliberately trying to stay away from this, I've been using 14717. This doesn't matter though, because
2) LDV on yours was 7. Wouldn't work, as my LDV = 5. I consider this donor material, though :)
 
N

nitram

VIP Member
Jan 10, 2012
36
0
UK
The nand I made you has CF LDV 5, its called jasper512.bin.

---------------------------------------------------------------
jasper512.bin image built, info:
---------------------------------------------------------------
Console : Jasper (big block)
NAND size: 64MiB (system only)
Build : Glitch
Xell : power on console with console eject button
CPU Key : E7CF9C601E2B94F70E089723F0C2C3A7
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 677C4D9F17E9F2594EB8A8AC1A909784
CF LDV : 5
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

I could make you a 14717 if you want
 
Last edited:
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
Reviewed and confirmed. Not sure where I got 7.
Waiting for Xell to boot....will have results soon, using file you provided, flashing with Xell/RawFlash4.
-----------------------------------
PROGRESS!!!!
Flashed, TON of "seems bad": 25, 3C, 52, 8B, 8F, A9, B6, C9, DB, FF, 133, 14A, 163, 16A, 174, 17F, 183, 18D, 198, 1D3, 1E8, 1E9 [Not that any of that matters....]

Fan is quieter now. What's the switch you're using to shunt that to 'normal' speed?

Boots, makes splash screen noise, then E71 on screen. Nothing plugged in except AV cables. No wired controller, removed USB stick from front USB.

I'll look into post-flash E71 while waiting for your thoughts....
-------------------------------------
Reading http://team-xecuter.com/forums/showthread.php?t=80381&page=6
DLed XNANDHealer, my "Take2.bin" isn't showing any bad blocks, but has 205 ECC errors. Similarly, "Take1.bin" has 156, "Take3.bin" 217. No 'bad blocks' showing, though. What causes ECC errors? Soldering or dirty power?
--------------------------------------
I wonder if reattaching HW flasher and manually hitting ""seems bad": 25, 3C, 52, 8B, 8F, A9, B6, C9, DB, FF, 133, 14A, 163, 16A, 174, 17F, 183, 18D, 198, 1D3, 1E8, 1E9" from above (noting the mention of "8" as opposed to "1", but I think NandPro 2.0e does that anyway...) might produce interesting results...? I'll sit tight and wait for commentary...
 
Last edited:
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
Flashed above file, same results, same "seems bad" blocks, same E71 on screen.
Boot animation doesn't even finish...E71.

Out of curiosity, which of my dumps are you using? Looks to me like #1 (CloudCash gives you a readout on what's been downloaded...), can we try #2?

I'm going to try again with the donor NAND I got (second post)....not sure why I'm getting same blocks wrong using it.

THANK YOU for continuing assistance/poking at my methodology....will try renaming USB file to "updflash.bin" and letting Xell handle it instead of RawFlash. An interesting idea.... :)
----------------------------------------------------------
Nope, image contains "Xell Reloaded", which contains "RawFlash v4" as it's flashing mech. Same results with "updflash.bin" at root of EMPTY USB drive, then....
 
Last edited:
A

agt_dale_

Junior Member
Apr 29, 2005
11
0
CA, USA
nitram said:
Here try this: http://www.mediafire.com/?2bpbn6b74ssr9fk

Flash the nand like this,

Nandpro usb: -w64 jasper512.bin
Click to expand...
SORTED!!!!!
Helps when one's programmer is NOT on the fritz. Tore jumper connections off programmer (I use Schmartboard header pins installed to the board, then attach jumpers to my programmer. Attach ends of jumpers to newly installed header pins and away we go. http://www.schmartboard.com/index.asp?page=products_jch&id=112 ), noted one was kinda iffy.

Replaced them all, hooked back up to board, flashed above file, boots 14719.

THANKS to everyone for their time and comments, my apologies to anyone who thinks I wasted their time because of my *(&^$*(&)(* programmer. Bleh.

Having a beer ATM, Avery's "Majarahaja" to celebrate :)
 
You must log in or register to reply here.