GENERAL Phat Demon on jasper big block demon nand does not boot?

[sfear2ugf]

Demon nand glitches to xell but does not boot freeboot? stock works find on 16203

ill be posting photos in a bit

here the J Runner Log:

Current: DemoN
Switching to XBOX
Success
Reading Nand to C:\Documents and Settings\SFEAR\Desktop\J-Runner v02 Beta (288) Core Pack\output\nanddump1.bin
XBOX360
Hardware : Demon Phat
Firmware : 1.4
Flash ID : 0xDAEC Samsung (256MiB - Big block)
Flash Size : 0x800 blocks of 0x21000 bytes
Invalid Blocks : 0xBB 0xF6 0x120 0x3D8 0x5A2 0x65C 0x6DB 0x7D2
Reading Nand
Done!
in 5:46 min:sec


Reading Nand to C:\Documents and Settings\SFEAR\Desktop\J-Runner v02 Beta (288) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Done!
in 5:13 min:sec


Comparing...Takes a while on big nands
Bad Block ID @ 0x00BB [Offset: 0x181B000]
Bad Block ID @ 0x00F6 [Offset: 0x1FB6000]
Bad Block ID @ 0x0120 [Offset: 0x2520000]
Bad Block ID @ 0x00BB [Offset: 0x181B000]
Bad Block ID @ 0x00F6 [Offset: 0x1FB6000]
Bad Block ID @ 0x0120 [Offset: 0x2520000]
Nands are the same
Load Files Initiliazation Finished
16203
Started Creation of the 16203 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.07.561
---------------------------------------------------------------
building glitch2 image




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


---------------------------------------------------------------
C:\Documents and Settings\SFEAR\Desktop\J-Runner v02 Beta (288) Core Pack\600076284305\updflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper (big block)
NAND size : 64MiB + NAND MU area
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 600076284305
ConsoleId : 027401143710
MoboSerial: 792172B119238425
Mfg Date : 10/18/2008
CPU Key : 402xxxxxxxx2DDD9EBxxxxxxxxxxxxxxxxx
1BL Key : DD88AD0C9ED6xxxxxxxxxxxxx68563EFA
DVD Key : DBFxxxxxxxxxxx64F613CF44CExxxxxxxx
CF LDV : 6
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Documents and Settings\SFEAR\Desktop\J-Runner v02 Beta (288) Core Pack\600076284305
Image is Ready
Current: XBOX
Switching to DemoN
Success
DEMON
Hardware : Demon Phat
Firmware : 1.4
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2A 0x2B 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38
Writing Nand
Done!
in 0:34 min:sec

 

[JohnWestBear]

Says you have a. Small block demon? Is that right?

 

[DreamZ]

Are you running a big block conversion kit?
Also post some pictures

 

[Martin C]

The process for DemoN installs with bad blocks is as follows:

1. Build your RGH NAND with the 'noremap' option checked (xebuild advanced options).
2. Erase the DemoN NAND
3. Write to the DemoN with the Advanced/Write DemoN option.

 

[jsinger47]

Write a 64mb file to a 16mb NAND.....yeah that sounds right to me. Did you consider reading the big block tutorial?

In the case of a spelling error, I blame Tapatalk.

 

[Martin C]

Write a 64mb file to a 16mb NAND.....yeah that sounds right to me. Did you consider reading the big block tutorial?

In the case of a spelling error, I blame Tapatalk.

^ Yeah, that too!!

 

[madhacker83]

To be fair, the BB demon tutorial is a bit hard to find

 

[sfear2ugf]

where is this BB demon tutorial?
yes im running a big block conversion kit

 

[Krafter]

You have to create a 16M NAND for the demon.


Tapatalk misspelled it. Knot me.

 

[madhacker83]

You have to create a 16M NAND for the demon.


Tapatalk misspelled it. Knot me.

Yeah your right, but for some newbs on here a tutorial would be helpful and as stated above by a SUPER-MOD there should be a Demon BB tutorial, but i can't find it. I was looking for it to link to the OP to help him as i've never done a Demon BB yet.

 

[AllyNerd]

Load your original NAND, cpu key, press create image, select 16mb Jasper, write to demon...
as quoted from jsinger from http://team-xecuter.com/forums/show...t-Glitch-image?p=908050&viewfull=1#post908050

 

[madhacker83]

