Rooting Toon (or boxx)
Moderators: marcelr, TheHogNL, Toonz
Re: Rooting Toon (or boxx)
It means that the function of pin 12 is unknown. You shouldn't connect anything to it. A standard null modem is a three-wire connection, GND, TxD and RxD, so connecting these should suffice.
Re: Rooting Toon (or boxx)
Ok that very clear to me but where does the 3.3V fit in this storymarcelr wrote:It means that the function of pin 12 is unknown. You shouldn't connect anything to it. A standard null modem is a three-wire connection, GND, TxD and RxD, so connecting these should suffice.
Code: Select all
serial port (3.3V logic levels, ttymxc0, 115200 baud, 8N1):
Re: Rooting Toon (or boxx)
Toon is a 3.3V device. 5V connections are likely to fry the hardware.
-
- Member
- Posts: 153
- Joined: Thu Oct 03, 2013 7:53 pm
Re: Rooting Toon (or boxx)
@gielie,
i assume you're using some kind of USB to TTL device (as described in the rooting manual) Or maybe and ESP8266
If that's the case you don't need the 3.3v connection. Just connect the three wires as described.
Check your comport (device management> ports) look for serial port and write down the "number" (E.g Com1 or Com3 or Com5, you get the idea)
Fire up Putty (or other preferred terminal client) with the described settings and boot Toon. (Settings: ComX (Where X is the "number") 115200 baud, 8N1):
If you see readable data then you're ok. If you see nothing or gibberish (unreadable) check your connections and settings.
i assume you're using some kind of USB to TTL device (as described in the rooting manual) Or maybe and ESP8266
If that's the case you don't need the 3.3v connection. Just connect the three wires as described.
Check your comport (device management> ports) look for serial port and write down the "number" (E.g Com1 or Com3 or Com5, you get the idea)
Fire up Putty (or other preferred terminal client) with the described settings and boot Toon. (Settings: ComX (Where X is the "number") 115200 baud, 8N1):
If you see readable data then you're ok. If you see nothing or gibberish (unreadable) check your connections and settings.
Re: Rooting Toon (or boxx)
@marcelr @Ierlandfan
Thanks for the help.
Yes I have a usb to TTL but my W10 laptop doesn’t recognize the cable, try to figure this out this weekend.
I already opened up my Tonn and it looks simple, I have good experience with putty so if the usb cable works I will manage.
I’ll report back when it’s done.
Thanks for the help.
Yes I have a usb to TTL but my W10 laptop doesn’t recognize the cable, try to figure this out this weekend.
I already opened up my Tonn and it looks simple, I have good experience with putty so if the usb cable works I will manage.
I’ll report back when it’s done.
Re: Rooting Toon (or boxx)
Many of those usb to TTL-cables are cheap chinese versions with a copied Prolific pl2303 chip. Recent drivers (from Microsoft auto update) block these variants. To make use of them you have to search for the older ones. Exact version depends, good luck.
Re: Rooting Toon (or boxx)
That's why I recommend the FTDI-based interfaces. If you want to use the prolific chipset-based stuff, download the drivers directly from prolific, and you may get your stuff to work, although it's still a challenge. The drivers that are shipped with windows (who needs that OS anyway?) are notoriously crippled.lsiepel wrote:Many of those usb to TTL-cables are cheap chinese versions with a copied Prolific pl2303 chip. Recent drivers (from Microsoft auto update) block these variants. To make use of them you have to search for the older ones. Exact version depends, good luck.
Re: Rooting Toon (or boxx)
True, I bought one for 1 euro, I measured the v and this was just right.lsiepel wrote:Many of those usb to TTL-cables are cheap chinese versions with a copied Prolific pl2303 chip. Recent drivers (from Microsoft auto update) block these variants. To make use of them you have to search for the older ones. Exact version depends, good luck.
Today I rooted my Toon with succes, the Toon App Store is already running.
Thank to all the guys who made this possible.
Re: Rooting Toon (or boxx)
Hi all,
Got myself a nice Toon (2nd hand), and updated it to the latest version 4.9.23 with the official Toon software.
Then I followed the guide on domoticaforum.eu/viewtopic.php?f=87& ... mp;t=11235 and found U-Boot 2010.09-R6 (Mar 14 2012 - 11:15:10) in my Toon. That was an easy entrance
After modifying inittab and passwd I resetted the device, expecting a shell, but all I see is this:
The message "eneco-001-xxxxxx login:" never appears.
Going back again to U-boot and dropping to /bin/sh and trying manually results in:
What is this 'applet' and why is it not found?
What is exactly going on here?
Got myself a nice Toon (2nd hand), and updated it to the latest version 4.9.23 with the official Toon software.
Then I followed the guide on domoticaforum.eu/viewtopic.php?f=87& ... mp;t=11235 and found U-Boot 2010.09-R6 (Mar 14 2012 - 11:15:10) in my Toon. That was an easy entrance

