AZ-Box premium hd.

jolatacqce

Looking for advice from the more experienced members on this forum.I'm trying to revive my receiver which is stuck in booting.I'v purchased a
UART TTL to serial/USB convertor.I'm now at the stage where Ineed an ip to use with putty.I'v tried pinging 192.168.1.###,changing the last digits about thirty times but I get the same reply,packets:sent4 received 4 lost 0. Now, I'm led to believe (how to recover AZ-Box) this indicates these ip's are no good to me,but my question is,roughly, how many different ip's should I have to try to get a free one,or is there a quicker way to find one?

Greenpiece

Do you know what firmware image is on this box? If it is enigma 2 to get the box into rescue mode you have to hold the vol+ button when you are powering it up and if you have it connected via Ethernet cable to router it should display the IP address.

If that does not work then there are instructions on sites such as satpimps on how to use a yamon cable to revive the box. Thankfully so far I have not yet had to go down that route so cannot help you with that, but I'm sure there are others here who may have done so.

shinobi

jolatacqce wrote: »

Looking for advice from the more experienced members on this forum.I'm trying to revive my receiver which is stuck in booting.I'v purchased a
UART TTL to serial/USB convertor.I'm now at the stage where Ineed an ip to use with putty.I'v tried pinging 192.168.1.###,changing the last digits about thirty times but I get the same reply,packets:sent4 received 4 lost 0. Now, I'm led to believe (how to recover AZ-Box) this indicates these ip's are no good to me,but my question is,roughly, how many different ip's should I have to try to get a free one,or is there a quicker way to find one?

Hi Joe,
I take it your connected to the box through Putty with the Serial cable and are at the very early stages of assigning an IP address to the box? What is the IP address of your modem? Should be something like 192.168.0.1 or 192.168.1.1.
When assigning an IP address I would suggest assigning for example 192.168.1.99. This IP address should more than likely be available to you to continue with. Let us know your progress & hopefully will be able to help you if there are any stumbling blocks along the way.

jolatacqce

Yes, enigma2,I'm got the convertor & cable,and I'v sussed out these connections, but I need a 'free' ip for receiver before I can experiment any further.Even using this 'ping' thing is new to me.I'm an 'AULD NEWBIE',if youy know what I mean,but thank you for reply,I'm sure someone will come up with right advice.

jolatacqce

Thank you Shinobi,I'v the AZ connected to the modem,and it is also connected to the laptop with the serial cable,is this correct?

tapfit2004

jolatacqce wrote: »

Thank you Shinobi,I'v the AZ connected to the modem,and it is also connected to the laptop with the serial cable,is this correct?

hi joe.

i had to do this last week and this is how i got it working.

first i brought up a command prompt window (dos window) in windows. i typed in ipconfig and pressed return and this gave me my computer ip address (ipv4 address 192.168.1.105) and my router address (default gateway 192.168.1.1).

i knew that my router gives out addresses from 100 to 255 so i picked 102.168.1.112 as there were 3 laptops and a couple of phones that were already connected.

i assigned these to the azbox by typing:

setxenv y.ipaddr "192.168.1.112"
setxenv y.gateway "192.168.1.1"
setxenv y.subnetmask "255.255.255.0"
net init

i got this from the openazbox forum. here is the rest of the instructions in case you haven't got them. (MY NOTES ARE IN CAPITALS)

here is the link: http://openazbox.info/viewtopic.php?f=8&t=209

Recovery of Azbox Elite, Premium, Premium+ and Ultra when stuck in BOOTING (kernel 3.4.4 inside of your Azbox)
by telesat®

Download the following from this link: http://www.4shared.com/zip/8gEfIi0U/Recovery.html
-TFTPD32
-kernel
-putty

You will also need an USB-to-TTL serial interface for connection with your Azbox.
Use the Internet to buy them, they are cheap and available everywhere, especially on ebay: http://www.ebay.com/sch/i.html?_nkw=usb ... c&LH_BIN=1

First you've got to find out what is IP address of your PC. Click on Start button of Windows, type cmd in Run field and press Enter. Then in command prompt type ipconfig and press Enter. It will list the IP address of your computer.
Let's assume that the IP of your PC is 192.168.1.105
In this case, we have to choose an IP address for your Azbox that will be in the same IP range with a PC, i.e. 192.168.1.112

1. Start TFTPD32

2. Start Putty, switch its option to serial, write in a COM-port number that's assigned to your USB-to-ttl serial interface, in Speed option put 115200.

3. Connect USB-to-TTL serial interface to Azbox.
Make sure that you connect ONLY RX, TX and GND. Do NOT connect VCC because you may fry your Azbox!
Use the following photos (courtesy of Hectore and Pr2) to determine where is the connector in your Azbox:

4. Power on your Azbox.

5. Press CTRL+C on your PC in order to cancel booting.

6. Type:

setxenv y.ipaddr "192.168.1.112"
setxenv y.gateway "192.168.1.1"
setxenv y.subnetmask "255.255.255.0"
net init