Load your original NAND, cpu key, press create image, select 16mb Jasper, write to demon...
as quoted from jsinger from http://team-xecuter.com/forums/show...t-Glitch-image?p=908050&viewfull=1#post908050

As me, you and other experienced members know its pretty straight forward, but you know the n00bs we get here cant search for sh$t. When JSinger said "Big Block Tutorial" thats what confused the OP....point blank there is not a Demon BB tutorial especially one when referring to using Demon BB on R-Jtag setups, I think it should be added to the Jrunner user guide PDF and we will stop getting these post from ppl being confused. Just my$0.02

Compared to "other" glitch chips there tutorials are the worst ever seen while TX always has the BEST detailed instructions you will ever find on the net.

 

[Martin C]

The problem is we have too many noobs attempting DemoN installs.

Ask any installer and they will tell you what size NAND is on a DemoN. Hell, you should already know since you've bought a CONVERSION kit. So building a 64MB BB image for a 16MB SB NAND is NEVER going to work.

There's a very good reason why DemoN installs are for experienced installers.

 

[sfear2ugf]

The point is that there's always going to be new people trying to do there own installs, as what you guys call noobs. I'm sure me and others are not always going to send in their console some experienced modder just because i added a 64Mb and not a 16Mb Lol. I'm Cool! ummm sorry i'll pass on that one.

Thanks for the help guys got it to work.

 

[AllyNerd]

As me, you and other experienced members know its pretty straight forward, but you know the n00bs we get here cant search for sh$t. When JSinger said "Big Block Tutorial" thats what confused the OP....point blank there is not a Demon BB tutorial especially one when referring to using Demon BB on R-Jtag setups, I think it should be added to the Jrunner user guide PDF and we will stop getting these post from ppl being confused. Just my$0.02

Compared to "other" glitch chips there tutorials are the worst ever seen while TX always has the BEST detailed instructions you will ever find on the net.

True I agree with you. You should write one up lol. @sfear2ugh glad you got it sorted. We all have to start from somewhere.

 

[TheGlow]

The problem is we have too many noobs attempting DemoN installs.

Ask any installer and they will tell you what size NAND is on a DemoN. Hell, you should already know since you've bought a CONVERSION kit. So building a 64MB BB image for a 16MB SB NAND is NEVER going to work.

There's a very good reason why DemoN installs are for experienced installers.

I had a 16mb and default Demon so I was fine.
But I always wondered, can you take a jasper with big block stock and go with a 16mb for the demon side?

 

[AllyNerd]

I had a 16mb and default Demon so I was fine.
But I always wondered, can you take a jasper with big block stock and go with a 16mb for the demon side?

:facepalm:

 

[Martin C]

The point is that there's always going to be new people trying to do there own installs, as what you guys call noobs. I'm sure me and others are not always going to send in their console some experienced modder just because i added a 64Mb and not a 16Mb Lol. I'm Cool! ummm sorry i'll pass on that one.

Thanks for the help guys got it to work.

That's your business. It doesn't negate the fact that TX warns you the DemoN is for experienced installers.

For me as a pro, I would have used basic common sense that a 64MB image will not fit on a 16MB NAND.

- - - Updated - - -

I had a 16mb and default Demon so I was fine.
But I always wondered, can you take a jasper with big block stock and go with a 16mb for the demon side?

What do you think the Jasper BB Conversion kit is for?

 

[TheGlow]

What do you think the Jasper BB Conversion kit is for?

Hence I wasn't sure, but I was under the impression for the Demon side if doing freeboot, then you had a little bit more leeway on what to get away with, unmatching dvdkeys, drives, etc.
And that the big block kit was for people who really wanted to have an internal MU on the demon side.
I figured there was a legit reason for the bigblock but since it came a little while after Demons release, and not immediately, I had a feeling it may have been optional.
I always interpreted it as more storage, not necessarily system critical files.

Like this weekend when my 2TB PC drive died. I had no problem putting a 250gb Win7 partition to a 120gb partition because the system was only really using 40gb. I thought big blocks worked something along those lines with only the 16MB being critical system data.

:facepalm:

thanks

 

[sfear2ugf]

That's your business. It doesn't negate the fact that TX warns you the DemoN is for experienced installers. For me as a pro, I would have used basic common sense that a 64MB image will not fit on a 16MB NAND.

It was a very small error i messed.