I purchased two RACHEL-Plus boxes in December 2015. The second one is in Tanzania. I have to bring mine up-to-date in order to swap out with the one in TZ which will come back to me and I’ll bring that up-to-date when it arrives.
Jonathan hand-crafted some fixes on mine, but because I don’t want to impose on him again to hand-craft the fixes on the second unit when it comes back, I felt it necessary to use the Recovery image on mine and simply use the Recovery image on the TZ box when I get it. Apparently, the December 2015 box doesn’t have sqlite on it: Add or Update Content - RACHEL-Plus 2017 Software Release
Any modules would only be the ones that were default in December 2015. There was no module management software back then.
My assumption from the top message in this thread was that a “bricked” box would be made whole by using the Recovery image. So I thought regardless of the state of the system, even patched as accomplished by Jonathan, all I simply had to do was use the Recovery process on my box, ship it to TZ and then do it again on the TZ box that comes back.
The process you folks have pulled together is very straightforward and easy to follow.
- I followed the instructions at: http://rachel.golearn.us/wiki/mdwiki.html#!rachel-usb-recovery.md (and noted that the indicator light timings were quite different)
- default method as downloaded:
method="1" # 1=Recovery (DEFAULT), 2=Imager, 3=Format
- OSX Sierra:
sudo dd if=/Users/admin/t/RACHEL_Recovery_USB_1-2-16_v9.2.0_20170420.img of=/dev/rdisk2 bs=1m
- from my Terminal history I noted that it matched:
~/t $ md5 RACHEL_Recovery_USB_1-2-16_v9.2.0_20170420.img MD5 (RACHEL_Recovery_USB_1-2-16_v9.2.0_20170420.img) = ab5634dd94676ea88357efc60eef900a ~/t
Thank you for all your time with this, Sam. I’m confident it will help other users who have old boxes or “bricked” boxes if the Recovery process accommodates the most number of situations.
. . . . . Ken