AMLogic Firmware Roll-Back Guide

A Firmware Roll-Back feature has been added to AMLogic firmware from v1.3.30 onwards.

Normal OTA updates will still use differential files but you can now roll back to specific images and then differentially update from there if you wish.

These images are available below as full firmware images and can also be used to update to later firmware if you've already rolled back to an earlier one.
There seemed little point going back before v1.2.22 so strategic points have been chosen at v1.2.22, v1.2.40 and v1.3.05. then you can OTA from there to wherever you like.

Please be aware that because databases are continually updated and their schemas changed to accommodate new features, it may be necessary to perform a factory reset after rolling back - it all depends how far back you go and what changed in between.

** Just a note to say that although this procedure is designed for rolling back G to non-G, there have been reports of it not working in some cases. Neither I nor the devs have been able to replicate this yet, but my advice is to hold off on that until we figure out what's going on **

Roll-Back is enabled by doing the following:

1. Go to the Update app and enter Mouse Mode

2. Hover the Mouse over the name of the box at the top and click <OK> three times and you'll see a notice at the bottom saying "No need, you are already a developer"

​

​

​

Your box is now ready to accept Roll-Back Firmware and you can disable Mouse Mode (you only need it for the above step).

3. Download one of the images below, bearing in mind that it may not be the one you actually want, but in that case pick the nearest earlier one.

4. Apply the firmware in the usual way. If you don't know what that is, you probably shouldn't be doing this.

5. Once the firmware has been loaded, check that the apps behave as expected - especially HT and the Music app - if not then that means the database has had too many updates in between and you'll need to perform a factory reset as explained above - do this from Settings/Recovery and reset/Restore Factory Settings.

To be fair, a factory reset under these circumstances is good practice and I'd recommend that anyway.

6. Now if you want to update to a later firmware, use the Online Update option in the Update App. I'd suggest leaving the Automatic Download option unticked otherwise you might inadvertently start an upgrade beyond where you want to go.

Note that the full firmware images are non-G only so if you're rolling back from a G version and want to retain Google Play Store, then you should apply one the appropriate G updates below after rolling back.


Now read all that again.



Firmware Images:

Z9X 8K

Z9X-8K_v1.2.22
MD5: 14cd3e7039a7e2e8659d6aaa58acce34

Z9X-8K_v1.2.40
MD5: 2aa0b14ee909ce088fc3b18be7186d0b


Z9X-8K_v1.3.05
MD5: dc935e932d9910ef442089ce3b7cec0a

Z9X-8K_v1.2.22_to_v1.2.22_G
MD5: 5607d221dc90ff8edef56823c9093738

Z9X-8K_v1.2.40_to_v1.2.40_G
MD5: fdb77d7995505b09727f6cb9f160e310

Z9X-8K_v1.3.05_to_v1.3.05_G
MD5: f08ca7edab8d09de9d058d75a6ccbc25


Z30 Pro

Z30-PRO_v1.2.22
MD5: 85665eb7340290a6ee6b4d5560d2f77f

Z30-PRO_v1.2.40
MD5: f1345bb9a8351a3ffe636a012b9a6b91

Z30-PRO_v1.3.05
MD5: 93d50cd66e38009a8194c5339118ba50


Z30-PRO_v1.2.22_to_v1.2.22_G
MD5: bad0606716ff834d8acf8e67d00a0532

Z30-PRO_v1.2.40_to_v1.2.40_G
MD5: df4220975be5b266cee35e10bdbff3cb

Z30-PRO_v1.3.05_to_v1.3.05_G
MD5: da7cb1af5582f133ef9d4dcd7ba9adbe


Z3000 Pro

Z3000-PRO_v1.2.22
MD5: ffcd95331d0c10fbe686814472ad44c3

Z3000-PRO_v1.2.40
MD5: ad162bb90da3d0e60423a4d0af7937d3

Z3000-PRO_v1.3.05
MD5: 41978c0b42df8855f51e529f2ff6857a


Z3000-PRO_v1.2.22_v1.2.22_G
MD5: a571f6cb4d77b0f0b737e6596e47e972

Z3000-PRO_v1.2.40_to_v1.2.40_G
MD5: adfceeda548f7635084afc4338a6350d

Z3000-PRO_v1.3.05_to_v1.3.05_G
MD5: 2ea634f32f44b3ff0122376d990f9fce


UHD8000

UHD8000_v1.2.22
MD5: 5e6177b03c796b87735a2e2cff5c6914

UHD8000_v1.2.40
MD5: 1370bd8cece18727af7e68ae8bc1d0cd

UHD8000_v1.3.05
MD5: be53eefd6610b88537a4f286a15492b7


