xboxscene.org forums

Author Topic: Jtag 12611 Won't Take (stuck At 9199)  (Read 27 times)

zciou87

  • Archived User
  • Newbie
  • *
  • Posts: 5
Jtag 12611 Won't Take (stuck At 9199)
« on: November 20, 2010, 02:13:00 AM »
I followed the instructions pretty carefully and using fbuild 0.11. When I flashed it to my 360 using flash360, and boot it back up, it seems like the dash has reset, but it's still 9199. Is there any reason that the update didn't take? I've done this before (ie updated to 9199 from xbr), so this isn't my first time. But somehow I can't get it to work. Can anyone point me in the right direction?

I've tried this a couple of times, so I know it's not some dumb error in building the updflash.bin.  What possible reasons are there for this?  Is there some way that the nand is in read only mode or would not be updated properly?

Thanks!
Logged

Ketchup_Bomb

  • Archived User
  • Full Member
  • *
  • Posts: 243
Jtag 12611 Won't Take (stuck At 9199)
« Reply #1 on: November 20, 2010, 12:29:00 PM »
It's got to be something in the process of building the updflash.bin image. The NAND isn't 'read-only.'

Try building the 12611 image using Easy FreeBoot. That was the most simple and intuitive app for me.
Logged

Maximize

  • Archived User
  • Full Member
  • *
  • Posts: 176
Jtag 12611 Won't Take (stuck At 9199)
« Reply #2 on: November 20, 2010, 12:50:00 PM »
yes definitely easy freeboot you can have it done inside of ten minutes
Logged

juggahax0r

  • Archived User
  • Hero Member
  • *
  • Posts: 602
Jtag 12611 Won't Take (stuck At 9199)
« Reply #3 on: November 21, 2010, 04:41:00 AM »
QUOTE(zciou87 @ Nov 20 2010, 04:13 AM) View Post

I followed the instructions pretty carefully and using fbuild 0.11. When I flashed it to my 360 using flash360, and boot it back up, it seems like the dash has reset, but it's still 9199. Is there any reason that the update didn't take? I've done this before (ie updated to 9199 from xbr), so this isn't my first time. But somehow I can't get it to work. Can anyone point me in the right direction?

I've tried this a couple of times, so I know it's not some dumb error in building the updflash.bin.  What possible reasons are there for this?  Is there some way that the nand is in read only mode or would not be updated properly?

Thanks!


 What did you use to flash the new image on to your system? Just use flash360 if you didn't already.  The update didn't "not take" you just didn't flash a new image on to it, you didn't build the image wrong if it still boots because the only way that could have happened is if you extracted a 9199 filesystem BUT the offsets for the patches in the Kernel/HV are not that same and I also think FbBuild checks the files before it builds an image and would fail if it were missing things or had the wrong files.
 Is it possible you had another updflash.bin somewhere on your computer and you just got it mixed up with the image you built? And take the others suggestion and use Easy Freeboot or Freeboot toolbox maker.
Logged