Rooting Toon (or boxx)

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

richardklasens
Starting Member
Starting Member
Posts: 15
Joined: Fri Feb 15, 2019 10:13 pm

Re: Rooting Toon (or boxx)

Post by richardklasens »

Hi guys.
I tried today to root my toon as following MarcelR's description.
Everything worked fine, bin/sh, changed passwd, ip tables, but can't install dropbear.
I used the ascii mode to transfer Dropbear to it but, changed the filename to dropbear.ipk >> dropbear.b64 and finaly back to dropbear.ipk with b64 command.
That all worked fine.
When i type in the command opkg install dropbear.ipk it gave some errors with the postinstalls.
Also tried to install the Busybox package from this website but, when i tried, it starts en then tried to install a package from feed.hae.int but then it hangs for a while and tells me that the package can't be installed.\
Any ideas?

Bootloader 2010R8
SW 4.5.3
s/n 15.xx.xx.xx.xx.xx.xx or so :)
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

Hi
I have a toon with U-Boot 2010.09-R8
I tryed to update to 5.0.4 and during or after the update nothing works
Get command not found.

I have read the posts and manuals
I think i have wrong libs with busybox

Now my question:
Where and how do i find the correct files and version of busybox and how do i replace them on the mounted rootfs file system
Because an install can not be performed and i dont want to break any more - thanks.

Here the boot of my box:

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:02:5f:c4


Enter password - autoboot in 10 sec...

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 mem=128M lpj=999424
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: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 203 at 0x000001960000
Bad eraseblock 250 at 0x000001f40000
Bad eraseblock 310 at 0x0000026c0000
Bad eraseblock 461 at 0x0000039a0000
Bad eraseblock 579 at 0x000004860000
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: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 258254
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 119 MiB
UBI: number of good PEBs: 947
UBI: number of bad PEBs: 5
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: 947
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 762/272
UBI: image sequence number: 855742193
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 0x04cc/0x1505
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 2019-02-16 13:25:55 UTC (1550323555)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 119089152 bytes (116298 KiB, 113 MiB, 923 LEBs)
UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 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
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<c00273d0>] (unwind_backtrace+0x0/0xf0) from [<c029e720>] (panic+0x60/0x190)
[<c029e720>] (panic+0x60/0x190) from [<c00223dc>] (init_post+0x78/0xc4)
[<c00223dc>] (init_post+0x78/0xc4) from [<c0008b54>] (kernel_init+0x110/0x14c)
[<c0008b54>] (kernel_init+0x110/0x14c) from [<c00238ec>] (kernel_thread_exit+0x0/0x8)
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

You now need to follow this manual: viewtopic.php?f=100&t=11235#p85621
Be ready for some hard learning curves and lost weekends.

The manual answers your question (like where to get the rootfs with working libs and busybox).

Are you sure this happened after/during the update? Currently updates are not working due to problems with the eneco servers. And if they would work, all known bugs which could cause this should have been fixed.
Member of the Toon Software Collective
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

richardklasens wrote:Hi guys.
I tried today to root my toon as following MarcelR's description.
Everything worked fine, bin/sh, changed passwd, ip tables, but can't install dropbear.
I used the ascii mode to transfer Dropbear to it but, changed the filename to dropbear.ipk >> dropbear.b64 and finaly back to dropbear.ipk with b64 command.
That all worked fine.
When i type in the command opkg install dropbear.ipk it gave some errors with the postinstalls.
Also tried to install the Busybox package from this website but, when i tried, it starts en then tried to install a package from feed.hae.int but then it hangs for a while and tells me that the package can't be installed.\
Any ideas?

Bootloader 2010R8
SW 4.5.3
s/n 15.xx.xx.xx.xx.xx.xx or so :)

Always post the logs if you say 'postintstall gives errors' :-)
Why are you still using the manual rooting guide? The auto rooter fixes this dropbear postinstall thing.
If you really want to do it manually, check here how the auto rooter installs dropbear: https://github.com/martenjacobs/ToonRoo ... oon.sh#L37

But try "opkg --nodeps install packagename.ipk' so it will not download the file from feed.hae.int.
Member of the Toon Software Collective
richardklasens
Starting Member
Starting Member
Posts: 15
Joined: Fri Feb 15, 2019 10:13 pm

Re: Rooting Toon (or boxx)

Post by richardklasens »

TheHogNL wrote: Always post the logs if you say 'postintstall gives errors' :-)
Why are you still using the manual rooting guide? The auto rooter fixes this dropbear postinstall thing.
If you really want to do it manually, check here how the auto rooter installs dropbear: https://github.com/martenjacobs/ToonRoo ... oon.sh#L37

But try "opkg --nodeps install packagename.ipk' so it will not download the file from feed.hae.int.
I will do next time, but when i posted the message here i wasn't in the opportunity to post my log :)
I'll try opkg --nodeps for installing dropbear.
I'd like to do it manually... nice way to learn some programming in linux :)
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

