Rooting Toon (or boxx)

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

xinetic
Starting Member
Starting Member
Posts: 1
Joined: Tue Feb 25, 2014 11:51 pm

Re: Rooting Toon (or boxx)

Post by xinetic »

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.
Here are fixed drivers for fake Prolific pl2303 chips

https://howto.tweakblogs.net/blog/12645 ... el-usb-fix
rudolfpi
Starting Member
Starting Member
Posts: 3
Joined: Mon Mar 19, 2018 7:58 pm

Re: Rooting Toon (or boxx)

Post by rudolfpi »

Somebody did this?
https://www.quby.com/open-system
Open system
Hi, it is nice to see that you like our product so much that you want to do even more with it. You can take a look at the developer.toon.eu, that might serve you. If you really want to get root access on your display, please send an email to devsupport@toon.eu. stating your display serial number and displaycode. We will then see how we can help you rooting your display. Please note, if you decide to root your display you won’t be able to revert to the original connected product anymore.
rudolfpi
Starting Member
Starting Member
Posts: 3
Joined: Mon Mar 19, 2018 7:58 pm

Re: Rooting Toon (or boxx)

Post by rudolfpi »

So I opened bij Toon. And now?
Is there not an easy manual explaining all the steps (with pictures)?
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

No, there isn't. There's just the written manual.

You need the reading skills of a 12-year old (Dutch or English), and some tools.
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

Plus one! for a Donald Duck style of how to root a Toon. Who's in?
Member of the Toon Software Collective
michel30
Member
Member
Posts: 286
Joined: Fri Aug 25, 2017 4:42 pm

Re: Rooting Toon (or boxx)

Post by michel30 »

And if you not want to read everything than use the automatic scrip

domoticaforum.eu/viewtopic.php?f=87&amp ... mp;t=11999
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

TheHogNL wrote:Plus one! for a Donald Duck style of how to root a Toon. Who's in?
Don't let anything hold you back!
Smiggel
Member
Member
Posts: 57
Joined: Wed Apr 11, 2018 2:20 pm

Re: Rooting Toon (or boxx)

Post by Smiggel »

Hi all,

Have an issue here. I have a pi connecties go my Toon. I use my computer to SSH to my pi. I can watch the output of the toon during the boot using screen and minicom. However, when I want to loging using the pasword given in the documentation, I have a problem.

When I use screen I can simple paste my password and login. I was able to do some adjustments already too. But as the documentation says, I need minicom to send over files. When I try to login in Toon using the minicom, the system keeps booting. No matter when I paste my password. :-( For some reason I can’t seem to get in using minicom.

Is anyone else experiencing this too and how can I solve this? All help would be welcome. :-)
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

Smiggel wrote: But as the documentation says, I need minicom to send over files
You only need to send the files if you are rooting a Toon with current firmware 4.9 or higher.
Try to boot the Toon after changing the password and inittab files, see if you get normal console access. If not then and only then you need the modified busybox in the uboot shell.

The files transfer over minicom has put a lot of users in troubles so I would not recommend to use that. If you really need the modified busybox, you can also just put a UTP network kabel in the Toon (in the shell after uboot, the wifi drivers are not running) and simply install the modified busybox over the internet with

Code: Select all

get an ip address on the Toon UTP port with: udhcpc
install busybox with:  opkg install http://files.domoticaforum.eu/uploads/Toon/apps/busybox-1.27.2-r4/busybox_1.27.2-r4_qb2.ipk
Member of the Toon Software Collective
Smiggel
Member
Member
Posts: 57
Joined: Wed Apr 11, 2018 2:20 pm

Re: Rooting Toon (or boxx)

Post by Smiggel »

TheHogNL wrote:
Smiggel wrote: But as the documentation says, I need minicom to send over files
You only need to send the files if you are rooting a Toon with current firmware 4.9 or higher.
Try to boot the Toon after changing the password and inittab files, see if you get normal console access. If not then and only then you need the modified busybox in the uboot shell.

The files transfer over minicom has put a lot of users in troubles so I would not recommend to use that. If you really need the modified busybox, you can also just put a UTP network kabel in the Toon (in the shell after uboot, the wifi drivers are not running) and simply install the modified busybox over the internet with

Code: Select all

get an ip address on the Toon UTP port with: udhcpc
install busybox with:  opkg install http://files.domoticaforum.eu/uploads/Toon/apps/busybox-1.27.2-r4/busybox_1.27.2-r4_qb2.ipk
After doing the changes in the manual, and rebooting Toon, I don't get in. I can type root, but nothing happens. :-( My software version according to toon is: 3.3.8.
Smiggel
Member
Member
Posts: 57
Joined: Wed Apr 11, 2018 2:20 pm

Re: Rooting Toon (or boxx)

Post by Smiggel »

