PDA

View Full Version : How to recover azbox stuck in booting



majz
02-06-2011, 01:06 PM
Here is a excellent manual to recover an Azbox stucked in booting, most of the time caused after trying to upgrade your Azbox to Enigma 2.
This works I repaired my azboxhd by following the manual.
All the files you need to repair all azboxes but you need to buy some hardware cost around 20 to 30euros, where to buy and how to install are discribed in the manual, also all the programs to use are in the rar file


Good Luck
:king-042:
to mods please make this a sticky
:respect-067:

MbTsM
16-06-2011, 11:03 PM
what about nokia ca-42:confused:

majz
20-06-2011, 10:56 AM
what about nokia ca-42:confused:
What about IT?
this is the azbox section

pr2
20-06-2011, 01:52 PM
what about nokia ca-42:confused:

Hi,

The procedure to follow is exactly the same, if you can make work you CA-42 cable to display the boot process and press CTRL-C while Yamon boot, all the rest is the same.

I only explain with USB since most modern PC no longer have a serial port.

Pr2

MbTsM
20-06-2011, 04:26 PM
ok
i used cable nokia dku-5 it work but cannot stop process c+ctrl
i want buy ca-42 what difference between nokia dku-5 vs nokia ca-42 ??
check the video youtube it is used ca-42
http://www.youtube.com/watch?v=lSsYPleck-o

iq180
18-07-2011, 03:40 PM
i used the usb 2.0 ttl uart serial converter and made my wires for it,if you go this way
remember that the send wire from the usb goes to the recive pin of the reciver and
the recive wire from the usb goes to the send pin on the reciver and ground goes to
ground / only 3 wires used from the usb to the reciver / and i used a rj 45 crossover
cable.
you must be fast with the key board to stop the process if it dont stop you will need to start over and be ready to stop it fast.

pubs
03-10-2011, 11:38 PM
Hi
I also use the usb 2.0 TTL but if i cross the rx and tx i get nothing however if i leave tx-tx and rx-rx i can get into yamon. Once in yamon all the commands go through fine and pumpkin loads vmlinux.bin but when i type the go command i get different results and errors, i have actually got to the login prompt twice but the cursor then freezes. Any help would be great

