serious help

[sperr1]

pls help my azbox is stuck in booting and i no buy reading posts that involves cables and leads which i am not good with.does anyone no a simple way to flash the box or anywhere i can send it to get it fixed pls help thanks

[Carp95]

There's no other way

I could help you but i'am on the main land that means you have to ship it. ( Holland )

I'am shure there are people in the UK wich could help you

[beamobhoy]

Doesn't necessarily mean your azbox is bricked. What have you done to get to that stage? Describe what exactly you have been doing/trying to do then you'll get help from the multitude of experts on this site.

[sperr1]

i had rti core v1.0 fix on i then used jazup 2.3 to flash back to original then rienstalled rti core one on no prob. when i went to put the new spaze team image on the progress bar on jazup stuck on about 25%, i left it for an hour still no progress so rebooted the box now it is stuck on booting

[xanadu]

This can often be fixed with USB stick installed with an old original FW patch.bin.

If you leave the USB in long enough it takes you to the original Azbox boot menu.

Can you get this far?

[sperr1]

will try now thanks

[sperr1]

no did not work left it booting for an hour any other way to do it i dont want to throw it in the bin lol

[jimmyjim11]

If your box in still in warranty 2 years you can send it back to opensat for repair

you are trying volume + to try to go in to rescue mode ?

[sperr1]

yes tried that how do i get in touch with opensat do they have an email

[pr2]

Hi,

Please post you JaZUp 2.3 log file.
You can find it in a subfolder log created by JaZUp in the folder where it is started.

Pr2

[sperr1]

JaZUp! By Hectore & Pr2 V2.3 - The safest way to upgrade your Azbox
Running OS : Windows 7
Java Version : 1.6.0_26-b03
Start at 27/06/2011 @ 20:36:54




Powered by The Ripper, telesat && MickeySa ;)

Linux/mips 2.6.29.4-13-the-ripper



(none) login: root
Password:
#
JaZUp! is connected to your AZbox IP: 192.168.1.2

Your AZbox kernel is Enigma2

Your AZbox is in rescue mode
KernelSize -> 6556672

Your AZbox CPU mode is normal

Description Kernel : 2.6.29

FTP sending data kernel...
FTP Connected Send : kernel-jazup
FTP Send is true

FTP Transfer Ok!

Copying kernel (Hot!)... Please wait, this operation takes time!

[sperr1]

sorry thats all ther is it froze as i said

[Carp95]

i had rti core v1.0 fix on i then used jazup 2.3 to flash back to original then rienstalled rti core one on no prob. when i went to put the new spaze team image on the progress bar on jazup stuck on about 25%, i left it for an hour still no progress so rebooted the box now it is stuck on booting

You interrupted the upgrade process, now you can restore by using a usb2serial cable, Pr2 wrote a great How-To

[pr2]

Hi,

Indeed you can only try to recover it with a "Yamon" cable or your Azbox has an hardware problem.
After the operation mentionned in the log, the next step runs on the Azbox itself (kernel flashing is just a dd command that is send). So perhaps that your Azbox had an internal flash problem.

If you are sure that VOL+ trick didn't boot your Azbox in Rescue Mode, then the kernel flashing gets corrupted, so Yamon is the only way and if Yamon method fails too, it is clearly a hardware problem and your Azbox needs repairs by Opensat (you can open a RMA request from their website).

Pr2

[sperr1]

with yamon method not sure what cable to buy do i need UART TTL to serial/USB connector or just TTL232R-5V-WE cable best to give it a go myself eager to learn.

[mirov68]

I buy this cable and it works ok - USB to serial adapter PL2303 TTL console Recovery RS232

[sperr1]

is it just that cable i need.

[mirov68]

yes - do not conect 5V(red wire)

[sperr1]

ok will order one today 2 weeks to come so will update then

[suites]

i am reading this thread with great interest ,i am in much the same position only slightly different,i flashed the box premium hd + and after 30% is stopped . so i followed the post s here and was able to get it back to rescue mode using azup 201 it ***unicated with the box then a little window came up could not write the file this was at the original restore off it worked its way to kernel same message as before coild not file it carried on till it finished and booted itself then back to where it was at the beginning any help please thanks in advance

[wullieb25]

guys if your box is less than two years old take out a line on the azbox website and they'll ask you to send it to them I sent mine it cost 45 pnd for shipping but was worth it

[wullieb25]

sorry forgot to say I'm from the uk

[sperr1]

i have ordered the cable it only cost £7.95 getting shipped from hong kong so it will take 2 weeks i will try the yamon method first cos i like to have a play around with images and i am sure there will be different images out soon so better to learn than to spend £45 pound everytime it bricks lol still the yamon method still might not work lol.

[Dig Deep]

Horrible shipping price I must say

[sperr1]

hi got my cable today but no cable coding i got four wires on the end of the cable not sure which is which

red
black
green
pink

not sure how to connect to azbox any suggestions

[jimmyjim11]

Did you ask the seller ? any pics ?

[sperr1]

