Jump to content
RealModScene

BlueSn00w

Members
  • Content Count

    86
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by BlueSn00w


  1. That'd be somewhat normal, as you're effectively resetting the hardware while it's trying to do it's thing... i never actually used a MTX SPI Flasher for this fix myself, i only used NAND-X (and a Olimex whatever it was, the hardware it's originally made with before NAND-X was created) which work faster then MTX SPI Flasher, it's possible that MTX SPI Flasher is too slow to handle it... not sure... i'm not going to try that theory either as i don't want to mess up a console just to try it...

    Well im stuck here i dont know what 2 do and even when im not pwr cycleing it its still doing bulk error


  2. That message don't matter, it's compatible despite complaining about it... just try it... see if it works...

    It might be a hardware issue tho seeing as you're getting flashconfig 0x0000001 there? are you sure you connected the MTX Flasher correctly? (you didn't flip the pinheader by accident?) it could also be that the soldering got torn inside of the console on one or more wire...

    its not the wires and the flasher is pluged in correctly

    That message don't matter, it's compatible despite complaining about it... just try it... see if it works...

    It might be a hardware issue tho seeing as you're getting flashconfig 0x0000001 there? are you sure you connected the MTX Flasher correctly? (you didn't flip the pinheader by accident?) it could also be that the soldering got torn inside of the console on one or more wire...

    Its also spiting out usb bulk read errors -166

  3. Yeah, you didn't do what i told you to either so... there's that...

    Open notepad and type this in:

    nandpro usb: -e16 0 1runme.bat

    Save this in a file named "runme.bat" next, run the batch script, this should make it automatically run itself over and over and run NANDPro over and over, i would also recommend using NANDPro 2.0b for this and not 3.0a (2.0b is compatible with newer ARM firmwares while 3.0a isn't backwards compatible and 2.0b works with corona motherboards aswell)

    Once you have the script running, you simply unplug and plug the power cord into the console a few times, eventually you'll see it successfully erasing the first block, at this point you stop it using Ctrl + C and just continue like normal (it will now work in JRunner again), it's a timing thing so just try it for a bit (if you spend more then 30 minutes it's probably not going to work)

    Nope :(http://prntscr.com/d8lv7b

    It's a Trinity. What's your OS system ?

    Windows 7 Pro with a msi z97 pcmate

    Yeah, you didn't do what i told you to either so... there's that...

    Open notepad and type this in:

    nandpro usb: -e16 0 1runme.bat

    Save this in a file named "runme.bat" next, run the batch script, this should make it automatically run itself over and over and run NANDPro over and over, i would also recommend using NANDPro 2.0b for this and not 3.0a (2.0b is compatible with newer ARM firmwares while 3.0a isn't backwards compatible and 2.0b works with corona motherboards aswell)

    Once you have the script running, you simply unplug and plug the power cord into the console a few times, eventually you'll see it successfully erasing the first block, at this point you stop it using Ctrl + C and just continue like normal (it will now work in JRunner again), it's a timing thing so just try it for a bit (if you spend more then 30 minutes it's probably not going to work)

    Sorry just saw the thing about nandpro v3 and i cant find a dl for it tho xboxscene is down :p

  4. It's a bad smc, you need to run an erase using something like nandpro and have it do that until it fixes itself (power cycle until it starts erasing the nand) this will fix the issue

    Sent from my SM-G903F

    Ok i wil try that when i get home :D thx

    It's a bad smc, you need to run an erase using something like nandpro and have it do that until it fixes itself (power cycle until it starts erasing the nand) this will fix the issue

    Sent from my SM-G903F

    http://prntscr.com/d8lprb No luck :p just get an error
×
×
  • Create New...