em86xx_eth ethernet stop
Linux version 2.6.22.19-19-the_ripper (root@debian) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #185 PREEMPT Mon May 31 16:44:40 CEST 2010
Configured for SMP863x (revision ES6+/RevA+), detected SMP8634 (revision ES9/RevC).
Detected CPU/System/DSP Frequencies: 347.62/231.75/347.62MHz
SMP86xx Enabled Devices under Linux/XENV 0x48000000 = 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
Valid MEMCFG found at 0x10000fc0.
CPU revision is: 00019069
Determined physical RAM map:
memory: 06be0000 @ 10020000 (usable)
User-defined physical RAM map:
memory: 06ae0000 @ 10020000 (usable)
Wasting 2098176 bytes for tracking 65568 unused pages
Initrd not found or empty - disabling initrd
On node 0 totalpages: 92928
DMA zone: 726 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 92202 pages, LIFO batch:31
Normal zone: 0 pages used for memmap
Built 1 zonelists. Total pages: 92202
Kernel command line: mem=107m console=ttyS0,115200
Primary instruction cache 16kB, 2-way, physically tagged, linesize 16 bytes.
Primary data cache 16kB, 2-way, virtually tagged, cache aliases, linesize 16 bytes
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
Using 173.813 MHz high precision timer.
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 96384k/109440k available (4018k kernel code, 12948k reserved, 1013k data, 4408k init, 0k highmem)
Calibrating delay loop... 343.04 BogoMIPS (lpj=171520)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
tangox: creating TLB mapping for 0x20000000 at 0xc0000000, size 0x08000000.
PCI: Initializing SMP86xx PCI host controller
PCI: Remapped PCI I/O space 0x58000000 to 0xc8020000, size 64 kB
PCI: Remapped PCI config space 0x50000000 to 0xc8004000, size 10 kB
PCI: device 1 disabled
PCI: device 4 disabled
PCI: Configured SMP86xx as PCI slave with 128MB PCI memory
PCI: Region size is 16384KB
PCI: Map DMA memory 0x10020000-0x16b00000 for PCI at 0x11000000
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Time: TANGOX clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
CPU 0 Unable to handle kernel paging request at virtual address 56a77b10, epc == 9050cfe8, ra == 9050d3b8
Oops[#1]:
Cpu 0
$ 0 : 00000000 96aa0000 56a77b08 00000008
$ 4 : 00000063 00000001 00000009 002605ba
$ 8 : 00000001 00426810 90960000 56a77b10
$12 : 90532000 00426810 90960000 9040f188
$16 : 00000003 000003b7 00000000 00000146
$20 : 90960000 00000005 00000001 90960000
$24 : 00000010 9007fb0c
$28 : 90ce2000 90ce3e58 0000000f 9050d3b8
Hi : 2a7c871d
Lo : fde56be0
epc : 9050cfe8 inflate_codes+0x1bc/0x5bc Not tainted
ra : 9050d3b8 inflate_codes+0x58c/0x5bc
Status: 10001c03 KERNEL EXL IE
Cause : 70808008
BadVA : 56a77b10
PrId : 00019069
Modules linked in:
Process swapper (pid: 1, threadinfo=90ce2000, task=90ce1898)
Stack : 0000000b 00000000 96a768fc ffffffff 0000003f 000001ff 90960000 9040f188
00000000 96a62000 00000011 90960000 90960000 0000011e 0000001e 90960000
90960000 9050e664 96a6c008 96a59808 00000009 00000006 9040f268 96a27284
90ce3ecc 900ea160 96a6c008 96a59808 00000009 00000006 90960000 90532000
00000000 9052fdc0 00000000 00426810 90960000 90532000 00000000 00000000
...
Call Trace:
[<9050cfe8>] inflate_codes+0x1bc/0x5bc
[<9050e664>] inflate_dynamic+0x5f8/0x63c
[<9050f1d8>] unpack_to_rootfs+0x95c/0xa94
[<9050f33c>] populate_rootfs+0x2c/0xd8
[<9050b37c>] kernel_init+0xd4/0x338
[<90028d00>] kernel_thread_helper+0x10/0x18


Code: 00a31824 000318c0 00435821 <91680000> 2d020011 1040002b 00a08821 ae87906c 91620001
Kernel panic - not syncing: Attempted to kill init!



This is one of the errors

Thanks

Pubs

muja
04-10-2011, 07:53 PM
Who has deleted my previus post??have to repeat qustion again..
Can not execute CTRL+C to(brake) Yamon,so...can anyone help me out mates.Folowed this wery god guide til that ctrl+c thingy and simply can not do that!!Any workaround for this??
Thanks in advance.

muja
05-10-2011, 11:04 AM
And this is what i get:
xosPe0 serial#14ff872bd23dd7a2c0b570171f 6866a4 subid 0x50
xenv cs2 ok
xosPe0 serial#14ff872bd23dd7a2c0b570171f 6866a4 subid 0x50
xenv cs2 ok
power supply: failed
dram0 ok (7)
dram1 ok (9)
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/0x000b7787).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a7676).
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:27:e1
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.

cxrpc failed (9)--- if a xtask is using a cipher or if you reboot
--- xrpc will fail with RM_BUSY
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff
YAMON


help mates if you can ofcourse.
thanks in advance

Blagi
05-10-2011, 12:46 PM
Who has deleted my previus post??have to repeat qustion again..
Can not execute CTRL+C to(brake) Yamon,so...can anyone help me out mates.Folowed this wery god guide til that ctrl+c thingy and simply can not do that!!Any workaround for this??
Thanks in advance.

Hi, muja!

Try this, post no. 18 and be fast when you're doing it: http://www.satpimps.co.uk/showthread.php?150610-Two-types-of-problems-with-installation-and-how-to-solve-them...

And do tell if you succeeded, please! It would be important to know!!!:)

Good luck!:coolgleamA:

muja
05-10-2011, 01:15 PM
Thanks mate,no joy whatsoewer,thanks gain.

