Need help with E66
- Thread starter Trussy
- Start date
No....Bacon said:
Do you have a samsung?
It sounds like you have a ms25 and the version strings in your firmware are ms28. This would result in E66. Do you still have your orig.bin or hacked.bin that you flashed to the drive?
Caster.
Obisouly the guy didnt know what he was doing. READ the tutorials and do it yourself or have someone who KNOWS WHAT THEY ARE DOING to fix it if you have a samsung.Trussy said:
throw your 360 in the garbage bin.. it's worth nothing anymore without the original firmware.
end liek ur spellieng is greet -_-
end liek ur spellieng is greet -_-
Nice advice jelle2503, except it's wrong.
The only really important part of the original firmware is a drive key. And since his drive was working fine before this update, that means his drive firmware already has his drive key on there. His drive is fixable.
Trussy, the drive must be reflashed using ms25 version strings. The easiest way to do that is to backup your current drive's firmware (even though it is hacked). You will need to backup the firwmare with the MS28 VIA bad-flash method. Just use the command mtkflash r /m /sata orig.bin at DOS.
Once you get a backup of that drive's firmware containing your drive key, you can put it through the "Make Xtreme Firmware" and make it report as ms25, then reflash the drive.
The only really important part of the original firmware is a drive key. And since his drive was working fine before this update, that means his drive firmware already has his drive key on there. His drive is fixable.
Trussy, the drive must be reflashed using ms25 version strings. The easiest way to do that is to backup your current drive's firmware (even though it is hacked). You will need to backup the firwmare with the MS28 VIA bad-flash method. Just use the command mtkflash r /m /sata orig.bin at DOS.
Once you get a backup of that drive's firmware containing your drive key, you can put it through the "Make Xtreme Firmware" and make it report as ms25, then reflash the drive.