Hope somebody can help with this. (possible brick)
14 March, 2013 - 16:12
Ok, after following the HAH for a while now i decided to take the plunge and got a box off ebay. it arrived and great i thought. today went through the process to install HA but seem to have hit a "brick" wall.
this is what i did.....
Downgraded firmware from 5.10.7-uk to 5.04-uk. this was successful (using the 'RGWRepair.exe' software)
Then i did the windows telnet/ftp method, and could successfully open a telnet session to the livebox
I then got a little carried away and did step 7. Stopping 'phone home' behaviour.
Next i then moved onto the Replacing the RedBoot loader. i downloaded redboot_blueg5.6-patched.gz and extracted this on my windows machine.
then from a telnet session ran:
# cd /tmp
# wget ftp://<HOST SERVER>/redboot_blueg5.6-patched (pointing to my ftp server)
# fcp -v redboot_blueg5.6-patched /dev/mtd0
this last command did some small write..... i forget the rest. no mention of any error. i was slightly relieved at this point as the warning of bricking your device if you did extract the file.
I then downloaded firmware-287.zip and ran the RGWRepair.exe program to use this and at the point of putting the power cable back in the hub and holding down 1, this is when things have gone wrong.
all I am left with is a single red light in the middle. (i believe the >> led)
is the device bricked? did I miss something or could this be something else the matter? do i now need to JTAG this?
hope someone can help me with some ideas/solutions.
Regards,
Michael
15 March, 2013 - 06:26
#2
The flashing of /dev/mtd0
The flashing of /dev/mtd0 won't immediately let you know you have a brick until you reboot this is when you know if things went wrong or not as you have just scorched the startup firmware with junk. You did decompress the redboot file you obtained? Its a simple mistake.
To give you piece of mind you don't have a brick fireup wireshark and look for the arp requests and various packets coming in from the Livebox as it looks around for something to load an image from when holding down button 1 from a power cycle.
Without a serial console cable its hard to know what is going on by looking at flashing leds, I tend to never to use RGWrepair as I never had good experience with it, if you know linux you could try setting up a TFTP server. At least this way you will see the RRQ coming in and know your redboot isn't toasted.
Brett
15 March, 2013 - 10:11
#4
Once the livebox firmware has
Once the HAH firmware has been flashed you MUST return the livebox to network with a DHCP server on it for it to obtain an IP address and bootup. By default it does not have a static IP nor will it fall back to some default if it can't obtain one via a DHCP server.
If it does not get an IP all you will see a one LED on solid and nothing much will happen and you can't get in. I turned mine off and unplugged it network cable to check. Once its obtains its IP two LED will light up and one will start flashing away,
Maybe everything is ok and its just not getting an IP address !
UPDATE: The easiest way to locate its IP is to simple have xFxViewer running and watch for the xap-hub heartbeat. Note v3 does not need a hub, v4 its mandatory to have a hub. I use v3 on windows.
Brett
15 March, 2013 - 10:26
#6
Oh if you didn't flash the
Oh if you didn't flash the HAH firmware.
A console cable is your best bet and/or use wireshark to watch for its initial TFTP RRQ messages to IP 10.7.58.114 (which is hardcoded into the redboot firmware) If you want to use TFTP make sure your windows box has THAT IP address and watch your logs for the request coming in., I've not played with tftp on windows but it should be possible. You livebox whilst attemping to TFTP new firmware will have it's IP as 10.7.58.112
See http://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol (sorry I use abbreviations like RRQ and forgot that people might not know it)
On a linux box 10.7.58.114: From the /var/log/tftp.log
Sep 17 15:38:53 gumby atftpd[5060.-1210337088]: Advanced Trivial FTP server started (0.7) Sep 17 15:49:24 gumby atftpd[5061.-1210496112]: Serving inventel/blue_5/factory_script_crypt to 10.7.58.112:7700
15 March, 2013 - 10:41
#8
The problem with making a
The problem with making a console cable with a broken livebox is you won't know if you're console cable hardware is faulting or if the livebox is faulty.
Its best to know your console cable is ok before need it whilst the livebox is still happy. Mind you from what you have said you have done I can't find anything wrong with your steps so I'm just hoping its the RGWRepair util playing up. TFTP is your best bet its works 100% of the time. Mind you having a console cable for when I really screw things up making changes to the kernel/startup scripts does come in handy. Bah its on only a few quid and it goes to a good cause. :)
Brett
15 March, 2013 - 11:06
#9
RGWRepair ain't too bad
I've broken into at least 30 Livebox units and used RGWRepair on each and every one. It's probably a bit more prone to needing a 'second attempt' than TFTP, but it does work.
Reading your original post
"I then downloaded firmware-287.zip and ran the RGWRepair.exe program to use this and at the point of putting the power cable back in the hub and holding down 1, this is when things have gone wrong."
I suspect that the HAH firmware might well be on your unit & running. Waiting for a DHCP server to give it an IP address. Do try plugging the Livebox directly into the back of your router (use a standard patch cable - not a x-over), power-on & see if that single red LED changes to a pattern where the other LEDs flash too.
Cheers,
Derek.
25 March, 2013 - 22:23
#11
Not good
Looks like no other Livebox bootup that I've seen.
Something more like http://www.dbzoo.com/livebox/commandlineaccess#bootlog
is what you should be seeing.
Hopefully, those other Liveboxes that you now have will do better.
Derek
26 March, 2013 - 21:46
#13
You may be aware
You may be aware already...but the non Inventel Livebox isnt compatible with the HAH project
saying that the DV4210-WA does appear to be an Inventel model from various google searches
i wonder if this is the cause of your issues
28 March, 2013 - 18:29
#14
I seemed to have acquired a
I seemed to have acquired a few liveboxes from 'accidentally' bidding on fleabay
If you can't get RGWrepair to communicate then it doesn't sound good, although I'm no expert.
reading through your post though I can't see where you went wrong?
anyone else?
Garry