Print

[Ranger72]

Some more info would be nice.

Are you talking about stock 9199 on a non jtaged console or are you talking about freeboot 9199 on a jtaged console?

[juggahax0r]

QUOTE(damesi @ Apr 27 2010, 05:39 PM)

It a falcon that used to have xbr3 a, and i used a software call freeboot tool box maker to make a bin file that later i updated using flash360, all worked fine for like two days now it seem to not getting power at all

 No power at all means your SMC is not right..Try building the image with iBuild using the command line , i am not sure if they have all the files for all revisions yet with freeboot toolbox maker.

[damesi]

QUOTE(juggahax0r @ Apr 27 2010, 03:03 PM)

No power at all means your SMC is not right..Try building the image with iBuild using the command line , i am not sure if they have all the files for all revisions yet with freeboot toolbox maker.

Thanks for the reply, i would like to know how to power up the xbox, cause the pc is not seeing it, i try to go back to xbr3a but nandpro cant find flash controler

[juggahax0r]

QUOTE(damesi @ Apr 27 2010, 06:16 PM)

Thanks for the reply, i would like to know how to power up the xbox, cause the pc is not seeing it, i try to go back to xbr3a but nandpro cant find flash controler

 Yea when you get the wrong SMC that will happen haha. To get Nandpro to detect your controller again , type your command in nandpro have your 360 unplugged but have the plug inserted in the hole so you can plug it in very fast , hit enter on nandpro and plug in your 360 as close to at the same time as humanly possible, with a little luck and a few tries possibly you should have nandpro reading or writing your NAND. I have had to do that so i know it works , if you can't get it working you might want to search around or ask someone which pins too short on the NAND. Basically what the SMC is responsible for is controlling the system powerup , ROL board , NaNd , power off and many more things , when you have an incorrect SMC file in your NaNd it cannot power up because it is from the wrong MoBo revision. I would take a break from it today after you get xbr3 running again , and try building freeBOOT from scratch again tomorrow , it really is worth getting freeBOOT working as xbr will be obsolete now that freeBOOT doesn't need 2 NaNds.

Edit: If you are doing the trick i mentioned above you should be running a write command to your NaNd with your xbr image , and don't be surprised if it powers up with it still connected either , mine did when i had that problem , when it got too 0x3FF my system powered itself on.

[damesi]

QUOTE(juggahax0r @ Apr 27 2010, 03:32 PM)

Yea when you get the wrong SMC that will happen haha. To get Nandpro to detect your controller again , type your command in nandpro have your 360 unplugged but have the plug inserted in the hole so you can plug it in very fast , hit enter on nandpro and plug in your 360 as close to at the same time as humanly possible, with a little luck and a few tries possibly you should have nandpro reading or writing your NAND. I have had to do that so i know it works , if you can't get it working you might want to search around or ask someone which pins too short on the NAND. Basically what the SMC is responsible for is controlling the system powerup , ROL board , NaNd , power off and many more things , when you have an incorrect SMC file in your NaNd it cannot power up because it is from the wrong MoBo revision. I would take a break from it today after you get xbr3 running again , and try building freeBOOT from scratch again tomorrow , it really is worth getting freeBOOT working as xbr will be obsolete now that freeBOOT doesn't need 2 NaNds.

Edit: If you are doing the trick i mentioned above you should be running a write command to your NaNd with your xbr image , and don't be surprised if it powers up with it still connected either , mine did when i had that problem , when it got too 0x3FF my system powered itself on.

Thank for the trick, worked the as soon as the second time.