Howto update to 01.01

[qwiksilver96]

I'm trying to do the upgrade from 2.19 to 2.49 and when I run /root/platform/upgrade.sh in step 4 i get the error message "URL or certificate information missing, update canceled."

It looks like i'm missing /database/cf_url and /database/cf_cert. Does anyone know where I can get these? Also any idea why i don't have them?

I do not have either of those files in /database but my upgrade was successful a few days ago.

[strex]

First of all, thanks to everyone who contributed to this post thus far.
Today I took a brand new (from HomeDepot) wink, rooted it via the NAND flash method, then followed the update procedure exactly (on page 1), and now I have a fully updated, rooted wink! Just to verify the versions, here ya go:

Code: Select all

[root@flex-dvt database]# for i in `ls cf_*`; do echo -n "$i "; cat $i; done
cf_build 00.01
cf_fver0 00.01
cf_fver1 00.12
cf_fver2 00.01
cf_fver3 02.49


So for anyone who's interested, yes the instructions are still valid, and yes they still work great! Thanks again everyone..

[CloneNum3]

I'm trying to do the upgrade from 2.19 to 2.49 and when I run /root/platform/upgrade.sh in step 4 i get the error message "URL or certificate information missing, update canceled."

It looks like i'm missing /database/cf_url and /database/cf_cert. Does anyone know where I can get these? Also any idea why i don't have them?

I do not have either of those files in /database but my upgrade was successful a few days ago.

I've been out of the loop for a while, but working on brushing up.

Appears the cf_cert file only exists when in update mode.

Code: Select all

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAumZE0qsNgtTQNCOhqx8+
+3DQG33HIvgqdPJ9qa4A9rdtuTADJ3FUnO53+EQYFuZaZ8RK76DQddtqCUzRyra7
JI9RTXxYX4VWxTMEfKMoi2R79BFPOXg61Q3ZCZ4RP2gz1Mkso59ULNziLmeSQwSK
udeTSmkcLUql9Ygtx8iro+JiFBr6wwyLFm+KblkRvk7aYjctdJvGOGUfoYKyKQJz
5mXQiHoCqpkqdNL436paQjsxIdcEqu+iRl8n2BIgDqxHg1ZTdiNe6NIyohkaG97r
Rfzv2LZQ9zgfdQfGArwc9B+AGyKFJ4FgW0SdCmZSNrpqoEVCS1Xuw8QLe6oraMuC
MwIDAQAB
-----END PUBLIC KEY-----

[JustinAiken]

Does anyone have old firmwares? I need to update my 00.01 backup rooted hub, but I don't want to lose PHP/etc...

[lordpengwin]

Is anyone still maintaining their rooted hub? I just tried the update process but it doesn't seem to work. I just end up with 2.49.

[duren]

Does anyone have old firmwares? I need to update my 00.01 backup rooted hub, but I don't want to lose PHP/etc...

00.01: https://file.io/BXXn7Y
00.86?: https://file.io/LPRQ2v

[lordpengwin]

So... I gave up on waiting for someone else to figure out how to do the upgrade and figured that I would give up root and tell the app to do it. I removed the blocks from /etc/hosts and told the app to upgrade. The hub flashed green for a while then went to a state of yellow and sat there. I was still logged in and it seemed that some of the upgrade process might have run but it did not reboot. I figured that might be because I had already set things up to prevent the reboot, so i did it by hand. The hub rebooted and I got back into it and could see that it had mounted the upgrade partition, then it rebooted on its own again and was up and running 2.66 and I could still ssh in. Happy Days!

I went through the process on the first page of the thread to return the hub to the state where ssh will still be enabled on the next upgrade but the reboot must be done by hand. Before I went through this process the app showed 2.68 as being available but it is not showing now, it may show up again in a day or two.

So long story short, it looks like if your hub is rooted and both the main partition and the upgrade partition are set up to still allow ssh, you "should" be able to let the app do the upgrade and still have root on the hub afterward. At least that was the case going from 2.49 to 2.66.

[mattjm]

pengwin's procedure seemed to work for me....what I did:

1. fix /etc/hosts to allow upgrade via app
2. upgrade via app. The light sequence was:

-flashing red
-solid yellow--at this point I was stilled logged in and rebooted via command line
-blinking yellow (ssh logins time out)
-blinking red (ssh logins time out)
-blinking yellow (ssh logins time out)
-solid blue (finally after a wait lets me in via SSH--note server SSH keys are regenerated and your client may complain)

I'm not clear on pengwin's comment:

"I went through the process on the first page of the thread to return the hub to the state where ssh will still be enabled on the next upgrade but the reboot must be done by hand."

I thought maybe this was about step 5 on the first page of this thread so I went ahead and did that. It's not clear what that gets me...

[lordpengwin]

What I meant by going through the process is that i mounted the update partition and commented out things to make sure that I would be able to ssh in after it booted to that partition.

I did the update to the latest today and was able to log in during the process and had to reboot the hub manually after each step. Unfortunately after the final reboot I could no longer ssh into the box. It looks like ssh is still enabled but my key didn't work so either i missed a step or they've taken measures on the update to block jailbreaking it. Not really a big deal, I never used root access for anything and now i can just tell it to update and forget about it.

[lordpengwin]

Today i updated my hub to 3.4.4 and it hung during the process. Thinking that maybe the upgrade partition was still rooted and blocking the reboot, i tried and was able to log into the hub. I was then able to root the new partition and restore access by adding my ssh keys and disabling dropbear (now in /etc/init.d). After I rebooted, the hub came up running 3.4.4.xxx and I had regained root access. I'm a happy camper