Yes, I'm sure this was after update.
First i did update to the newest update-rooted.sh
I did get some download problems with that: wget did not support https
I downloaded the latest from the website
transfered it with Winscp to toon
and run the script.
The script stopped with an error
Than i could not ls, cat and so on

Can i use the image-base-qb2 as a file system, or is this one depending on a typical kernel type.
So you can see the box starts with linux version 2.6.36-R10-h27
If it is depending - do i have to build my own filesystem and kernel or do you have
a woking filesystem-kernel-set on hand
Thanks
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

First boot from the nfs enabled kernel (from the manual) and that rootfs you are talking about. Then you can mount your current filesystem within that 'rescue' boot.

Next thing is to check what is going wrong (probably busybox or libraries) by just going into the mounted directory. You can replace the busybox from the nfs rootfs. Using the libs from the rootfs is probably not possible due to older kernel.

I also have a backup rootfs of a working toon. You could use that as a final method if everything else fails. You only need to make a backup of (yourbrokentoon-rootfs):/etc/openvpn and all dirs/files inside of it so you can keep your VPN working after restoring.

If this is all a bit too much, just let me know. I could help you over teamviewer with a small voluntairy fee.
Member of the Toon Software Collective
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

Hi,

I tryed with copy-ing the busybox from the rootfs to my old rootfs
(cp /bin/busybox /mnt/bin/busybox) and restarted but did get an kernel panic.posting.php?mode=reply&f=101&t=11230#
I think i need a busybox which fits the linux kernel 2.6.36-R10-h27.

Can you help me with that. Thanks.
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

Busybox isn't kernel depended. Probably your libraries are missing.
Member of the Toon Software Collective
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

I have just put a rootfs from a toon 1 with firmware 4.20.7 on http://qutility.nl/toon.4.20.7.rootfs.d ... ned.tar.gz

This is the complete file system (without /etc/openvpn). So you can restore your toon if you extract this over your current toon. Be sure to first make a copy of your current /etc/openvpn

After unpacking this over your broken toon, you only need to restore /etc/openvpn and set your toon hostname (eneco-001-xxxxx) in these files:
/etc/hosts
/etc/hostname
/etc/network/interfaces

Then reboot. And it should work again, clean, factory reset and from firmware 4.20.7.
Member of the Toon Software Collective
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

Hi,

Thanks for the filesystem.
I tryed it yesterday with nfs boot, it mounted perfectly and started
Only quby does a test on NFS mounts, and droped the eth0, and process got waiting - no prompting...
But, it starts, so i did try to burn it today.

I installed mtd-utils on a host
Unpacked the file system, made changes to hostname, hosts, interfaces and copyed etc/openvpn
Then i did on the host
mkfs.ubifs -r ./rootfs/ -m 512 -e 129024 -c 954 -o toon_rootfs_ubifs.img

I tryed
ubinize -vv -o rootfs.ubi -m 2048 -s 512 -p 128KiB ubinize.ini

but got a warning ubinize.ini not found
Then i created ubinize.ini on the host

I transfered to the nfs-mount ubinize.ini and toon_rootfs_ubifs.img
Did on toon:
ubinize -vv -o rootfs.ubi -m 2048 -s 512 -p 128KiB ubinize.ini

ubiformat /dev/mtd4 -f rootfs.ubi
get an error: try first detach mtd4
ubidetach -p /dev/mtd4

ubiformat /dev/mtd4 -f rootfs.ubi
# ubiformat /dev/mtd4 -f rootfs.ubi
ubiformat: mtd4 (nand), size 124780544 bytes (119.0 MiB), 952 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 951 -- 100 % complete
ubiformat: 947 eraseblocks have valid erase counter, mean value is 273
ubiformat: 5 bad eraseblocks found, numbers: 131, 178, 238, 389, 507
ubiformat: flashing eraseblock 474 -- 100 % complete
ubiformat: formatting eraseblock 951 -- 100 % complete


<REBOOT>
...
Scanning device for bad blocks
Bad eraseblock 203 at 0x000001960000
Bad eraseblock 250 at 0x000001f40000
Bad eraseblock 310 at 0x0000026c0000
Bad eraseblock 461 at 0x0000039a0000
Bad eraseblock 579 at 0x000004860000
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: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 0
UBI: volume 0 ("rootfs") re-sized from 469 to 934 LEBs
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 119 MiB
UBI: number of good PEBs: 947
UBI: number of bad PEBs: 5
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: 947
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 764/274
UBI: image sequence number: 221618967
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 0x04cc/0x1505
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 2019-02-19 11:22:24 UTC (1550575344)
UBIFS error (pid 1): validate_sb: min. I/O unit mismatch: 512 in superblock, 2048 real
UBIFS error (pid 1): validate_sb: bad superblock, error 1

