RGH Jasper 16mb E71

[thebomber]

Hello guys, this is one weird jasper i came through

read the nand twice same bad block gives the following error, anyway wrote xell, bamm booted, got cpu key bulit the img and ready to flash with xell to remap, everything fine, turned console boot animation then baam e71:facepalm:, wrote it with the nandx, bam e71:eek2:,

wrote back the original, and switched off the coolrunner works:crazy:, read the nand again incase something was wrong , same bad block, and boots xell normally, but dash e71.

btw, it boots xell normally without any issue

trying to bulid the 14719 glitch img

this is the log


===================================================
Tuesday, May 08, 2012 3:16:54 AM
J-Runner v0.2 Beta (273) Started

Checking Files
Finished Checking Files
Downloaded *xeBuild/14719/_glitch.ini
Finished Checking Files
Initializing Nand..
Nand Initialization Finished
Cheking for bad blocks...
Done
Load Files Initiliazation Finished
14719
Started Creation of the 14719 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.02.477
---------------------------------------------------------------
building glitch image
***** WARNING: naddump.bin has a mixed controller LBA at block 0x323 (raw offset 0xcf0600), block ignored
this is likely caused by previously using jaspersb on a jasper type console!
---------------------------------------------------------------
C:\Users\Max\Desktop\Xbox arcade\008900494507\nandflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper
NAND size: 16MiB
Build : Glitch
Xell : power on console with console eject button
CPU Key : 0E0B21B7B17DBF6A6077150C2DA5920B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : FE5C58EF80D760A091F2A4ED64F9D016
CF LDV : 3
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
press <enter> to quit...
Saved to C:\Users\Max\Desktop\Xbox arcade\008900494507
Image is Ready
Arm Version: 3
Flash Config: 0x00023010
Writing Nand
nandflash.bin
Error: 202 writing block 117
Done!

---------- Post added at 18:30 ---------- Previous post was at 18:26 ----------

solved the problem, xnandhealer detected it, as small black jasper

went to jrunner and choose 16mb big block jasper, and said what the hell, and created an image and wrote it,

gave me the same error when buliding,

but console boots

and thats all i want

 

[hersheys247]

solved the problem, xnandhealer detected it, as small black jasper

went to jrunner and choose 16mb big block jasper, and said what the hell, and created an image and wrote it,

gave me the same error when buliding,

but console boots

and thats all i want

So lets see what you can learn from experience,

J-Runner is awsome


If i helped you in anyway, please press the THANKS and REP button

Sent from my brain tumor causing device using Tapatalk

 

[thebomber]

i use both actually, never had this issue before

 

[tingedace]

00023010 is a small block jasper so Xnandhealer is correct.

However, did you notice this in your log...

***** WARNING: naddump.bin has a mixed controller LBA at block 0x323 (raw offset 0xcf0600), block ignored
this is likely caused by previously using jaspersb on a jasper type console!

 

[Martin C]

0x00023010 is a BB Jasper (same as Trinity).
0x01198010 is SB Jasper as it's the same flash controller as Xenons, Zephyrs and Falcons.

 

[tingedace]

I’m afraid I’m going to have to disagree there Martin. Trinity is small block.
*
Here’s what I have:
*
16 MB Xenon/Zephyr/Falcon (01198010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
16 MB Jasper / Trinity (00023010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
16 MB Jasper (00023020 or 00023010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
256 MB Jasper (008A3020), block size 0x21000 bytes (132 KBytes, 135168 bytes)
512 MB Jasper (00AA3020), block size 0x21000 bytes (132 KBytes, 135168 bytes)
*

 

[Fisticuffs]

FlashConfig - System Types

01198010 - Xenon, Zephyr, Opus, Falcon, (Jasper 16mb small block)
00023010 - (Jasper 16mb Big Block) / (Trinity)
008A3020 - Jasper 256mb
00AA3020 - Jasper 512mb
00043000 - Corona 16mb
C0462002 - Corona 4GB (Phison)

Original Thread →→ http://www.team-xecuter.com/forums/showthread.php?t=55355

 

[thebomber]

there are 2 16mb jaspers, either small or big block
and also 2 big blocks jasper 256/512

i seriously dont know how a 16mb has 2, i always choose it as small block, but this is the first time i encounter it,

 

[tingedace]

I'd heard about this rare NAND but I've never seen one.
Would you mind uploading it so I could analyse it?

Thanks!

 

[Martin C]

I’m afraid I’m going to have to disagree there Martin. Trinity is small block.
*
Here’s what I have:
*
16 MB Xenon/Zephyr/Falcon (01198010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
16 MB Jasper / Trinity (00023010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
16 MB Jasper (00023020 or 00023010), block size 0x4200 bytes (16 KBytes, 16896 bytes)
256 MB Jasper (008A3020), block size 0x21000 bytes (132 KBytes, 135168 bytes)
512 MB Jasper (00AA3020), block size 0x21000 bytes (132 KBytes, 135168 bytes)
*

To echo what thebomber says, we're talking controllers, not NAND sizes.

The Jasper 16 SB has a flashconfig of 0x01198010 which is a small block controller with a small block NAND.

The Jasper 16 BB has a flashconfig of 0x00023010 and has a big block controller with a small block NAND.


http://forums.xbox-scene.com/index.php?showtopic=741981

 

[tingedace]

Thanks for pointing out the subtle difference there.

Question though. When do we need to care about controller type? It seems like nandpro will abstract that.

Isn't it always the NAND block size that we care about and that needs to be entered as a parameter to image building apps?

Cheers

 

[Martin C]

I believe it has to do with bad block remapping.

OP - can you upload a copy of the NAND for us to take a look?

 

[tingedace]

Ah ok. So you think in the case of a small block NAND with big block controller, where we have a bad small (0x4200) block, we'd need to remap the 8 small blocks of the effective big block it's contained in?

 

[Martin C]

I'm not sure TBH - I've only seen a handful of 16MB SB Jaspers and none had bad blocks.

I'll be better prepared once I see one with remapped blocks

 

[thebomber]

will upload it for you martin right now

---------- Post added at 18:55 ---------- Previous post was at 18:50 ----------

http://www.mediafire.com/?bq5cub4tzi53bb5

 

[joshyeo]

glad you solved the problem and got your jasper up and running