Fully automated rooting script

Everything about rooting Toons 1 and 2.

Moderators: marcelr, TheHogNL, Toonz

RichardGorter
Starting Member
Starting Member
Posts: 9
Joined: Sun Apr 14, 2019 2:19 pm

Re: Fully automated rooting script

Post by RichardGorter »

I can find my WIFI network but it won't connect.

So when it's on the screen/page for wifi searching I have to plug in the UTP. cable? Beceause I tried yesterday, but I connected it to the router before booting.
And it didn't overruled the wifi.

I still have a quastion about this part of the rooting?

pi@raspberrypi:~/ToonRooter $ ssh root@192.168.0.102
The authenticity of host '192.168.0.102 (192.168.0.102)' can't be established.
RSA key fingerprint is SHA256:I+DcNE5XYtSjmVaAIvT1y2ygYaYHI+Q8in+S71PI4+o.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.102' (RSA) to the list of known hosts.
root@192.168.0.102's password:
eneco-001-171151:~#

I could login with the password created in the script, and reboot my Toon with the SSH. But after that it wasn't rooted. How could this happen?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Fully automated rooting script

Post by TheHogNL »

RichardGorter wrote:
I could login with the password created in the script, and reboot my Toon with the SSH. But after that it wasn't rooted. How could this happen?
What do you mean 'after that is wasn't rooted'? Only possible way is that you installed a firmware update from Eneco just after you rooted your toon. That will reset the internal firewall and therefore blocking your SSH.

If you plugin your LAN cable it will override the wifi (even from boot). That will allow your to login to your toon on the LAN ip adress even when the screen is asking for a wifi in the install wizard.
If you are logged in run the rooted toon update script with option -f to install the apps we provide and fix some files so you toon is completly free from eneco (and it also ends the install wizard). This is also in the how to root your toon guide: viewtopic.php?f=100&t=11235#p82533
Member of the Toon Software Collective
MaxBlasto
Starting Member
Starting Member
Posts: 1
Joined: Sun Apr 21, 2019 7:04 pm

Re: Fully automated rooting script

Post by MaxBlasto »

Hi everyone, after reading this forum quite a lot for over two years, it was finally warm enough for me to attempt to root my Toon.

Except for a few hiccups, everything went flawlessly. I just wanted to say a big THANK YOU to all the awesome people here for the good manuals, scripts and apps.
I am trying to integrate Toon into my not-so-smart-yet-home, so I hope I can someday contribute something as well.
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Fully automated rooting script

Post by marcelr »

Well done!

And welcome to the party :-)
RichardGorter
Starting Member
Starting Member
Posts: 9
Joined: Sun Apr 14, 2019 2:19 pm

Re: Fully automated rooting script

Post by RichardGorter »

This weekend I finished my Toon to, thanks for your patients and support!
rotzen
Starting Member
Starting Member
Posts: 9
Joined: Fri Feb 08, 2019 10:23 am

Re: Fully automated rooting script

Post by rotzen »

Ok what could have happened... I rooted my Toon in februari. All was working fine even with home assistant. Suddenly (well perhapse I clicked on something) I've got my old Toon back, the menu is back to normal, no Toon store and stuff like that. Anyone has an easy idea to get it back without opening the whole Toon again?
marcelr
Global Moderator
Global Moderator
Posts: 1153
Joined: Thu May 10, 2012 10:58 pm
Location: Ehv

Re: Fully automated rooting script

Post by marcelr »

Probably it was still connected to eneco and you did an update?
Tsk, tsk, tsk.

If you can still get in through ssh, there's no issue, otherwise: You're back to square one.
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Fully automated rooting script

Post by TheHogNL »

marcelr wrote: If you can still get in through ssh, there's no issue, otherwise: You're back to square one.
If he is lucky the Toon was on the newest TSC version. This will always force SSH open. The TSC script will always run even after a official Toon upgrade.
So, then SSH would still work. Next step would be to run the update-rooted.sh script with the -f option and that would be all.
Member of the Toon Software Collective
rotzen
Starting Member
Starting Member
Posts: 9
Joined: Fri Feb 08, 2019 10:23 am

