Wow! That is contrary to everything people have been telling us to do forever...
I wonder how is that possible?
Wow! That is contrary to everything people have been telling us to do forever...
I wonder how is that possible?
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.
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?!?
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.
its deffo tx to tx and rx to rx
Blagi have you tried this how says Bundersuk and ManikM?
Has anyone tried it so.
Thank you.
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
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.
Remark: to boot kernel 3.4.4 and 3.5.5 the value is:Code:setxenv y.start "xrpc 0xac080090; load zbf 0xb3000000; go"
Hope this help,Code:setxenv y.start "dump romfs 0xac080000;load zbf 0xac080090; go"
Pr2
P.S.: May I suggest to moderator to include this in the first post.
Last edited by pr2; 23-11-2012 at 06:16 PM. Reason: Mention that kernel 3.5.5 use same values as 3.4.4
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.
No, I haven't. Thankfully, there was no need to...
the guide is amazing, cant beleive how helpful it is! brought a dead az back to life !
never trying that AZTRINO nonsense again.
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.
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.
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.
twice now this guide has saved my azbox! top guide, a little confusing at times, but not that hard
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
arthurbf, you have to use JTAG.
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)
Putty.JPG
I've also tried all the other bits/sec setting but none is readable. Anyone familiar with this?
Try to change RX and TX
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...
Bookmarks