Update Firmware on RACHEL-Plus 1.0 (WRTD-303N Model)

Support RACHEL-Plus 1.0 (2015 - 2016)
1

**verify that you are using the 1.0 device – on the back it will have a label with the model number: WRTD-303N

assuming you’ve got the 1.0 hardware, download the recovery image here:

http://rachelfriends.org/downloads/public_ftp/other/CAP1_RACHEL_Recovery_USB_1.2.1.img.zip

next you’ll need to unzip it and write it to a USB with something like win32diskimager:

shut down your RACHEL-Plus completely, insert the USB, restart

Wait at least 8 minutes until the lights on top are lit solid (depending on the speed of your USB stick it could be much longer)

power off, remove the USB, restart

wait at least 5 minutes for the new software to load and restart itself

After that you should have an updated RACHEL-Plus with updated firmware and all your previous content remaining. Those are the two things I’d love to have you check – make sure the content is working as before (ka-lite, wikipedia, etc.) and make sure that you did get the new version (look in the admin page under “version” and you should see “RACHEL Installer v1.2.1”.

3

Good Morning, I just has some follow up questions so I can proceed with my project.

How was testing completed to verify that the Firmware was the point of fault and that this issue is corrected?

How confident are you/your agency in the firmware fix?

Are you confident the devices can be used in a fashion with the current battery and new firmware in place; that we can use them in a fashion that does not require the battery to be plugged in 24/7. Our goal is to use them in a mobile cart set up that will require them to be unplugged frequently mitigated over charging issues.

Are you guys still keeping a watch on these issues or are you continuing to run tests?

Thank you for your time on this matter.

4

I have updated my WRTD-303N Rachel as directed. Rachel Installer now 1.2.0 and K A Lite module is 0.17.0 for system software. Kalite module is showing version en-kalite 2016.20. K A lite is not working as before. Several of the exercises are not loading completely. The videos seem to all load normally. Is there a way to update or reload just the K A Lite module. Also am getting an admin message to update the language

5

The link given for .img file seems broken

6

Apologies, link is here: http://rachelfriends.org/downloads/public_ftp/other/CAP1_RACHEL_Recovery_USB_1.2.1.img.zip

1 Like
7

I have the said device. I tried the update using CAP1_RACHEL_Recovery_USB_1.2.1 as I couldnt locate CAP1_RACHEL_Recovery_USB_1.2.0.img file on the web (I did before the link was corrected.)

Followed all the instructions and the process got completed successfully. After the restart the device no longer works as expected.

  1. I cannot connect via LAN
  2. If I connect wireless I cannot access the homepage (192.168.88.1) but I can access 192.168.88.1:8080 and 8090 respectively
  3. To my surprise it is now reporting to be a WAPD-235N

What DO I DO?

9

@bsanford121 - I just sent you an email. If you can connect your device to the internet and send me the device ID (listed under the hardware tab on the RACHEL admin page) I would like to take a look and see what happened.

10

Hi Gurta, sorry for the problems you ran into. Just to start at the beginning, have you tried rebooting the machine and/or running the update process again?

The next step would be to reformat the device (also done with the USB) but then you would have to re-download the content. What kind of internet connection are you using?

11

I just finished creating a new bootable USB from CAP1_RACHEL_Recovery_USB_1.2.1.img. I tried updating the firmware on one of my 6 CAPs and it now thinks it’s a model WAPD-237N. I can not connect to the homepage via either the WAN or the LAN. It actually wiped out the LAN IP address, but it did add the new file schema (see below). I can also connect to 192.168.88.1:8080 or :8090. Any ideas?
login as: root
root@192.168.88.1’s password:
root@WAPD-237N-Server:~# sgdisk -p /dev/sda
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 211BC930-0D41-4DE6-9AC0-E7396A326B1B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 6293503 3.0 GiB 8300 preloaded
2 6293504 41945087 17.0 GiB 8300 uploaded
3 41945088 976771086 445.8 GiB 8300 RACHEL
root@WAPD-237N-Server:~# ifconfig
eth0 Link encap:Ethernet HWaddr 1c:49:7b:56:cb:8d
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:87 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13068 (13.0 KB) TX bytes:4788 (4.7 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:33216 errors:0 dropped:0 overruns:0 frame:0
TX packets:33216 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2027693 (2.0 MB) TX bytes:2027693 (2.0 MB)

wlan0 Link encap:Ethernet HWaddr 1c:49:7b:56:0d:3a
inet addr:192.168.88.1 Bcast:192.168.88.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5113 errors:0 dropped:0 overruns:0 frame:0
TX packets:634 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1119313 (1.1 MB) TX bytes:113750 (113.7 KB)
Interrupt:16 Base address:0x8000

root@WAPD-237N-Server:~#

12

I had a similar scenario with my device. I may be wrong, but something is not right with the image file or it is not meant for a WRTD device. I dunno

I didnt find any easier way out, so I had to do a fresh install

13

Answering your questions:

We worked with manufacturer Gemtek to identify the cause of the fault. Their determination was that the battery was being kept at too high a charge level when continuously plugged in. The firmware update rewrites the battery charger instructions to keep the battery at a slightly lower charge level that is safe for 24/7 operation.

In your case, where the device is regularly unplugged, there should not be a problem even with the old firmware. The problem was specifically related to devices that were plugged in 24/7 for months at a time.

We are definitely keeping a watch on the issue and welcome user feedback. We have several devices here that are plugged in 24/7 as well. If we find any new problems we will let people know.

14

For some reason the firmware update does change the reported model number at the command line. This was how the firmware was delivered to us by the manufacturer. Sorry for any confusion there - but the devices are still distinct (one is 32 bit, one 64 bit, with different underlying operating systems).

I haven’t been able to reproduce the problem where the device has no homepage – is it possible for you to send me the update.log file that would be in the USB after updating? It will hopefully give me some insight into what is going wrong.

15

Any chance you can send me the update.log file that would be on the recovery USB after you’ve done your update?

16

No. I tried to upload it, but you only allow .jpg, .jpeg, .png, and .gif. I renamed it .jpg but then it said that the image was corrupt. Do you have an email address?

17

Actually it may be too late. I finally reformatted the disk & reinstalled everything.
Here’s the file.

Export GPIO 84…
Export GPIO 85…
Export GPIO 87…

[+] Running update.sh in FORMAT mode (method=3)

[+] Call partition update script (overwriting emmc with new versions)

[*] Copying original rootfs partitions to eMMC.

[*] Search partition image from dir /boot/efi
[+] Done.

[*] Copy EFI System Partition.
.tar: ./EFI/ubuntu/boot.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
…tar: ./EFI/ubuntu/grubia32.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/ubuntu/shimx64.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/ubuntu/grubx64.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/ubuntu/MokManager.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/ubuntu/grub.cfg: Cannot change ownership to uid 0, gid 46: Operation not permitted
.tar: ./EFI/ubuntu/bootia32.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/ubuntu: Cannot change ownership to uid 0, gid 46: Operation not permitted
.tar: ./EFI/boot/bootia32.efi: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI/boot: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./EFI: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: ./NvVars: Cannot change ownership to uid 0, gid 46: Operation not permitted
tar: .: Cannot change ownership to uid 0, gid 46: Operation not permitted
Total bytes read: 59822080 (58MiB, 13MiB/s)
tar: Exiting with failure status due to previous errors
[+] Done.

[*] Copy Linux boot partition.
…Total bytes read: 153384960 (147MiB, 9.6MiB/s)
[+] Done.

[*] Copy rootfs partition.
mke2fs 1.42 (29-Nov-2011)
Discarding device blocks: 4096/1418997 528384/14189971052672/1418997 done
Filesystem label=ec_root
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
354816 inodes, 1418997 blocks
70949 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1455423488
44 block groups
32768 blocks per group, 32768 fragments per group
8064 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: 0/44 1/44 2/44 3/44 4/44 5/44 6/44 7/44 8/44 9/4410/4411/4412/4413/4414/4415/4416/4417/4418/4419/4420/4421/4422/4423/4424/4425/4426/4427/4428/4429/4430/4431/4432/4433/4434/4435/4436/4437/4438/4439/4440/4441/4442/4443/44 done
Writing inode tables: 0/44 1/44 2/44 3/44 4/44 5/44 6/44 7/44 8/44 9/4410/4411/4412/4413/4414/4415/4416/4417/4418/4419/4420/4421/4422/4423/4424/4425/4426/4427/4428/4429/4430/4431/4432/4433/4434/4435/4436/4437/4438/4439/4440/4441/4442/4443/44 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/44 1/44 2/44 3/44 4/44 5/44 6/44 7/44 8/44 9/4410/4411/4412/4413/4414/4415/4416/4417/4418/4419/4420/4421/4422/4423/4424/4425/4426/4427/4428/4429/4430/4431/4432/4433/4434/4435/4436/4437/4438/4439/4440/4441/4442/4443/44 done

…Total bytes read: 4113592320 (3.9GiB, 9.4MiB/s)
[+] Done.

[+] Call init content script (arg:1 - repartition and reformat)

[*] Checking for root permissions.
[+] Yeah…you are root, continuing.

[*] Checking for parameter 1 [/dev/sda] and 2 [1].
[+] Parameter 1 passed: /dev/sda
[+] Parameter 2 passed: 1

[*] Running create_disk_image function.

[*] Starting function: create_disk_image.

[*] Create GPT parition table.
[+] Done.

[*] Create preloaded content partition.
The operation has completed successfully.
[+] Done.

[*] Create teacher partition.
The operation has completed successfully.
[+] Done.

[*] Create RACHEL partition.
The operation has completed successfully.
[+] Done.

[*] The partition table is as follows:
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 905D1061-1998-43A5-9AA2-6BEF67BE62F7
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 6293503 3.0 GiB 8300 preloaded
2 6293504 41945087 17.0 GiB 8300 uploaded
3 41945088 976771086 445.8 GiB 8300 RACHEL

[*] Running format_disk function.

[*] Formatting ‘preloaded’ partition.
[+] Done.

[*] Formatting ‘uploaded’ partition.
[+] Done.

[*] Formatting ‘RACHEL’ partition.
[+] Done.

[+] Formatting complete

[*] The partition table after format is as follows:
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 905D1061-1998-43A5-9AA2-6BEF67BE62F7
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 6293503 3.0 GiB 8300 preloaded
2 6293504 41945087 17.0 GiB 8300 uploaded
3 41945088 976771086 445.8 GiB 8300 RACHEL
[*] Mounting /dev/mmcblk0p4 (root partition)

[+] Copying autoinstall files to /tmp/861/root/rachel-scripts/files
[*] Mounting /dev/sda3 (RACHEL partition)

[+] Adding kacontent symlink /media/RACHEL

Change status >>>>>>>>>>>>>>>
OK
Export GPIO 85…
Export GPIO 86…
Export GPIO 84…
<<<<<<<<<<<<<< Update Over <<<<<<<<<<<<<<<<

18

Thanks for the log, but yeah, that looks like the successful re-formatting. I’m guessing that you now have a blank but working RACHEL?

Getting the content back takes a long time downloading but should be straightforward at this point - go to the install tab of the admin panel and select modules manually, or you can click the “advanced” button on the right side of the install page and choose “full” from the .modules dropdown.

Let me know if you run into any problems there.

19

page not found. can you resend firmware again pliz.
I need help on Login/password after reset on my Rachel plus 1.0

20

Hello @KENYAN_GAMING_CHANNE

The last firmware recovery available for the RACHEL-Plus V1.0 is at the following link

CAP1_RACHEL_Recovery_USB_1.2.1.img.zip

James

21

Can you help me with login/password after reset?

22

You can try the default login/pass of root/123lkj.