After modifying inittab and passwd I resetted the device, expecting a shell, but all I see is this:
Code: Select all
HCBv2 apps started via runlevels, performing 'addstartables && reload && init 5 or 5'.
HCBv2 adding: comm eventmgr kpi pwrusage scsync smartplug thermstat usermsg weather bxtproxy config log rrd watchdog hue p1 zwave lighttpd.
HCBv2 startables unchanged, not writing /etc/inittab.
getty: applet not found
getty: applet not found
getty: applet not found
getty: applet not found
getty: applet not found
getty: applet not found
getty: applet not found
INIT: Id "gett" respawning too fast: disabled for 5 minutes
Going back again to U-boot and dropping to /bin/sh and trying manually results in:
Code: Select all
/sbin/getty -L 115200 ttymxc0 vt102
getty: applet not found
What is exactly going on here?
-
- Member
- Posts: 153
- Joined: Thu Oct 03, 2013 7:53 pm
Re: Rooting Toon (or boxx)
Let's check some basics:
Since you modified inittab and paswd so I assume you know how to reach single mode
Try on the commandline and see whether "getty" exist.
Should say:
If it exist it's probably some error in /etc/inittab/
The line in /etc/inittab looks like this
#Not default stuff
gett:235:respawn:/sbin/getty -L 115200 ttymxc0 vt102
Let's start from there.
Since you modified inittab and paswd so I assume you know how to reach single mode
Try
Code: Select all
ls -la /sbin |grep gett
Should say:
Code: Select all
lrwxrwxrwx 1 root root 14 Aug 29 2012 getty -> ../bin/busybox
The line in /etc/inittab looks like this
#Not default stuff
gett:235:respawn:/sbin/getty -L 115200 ttymxc0 vt102
Let's start from there.
Last edited by Ierlandfan on Sat Nov 11, 2017 10:59 pm, edited 1 time in total.
Re: Rooting Toon (or boxx)
I checked some basics and have some more information:
The relevant line is in place:
My complete /etc/inittab in a gist:
gist.github.com/Rubyan/dee691c6affbb213 ... le-inittab
Could it be that I updated to Toon software version 4.9.23 before rooting? This version is only 2 days old as can be read on the toon forum forum.toon.nl/software-updates-26/softw ... ie-4-9-871
Code: Select all
/ # ls -la /sbin|grep gett
lrwxrwxrwx 1 root root 14 Aug 29 2012 getty -> ../bin/busybox
/ #
Code: Select all
# HCBv2 static stuff
#ovpn:235:respawn:/usr/sbin/openvpn --config /etc/openvpn/vpn.conf --verb 0 >/dev/null 2>&1
qtqt:245:respawn:/usr/bin/startqt >/dev/null 2>&1
# add serial console access: (added, MR!):
gett:235:respawn:/sbin/getty -L 115200 ttymxc0 vt102
gist.github.com/Rubyan/dee691c6affbb213 ... le-inittab
Could it be that I updated to Toon software version 4.9.23 before rooting? This version is only 2 days old as can be read on the toon forum forum.toon.nl/software-updates-26/softw ... ie-4-9-871
Re: Rooting Toon (or boxx)
Highly unlikely.
busybox hasn't changed since version 1.9.10 or thereabouts.
What happens when you try this:
busybox hasn't changed since version 1.9.10 or thereabouts.
What happens when you try this:
Code: Select all
/bin/busybox getty -L 115200 ttymxc0 vt102
Re: Rooting Toon (or boxx)
The following happens:What happens when you try this:
Code: Select all
/bin/busybox getty -L 115200 ttymxc0 vt102
Code: Select all
/ # /bin/busybox getty -L 115200 ttymxc0 vt102
getty: applet not found
/ #
Code: Select all
/ # /bin/busybox getty
getty: applet not found
Code: Select all
/ # /bin/busybox ls
HCBv2 configured lib proc sbin usr
bin dev linuxrc qmf sys var
boot etc mnt root tmp
/ #
The way busybox work is it looks at it argv[0] parameter which is the name of the symlink; vim in your case. It then does a look-up and it has no applet named vim. You can make a script that does busybox vi and symlink that script to vim. The syntax busybox applet, is another way to select the program; but why not just type vi. An applet in busybox parlance is the emulated program. busybox has base infrastructure (command line parsing, etc) with a main driver file that is an applet emulating the normal program. –
Nice. I didn't know this. All the common programs are symlinks.
So is my busybox incomplete somehow? Lets see the details:
Code: Select all
/ # ls -liah /bin/busybox
125032 -rwsr-xr-x 1 root root 679.2K Oct 3 12:22 /bin/busybox
Some more googling shows you can list all busybox applets with the plain busybox command:
Code: Select all
/etc # busybox
BusyBox v1.27.2 (2017-10-03 14:20:01 CEST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.
Usage: busybox [function [arguments]...]
or: busybox --list
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.
Currently defined functions:
[, [[, acpid, ar, ash, awk, base64, basename, beep, blkid, blockdev,
bootchartd, bunzip2, bzcat, cat, chattr, chgrp, chmod, chown, chroot,
chvt, clear, cmp, conspy, cp, cpio, cut, date, dc, dd, deallocvt, df,
dhcprelay, diff, dirname, dmesg, dnsdomainname, du, dumpkmap, echo,
egrep, env, expr, factor, fallocate, false, fatattr, fbset, fbsplash,
fdisk, fgconsole, fgrep, find, flock, free, freeramdisk, fsck,
fsfreeze, fstrim, fsync, ftpd, fuser, getopt, grep, groups, gunzip,
gzip, halt, head, hexdump, hostname, hwclock, i2cdetect, i2cdump,
i2cget, i2cset, id, ifconfig, ifdown, ifplugd, ifup, init, ionice,
iostat, ip, ipneigh, kill, killall, klogd, less, link, linux32,
linux64, linuxrc, ln, loadfont, loadkmap, logger, logname, logread,
losetup, ls, lsof, lspci, lsscsi, lsusb, lzcat, lzma, lzop, makedevs,
md5sum, mdev, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2, mkfs.vfat,
mknod, mkpasswd, mktemp, modinfo, more, mount, mpstat, mv, nbd-client,
netstat, nice, nl, nohup, nproc, nslookup, ntpd, od, openvt, partprobe,
paste, pidof, ping, ping6, pivot_root, pmap, poweroff, powertop,
printf, ps, pstree, pwd, pwdx, rdate, rdev, readlink, readprofile,
realpath, reboot, renice, reset, rev, rm, rmdir, route, run-parts,
scriptreplay, sed, seq, setconsole, setfont, setpriv, setserial, sh,
sha256sum, sha3sum, sha512sum, showkey, shred, shuf, sleep, smemcap,
sort, ssl_client, start-stop-daemon, strings, stty, svc, swapoff,
swapon, switch_root, sync, sysctl, syslogd, tail, tar, tee, test, time,
timeout, top, touch, tr, traceroute, traceroute6, true, truncate, tty,
tunctl, ubiattach, ubidetach, ubimkvol, ubirename, ubirmvol, ubirsvol,
ubiupdatevol, udhcpc, uevent, umount, uname, uniq, unlink, unshare,
unxz, unzip, uptime, usleep, vi, volname, watch, wc, which, whoami,
whois, xargs, xxd, xz, xzcat, yes, zcat
Re: Rooting Toon (or boxx)
I'm running:
Every time I log in I get
I simply ignore it 
Code: Select all
BusyBox v1.18.3 (2011-08-26 19:32:05 CEST)
Code: Select all
uname -a
Linux Toon 2.6.36-R10-h27 #1 PREEMPT Tue Oct 25 20:03:05 CEST 2016 armv5tejl GNU/Linux
Every time I log in I get
Code: Select all
sh: xauth: not found

Re: Rooting Toon (or boxx)
Hmmm ... apparently, in 4.9.23, busybox got updated.
and getty removed from the busybox features.
I just downloaded the latest busybox code, will try and build one with getty on board.
Will also take a look at the latest installation, see if a rollback can be done easily. (the first installation of busybox is built routinely in the oe-tree).
and getty removed from the busybox features.
I just downloaded the latest busybox code, will try and build one with getty on board.
Will also take a look at the latest installation, see if a rollback can be done easily. (the first installation of busybox is built routinely in the oe-tree).