If you don't know how a modchip works, this is my understanding. It overrides the motherboard with BIOS that are flashed on it and as quickly as that, you have a bios up and running. Normally if you have a bad flash then the chip will just frag out when you try to turn it on.
However, this chip had a wierd problem with an M8 flash where it wasn't fragging, but there was no A/V output. (blue screen and no audio while the chip was on)
This chip is a type that turns on if you hold down the power button. I saw this wierd thing that I stumbled upon by chance.
UDE2 and nkpatcer were installed, with PBL-Metoo as an app. Evox was replaced with UnleashX. PBL-Metoo was run as an app and shadowc gave way to C:\, ending up on a different version of UnleashX. The controller was used to soft reset twice. The xbox was powered off before loading finished, during the black screen before UnleashX booted up. The power button was held down a split second or two later. The chip then booted up yet got around the blue screen! It was possible to get to Evolution-X from there. The box was powered off, the chip was powered on the normal way as a test, and blue screen happened again. The UDE2/PBL/UnleashX method was tried again. The chip booted and got around blue screen mode once again. It was possible to get into Evolution-X and flash the chip from there.
It was like something was left in ram or cache that allowed that to happen. The chip was flashed the second time, but I think it could have worked infinite times. Does anyone have a theory or explanation for this thing?
Author
Topic: Was Able To Use Ude2 To Reflash A Wierd Flash (Read 46 times)