xboxscene.org forums

Author Topic: Bad Block On 40 Can't Boot Xell Jasper 512  (Read 61 times)

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« on: July 07, 2010, 09:01:00 AM »

hello all,

im trying to flash this BB Jasper 512 but it had a bad block 202 on 40 ive tried to move blocks around but I always get no response from the ring of light and I get a black screen, ive had similar problems with other BB jaspers but usualy I just remap the blocks but with doing this I need to flash on XELL tp get the CPU key I flash on jasper_6723_hack_for_256mb_512mb.bin but it also gets a write error and fails to boot XELL on eject.

ive tried remapping blocks for the Xell image and also the freeboot and XBR images but I always get the same result. I cant get the CPU key and I cant seem to boot anything.

is there any other remapping methods I can try?

thanks

Zellcorp

Logged

deadair4ever

  • Archived User
  • Newbie
  • *
  • Posts: 38
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #1 on: July 07, 2010, 09:07:00 AM »

Sorry to say...  a bad block in the first 50 = no joy.
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #2 on: July 07, 2010, 09:10:00 AM »

Ouch well good to have confirmation thanks.

Logged

ydgmms

  • Archived User
  • Sr. Member
  • *
  • Posts: 446
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #3 on: July 07, 2010, 11:17:00 AM »

are you sure that a bad block in the 1st 50 means no joy?

I thought you could still get it to work, it just takes a lot more work.

http://docs.google.com/View?id=dnfmv5h_186pp2zddm

read the part thats in RED.

furthermore:

I have a Badblock between blocks 0x000 and 0x050, and can’t boot into Xell (free60 version).

              First of all ensure your using the free60 version of Xell.  Next you will need to backup the location of the remapped BadBlocks like so (Remeber your first Badblock always goes to 0xFF8, and each following Badblock gets remapped to the spare):

              nandpro lpt: -r256 backupFF8.bin FF8 8

Assuming your first Badblock was at 0x010 followed by seven more errors, you will need to remap the free60 Xell data that was intended to be stored in that block. Like this.

              nandpro xell.bin: -r16 xell10.bin 10 8

              nandpro lpt: -w16 xell10.bin FF8 8

This post has been edited by ydgmms: Jul 7 2010, 06:18 PM
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #4 on: July 08, 2010, 05:03:00 AM »

done it like 5 times ive remapped over and over just wont boot xell

This post has been edited by Zellcorp: Jul 8 2010, 12:03 PM
Logged

Fornow

  • Archived User
  • Newbie
  • *
  • Posts: 35
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #5 on: July 08, 2010, 05:07:00 AM »

Might be worth a try, but no guarantee. Not quite sure how or why I did this now. But erase the nand and put xellous in higher. As I remember it booted into xellous with the main power button.
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #6 on: July 08, 2010, 05:31:00 AM »

ahh no I fixed this problem after some desperation I decided to try flashing on a image of freeboot from another box I jtagged before and low and behold xell boots now!!!

So if you can get a donor freeboot nand and flash it on seem it works ok

enjoy!!
Logged

TingedAce

  • Archived User
  • Full Member
  • *
  • Posts: 101
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #7 on: July 08, 2010, 03:53:00 PM »

I agree with ydgmms and his commands to move the bad block to 0xFF8 (other than you need to use -r512/-w512)
However, I think that you also need to mark block 40-47 on your xell as bad, otherwise the system won't know to use 0xFF8 instead. At least that's my assumption, otherwise why do they get marked as bad in the first place?

So assuming your original nand is saved as orig.bin do:

// Backup FF8
nandpro lpt: -r512 backupFF8.bin FF8 8

// Move the Xell block to FF8
nandpro xell.bin: -r512 xell40.bin 40 8
nandpro lpt: -w512 xell40.bin FF8 8

// Patch Xell with the bad block
nandpro orig.bin: -r512 bad.bin 40 8
nandpro xell.bin: -w512 bad.bin 40 8

then flash Xell.bin back
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #8 on: July 09, 2010, 08:02:00 AM »

Well the box is booting freeboot now this is what I did

Used a already compiled donor freeboot nand from another BB 360 to boot Xell

got CPU Key

Remapped the bad blocks on the original nand backup using a program called XNandHealer using just another backup to compare.

opened and compiled a new freeboot image with freebootoolboxmaker, fixed nand and cpu key

flashed new freeboot image with nandpro

bingo!!

hope this helps others.

special thanks to Keystroke.

This post has been edited by Zellcorp: Jul 9 2010, 03:03 PM
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #9 on: July 09, 2010, 10:16:00 AM »

LoL looks like I spoke too soon I didnt really notice til I stuck it back in the case the 360 now boots like normal then hangs at the 360 logo.

looks like its still having issues with the nand.

the box is in a state now where freeboot will flash updflash from a DVD ive tried reflashing a few freeboot images but no luck.

if anyone has any ideas would be great but i really think ive done everything I can at this point

Ive manually remapped

Ive used XBR_Flash to reflash

Ive use XNand Healer

please stop posting me guides on manual remapping ive done this like 10 times, doesnt work.

thx
Zellcorp
Logged

Zellcorp

  • Archived User
  • Newbie
  • *
  • Posts: 41
Bad Block On 40 Can't Boot Xell Jasper 512
« Reply #10 on: July 09, 2010, 12:15:00 PM »

Actually its booting ok now I just remapped the freeboot image again manually using 8 blocks and it worked.

Logged