load -b tftp://192.168.1.14/kernel1 0xb0100000 (THE FILE I DOWNLOADED WAS CALLED KERNEL AND NOT KERNEL1)
(!!!!! WHEN THIS FINISHES MAKE A NOTE OF THE LENGTH WHICH WILL BE IN THE FORMAT 0x6....)

pflash write -f 0x80000 0xb0100000 0x6AAAA - this 6AAAA overwrite with info of the length... so, when you issue previous command load -b... and when it completes the loading process, it will give you a length info which you have to put at the end of this line, instead of 0x6AAAA

(I DIDN'T HAVE TO DO THIS AS IT WAS WORKING ALREADY)
Switching to Licensed Kernel:

setxenv y.start "xrpc 0xac080090; load zbf 0xb3000000; go"
If you have flashed the new kernel 3.4.4 and something went wrong, then load the Kernel RTi 1.7.0 (available at link at the top!) and issue the command above.

shinobi

jolatacqce wrote: »

Thank you Shinobi,I'v the AZ connected to the modem,and it is also connected to the laptop with the serial cable,is this correct?

Yes this is correct. To ping means your sending a call to a specific IP address. so something like 192.168.0.99 say for example should be free, Unless you have it otherwise configured or have 98 other devices connected to the modem.

Something simple to try might be to reboot the modem as possibly over time some addresses may have been taken.

Something else which may help, as it caught me out when I was doing it, make sure the Ethernet connection goes into the firs free slot on the back of the modem. Once the modem end of it is sorted the recovery is pretty plain sailing. Keep us informed how you get on & good luck!

jolatacqce

thank you,Tapfit&Shinobi,great info.,will give it a go later & report back.

jolatacqce

I'v reached step5. Loading and Starting Rescue Linux.More advice needed,this is where I'm at now,'YAMON> load -b tftp://192.168.1.99/vmlinux.bin 0x90020000
About to load tftp://192.168.1.99/vmlinux.bin
Press Ctrl-C to break

Error : Internal, code = a038'
What to do now?

jolatacqce

YAMON> load -b tftp://192.168.1.14/kernel 0xb0100000
About to load tftp://192.168.1.14/kernel
Press Ctrl-C to break
................................................................
................................................................
................................................................
...............

Start = 0xb0100000, range = (0xb0100000,0xb077cfff), format = BINARY
Length = 0x67d000 (6803456)
Checksum = 0xd0afa4d7

YAMON> go
em86xx_eth ethernet stop

* Exception (user) : Reserved instruction *
BadVAddr = 0xfffa6691 Cause = 0x30800028
Compare = 0xffffffff Config = 0x80200483
Config1 = 0xbed96c8e Config2 = 0x80000000
Config3 = 0x00000020 Context = 0xfffffd30
Count = 0x23be3141 DEPC = 0xfffbddf3
Debug = 0x0e011439 EBase = 0x91000000
EPC = 0xb0100000 EntryHi = 0x9007c000
EntryLo0 = 0x00000000 EntryLo1 = 0x00000000
ErrorEPC = 0x7ffffffb HWREna = 0x00000000
Index = 0x80000000 IntCtl = 0x00000000
PRId = 0x00019069 PageGrain = 0x00000000
PageMask = 0x00000000 Random = 0x00000019
SRSCtl = 0x00000000 SRSMap = 0x00000000
Status = 0x00009c02 WatchHi = 0x80000000
WatchLo = 0x00000000 Wired = 0x00000000
Hi = 0x0000002e Lo = 0x76c8b462

$ 0(zr):0x00000000 $ 8(t0):0x00000000 $16(s0):0x00000000 $24(t8):0x00000000
$ 1(at):0x00000000 $ 9(t1):0x00000000 $17(s1):0x00000000 $25(t9):0x00000000
$ 2(v0):0x00000000 $10(t2):0x00000000 $18(s2):0x00000000 $26(k0):0x00000000
$ 3(v1):0x00000000 $11(t3):0x00000000 $19(s3):0x00000000 $27(k1):0x910f8f20
$ 4(a0):0x00000001 $12(t4):0x00000000 $20(s4):0x00000000 $28(gp):0x00000000
$ 5(a1):0x910fa220 $13(t5):0x00000000 $21(s5):0x00000000 $29(sp):0x91105520
$ 6(a2):0x9107b4f8 $14(t6):0x00000000 $22(s6):0x00000000 $30(s8):0x91105520
$ 7(a3):0x10000000 $15(t7):0x00000000 $23(s7):0x00000000 $31(ra):0x91045614

em86xx_eth ethernet start
YAMON>
I seem to have made a little progress since post #9,but this is not the reply Iwas hoping for from YAMON. HELP.

shinobi

tapfit2004 wrote: »

Recovery of Azbox Elite, Premium, Premium+ and Ultra when stuck in BOOTING (kernel 3.4.4 inside of your Azbox)
by telesat®

Download the following from this link: http://www.4shared.com/zip/8gEfIi0U/Recovery.html.

Are you using this Kernel that tapfit2004 put the link up for?
If not transfere these files to the box using Filezilla and repeat instructions from there.
It may be that you are trying an earlier kernel version than the one already on the box.
Kernel may be named slightly different, ie kernel1 or kernel_334 etc. Just to bear this in mind when completing the load command.

jolatacqce

filzilla is unable to connect to 192.168.1.99

jolatacqce

Yes I'v downloaded that kernel from the link given by Tapfit,and I'v followed the instructions to the point where Iget the following from Yamon,
YAMON> setxenv y.ipaddr 192.168.1.99
Original value: "192.168.1.99", New value: "192.168.1.99"
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setxenv y.gateway 192.168.1.1
Original value: "192.168.1.1", New value: "192.168.1.1"
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setexenv y.subnetmask255.255.255.0
Error : Command not found : setexenv
YAMON> setxenv y.subnetmask 255.255.255.0
Original value: "255.255.255.0", New value: "255.255.255.0"
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> net init
Ethernet driver for EM86XX (v1.0)
(MAC 00:02:14:15:49:57, tx_desc/rx_desc = 16/32)
em86xx_eth::open(em86xx_eth) - Full-duplex mode
em86xx_eth::open(em86xx_eth) - 100 Mbit/s
em86xx_eth ethernet start
ipaddr: 192.168.1.99
subnetmask: 255.255.255.0
gateway: 192.168.1.1
YAMON> load -b tftp://192.168.1.14/kernel 0xb0100000
About to load tftp://192.168.1.14/kernel
Press Ctrl-C to break
Error : TFTP READ-REQ timeout ERROR
Hint : Check TFTP-server is up and running, or try command "net down"/"net up"
YAMON> load -b tftp://192.168.1.14/kernel 0xb0100000
About to load tftp://192.168.1.14/kernel
Press Ctrl-C to break
................................................................
................................................................
................................................................
...............
Start = 0xb0100000, range = (0xb0100000,0xb077cfff), format = BINARY
Length = 0x67d000 (6803456)
Checksum = 0xd0afa4d7
YAMON>
I don't seem to be able to make any progress from here,all advice welcome.

shinobi

jolatacqce wrote: »

filzilla is unable to connect to 192.168.1.99

Filezilla worked ok earlier on I take it? There are 2 files you need to transfer each time you do this procedure.
If it did then reboot the box & start from scratch.
I'll look for the instructions I used & upload them to a file server, most probably get around to doing it in the morning as I'm not using that PC at the moment.

jolatacqce

Thank you shinobi,as regards rebooting the box,the problem is, its still stuck in booting,I'v been at this since this afternoon ,I think I'll give it a break now,the eyes are getting sore,I'll check back here tomorrow,thank you again.

jolatacqce

Back again,still 'stuck in booting',been trying to follow Tapfit& Shinobi's instructions but with no joy.I found much the same instructions in,'RecoverAZbox kernel344',tried that with the following results: YAMON> setenv ipaddr 192.168.1.19
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setenv subnetmask 255.255.255.0
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setenv gateway 192.168.1.254
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> net init
Ethernet driver for EM86XX (v1.0)
(MAC 00:02:14:15:49:57, tx_desc/rx_desc = 16/32)
em86xx_eth::open(em86xx_eth) - Full-duplex mode
em86xx_eth::open(em86xx_eth) - 100 Mbit/s
em86xx_eth ethernet start
ipaddr: 192.168.1.19
subnetmask: 255.255.255.0
gateway: 192.168.1.254
YAMON> net up
em86xx_eth ethernet start
YAMON> ping 192.168.1.19
.
64 bytes ICMP-ECHO-REPLY user data received from 192.168.1.19
YAMON> load -b tftp://192.168.1.19/vmlinux.bin 0x90020000
About to load tftp://192.168.1.19/vmlinux.bin
Press Ctrl-C to break
Error : Internal, code = a038
YAMON>
Perhaps someone with more experience could take a look at the above and spot where I'm going wrong,bearing in mind,I'v not used putty or pumkin prior to this.

tapfit2004

jolatacqce wrote: »

Back again,still 'stuck in booting',been trying to follow Tapfit& Shinobi's instructions but with no joy.I found much the same instructions in,'RecoverAZbox kernel344',tried that with the following results:


Error : Internal, code = a038
YAMON>

here is a link on satpimps about getting an error code same as you have. he said it was a problem with tftp not talking to putty. maybe try the pumpkin program that wouldn't work for him.

http://www.satpimps.com/showthread.php?149953-serious-help

here is a link from another forum but its in greek and i don't know if it has a solution. worth a look anyway.

http://www.avclub.gr/forum/printthread.php?t=48502&pp=10&page=332

jolatacqce

thank you Tapfit,I'll check those links and report back later.

endap

would anyone here repair an elite stuck on booting. Id pay of course.!