Re: Rooting Toon (or boxx)
Posted: Mon Nov 20, 2017 12:56 pm
Apparently, something else is missing in 4.9.23, that escaped my notice. Will check and get back to you.
Home Automation Domotica Forum Europe, Bwired Forum
Domotica - Home Automation Forum
https://www.domoticaforum.eu/
Rooting Toon (or boxx)
Page 19 of 55
Re: Rooting Toon (or boxx)
Posted: Wed Nov 22, 2017 3:08 pm
is there any News about the rooting with firmware 4.9.23?
Re: Rooting Toon (or boxx)
Posted: Wed Nov 22, 2017 4:42 pm
Not yet, apparently there's a glitch in the dropbear installation. I'm working on it, but it will take some time, I'm afraid.
Re: Rooting Toon (or boxx)
Posted: Sat Nov 25, 2017 4:35 pm
Get it for each other to rootte my show who can help me get a connection with PuTTY tried everything described there is
Re: Rooting Toon (or boxx)
Posted: Sun Nov 26, 2017 3:18 pm
Seems that 4.9.23 from 4.8.25 does update good. Still got getty and going to look in the ipk if its still in there. Seems its still good go to it!
Re: Rooting Toon (or boxx)
Posted: Sun Nov 26, 2017 4:03 pm
Can you post that ipk version number?
Re: Rooting Toon (or boxx)
Posted: Sun Nov 26, 2017 9:14 pm
Had another shot at this issue.densoft wrote:HI all,
I have the same error as @rybyan when i try to install Dropbear with firmware 4.9.23.
opkg install dropbear_2015.71-r0_qb2.ipk
Collected errors:
* pkg_run_script: package "dropbear" postinst script returned status 255.
* opkg_configure: dropbear.postinst returned 255.
this is what i have done before (manual Marcelr):
1) connect my serial interface to toon ->Works
2) enter the password for U-Boot 2010.09-R8 ->Works
3) command "printenv" -> Works
4) command "setenv addmisc setenv bootargs \$\{bootargs\} mem=\$\{mem\} lpj=999424 init=/bin/sh" -> Works
5) command "run boot_nand" ->Works
6) not edit "/etc/inittab", because getty not works with firmware 4.9.23. (manual marcelr)
7) edit "/etc/passwd" remove disabled to line "root::0:0:root:/root:/bin/sh" ->Works
no reboot toon/go to Dropbear installation with firmware 4.9.23
9) download package dropbear_2015.71-r0_qb2.ipk ->Done
10) package to ASCII with command "base64 dropbear_2015.71-r0_qb2.ipk > dropbear_2015.71-r0_qb2.ipk.b64" ->Done
11) then command "cat > dropbear_2015.71-r0_qb2.ipk.b64". After 15 minutes to wait no response from MInicom, but i can select <Ctrl+A> S en transfer the file to Toon.
When i connect with MInicom back to Toon <Ctrl+D> , i see the transfer file "dropbear_2015.71-r0_qb2.ipk.b64 " in the directory of Toon.
12) after command "base64 -d dropbear_2015.71-r0_qb2.ipk.b64 > dropbear_2015.71-r0_qb2.ipk", i see the file "dropbear_2015.71-r0_qb2.ipk"in the directory of Toon.
13) Now i try install the file with "opkg install dropbear_2015.71-r0_qb2.ipk" ,but now i see the error :
Collected errors:
* pkg_run_script: package "dropbear" postinst script returned status 255.
* opkg_configure: dropbear.postinst returned 255.
What i did wrong?
You did nothing wrong.
The dropbear (post)installer relies on some code that cannot be reached when toon is booted in the way that's proposed in the rooting manual (using init=/bin/sh). I hadn't tested this, so there we are. I need to rebuild dropbear with a changed postinstall script. Not sure how to make it work, yet, but I'll find something.
Re: Rooting Toon (or boxx)
Posted: Mon Nov 27, 2017 9:31 am
Okay, let's hope you find something. Perhaps a possibility to downgrade the firmware? or dropbear?
Re: Rooting Toon (or boxx)
Posted: Mon Nov 27, 2017 12:56 pm
I can't test it myself, but wouldn't it be possible to start dropbear installation on boot (by adding it to /etc/rc.local for example) and reboot Toon?
Re: Rooting Toon (or boxx)
Posted: Mon Nov 27, 2017 1:09 pm
That's a good suggestion. Will look into it.lxz wrote:I can't test it myself, but wouldn't it be possible to start dropbear installation on boot (by adding it to /etc/rc.local for example) and reboot Toon?
Re: Rooting Toon (or boxx)
Posted: Sun Dec 03, 2017 10:41 am
Is there News about rooting the 4.9.23 firmware?
Re: Rooting Toon (or boxx)
Posted: Sun Dec 03, 2017 12:20 pm
Work in progress ...
Zambia traffic rule #4 puts it nicely:
Exercise patience and hang back when necessary.
Zambia traffic rule #4 puts it nicely:
Exercise patience and hang back when necessary.
Re: Rooting Toon (or boxx)
Posted: Mon Dec 04, 2017 9:09 am
I am now very patiently waiting in my chair with a beer waiting for the presents. 
Re: Rooting Toon (or boxx)
Posted: Mon Dec 04, 2017 9:07 pm
I am running into the same issue with the recent firmware. Eagerly awaiting your fix, I'm happy to try anything you throw at me.
I was also unable to set a passwd for the root user, that applet is also missing.
(Wouldn't it be easier to install the previous version of busybox with getty included?)
Another issue I'm running into is the activation, I cannot get past step 2 (connect to SC)
Should I re-enable VPN, or is there a workaround once properly rooted?
I was also unable to set a passwd for the root user, that applet is also missing.
(Wouldn't it be easier to install the previous version of busybox with getty included?)
Another issue I'm running into is the activation, I cannot get past step 2 (connect to SC)
Should I re-enable VPN, or is there a workaround once properly rooted?
Re: Rooting Toon (or boxx)
Posted: Mon Dec 04, 2017 11:26 pm
What are you trying to use?Rudolf wrote: I was also unable to set a passwd for the root user, that applet is also missing.
You will bump into the same problem. Getting the code onboard.Rudolf wrote: (Wouldn't it be easier to install the previous version of busybox with getty included?)
Plus, rollback of busybox is a bit tricky; it holds all commands needed to do something, including (partially) installation of code. One typo in that rollback and your toon is nothing more than a paperweight.
Yes, there is, just edit /qmf/config/config_happ_scsync.xml to reflect an activated toon.Rudolf wrote: Another issue I'm running into is the activation, I cannot get past step 2 (connect to SC)
Should I re-enable VPN, or is there a workaround once properly rooted?