snakemetal
04-11-2011, 12:18 PM
I have just bought a zxbox elite from **** with the fault booting
Im aware ill probably have to do the usb to ttl but i thought ill give the patch.bin on a usb a try

what worries me is i get nothing on the screen
the azbox says powering on then booting but my screen says no hdmi input, so the box is not outputting anything
my usb stick doesnt light up to say its being accessed either?

Is this all normal or am i looking at a box that is unrecoverable even via the usb to ttl methord?

thanks

Burnham
04-11-2011, 02:20 PM
Probably won't work, but try all the other possible outputs - Scart - RF Modulator - video phono output - Component

iq180
04-11-2011, 03:07 PM
snakemetal the usb to ttl will work but what i want to know is where did you get a azbox that was stuck in booting, i have been looking for 3 of them to test, i have recoverd 5 of them that were stuck in booting and would like to find some more
to test and work on. the usb wont power up if the azbox is in booting but if you could find a way to power up the usb then
it mite load but i have not tested that at this time.

bundersuk
10-12-2011, 06:59 PM
Brilliant tutorial. Worked a treat i now have Update:USB on the display of my Premium box instead of BOOTING. I used a usb to ttl converter that i bought from your favourite ******* site for £5. I had the tx and rx crossed at first but didnt work i had to put the rx pin of azbox to rx pin of ttl converter and the same for tx.

Cant thank you enough, cheers.

Blagi
10-12-2011, 11:03 PM
Wow! That is contrary to everything people have been telling us to do forever...

I wonder how is that possible?

bundersuk
11-12-2011, 07:45 AM
I dont know Blagi. Im sure i read it somewhere to try it. The crossover of tx to rx didnt work for me so i thought id give it a go and it worked first time in PUTTY.

Blagi
11-12-2011, 09:38 AM
Of course, I am happy it did!

Just asking how come, for all those who couldn't get it going.

Some even reported messed up units, if I remember correctly, when they "misconnected them"...

Boy, is this box full of surprises or what?!?

medonjonjo
22-12-2011, 04:42 PM
I am also have Azbox Elite on Booting 4 months. I tried with TTL cable and I have this:

xosPe0 serial#820febe7f9abab9f5e08fd3d33 fd0e73 subid 0x50
xenv cs2 failed
xenv cs3 failedĄřpower supply: ok
dram0 ok (9)
zboot (1) failed

Is there any news?
Please help.

ManikM
23-12-2011, 03:23 AM
its deffo tx to tx and rx to rx

medonjonjo
23-12-2011, 06:24 PM
Blagi have you tried this how says Bundersuk and ManikM?
Has anyone tried it so.
Thank you.

Blagi
23-12-2011, 08:58 PM
No, I haven't. Thankfully, there was no need to...

raullo
04-02-2012, 08:17 PM
Brilliant tutorial. Worked a treat i now have Update:USB on the display of my Premium box instead of BOOTING. I used a usb to ttl converter that i bought from your favourite ******* site for £5. I had the tx and rx crossed at first but didnt work i had to put the rx pin of azbox to rx pin of ttl converter and the same for tx.

Cant thank you enough, cheers.

Thanks a lot for that advice. Worked for me too that way. Regards

bozo
13-02-2012, 04:12 PM
i am trying to recover an azbox premium stuck on bootup but when click open on putty and switch on azbox i get this message from putty:

yxosPc0 serial#e153f9baec7f4e68ad9aefa392 582dce subid 0xc4
xenv cs2 ok
Power supply: FAIL

any help will be very appreciable

ManikM
13-02-2012, 06:07 PM
the guide is amazing, cant beleive how helpful it is! brought a dead az back to life !

never trying that AZTRINO nonsense again.

carshalton
13-02-2012, 08:45 PM
My Az Box was stuck on wizard zamba and not booting up.Found official firmware on a italian az box forum .File was in rapidshare.Downloaded it and booted up usb stick.Had option to format which I did first.I then put usb stick back in and used update option.Az box then updated and started working normally.
If you dont format nothing happens.Use at own risk.

niallerf2
18-02-2012, 04:16 PM
Hi Muja,

