PDA

View Full Version : azup: File Not Found-Unable to...



slarva
25-10-2010, 07:32 PM
Hello,

I have Azbox HD Premium.
Latest original firmware.
Rebooted with usb stick (fat32) with new E2 (.27) patch.bin image.
Installed E2 from usb stick
rebooted
Got IP on display
Ran azup 1.1 and got "Rescue mode ok" and "Patch.cramfs created"
and then "File Not Found-Unable To Complete Request"

I can do recovery only manually to original firmware like this:
mkdir /hdb
mount /dev/hdb1 /hdb
dd if=/hdb/patch.bin of=/hdb/patch.cra bs=56 skip=1
then will be the cramfs be mounted whith loop
mkdir /Patch
mount -o loop /hdb/patch.cra /Patch
dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024

Can somebody help with this problem?

mounirmoune12
25-10-2010, 09:13 PM
I have the same problem plz help:confused:

fishdevil
25-10-2010, 09:38 PM
Hi just leave usb in receiver with e2 patch then reboot box, run azup again. this worked for me as I had same problem. Hope this helps?

slarva
26-10-2010, 05:40 PM
With orginal firmware setup > datareset > factorysettings
boot box with usb stick (e2)
format application area
install E2

This worked for me
Thanks to Team for wonderful work

mounirmoune12
26-10-2010, 06:29 PM
I tried all fw but nothing work can you explain more what do you mean bay setup > datareset > factorysettings
:001_302:

slarva
26-10-2010, 06:50 PM
When you are running original firmware not e2
select setup
select "settings"
select "datareset"
and then select "factoryreset"

mounirmoune12
26-10-2010, 08:10 PM
not i am stuck i cant install fw . i got Azup error :"File Not Found-Unable To Complete Request"

mounirmoune12
26-10-2010, 09:01 PM
my azbox don all the steps but my problem is azup error

(file not foond unable to complete rquest). i tried all fw, unstall and install azup and used tow usb stick one formated fat 32 and one ntcs , windows vesta and xp.
nothing work and i dont know what to do .3 days no tv so far

pls help

slarva
26-10-2010, 09:07 PM
You can recovery manually to original firmware like this, you must have harddisk inside the box and original patch.bin (copy it with ftp program like FileZilla) in there too:
telnet (use Putty or something else) to box
mkdir /hdb
mount /dev/hdb1 /hdb
dd if=/hdb/patch.bin of=/hdb/patch.cra bs=56 skip=1
then will be the cramfs be mounted whith loop
mkdir /Patch
mount -o loop /hdb/patch.cra /Patch
dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
reboot box

If you don't have internal harddisk in the box then you can do it with usb stick. I have not tested recovery with usb stick.

Please be carefully with these commands...
I hope this helped...

mounirmoune12
26-10-2010, 10:25 PM
HI! Slarva thanks for replay
are you shore about last command?


> # dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
> dd: can't open '/Patch/FLASH/loader.bin': No such file or directory
-sh: dd:: not found
# # dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
# dd: can't open '/Patch/FLASH/loader.bin': No such file or directory
> # dd if=/Patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
> dd: can't open '/Patch/FLASH/loader.bin': No such file or directory
-sh: dd:: not found

mounirmoune12
26-10-2010, 11:08 PM
Powered by The Ripper, telesat && MickeySa ;)
Linux/mips 2.6.22.19-19-the_ripper

(none) login: root
Password:
# mkdir/hdb
-sh: mkdir/hdb: not found
# mkdir /hdb
# mount /dev/hdb1 /hdb
mount: mounting /dev/hdb1 on /hdb failed: No such device or address
# dd if=/hdb/patch.bin of=/hdb/patch.cra bs=56 skip1
BusyBox v1.16.1 (2010-05-23 13:26:55 CEST) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

Options:
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

# mkdir /patch
# mount -0 loop /hdb/patch.cra /patch
mount: invalid option -- 0
BusyBox v1.16.1 (2010-05-23 13:26:55 CEST) multi-call binary.

Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE

Mount a filesystem. Filesystem autodetection requires /proc.

Options:
-a Mount all filesystems in fstab
-f Dry run
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification time
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a file or directory to another location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing flags
ro/rw Same as -r/-w

There are filesystem-specific -o flags.

# dd if=/patch/FLASH/loader.bin skip=512 of=/dev/mtdblock4 bs=1024
dd: can't open '/patch/FLASH/loader.bin': No such file or directory
# dd if=/patch/FLASH/loader.bin skip=512 of=/dev//mtdblock4 bs=1024

slarva
27-10-2010, 06:17 PM
[mount: mounting /dev/hdb1 on /hdb failed: No such device or address]

You don't have harddisk in the azbox?
If you don't have harddisk then you have to do those mount operations to usb stick.
What gives "dmesg |grep hd" and "cat /proc/partitions" ?

zfeet
27-10-2010, 07:00 PM
Copied from another thread:

I had the same issue when Azup was installed in the default location in Program Files. Copy AZUp.exe from "C:\Program Files\telesat\AZUp" to a different location (for example c:\azup\AZUp.exe" and run as Administrator.