TheHogNL wrote:
Smiggel wrote: But as the documentation says, I need minicom to send over files
You only need to send the files if you are rooting a Toon with current firmware 4.9 or higher.
Try to boot the Toon after changing the password and inittab files, see if you get normal console access. If not then and only then you need the modified busybox in the uboot shell.

The files transfer over minicom has put a lot of users in troubles so I would not recommend to use that. If you really need the modified busybox, you can also just put a UTP network kabel in the Toon (in the shell after uboot, the wifi drivers are not running) and simply install the modified busybox over the internet with

Code: Select all

get an ip address on the Toon UTP port with: udhcpc
install busybox with:  opkg install http://files.domoticaforum.eu/uploads/Toon/apps/busybox-1.27.2-r4/busybox_1.27.2-r4_qb2.ipk
Check! It worked. I made a mistake with adding the Getty line to inittab. It was not saved properly. Did it again and could login as root. :-) Thanks for the help so far.
Rick083
Starting Member
Starting Member
Posts: 5
Joined: Thu Mar 08, 2018 10:36 pm

Re: Rooting Toon (or boxx)

Post by Rick083 »

After several attemps i need some help rooting my Toon. Its a 2010 09-R8 version, softw 4.13.7.
By following the root manual, using a Seriel adapter, getting acces using the password to the U-Boot prompt is no problem.
The following steps, printenv, edit the addmisc line, and boot_nand command are also clear, but.....in Putty the bootproces is never ending; there is no" New command shell or console" opening for the next steps off the rooting manual.[

Am i missing something, or a result off the latest software version ?

Code: Select all


U-Boot 2010.09-R8 (Dec 03 2012 - 12:50:30)

CPU:   Freescale i.MX27 at 400.168 MHz

Prodrive B.V. ED2.0
DRAM:  128 MiB
NAND:  128 MiB
LCD: Initializing LCD frambuffer at a1400000
LCD: 800x480, pbb 4
LCD: Drawing the logo...
In:    serial
Out:   serial
Err:   serial
Display-bmp: 800 x 480  with 16777216 colors
Net:   FEC
Warning: FEC MAC addresses don't match:
Address in SROM is         00:00:20:03:00:00
Address in environment is  00:0f:11:05:2a:7a


Enter password - autoboot in 2 sec...
U-Boot> printenv
bootdelay=2
baudrate=115200
loadaddr=0xA1000000
bootdelay=2
mtdids=nand0=mxc_nand
mtdparts=mtdparts=mxc_nand:1M(u-boot)ro,512K(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs)
mtdparts_kernel=mtdparts=mxc_nand:512K@0x00100000(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs)
mem=128M
autoload=no
backlight_brightness=50
baudrate=115200
console=ttymxc0
addtty=setenv bootargs ${bootargs} console=${console},${baudrate}
addmtd=setenv bootargs ${bootargs} ${mtdparts_kernel}
nandargs=setenv bootargs ubi.mtd=4 root=ubi0:rootfs rw rootfstype=ubifs
boot_nand=run nandargs addmtd addtty addmisc; nand read ${loadaddr} kernel; bootm ${loadaddr}
boot_nand_backup=run nandargs addmtd addtty addmisc; nand read ${loadaddr} kernel-backup; bootm ${loadaddr}
bootcmd=run boot_nand
splashimage=0x180000
ethact=FEC
sn=15-32-002-087
pn=6500-1500-0000
software_compatibility=0
manufacture_date=2015/08
ethaddr=00:0F:11:05:2A:7A
addmisc=setenv bootargs ${bootargs} mem=${mem} lpj=999424

Environment size: 1023/131068 bytes
U-Boot> editenv addmisc
edit: setenv addmisc setenv bootargs \$\{bootargs\} mem=\$\{mem\} lpj=999424 init=/bin/sh
U-Boot> run boot_nand

NAND read: device 0 offset 0x300000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at a1000000 ...
   Image Name:   Linux-2.6.36-R10-h27
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1944336 Bytes = 1.9 MiB
   Load Address: a0008000
   Entry Point:  a0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.36-R10-h27 (jbraam@dvl) (gcc version 4.5.3 20110223 (prerelease) (GCC) ) #1 PREEMPT Tue Oct 25 20:03:05 CEST 2016
CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Prodrive B.V ED2.0
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: ubi.mtd=4 root=ubi0:rootfs rw rootfstype=ubifs mtdparts=mxc_nand:512K@0x00100000(u-boot-env)ro,1536K(splash-image),3M(kernel),3M(kernel-backup),119M(rootfs) console=ttymxc0,115200
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 126092k/126092k available, 4980k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffa00000 - 0xffe00000   (   4 MB)
    vmalloc : 0xc8800000 - 0xf4000000   ( 696 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0022000   ( 104 kB)
      .text : 0xc0022000 - 0xc0367000   (3348 kB)
      .data : 0xc037e000 - 0xc03a17a0   ( 142 kB)
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:272
MXC IRQ initialized
MXC GPIO hardware
Console: colour dummy device 80x30
Calibrating delay loop (skipped) preset value.. 199.88 BogoMIPS (lpj=999424)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Configured for LCD: TM070RDH11
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 246
io scheduler noop registered (default)
imx-fb imx-fb.0: PreserveUBootFramebuffer(1): xres=800, yres=480 [skip _update_lcdc]
imx-fb imx-fb.0: PreserveUBootFramebuffer(2): xres=800, yres=480 [skip _update_lcdc]
Console: switching to colour frame buffer device 100x30
imx-fb imx-fb.0: fb0: DISP0 BG fb device registered successfully.
imx-fb imx-fb.0: PreserveUBootFramebuffer(3): xres=800, yres=480 [skip _update_lcdc]
imx-fb imx-fb.0: fb1: DISP0 FG fb device registered successfully.
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x1000a000 (irq = 20) is a IMX
console [ttymxc0] enabled
imx-uart.1: ttymxc1 at MMIO 0x1000b000 (irq = 19) is a IMX
imx-uart.2: ttymxc2 at MMIO 0x1000c000 (irq = 18) is a IMX
NAND device: K9F1G08U0E detected, disabling sub-page writes
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
RedBoot partition parsing not available
5 cmdlinepart partitions found on MTD device mxc_nand
Creating 5 MTD partitions on "mxc_nand":
0x000000100000-0x000000180000 : "u-boot-env"
0x000000180000-0x000000300000 : "splash-image"
0x000000300000-0x000000600000 : "kernel"
0x000000600000-0x000000900000 : "kernel-backup"
0x000000900000-0x000008000000 : "rootfs"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       193922
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            119 MiB
UBI: number of good PEBs:        952
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 952
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 612/203
UBI: image sequence number:  203163306
UBI: background thread "ubi_bgt0d" started, PID 309
at25 spi0.0: 32 KByte at25640B eeprom, pagesize 64
spi_imx spi_imx.0: probed
FEC Ethernet Driver
fec_enet_mii_bus: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
mxc-ehci mxc-ehci.0: portsc setup 1: 0x80000000
mxc-ehci mxc-ehci.0: Work around for USB enabled
ULPI transceiver vendor/product ID 0x0424/0x000d
mxc-ehci mxc-ehci.0: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.0: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.0: irq 56, io mem 0x10024000
mxc-ehci mxc-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.36-R10-h27 ehci_hcd
usb usb1: SerialNumber: mxc-ehci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mxc-ehci mxc-ehci.2: initializing i.MX USB Controller
mxc-ehci mxc-ehci.2: portsc setup 1: 0x80000000
mxc-ehci mxc-ehci.2: Work around for USB enabled
mxc-ehci mxc-ehci.2: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.2: new USB bus registered, assigned bus number 2
mxc-ehci mxc-ehci.2: irq 55, io mem 0x10024400
mxc-ehci mxc-ehci.2: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Freescale On-Chip EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.36-R10-h27 ehci_hcd
usb usb2: SerialNumber: mxc-ehci.2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
input: TSC2007 Touchscreen as /devices/virtual/input/input0
rtc-isl1208 1-006f: chip found, driver version 0.3
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0
i2c /dev entries driver
tmp431 0-004c: Could not read configuration register (-5)
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
adt7410 0-0048: adt7410 temperature sensor registered.
adt7410 0-0049: adt7410 temperature sensor registered.
nf_conntrack version 0.5.0 (1970 buckets, 7880 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
rtc-isl1208 1-006f: setting system clock to 2018-04-28 11:22:22 UTC (1524914542)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   117833728 bytes (115072 KiB, 112 MiB, 928 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
usb 2-1: new high speed USB device using mxc-ehci and address 2
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 104K
usb 2-1: New USB device found, idVendor=148f, idProduct=5370
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: 802.11 n WLAN
usb 2-1: Manufacturer: Ralink
usb 2-1: SerialNumber: 1.0
INIT: version 2.86 booting
 (print_boot_msg)
Please wait: booting... (print_boot_msg)
* Kernel            2.6.36-R10-h27 (print_boot_msg)
* Firmware          qb2/uni/4.13.7-1217-0 (print_boot_msg)
* Hostname          eneco-001-161957 (print_boot_msg)
usbcore: registered new interface driver r871x_usb_drv
usbcore: registered new interface driver rt2870
Loading iptables settings: iptables.
 (print_boot_msg)
Configuring network interfaces...  (print_boot_msg)
Configuring network interfaces...
Running 'ifup -a' in the foreground (ifup-fg)
ifup: interface lo already configured
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
Lease failing, starting in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-161957
udhcpc: option -h NAME is deprecated, use -x hostname:NAME
udhcpc: started, v1.27.2
udhcpc: no lease, failing
grep: /proc/557/cmdline: No such file or directory
udhcpc: sending discover
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy informa(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
tion
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
Lease failing, starting in bg: udhcpc -b -R -i wlan0 -A 5 -p /var/run/udhcpc.wlan0.pid -H eneco-001-161957
udhcpc: no lease, failing
udhcpc: option -h NAME is deprecated, use -x hostname:NAME
udhcpc: started, v1.27.2
* Wired (eth0)      00:0f:11:05:2a:7a  [No IP from DHCP Server] (print_boot_msg)
udhcpc: sending discover
* Wireless (wlan0)  28:c2:dd:0c:41:0f  [No IP from DHCP Server] (print_boot_msg)
Setting up IP spoofing protection: rp_filter.
Lease failing, already running in bg: udhcpc -b -R -i eth0 -A 5 -p /var/run/udhcpc.eth0.pid -H eneco-001-161957
udhcpc: no lease, forking to background
INIT: Entering runlevel: 5
Starting syslogd/klogd: done
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.
udhcpc: sending discover
imx-fb imx-fb.0: PreserveUBootFramebuffer(4): xres=800, yres=480 [do _update_lcdc]
udhcpc: sending discover
Lease failing, already running in bg: udhcpc -b -R -i wlan0 -A 5 -p /var/run/udhcpc.wlan0.pid -H eneco-001-161957
udhcpc: no lease, forking to background
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
DeQueueRunning[0]= TRUE!
DeQueueRunning[0]= TRUE!
DeQueueRunning[0]= TRUE!
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000

BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
DeQueueRunning[0]= TRUE!
DeQueueRunning[0]= TRUE!
DeQueueRunning[0]= TRUE!
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
BIRIdx(0): RXDMALen not multiple of 4.[25397], BulkInBufLen = 292)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
BIRIdx(0): RXDMALen not multiple of 4.[25397], BulkInBufLen = 292)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
DeQueueRunning[0]= TRUE!
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
ERROR!!! RTMPSetTimer failed, Halt in Progress!
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
Key1Str is Invalid key length(0) or Type(0)
Key2Str is Invalid key length(0) or Type(0)
Key3Str is Invalid key length(0) or Type(0)
Key4Str is Invalid key length(0) or Type(0)
NVM is Efuse and its size =2d[2d0-2fc]
phy mode> Error! The chip does not support 5G band 15!
RTMPSetPhyMode: channel is out of range, use first channel=1
(Efuse for 3062/3562/3572) Size=0x2d [2d0-2fc]
AntCfgInit: primary/secondary ant 0/1
0x1300 = 00064300
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:10, irq=-1)
Rcv Wcid(1) AddBAReq
Start Seq = 00000000
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
BUG: RTUSB_VendorRequest is called from invalid context
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Rooting Toon (or boxx)

Post by marcelr »

Did you update busybox yet?
This morning I added a new section to the rooting manual, explaining how to replace busybox in a simple way. For your firmware, busybox replacement is a necessary step for successful rooting.
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

Rick083 wrote:After several attemps i need some help rooting my Toon. Its a 2010 09-R8 version, softw 4.13.7.
By following the root manual, using a Seriel adapter, getting acces using the password to the U-Boot prompt is no problem.
The following steps, printenv, edit the addmisc line, and boot_nand command are also clear, but.....in Putty the bootproces is never ending; there is no" New command shell or console" opening for the next steps off the rooting manual.[

Am i missing something, or a result off the latest software version ?
Not sure what you are doing here:

Code: Select all

Environment size: 1023/131068 bytes
U-Boot> editenv addmisc
edit: setenv addmisc setenv bootargs \$\{bootargs\} mem=\$\{mem\} lpj=999424 init=/bin/sh
U-Boot> run boot_nand

The root manual says just type:

Code: Select all

setenv addmisc setenv bootargs \$\{bootargs\} mem=\$\{mem\} lpj=999424 init=/bin/sh
and then the "run boot_nand".

Your logs after that is showing a normal boot instead of a boot into init=/bin/sh
Member of the Toon Software Collective
Rick083
Starting Member
Starting Member
Posts: 5
Joined: Thu Mar 08, 2018 10:36 pm

Re: Rooting Toon (or boxx)

Post by Rick083 »

Exactly TheHog !..i found this out yesterdag; :lol: thougt i needed a Putty command to edit the addmisc line.. not
knowing that setenv is already the command.

With this and the additional info for downloading the Busybox by SSH made me pull Toon off the wall agian for another attemp..Let you know when i succeed

Thanx for your feedback.
Post Reply

Return to “Toon Rooting”