I get the exact same error in Putty as you. Have been trying to recover my Azbox. I have followed the full instructions, however that is the result I get. I have tried 3 times now and get the same result each time. Any suggestion? We're you able to resolve this issue? Any help would be appreciated

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.

xrpc failed (9)--- if a xtask is using a cipher or if you reboot
--- xrpc will fail with RM_BUSY
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff

thanks
niall

ManikM
18-02-2012, 05:07 PM
it does say in the guide, that if you get anything other than a certain error\code, then the process is no good, and its bricked.

neo.70
18-02-2012, 07:32 PM
i was getting the ffffffff error with windows 7, i kept trying and by chance it worked all of a sudden, don`t know whether it was a windows 7 problem or not, do you use windows 7?, and make sure all firewalls are off.

majz
09-04-2012, 11:29 AM
the yamon in the flash mem is damaged which means you cannot use any of the files to repair it if tou are a electronic wizard then ok you need to jtag the chip if not it looks like you need to send the box back to where you bought it from first you must go to this site and make out a work ticket they are very helpfull

http://www.azbox.com

gorgeit
12-09-2012, 12:13 PM
xosPe0 serial#820febe7f9abab9f5e08fd3d33 fd0e73 subid 0x50
xenv cs2 failed
xenv cs3 failedĄřpower supply: ok
dram0 ok (9)
zboot (1) failed

Is there any news?
Please help.

I have the same issue is there an alternative other than the jtag solder or
Returning to opensat .
Thanks

pr2
28-09-2012, 09:56 AM
Hi,

For people that follow this recovery procedure, the provided kernel is an old one.
Since they change the boot parameter in Yamon when you are in Yamon, you need to type this command to restore "old kernel" boot parameter otherwhise your Azbox will not boot the old kernel.



setxenv y.start "xrpc 0xac080090; load zbf 0xb3000000; go"


Remark: to boot kernel 3.4.4 and 3.5.5 the value is:



setxenv y.start "dump romfs 0xac080000;load zbf 0xac080090; go"


Hope this help,

Pr2
P.S.: May I suggest to moderator to include this in the first post.

ManikM
01-11-2012, 08:42 PM
twice now this guide has saved my azbox! top guide, a little confusing at times, but not that hard

boc555
05-11-2012, 10:55 PM
the yamon in the flash mem is damaged which means you cannot use any of the files to repair it if tou are a electronic wizard then ok you need to jtag the chip if not it looks like you need to send the box back to where you bought it from first you must go to this site and make out a work ticket they are very helpfull

http://www.azbox.com

are there any tutorials/video clips out there on jtag-ing the chip - i found one on youtube in relation to the dm box - but cant find any for the azbox - thanks

Discovery28
12-11-2012, 03:37 PM
are there any tutorials/video clips out there on jtag-ing the chip - i found one on youtube in relation to the dm box - but cant find any for the azbox - thanks
Please try again with another cable or adapter, if it is possible with Nokia cable, since you have zboot OK. "Checking zboot file signature at 0x13000000 .. OK " Could be conexion problem.

If not you can follow the spanish instruccion of this tutorial.: http://openspa.info/threads/tutorial-recuperar-deco-en-booting-via-jtag.12602/

Discovery28
12-11-2012, 11:43 PM
are there any tutorials/video clips out there on jtag-ing the chip - i found one on youtube in relation to the dm box - but cant find any for the azbox - thanks

You could read the solution here :
http://www.satpimps.co.uk/showthread.php?158389-ha-ha-ha-he-he-he-my-azbox-booting-did-not-beat-me-!!!!!!!

arthurbf
14-11-2012, 10:21 PM
This is what I get:

ĢxosPe0 serial#94fa0efeecaed757143d3c8d1d 0e876b subid 0x50
xenv cs2 failed
xenv cs3 failed°√xosPe0 serial#94fa0efeecaed757143d3c8d1d 0e876b subid 0x50
xenv cs2 failed
xenv cs3 failed°√xosPe0 serial#94fa0efeecaed757143d3c8d1d 0e876b subid 0x50
xenv cs2 failed
xenv cs3 failed°√power supply: failed
dram0 ok (8)
zboot (1) failed

Discovery28
17-11-2012, 09:01 PM
arthurbf, you have to use JTAG.

asgeir
28-12-2012, 03:44 PM
Hi, can someone help me on this?

I have a AZbox premium HD that is stuck in booting. I've connected a serial to the Yamon interface and used 115200 bits/sek but the outcome from Putty is not readable (see image)

55937

I've also tried all the other bits/sec setting but none is readable. Anyone familiar with this?

voki081
29-12-2012, 11:14 PM
Try to change RX and TX

pr2
30-12-2012, 12:09 AM
This is clearly explained in the tutorial, wrong speed/parity settings in your PC for your cable adaptor... please read the manual, don't think that some step are useless...

asgeir
30-12-2012, 06:11 PM
My problem was that I used serial cable directly to the AZbox, not TTL. All the settings were correct. Bought MAX232 and build a RS232 to TTL converter and after that it worked.

ManikM
26-01-2013, 02:02 PM
yes twice now ive recovered my azbox

the unit on famous orkshon site works very well
item number: 320923619625

dito1313
27-01-2013, 10:23 PM
Hello everybody,

I need some help from you
I have my Azbox stuck in booting... I am following all the steps from the manual and in the last one, the one to load the firmware when I type ./update backup_kernel_344 I always have return "segmentation fault"

I have no more ideas and I canīt find information about it.

Thank you very much

gorgeit
12-02-2013, 07:23 PM
my azbox hd was in need of jtag considered sending to holland but i found a service on a well known
******* site , sent it off and it came back quick and fixed . .
thanks ryan a job well done mate

xanadu
12-02-2013, 10:18 PM
For less than £5 I am making my own JTAG adapter, but if you are not sure what you are doing then probably better to take a chance on a flea bay site repair seller.

GreenSmurf
05-04-2013, 10:48 AM
Hi,

Azbox Premium Plus

I've got the 'stuck in booting' problem after trying to downgrade from RSiOpen v3 to v2. I sourced a cable (I'll post details if anyone is interested) downloaded the excellent tutorial and got all the way to the end when the box is supposed to restart, which it does with the following output from YAMON..

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

ROMFS found at 0xac080000, Volume name = MIPS_LINUX_XRPC
ac080040 : Name = ., Type = dir, Size = 00000000, Next = 00000040
ac080060 : Name = .., Type = hard link, Size = 00000000, Next = 00000060
ac080090 : Name = xrpc_xload_vmlinux_ES4_prod.bin, Type = file, Size = 0064bf44, Next = 00000000
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff
YAMON>

Can anyone shed any light on the above? I get the feeling I'm so near and yet so far...

Thanks for any help.

pr2
05-04-2013, 12:41 PM
Hi,

Do you reflash the old kernel?

To boot the old kernel you can type this in Yamon:



setxenv y.start "xrpc 0xac080090; load zbf 0xb3000000; go"


Power off the box and restart it, if you flash the old kernel it will start.

You will then problably need to stop it in Rescue Mode (by pressing the VOL+ front pannel button).

Then you can flash an old firmware.

But what a strange idea to return to OpenRSI 2

Pr2

GreenSmurf
06-04-2013, 10:06 AM
pr2 you are a star! Your string of gobbledegook allowed me to get into update mode. I installed an OFW which with hindsight was not a good idea but it allowed me to do an automatic update via the internet which got me into rescue mode and I was away. Bit convoluted but I'm back in business. The reason I wanted to 'downgrade' from RSi v3 to v2 was because of various bugs (green screens, refusing to play some .avi files, TV freezing, lots of gearwheels...) so I did some research on the RSiOpen forum to find that v2 was better for the older Azboxes so I thought I'd give it a go but apparently you are supposed to go via an intermediate stage which I didn't do. I'm still testing, but a video file that previously failed to run ran OK last night, so we'll see. It's complicated in the Azbox world....

Just out of interest, if it's not too complicated, what did your command line do...

Many thanks pr2

Ghanooo
10-08-2013, 12:56 PM
thanks for this i will try it