Re: Fully automated rooting script

Post by rotzen »

Ah ssh is indeed enabled :D Now I just have to find out what the generated root password was :lol:

How can I prevent the eneco updates in future? I do remember clicking on something of a TSC update :roll:
Toonz
Forum Moderator
Forum Moderator
Posts: 1873
Joined: Mon Dec 19, 2016 1:58 pm

Re: Fully automated rooting script

Post by Toonz »

you can reset the password via the TSC menu on Toon: 'Menu' --> 'Instellingen' --> 'TSC tab' --> button 'reset password' .
After pressing that button your password will be reset to 'toon' (without the quotes).

Also, in this tab you see the 'Check for updates' button which will check for resourcefile updates (with this TSC menu) as well as firmware upgrades.
A firmware upgrade via the TSC menu will preserve root access and firewall settings.
member of the Toon Software Collective
rotzen
Starting Member
Starting Member
Posts: 9
Joined: Fri Feb 08, 2019 10:23 am

Re: Fully automated rooting script

Post by rotzen »

Uhoh, 'Houston we have a problem', used ssh to get into Toon (this was luckilly still enabled and I found my password again). Used the description on https://github.com/IgorYbema/update-rooted to run

Code: Select all

 sh /root/update-rooted.sh -f
Then rebooted Toon, but it only shows the load icon (the T).

So I thought, well ok, lets open up again and rerun the root script. Connected the three pins but the root script doesn't get past

Code: Select all

INFO:rooter:Waiting for Toon to restart
Luckily its not that cold outside anymore :roll:

Any thoughts?
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Fully automated rooting script

Post by TheHogNL »

How did you reboot after the update-script? It looks like you did a power cycle instead of a reboot command.

You now need to connect to the serial console of the Toon and check if you can still get into u-boot.
Member of the Toon Software Collective
rotzen
Starting Member
Starting Member
Posts: 9
Joined: Fri Feb 08, 2019 10:23 am

Re: Fully automated rooting script

Post by rotzen »

Srry, thought I editted my last post yesterday. You are correct, I pressed the reset button instead of a reboot command. Connecting the 11 wires I'm able to get into u-boot, asking which runlevel I want.
TheHogNL
Forum Moderator
Forum Moderator
Posts: 2125
Joined: Sun Aug 20, 2017 8:53 pm

Re: Fully automated rooting script

Post by TheHogNL »

How far does the Toon get if you just let it boot? What is the last lines you see on the serial console?
Member of the Toon Software Collective
rotzen
Starting Member
Starting Member
Posts: 9
Joined: Fri Feb 08, 2019 10:23 am

Re: Fully automated rooting script

Post by rotzen »

Perhaps we should create a new topic for this as it has nothing to do with the automated rooting script? Not sure if a mod can move the messages or I should start a new topic from here?

Attachted all 11 pins again and ran the command: pi@raspberrypi:~ $ sudo screen /dev/serial0 115200

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:06:ab:0c



Enter password - autoboot in 2 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-h28

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1944236 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-h28 (jbraam@dvl) (gcc version 4.5.3 20110223 (prerelease) (GCC) ) #1 PREEMPT Fri Sep 28 15:51:09 CEST 2018
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: 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:       322639
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: 902/338
UBI: image sequence number:  239823495
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-h28 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-h28 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-05-08 17:43:43 UTC (1557337423)
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)
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: version 2.86 bootingusb 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

Enter runlevel: 0

INIT: Entering runlevel: 0


INIT: no more processes left in this runlevel

The command is waiting on "INIT: Entering runlevel:" no matter what number you enter the result is always the no more processes message
Toon then just shows the T logo on a black sreen
Post Reply

Return to “Toon Rooting”