The reset isn't due to any specific action of the kit itself, which simply contains the same BIN file components as other firmware files (RGN or GCD). In the flash kit, they are in their individual components, i.e. fw_all.bin (the main system software) and Ldr.bin (the boot.bin, renamed). In other words it also gives the same result as flashing any fw version as an RGN in preboot, or using a gupdate.gcd to flash a higher version. Result from any of the 3 methods being that the required version is loaded to the device.
The reset is forced because of the difference in firmware versions and it can happen the same way if a device which has a much older version is loaded with a much later. The reset is the same as one available to the user via the settings/tools menu (if the screen worked).
An even more comprehensive reset can be done by clearing the non-volatile memory but that's not available to you because the screen doesn't work and although nonvol cannot be cleared by SD command, the entire region may be erased using "ergn" command. It's highly unlikely to help you but the device is toast anyway so it won't matter if it doesn't work but understand that it may kill it too by over-stressing the chip. If it does re-enable the screen i'll be very surprised but then there may be some device functionality permanently missing anyway. If you wish to try it, remove the file "last_id bin" from the 1275 folder, open update.txt file in Notepad and change it to
ergn,41
reboot
then save the change. Ensure you have no extra spaces at the ends of the lines nor additional carriage-returns if you copy/paste that command. It you leave last_id.bin in place the flash won't start. It's ok to leave update.log though. You can either remove fw_all.bin from the root of the card or leave it there, it won't matter in this case.
Bookmarks