UHD8000_v1.2.22_to_v1.2.22_G
MD5: 652404332d8a994a7ade7c59b9d8b94b

UHD8000_v1.2.40_to_v1.2.40_G
MD5: bf658a0dbc58789c70ae8184048156d6

UHD8000_v1.3.05_to_v1.3.05_G
MD5: 2d640b12f7bc8f193653adc8154c8a56



And one last thing...

This information is provided "as is" and the use of this information and these links is entirely at your own risk.

Make sure you understand what you're doing. Make sure you download the CORRECT firmware for your box. Backup HT. Take a note of settings etc etc blah blah blah...

And just to note that updating from a full image like this can take longer that a normal differential update.
​

 

Thanks to Mark for securing a firmware rollback for us. Gentlemen, I assure you, without his efforts, we would never have had this opportunity.

 

Thank you my friend. Appreciated.

It took a while...

 

One question Mark. I‘ve got my UHD8000 second hand and unfortunately the _G version was installed.

So far I had no other option than to wait for a stable/official non_G update over OTA.

Did I get it right that I now can downgrade to 1.3.05_non_g and then rejoin the beta path and upgrade again the latest non_G Beta? And if so, would that be recommendable? Or better just stick with the _G beta path and switch to non_G once the official release is available?

Many thanks,
Houbi

 

Yes indeed, thank so much @Markswift2003 !

Being able to do roll-back is a real life (or at least media player) saver!

 

Yes, exactly right - you can roll back to v1.3.05 non_G and then follow the non_G upgrade path.

 

@Markswift2003
Mark, you’re amazing! You, as a person, are one of the few reasons why—despite everything—I’ve remained loyal to Zidoo. Your support is fantastic and vital to this forum. I performed the rollback procedure, and everything worked perfectly. On behalf of everyone, I want to thank you for everything you do for us and for this company every day.

 

Awesome news. I don't need it currently but still grabbing all the relevant image files just in case

 

@Markswift2003

You can disregard below. Some idiot downloaded Z30 instead of Z3000. No I need help getting back to a place where I can install the right software. Any help would be humbly appreciated.

I received an Activation Information screen and on that screen it says "Authentication failure uuid" and Illegal authorized (4). This is on my z3000, and I rolled back to v1.3.05. Am I hosed until I contact Zidoo service?

 

Great. Thanks a lot Mark

 

Not sure - I've asked the devs. Can you post a pic of the screen?

 

Here you go. Thanks. And yes, I am the idiot.

 

And to confirm, this is a Z3000 Pro?

 

Can these full images be used on a USB stick with the recovery boot loader? If so, are there any special steps required? (Maybe a rename to follow a specific pattern or the USB drive partitioned/formatted in a particular way?)

 

When you say "The Recovery Bootloader", what do you mean?

 

Yes, it is a Z3000 Pro. I was able to reboot and get to the Update screen, but as I just told support, when I went through the update process again with the correct firmware loaded, it ingested the zip file, presented some of the expected messaging (do not power down, etc) and then returned to the update screen displaying the Model Z30 still. So it looks like the update did not process.

 

I can understand that - if it thinks it's a Z30 Pro, then it shouldn't accept Z3000 Pro firmware - what I don't understand is how you managed to update Z30 Pro firmware in the first place - that shouldn't be able to happen...

Let's see what support come up with.

 

I agree. This process is apparently not idiot-proof if it let me upload the Z30 firmware in the first place. The device appears to be fully functional under the Z30 firmware. I will wait for some guidance from Zidoo, but I'm also wondering if the system just saw that I was going from v1.3.05 to v1.3.05 (during the attempt to fix) and ignored the update for that reason. I may have to roll back further!

The impatient engineer in me couldn't wait. So I was able to get back to v1.3.35 software after a full "Restore Factory Settings". However, my system still believes it is a Z30 and one very significant implication is that I don't have the dual HDMI output functionality of my Z3000. So apparently I need this thing somehow to think it's a Z3000 to get fully updated and functional. Any ideas?

Apparently I'm dealing with what is called a "cross-flashed unit". I'm hearing that there is a process to reflash my unit with specific image on a usb drive, but that has to come from you or the Zidoo support team. Does this make sense, and if so, can you help me get that image and instructions? Much appreciated!

 

The Android bootloader recovery screen that you get when you plug in a USB stick with Linux/ISO9660 partitions. Or maybe it is even with a FAT32 partition but with the right flags. I don't know the exact trigger mechanism, but it's happened to me before and left me in a panic for a while, until I figured it was caused by a USB drive being connected. There was another post I made, which had more details, but I can't find it.

 

Ah - no, you shouldn't see that!

This firmware is to be simply loaded from the Update App in the Zidoo - as far as I know the bootloader needs a full recovery image.