WKF / WASP 1.2 recovery iso

ViperGC/Qoob/etc
Post Reply
User avatar
megalomaniac
Posts: 2480
Joined: Sun Aug 21, 2011 5:33 am
Location: Drunk in Texas
Contact:

WKF / WASP 1.2 recovery iso

Post by megalomaniac » Mon Apr 20, 2015 1:55 am

Q. whats the difference between 1.2 update.iso and the 1.2 recovery.iso?
A. nothing........(almost nothing)




WKF/WASP released several update.isos, v1.1, v1.2, v1.3, v1.4, v1.5
All updates were written onto SD card with WBFS manager and selected from the WKF menu to begin the update process.

in the event there may have been any possible firmware corruption, the 1.2 recovery.iso was released to put the WKF back into a known working condition. The recovery.iso required special instruction to write the info as raw data. This allowed the WKF/WASP to immediately boot into flash recovery.



Getting the recovery iso onto an SD card may be challenging for people not use to working within a command prompt. This recovery.iso has only been known to function properly with following the instruction provided since attempts to write data with imgburn or other utilities have previously been reported to fail.

spoiler not important, just shown for reference:
here is a quick glimps into the command line requirements for getting the recovery iso onto the SD card
Spoiler
Show
-----------------------------------------------------
Instructions for adding the .iso image to the SD card
-----------------------------------------------------

1) From the command line, identify your SD card device by typing:

Linux: `cat /proc/partitions'
(use the device name without a partition number;
ie: '/dev/sdc' and not '/dev/sdc1')

MaxOSX: `diskutil list'
(use the device name without a partition number;
ie: '/dev/disk1' and not '/dev/disk1s1')

MS Windows: `dd --list'
(use the device with 'Partition0' appended to ensure
correct operation in MS Windows;
ie: '\\?\Device\Harddisk1\Partition0' and not '\\?\Device\Harddisk1\')

2) Once you are sure which device is your SD card, you can type the

following command. BE VERY CAREFUL HERE:

dd if=wkf_recover_1_2.iso of=<your device> bs=1M

Here are some examples of what you may type:

LINUX, with /dev/sdc as your device:
dd if=wkf_recover_1_2.iso of=/dev/sdc bs=1M

MAC OSX, with /dev/disk1 as your device:
dd if=wkf_recover_1_2.iso of=/dev/disk1 bs=1M

MS WINDOWS, with \\?\Device\Harddisk1\Partition0 as your device:
dd if=wkf_recover_1_2.iso of=\\?\Device\Harddisk1\Partition0 bs=1M

3) After the process has finished, the update is ready to apply to Wiikey Fusion.
For those not comfortable with commandline or those who have tried and failed to get the recovery.iso written onto an SD card, all attempts may have been made in vain. There is (almost) no difference between the 1.2 update.iso and the 1.2 recovery.iso



Open up 1.2 recovery.iso with any hex editor. This is a dol file used to flash WKF/WASP. The dol contains 884,736 bytes
now open up 1.2 update.iso with any hex editor. Look at address 0010:0000 - 001D:7FFF
you will find this data to be exactly the same. The exact same 884,736 bytes.



so what does this mean?
Lets use an iso9660 homebrew DVDs for example:

a homebrew DVD contains the typical El Torito Specification, boot image (gbi.hdr), and boot.dol
the 1.2 update.iso is nothing more than these 3 requirements with the boot.dol file located at 0010:0000.
the 1.2 recovery.iso is the boot.dol used in the 1.2 update.iso..



Since the flash data contained in the 1.2 recovery.iso provides nothing more than the 1.2 update.iso, then very plain and simple: every firmware update is a "recovery"...
....by these terms even flashing swiss as firmware is considered an update/recovery...
emu_kidid wrote: beer is like WD40 for megalomaniac's brain, gets the gears moving
>>> BadAssConsoles.com <<<

Image Image Image
Post Reply