JNIOR Series 3 Forced Entry

The following post talks about entering the processor bootloader.  Entering the bootloader could have unintended consequences should the wrong commands be entered.  Proceed at your own risk.

Note, this is for a series 3 JNIOR that went out of production in 2015. You can upgrade to Series 4 JNIORs easily in most cases.

Most JNIOR3 batteries should be dead and therefore removing power to reboot should restore the default accounts. If the battery is still doing its job you can force your way in using the following:

  1. Connect USB-to-Serial cable to COM/RS-232 port.
  2. Open Terminal program of your choice (Support Tool). Serial settings are 115200 baud, 8 data bits, 1 stop bit, and No Parity. No hardware buffer control. We are hoping that the DTR line (pin 4) is wired through the cable and is asserted by default.
  3. Access the JNIOR and prove to yourself that you cannot log in. Try jnior:jnior and admin:admin.
  4. With jumper (or screwdriver) short jumper next to COM port briefly (1/2 second).
  5. Immediately hit repeated (at least 3 or so) ENTER keystrokes. The bootloader banner should appear.
  6. Enter: B 02 <ENTER>
  7. Enter: F 00 0000 0100 <ENTER>
  8. Enter: E <ENTER>
  9. The JNIOR should reboot. Note the above switches to the Block for the Heap Memory (Bank 2); Clears the first 256 bytes of the Heap damaging its structure; And, then Exits restarting the system.
  10. Note in the dialog the indication “Blast HEAP”. This restores the original /etc/passwd file with the default credentials.
  11. Eventually log in using jnior:jnior

If shorting the jumper pins or inserting the jumper briefly does not reboot the JNIOR and accept your ENTER keystrokes, then DTR is not wired or asserted.

This test was done using Putty on an Ubuntu system with an old USB-to_Serial adapter.

By | Updated On November 3, 2023 1:21 pm | No Comments | Categories: | Tags:


INTEG Process Group, inc. © 2023

Real-Time
Mon - Fri, 8am - 4pm EST
P: 724-933-9350
PureChat
Always Available
Contact Form
sales@integpg.com
support@integpg.com

@integpg
@jniordev
5544