no dodnt think to ask will upload i pic now

[sperr1]

heres the pic

[jimmyjim11]

can you see where cables are attached on other side

[Sjaak66]

No schematic attached with the shipment ?
Pretty tricky to do the "trial and error" method :)

[sperr1]

i thought i might seriously damage box if wires are wrong

[jimmyjim11]

Do you have a multimeter ?

you could google RS232 pin out

or try and contact the seller !

[sperr1]

hi problem with connectivity got the cable to communicate but get this




xosPe0 serial#a014bcbf236a562a849bf3e80c 1ce255 subid 0x70
xenv cs2 ok
power supply: ok
dram0 ok (8)
dram1 ok (a)
zboot (0) ok
>
********************************* *****
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use 8KB DRAM as stack.
* Support XLoad format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0/1.
********************************* *****
Boot from flash (0x48000000) mapped to 0x8c000000.
Found XENV block at 0x8c000000.
CPU clock frequency: 300.37MHz.
System clock frequency: 200.25MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000b8888).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a8787).
Using UART port 0 as console.
Board ID.: "852-E2"
Chip Revision: 0x8634:0x86 .. Matched.
Setting up H/W from XENV block at 0x8c000000.
Setting <SYSCLK avclk_mux> to 0x00000000.
Setting <SYSCLK hostclk_mux> to 0x00000100.
Setting <IRQ rise edge trigger lo> to 0xff28ca00.
Setting <IRQ fall edge trigger lo> to 0x0000c000.
Setting <IRQ rise edge trigger hi> to 0x0000009f.
Setting <IRQ fall edge trigger hi> to 0x00000000.
Setting <IRQ GPIO map> to 0x20090820.
Setting <PB default timing> to 0x10101010.
Setting <PB timing0> to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Setting <PB timing1> to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
PB cs config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
MAC: 00:02:14:18:81:b4
PCI IRQ routing:
IDSEL 2: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
IDSEL 3: INTA(#15) INTB(#15) INTC(#15) INTD(#15)
Smartcard pin assignments:
OFF pin = 0
5V pin = 1
CMD pin = 2
Setting up Clean Divider 2 to 96000000Hz.
Setting up Clean Divider 4 to 33333333Hz.
Setting up Clean Divider 5 to 25000000Hz.
Setting up Clean Divider 6 to 20000000Hz.
Setting up Clean Divider 7 to 20000000Hz.
GPIO dir/data = 0x76000038/0x76000000
UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
UART1 GPIO mode/dir/data = 0x6e/0x00/0x00
XENV block processing completed.
Found existing memcfg: DRAM0(0x08000000), DRAM1(0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Default boot index: 0
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
Checking zboot file signature .. Not found.
Trying xrpc_xload format .. OK
Checking zboot file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load time total 173/255 msec.
Execute final at 0x91200000 ..









********************************* *


* YAMON ROM Monitor


* Revision 02.06-SIGMADESIGNS-01-2.8.0.1


********************************* *


Memory: code: 0x11000000-0x11040000, 0x11200000-0x11204000


reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000


Environment variable 'start' exists. After 1 seconds


it will be interpreted as a YAMON command and executed.


Press Ctrl-C (or do BREAK) to bypass this.





YAMON> setenv ipaddrr 192.168.1.9

Updating XENV block at 0x48000000.


.


XENV verification OK.


YAMON> setenv subnetmask 255.5 255.255.0

Updating XENV block at 0x48000000.


.


XENV verification OK.


YAMON> setenv gateway 192.168.1.1

Updating XENV block at 0x48000000.


.


XENV verification OK.


YAMON> net init

Ethernet driver for EM86XX (v1.0)


(MAC 00:02:14:18:81:b4, tx_desc/rx_desc = 16/32)


em86xx_eth: auto-negotiation failed.





em86xx_eth::open(em86xx_eth) - no link


em86xx_eth ethernet start


ipaddr: 192.168.1.9


subnetmask: 255.255.255.0


gateway: 192.168.1.1


YAMON> setenv gATEWAY ateway 192.168.1.3

Updating XENV block at 0x48000000.


.


XENV verification OK.


YAMON> net init

net have been initialized


ipaddr: 192.168.1.9


subnetmask: 255.255.255.0


gateway: 192.168.1.3


YAMON> net up

em86xx_eth ethernet start


YAMON> ping 192.168.1.9

re-configuring ..


em86xx_eth: auto-negotiation failed.





em86xx_eth::open(em86xx_eth) - no link


em86xx_eth ethernet start


no link, please check cable


Error : Internal, code = fffffffb


YAMON>

[sperr1]

silly question but could it be that am using win 7 64 bit

[sperr1]

also looked inside usb connector it is connected green-txd,white-rxd,black-gnd but when i hook it up to the box putty stays blank but when i swap the green and white it connects and ctrl-c works but still get no link grrrr also does the azbox need the ethernet cable connected

[jimmyjim11]

LAN cable required

[sperr1]

ok got ethernet sorted ping test ok but it wont talk to putty just says error any idea

[sperr1]

heres the log



xosPe0 serial#a014bcbf236a562a849bf3e80c 1ce255 subid 0x70
xenv cs2 ok
power supply: ok
dram0 ok (8)
dram1 ok (a)
zboot (0) ok
>
********************************* *****
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use 8KB DRAM as stack.
* Support XLoad format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0/1.
********************************* *****
Boot from flash (0x48000000) mapped to 0x8c000000.
Found XENV block at 0x8c000000.
CPU clock frequency: 300.37MHz.
System clock frequency: 200.25MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a8887).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a8787).
Using UART port 0 as console.
Board ID.: "852-E2"
Chip Revision: 0x8634:0x86 .. Matched.
Setting up H/W from XENV block at 0x8c000000.
Setting <SYSCLK avclk_mux> to 0x00000000.
Setting <SYSCLK hostclk_mux> to 0x00000100.
Setting <IRQ rise edge trigger lo> to 0xff28ca00.
Setting <IRQ fall edge trigger lo> to 0x0000c000.
Setting <IRQ rise edge trigger hi> to 0x0000009f.
Setting <IRQ fall edge trigger hi> to 0x00000000.
Setting <IRQ GPIO map> to 0x20090820.
Setting <PB default timing> to 0x10101010.
Setting <PB timing0> to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Setting <PB timing1> to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
PB cs config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
MAC: 00:02:14:18:81:b4
PCI IRQ routing:
IDSEL 2: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
IDSEL 3: INTA(#15) INTB(#15) INTC(#15) INTD(#15)
Smartcard pin assignments:
OFF pin = 0
5V pin = 1
CMD pin = 2
Setting up Clean Divider 2 to 96000000Hz.
Setting up Clean Divider 4 to 33333333Hz.
Setting up Clean Divider 5 to 25000000Hz.
Setting up Clean Divider 6 to 20000000Hz.
Setting up Clean Divider 7 to 20000000Hz.
GPIO dir/data = 0x76000038/0x76000000
UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
UART1 GPIO mode/dir/data = 0x6e/0x00/0x00
XENV block processing completed.
Found existing memcfg: DRAM0(0x08000000), DRAM1(0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Default boot index: 0
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
Checking zboot file signature .. Not found.
Trying xrpc_xload format .. OK
Checking zboot file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load time total 173/255 msec.
Execute final at 0x91200000 ..









********************************* *


* YAMON ROM Monitor


* Revision 02.06-SIGMADESIGNS-01-2.8.0.1


********************************* *


Memory: code: 0x11000000-0x11040000, 0x11200000-0x11204000


reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000


Environment variable 'start' exists. After 1 seconds


it will be interpreted as a YAMON command and executed.


Press Ctrl-C (or do BREAK) to bypass this.





YAMON> setenv ipaddr 192.168.1.80

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.1

Updating XENV block at 0x48000000.


.


XENV verification OK.


YAMON> net init

Ethernet driver for EM86XX (v1.0)


(MAC 00:02:14:18:81:b4, 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.80


subnetmask: 255.255.255.0


gateway: 192.168.1.1


YAMON> net up

em86xx_eth ethernet start


YAMON> ping 192.168.1.80

64 bytes ICMP-ECHO-REPLY user data received from 192.168.1.80


YAMON> load -btftp tftp://192.168.1.80/vmlinux.bin 0x90020000

About to load tftp://192.168.1.80/vmlinux.bin


Press Ctrl-C to break




Error : Internal, code = a038

[sperr1]

still cant get pumpkin and putty to talk to each other am i doing something wrong followed the guide by pr2 and hectore everthing going to plan until i go to the load command do i have to put the bin file into pumpkin and hit enter on yamon at the ame time cos that is not working someone pls help,my dodgy technomate is starting to play up aswell.

[sperr1]

got my box back my windows does not like pumpKIN for some strange reason used a different tftp client and it worked straight away thanks for all the help guys

[Blagi]

So, how did you get by the usual block, exactly, please?

You know, no response to some commands (CTRL...)...

[sperr1]

ctrl c just worked as i said i opened up the usb plug and looked at the wiring and the circuit board must of been printed wrong cos the green wire was tx but when i used that no ctrl c lol so i swapped them round it was then a matter of trial and error till it worked used pr2s instuctions must just be the way my router has configed my network but my pc does not like pumpkin so i just downloaded tftpd64 then it was all straight forward even put spaze image from ravemaster on working like a charm so far i think i am gonna have to get on to learning linux programming cos as much as it stresses me out i am glad i fixed it myself rather than fork out 50 quid for shipping

[Blagi]

Dig Deep and co. - did you see this? ;)

Good luck! :)

[Dig Deep]

DD is always reading mate.
Could be the reason why I can´t read the screen so I will test it.

[ladioslovakia]

Hi All

I have the same Problem

"Error : Internal, code = a038"

I have Restartrouter , I take another PC and DONE .

Im already on OpenRSI 2.1 and works fine .

Nice day !!!