Originally Posted by shadows6969
PM’d you the link, hopefully we can get them running again.
Thanks Shadows6969! This was an interesting journey and my advice to others new to Wink Relay recovery is just to keep going. Sooner or later the pieces fall together. For those that have a problem with /device/edison.zip errors, here's what I did:
Unscrew the back cover off the Relay
Soldered in a four pin right angle header to the PCB. (from the back this would be the lower right corner)
Used a Piriform serial TTL to USB adapter. The ends plug right into the pins on the board for easy connect/disconnect.
Leave the bottom pin open for now. At some point you may need to connect the red wire (+) for power. If used, this will power the Relay from your USB port but won't power wifi.
Next is the white wire (tx), then the green wire (rx), and the black wire(-) should be on top.
Carefully put the back cover on (with the wires connected, coming out of the right side) but only press down on the left side enough to make a good connection. (if you press too hard, the right side could pinch/cut the wires)
I used a cut off power cable and wire nuts to connect it to the Relay power supply. Much easier than fussing with it mounted.
Connect the Relay power supply to the far left position (don't plug it into the wall outlet yet)
Plug USB into computer you'll be using. Driver should self install (at least it did for me on Windows 10)
Download a copy of the ADB program for Android and unpack into a folder
Download "KingoRoot.apk" and "KingoUser.apk" and copy to same folder as ADB (Note - I've come to believe that "KingoUser.apk" for Super User access was not needed. I've included it here since it was part of the process I used.)
Download "edison.zip" and copy to same folder as ADB
Download and install "PUTTY" terminal program
Run PUTTY program. Change settings to use serial (mine was COM8, yours may be different) with 115200 baud.
Plug in Relay power supply
In a moment you should see a lot of text display in the PUTTY screen. Let this boot up process run it's course. It will frequently pause and start up again. Just wait a minute or two for it to settle down.
In the PUTTY screen, enter :
am start -n com.android.launcher/com.android.launcher2.Launcher
This will bring up a system screen on the Relay. Press the little squares icon at the bottom of the screen. This will bring up Settings.
Now go into Wifi and set up to your home network. Back in PUTTY there is an Android command that will give you the IP address, but you should see the number show up in the scrolling messages. If not it may be easier to just go to your router and look it up.
Go to the ADP folder on your computer and enter ADB Connect yourIPaddress (my command was "ADB Connect 192.168.1.210") If all goes well you should get a "connected" message back with the IP and port number (5555).
(at this point PUTTY is no longer needed)
Enter ADP push KingoRoot.apk /data/local/tmp
ADP push KingoUser.apk /data/local/tmp (If you're using this)
Now enter "ADP shell" to open up the shell environment
Enter "cd /data/local/tmp"
Enter "adb install KingoRoot.apk" (look at the PUTTY screen - you should see quite a few messages scroll by as it's installed)
If you're loading the superuser APK enter "adb install KingoUser.apk" (again, I believe this is unnecessary, but it doesn't hurt anything to install it)
Now go to the Relay and find the APPS screen. You should see two new icons - one for KingRoot and the other for KingUser (if installed). Run KingRoot. You'll see a circle show progress and a percentage number. Mine stuck at 90%, so I ended up going through the whole start up process again to get back to where I could run it again. Second time went through fine. You'll get a message saying root was successful.
Note - in all the rebooting, it should remember your WIFI info, so using PUTTY may not be required.
NOW you can get to the heart of the matter. Close out any ADB session you have. (possibly not necessary, but it's what I did).
Enter "ADB connect yourIPaddress" (you should see the connection message or one saying you're already connected)
Enter "ADB root"
Enter "ADB mount -o remount,rw /device"
Enter "ADB push edison.zip /device" (this takes a bit, but you see a progress indicator)
Press the reset button and hold the top switch in to bring up the system menu. I used the lower switch to select the last option (reset to factory image) and let it run. Instead of getting that "unable to verify edison.zip" error, you should see it load back to the factory default and go through the normal prompts.
Forgive me if there are typos or omissions, but as you can see it is a journey with many steps. It took hours of web searching and relying on the kindness of strangers to get to this point! Feel free to update with what worked for you.