xbox-scene.com archived forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

xbox-scene.com forum restored.  registration disabled.  thanks to xboxexpert for the db dump and netham45 for cleaning it up!

Author Topic: 351f-3cd6-1800-0703-c000-0099 Error Code  (Read 84 times)

cands

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« on: November 23, 2012, 11:04:53 AM »


Hi there

This noob would really appreciate some help. My kids have a jtagged xbox, for love nor money I could not get COD2 to work, so they pooled their money and went and bought it. Trues bob, still issues. It tells us we need to update to play, so grimaced and thought oh well no choice I suppose. Nah. Gives me error message 351F-3CD6-1800-0703-C000-0099. And now I am stumped.

Pretty please can someone take pity on this mom and tell me what to do in idiot speak.




Logged

warbeast

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« Reply #1 on: November 23, 2012, 03:12:30 PM »


Hi there

This noob would really appreciate some help. My kids have a jtagged xbox, for love nor money I could not get COD2 to work, so they pooled their money and went and bought it. Trues bob, still issues. It tells us we need to update to play, so grimaced and thought oh well no choice I suppose. Nah. Gives me error message 351F-3CD6-1800-0703-C000-0099. And now I am stumped.

Pretty please can someone take pity on this mom and tell me what to do in idiot speak.


so you had a working jtag and instead building a new jtag image for 16197 you tried to do a normal ms update from disk blink.gif ?
we need more info! has the dash updated at all? is the efuse resistor removed? are you using a flashed or spoofed drive with it?

at the end of the day if the jtag still works then you need to build a new 16197 image
i guess you didnt mod it so if you dont have a nand backup or a external programer then you will need to dump the nand with one of the homebrew nand tools made for 360 then take the cpu key from xell and use these to build a new 16197 freeboot with the newer dashlauch and flash it using the same apps
google will help you find a good tutorial for this smile.gif

if you have killed the jtag with a ms update then all you can do for now is make sure the nand and drive fw  is  stock+correct  as the update may need to flash the drive so if you have a samsung instead of a liteon that came with it then it will fail the update as it cant flash a samsungi with new liteon fw  

it does sound to me like the jtag is still ok




Edited by warbeast, 24 November 2012 - 12:13 AM.


Logged

cands

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« Reply #2 on: November 23, 2012, 03:55:23 PM »


The jtag still works thank god - they have been playing the other games as normal since, I have been trying to contact the seller for help to no avail so now I either need to try and do this myself or find someone to help.  So all those lovely numbery sounding things - how can I do it.  If you would be so kind to point me int he right direction I would be eternally grateful

so you had a working jtag and instead building a new jtag image for 16197 you tried to do a normal ms update from disk blink.gif ?
we need more info! has the dash updated at all? is the efuse resistor removed? are you using a flashed or spoofed drive with it?

at the end of the day if the jtag still works then you need to build a new 16197 image
i guess you didnt mod it so if you dont have a nand backup or a external programer then you will need to dump the nand with one of the homebrew nand tools made for 360 then take the cpu key from xell and use these to build a new 16197 freeboot with the newer dashlauch and flash it using the same apps
google will help you find a good tutorial for this smile.gif

if you have killed the jtag with a ms update then all you can do for now is make sure the nand and drive fw  is  stock+correct  as the update may need to flash the drive so if you have a samsung instead of a liteon that came with it then it will fail the update as it cant flash a samsungi with new liteon fw  

it does sound to me like the jtag is still ok






Logged

warbeast

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« Reply #3 on: November 24, 2012, 02:19:36 AM »


Ok the 1st thing you need to do is download a program from xbins that reads the 360 NAND such as 360flash
Once you have this copy it to the Xbox run the program select read NAND then ur need to copy the nanddump file it makes back to ur pc

Also while ur looking in the hdd if you use freestyledash make a note of where it is ie (hdd:/freestyle/default.xex now boot the 360 using the eject button and copy the CPU key down






Edited by warbeast, 24 November 2012 - 11:31 AM.


Logged

warbeast

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« Reply #4 on: November 24, 2012, 03:21:18 PM »


also once you have the nand backup and cpu key i would upload it for one of us here to look at then update it for you
the reason being is if you didnt mod it then you dont know what the smc wiring is without opening up the xbox
it could have had the aud_clamp fix and if you dont get this right the 360 wont boot and ur need a external programer to fix it

so i would dump the nand like i said upload the file and ask one of us here to update it then all you need to do is copy the new image to a usb drive and turn on the 360 with eject to have xell update it to the new dash

after that we can tell you the info you need incase you ever need to update it urself again




Edited by warbeast, 25 November 2012 - 12:23 AM.


Logged

johnyblackout

  • Guest
351f-3cd6-1800-0703-c000-0099 Error Code
« Reply #5 on: November 28, 2012, 05:17:52 PM »


The person who modded this for you should of included a copy of your original NAND and CPU key. Did they do this? Once you have these two items you can just load it up in J-runner, make a new NAND with the latest dash (16197). Then you just rename the new image to updflash.bin and flash by putting it onto a thumb drive (fat32), plug it into the xbox and start up xell. Xell will load and should update your NAND.




Logged
 

Page created in 0.073 seconds with 16 queries.