JaZUp 2.0 & RC12

Hello,

For update with JaZUp 2.0 use 'Update E2' button for the first e2 file(kernel) and use again 'Update E2' button for the second e2 file(Firmware).
It's work.

Regards.

Good to know, m8! Thank you kindly, for your effort!:respect-054:

But my concern is with going back to original FW.:smash:

Any words of wisdom, please?:o15:

Seen many machines KOed...:angelsad2:

Hello,

Use jazup 2.0 to go back at official FW.
You found the kernel file here

Regards.

Indeed. But the problems start when there is no connection with AZbug...

No Rescue Mode and no way AZ recognises any USB memory sticks...

Real mess!!!!

Hi,

JaZUp provide you the HP USB Format tools.
Use it on your USB stick.

Create a fake patch.bin on the USB key, connect it to your Azbox and reboot it.
the file should be name: patch.bin nothing less, nothing more

Your Azbox will go into Rescue Mode.

Pr2

No, it will not. Well, not in all cases.

That's the whole point. It should but.... it doesn't - all too frequently...

And then, it's a nightmare... It happened to me, not just in RC11, which had to have it sorted, apparently...

And I do use HP tool, most of the time. I try other tools, too. Windows included. But AZ frequently messes up the USB stick - sometimes completely ("nothing on the USB stick") or sometimes just the "badly formatted" or even "no valid USB stick inserted" kinda message.

Error 1 most of the time. Sometimes it just keeps going towards booting. Regardless of what is on the USB stick.

After that, sometimes it's stuck on "STARTING..." all the time.

There are a variety of situations whereby AZbox HD doesn't behave in an at all predictable manner...

Go figure...

Hello,

You can try this...
if you are in E2. Execute 'Restore Official boot', Jazup 2.0 try to put your azbox in rescue mode after a reboot.

Regards.

Indeed, I tried, m8! Again, thanx for your efforts!

The problem is that there is, by then, no connection to AZ...

So, no chance JaZUP can do anything. USB sticks are not recognised or ignored [not forcing the box into Recue mode].

Stuck on STARTING... or some "Error = 1" or some such nonsense...

I had a similar problem, the azbox didn't recognize the usb, it said was not format32.

You have to select first "format application area", then the box should accept your pendrive

I did.

It caused me no end of problems...

Blagi,you say it CAUSED youproblems.Does this mean you'v got it sorted now?

Yeah, I did, after god knows how many various attempts.

One USB wasn't erased/altered by AZbug [on connection], by chance...

It had dual boot 5300 original FW. When it booted from it, I was able to connect to the box, finally.

I struggled a lot after that, too - until I finally managed to put OFW back into AZ's DOM...

Not for the faint hearted, let me tell you!

After a failed RC12 upgrade I tired to use jazup to go back to original.
I managed to load the offical boot, and reboot witha usb drive containing a patch.bin file.
It loads the blue update screen but says theres no patch file on the usb drive. I have the 5304 offical bin on the drive and its formatted fat. It obviously reads it since it recognises thepatch.bin and fires up the update screen.
Any ideas?

The reason I ask is, I had exactly the same problem.I was advised to download, 'EASUS DATA RECOVERY ******', this program sorted the USB.I put this USB in the receiver,powered off n on,the box then went in to rescue mode. Hope this helps.

Keep trying...

This is just one of the situations I described...

It should be addressed by the coders of E2, it seems to me....

got it sorted. read elsewhere that for the OFW restore you need a ridiculously large usb drive. nfi why. but i formatted a 2gb drive and copied the same files to it and voila it worked.