List of all partitions:
1f00 512 mtdblock0 (driver?)
1f01 1536 mtdblock1 (driver?)
1f02 3072 mtdblock2 (driver?)
1f03 3072 mtdblock3 (driver?)
1f04 121856 mtdblock4 (driver?)
No filesystem could mount root, tried: ubifs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c00273d0>] (unwind_backtrace+0x0/0xf0) from [<c029e720>] (panic+0x60/0x190)
[<c029e720>] (panic+0x60/0x190) from [<c0008f10>] (mount_block_root+0x1cc/0x20c)
[<c0008f10>] (mount_block_root+0x1cc/0x20c) from [<c00090d0>] (prepare_namespace+0x8c/0x178)
[<c00090d0>] (prepare_namespace+0x8c/0x178) from [<c0008b50>] (kernel_init+0x10c/0x14c)
[<c0008b50>] (kernel_init+0x10c/0x14c) from [<c00238ec>] (kernel_thread_exit+0x0/0x8)

Bad superblock....
Is this recoverable ???
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Rooting Toon (or boxx)

Post by TheHogNL »

You only needed to unpack the rootfs over the mounted bad rootfs (/mnt/rootfs/*)

That ubinize etc within a linux hosts isn't necesarry (the manual is to over complicated on that).

Just start again with NFS boot and try to mount your rootfs again (which probably fails now).
It it fails you need to ubiformat your /dev/mtd4 again (without a file, so result is empty mtd4), create a ubi0_0 rootfs on top of it (ubimkvol) and then mount it (it would be empty). Then restore the supplied rootfs-tar.gz in that directory and you are done.

Code: Select all

ubiformat /dev/mtd4
ubiattach -p /dev/mtd4
ubimkvol /dev/ubi0 -m -N rootfs
mount -t ubifs /dev/ubi0_0 /mnt/rootfs/
cd /mnt/rootfs
tar zxvf /somewhere/rootfs.tar.gz
Member of the Toon Software Collective
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

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:02:5f:c4


Enter password - autoboot in 10 sec...

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 mem=128M lpj=999424
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: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 203 at 0x000001960000
Bad eraseblock 250 at 0x000001f40000
Bad eraseblock 310 at 0x0000026c0000
Bad eraseblock 461 at 0x0000039a0000
Bad eraseblock 579 at 0x000004860000
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: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 576
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 119 MiB
UBI: number of good PEBs: 947
UBI: number of bad PEBs: 5
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: 947
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 188/185
UBI: image sequence number: 1045606298
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 0x04cc/0x1505
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 2019-02-19 18:28:21 UTC (1550600901)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 119218176 bytes (116424 KiB, 113 MiB, 924 LEBs)
UBIFS: journal size: 5935104 bytes (5796 KiB, 5 MiB, 46 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 4952683 bytes (4836 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 104K
usb 2-1: new high speed USB device using mxc-ehci and address 2
INIT: usb 2-1: New USB device found, idVendor=13d3, idProduct=3309
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
version 2.86 bootingusb 2-1: Product: RTL8191S WLAN Adapter
usb 2-1: Manufacturer: Manufacturer Realtek
usb 2-1: SerialNumber: 00e04c000001

imx-fb imx-fb.0: PreserveUBootFramebuffer(4): xres=800, yres=480 [do _update_lcdc]
(print_boot_msg)
Please wait: booting... (print_boot_msg)
* Kernel 2.6.36-R10-h27 (print_boot_msg)
* Firmware qb2/uni/4.20.7-1264-0 (print_boot_msg)
* Hostname eneco-001-027316 (print_boot_msg)
==DriverVersion: v2.6.6.0.20120405==
MAC Address from efuse= 24-a-64-6-d6-ca
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
PHY: 1:10 - Link is Up - 100/Full
udhcpc: sending discover
udhcpc: sending select for 192.168.0.161
udhcpc: lease of 192.168.0.161 obtained, lease time 7200
/etc/udhcpc.d/50default: Adding DNS 192.168.0.1
/etc/udhcpc.d/70prepend-google-pub-dns: Prepending DNS 8.8.8.8 (skip with /mnt/persist/udhcpc-skip-prepend-google-pub-dns)
* Wired (eth0) 00:0f:11:02:5f:c4 192.168.0.161 (print_boot_msg)
* Wireless (wlan0) 24:0a:64:06:d6:ca [No IP from DHCP Server] (print_boot_msg)
Setting up IP spoofing protection: rp_filter.
INIT: Entering runlevel: 5
Starting Dropbear SSH server: dropbear.
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 changed, writing /etc/inittab.

Eneco Toon by Quby

eneco-001-0xxxxx: ~#



Pfff... Thanks a lot.
He is running again.
Thank you very much

Were can i find the manuals to backup NAND .... beter late than ...

Thanks again
Erik
Erik007
Starting Member
Starting Member
Posts: 16
Joined: Thu Feb 14, 2019 12:31 pm

Re: Rooting Toon (or boxx)

Post by Erik007 »

In /etc/openvpn there is a file eneco-001-0xxxxx.tar.gz
I think it was from update-rooted.sh
Can i delete that

And i think manually - walk steps for routing toon - check if all is set correct
Am i right??

Thanks
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!!
Keep that file and store it in a safe place. It contains the vpn access certificates etc. for your toon.
Post Reply

Return to “Toon Rooting”