Jump to content

495 PRO Android 7.1 upgrade 7.1 BETA (final version)


1 Screenshot

About This File

ATV 495 PRO upgrade to Android version 7.1

This is a beta version as we had to build this ourselves without the normal support through regular channels. This will not move passed BETA, so you may encounter minor issues with certain programs, but we currently have no known issues at the moment.

Difficulty level - 3/5

This will not work on the 495. It is meant for the 495 PRO. This is indicated on the sticker on the bottom of your 495 Pro unit. If it doesn't say "PRO" then its a different device.

Notable features:

-Updates from Android 5.1 to 7.1 for better support.
- New Home Screen
- Added Dual Boot Option to Libreelec
- Added Super User Support

****DO NOT ATTEMPT TO UPGRADE TO 7.1 THROUGH THE OPERATING SYSTEM. IT WILL POTENTIALLY BRICK YOUR DEVICE***

This update must be done using the below method only. 

NOTE: Processing this Firmware upgrade will wipe all your Data 

How to process the steps:

1. Download the zip file
2. Format your MicroSD Card to FAT32
3. Unzip the files into a folder on your computer before moving to step 4.
4. Drag and drop files from Unzip folder to root of your MicroSD card.  (unzip files to the main part of the card, not in a folder)
5. Insert sd card with files into the 495 PRO SD card slot
6. Connect HDMI, turn the TV on
7. Hold the Power button. 
8. Hookup power while holding down power button. 
9. Hold for 15 seconds

10. The front side lights should blink red to green repeatedly if the upgrade process has started properly.

you will see the android guy moving, give it 5 -10 minutes and it should bring you to the 7.1 setup screen.




User Feedback

Recommended Comments



Thanks for this.  Much appreciated to have our boxes still supported!

If we do have issues with this firmware is it possible to revert back to an old firmware?

Share this comment


Link to comment
Share on other sites
10 hours ago, Rick White said:

Thanks for this.  Much appreciated to have our boxes still supported!

If we do have issues with this firmware is it possible to revert back to an old firmware?

Yes you can revert to 5.1 using the other set of files in the 495 PRO Downloads section

Share this comment


Link to comment
Share on other sites

Anyone got this to work?   The instructions state to "Hold the Reset button at the back."    I assume what they mean is hold the button at the top/front since there is nothing at the back.

It did the install and now I have a bricked 495 PRO.

I definitely followed this instruction:  " DO NOT ATTEMPT TO UPGRADE TO 7.1 THROUGH THE OPERATING SYSTEM"

The only thing I did different from the instructions is I held down the power button for 15 seconds to trigger the update after plugging in the power.

Share this comment


Link to comment
Share on other sites

I spoke too soon.   I reformatted the SD card, redownloaded the file just for safety and reupdated the firmware.   I ended up with a lot of noise on screen and pulled the power to reboot it.

The TV image was freaking out and is why I assumed it was bricked (blinking image).   I had to unplug the HDMI cable and replug it back in.

From another post I saw Justin suggested this fix that I think applies:  

Quote

In the display settings of android

Turn off Automatic Display Resolution

And set it to your desired resolution

So far it looks like it working now.    Very happy!

  • Thanks 1

Share this comment


Link to comment
Share on other sites

Well that was an inordinate waste of time. Followed the instructions to the letter (NOT updating through the operating system). Went through the splash screen showing the update to completion. Waited 20 minutes, and nothing else happened. disconnected the device, removed sd card etc, rebooted. Nothing. Just a black screen.

Attempted a factory reset. Nothing.

So thanks guys, for bricking my device. It is appreciated immensely.

Will never see me as a user of MyGica products again.

Share this comment


Link to comment
Share on other sites

The update went relatively smoothly... :-)

First I just added the upgrade to the microSD card, but that did not work. I noticed it was not FAT32 format.

Removed it completely and used a WIN7 machine to format FAT32....transferred the upgrade files to the root. Inserted it back into my ATV 495pro, held down the power button while plugging it in, and 15 min later had a nice  Android 7.1 machine.

Thanks!

 

Share this comment


Link to comment
Share on other sites

Well Stickler, you're not alone. After waiting almost 2 years for a promised passthrough audio fix, I was absolutely shocked that MyGica actually came through with an Android upgrade. Unfortunately, despite carefully following the steps, my 495PRO promptly bricked. During the "upgrade" attempt (with a new SanDisk 32GB SD card), I saw absolutely no activity. There was no Android on screen, no flashing light, no menu - just black. I waited 30 minutes but it's dead. The only ray of hope is that the power light works and my PC recognizes the device when plugged in via USB. Normally, this would mean that I could attempt to recover the box with "USB Burning Tool", but it will not load MyGica's (non-standard?) img file. 

Support@mygica.com has been prompt but ABYSMAL. I asked if they had a method of unbricking and/or a proper recovery img file (containing 3 files: aml_sdc_burn.ini, aml_sdc_burn.UBOOT, and 495PRO.img). Their (shocking) response was "what Android 7.1 upgrade?" and they asked for the URL and a picture of the box. I sent both (as well as a photo of the NAND chip in case pins need to be shorted for flashing) and the response was:

Actually, this product does not support 7.1 system.
You can follow our latest products which support 7.1.

Obviously they have no idea what their own company is doing and they didn't even bother opening my link. I'll probably try to submit another request via their support ticket webpage, but I'm not hopeful.

 

 

 

 

Share this comment


Link to comment
Share on other sites

Support to date have not even bothered to respond to my query as to how to recover the device, and based on QVortex's experience (and the deafening silence from Support on this thread) I am not really holding my breath.

I even went as far as contacting the local Distributors in SA, but I suspect that they will be even more in the dark in relation to this if they even bother to respond).

Would really just be happy to restore the device to original state.

QVortex, does your device boot to recovery (as for the USB BT to work it needs to). Mine simply refuses to. The power light comes on when connected to power, but will not boot to recovery when power button is held down for the requisite 15 seconds.

Share this comment


Link to comment
Share on other sites
16 hours ago, Stickler said:

QVortex, does your device boot to recovery (as for the USB BT to work it needs to). Mine simply refuses to. The power light comes on when connected to power, but will not boot to recovery when power button is held down for the requisite 15 seconds.

*If* recovery mode is working, I can't tell because the HDMI and AV ports aren't putting out any video. Holding down the power button makes no difference. For what it's worth, USB Burning Tool immediately detects the device (shows "connect success") when I connect it to my PC (USB to USB). Also the orange light turns on. Now I need a proper img file to attempt a flash. 

Share this comment


Link to comment
Share on other sites

Stickler are you sure it is bricked?  I thought mine was too but it was the default display settings messing with the TV/HDMI cable.  Unplugging the HDM cable temporarily fixed the display setting.

After I thought it was bricked I reformatted the SD card to FAT32 and redownloaded a fresh copy of the ZIP file.   Dump all the contents of the .ZIP file into the root of the SD card (there will be sub folders in there though along with a few files).

When I attempted to upgrade the box a second time I did not see anything happening.  Black screen.   I just waited a safe amount of time, rebooted the box, and then temporarily pulled the HDMI cable and replugged it.   This allowed the TV to adjust to the different display settings.

After this I saw the box had booted and I went into the display settings and modified it.

Everything is great now.  The only complaint I have with the new version is that I don't have the STANDBY mode anymore.  Just have the POWER OFF and REBOOT.

Share this comment


Link to comment
Share on other sites

Hey guys, 

the burning tool should allow it to be unbricked. That’s our method as well. If you’re in Canada, we can check it out at the shop and try as well. 

As for the support@mygica.com, that is from the hq in China most likely. We have created this firmware separate from the normal channels and without support from the chipset builders, which is why others may be clueless. We are doing it to try and support our customers as best we can. 

For the SA guys, if it gets bricked, hopefully your local distributor will be willing to help fix, or replace somehow. 

Share this comment


Link to comment
Share on other sites

Hi Support:

Coincidentally, I'm located in Canada, but why not just make the img available? At this point, those of us with bricked boxes have nothing to lose and any version of Android will do.

Thanks, QV

Share this comment


Link to comment
Share on other sites

Hi Rick White. Before I attempted recovery to original image I tried the same methodology as you (based on your success in getting it to work). Unfortunately I was not as successful hence trying to them restore to the original firmware.

The local support guys advised the company I purchased these units from the same as the HQ guys, that the 495PRO does not support 7.1, nor are they going to adapt the firmware to support it. It might be worthwhile for the Admin and Support personnel to put an advisory on this forum that it is support for devices in your region only and direct anyone outside of this region to their local Support portals (I am from South Africa - local support advised that the units we received locally often do not have the same hardware as those in the US and Canada which could explain the failure to update).

QVortex, I have not tried the Amlogic Burning Tool Method yet (mainly due to the fact that I do not have a USB male to USB male cable. Will get one and attempt). The local support have advised that the unit can be sent to them to try and recover, but to be quite honest, I am quite annoyed by this whole thing and if I cannot effect a recovery I am probably going to turf the device and buy another brand that supports a more recent iteration of Android and who offer a less confusing and fragmented Support when things go wrong or updates are required.

Share this comment


Link to comment
Share on other sites
3 hours ago, QVortex said:

Hi Support:

Coincidentally, I'm located in Canada, but why not just make the img available? At this point, those of us with bricked boxes have nothing to lose and any version of Android will do.

Thanks, QV

What image do you mean? There are multiple versions of android in the downloads section that each have an .img file in them. Sorry if I’m confused. 

 

To comment on the other pist about turning people away at the door, we try to support the product as best we can from anywhere the unit was purchased. We can’t tell people to not come here for support. 

If your unit is bricked, and you can’t aend it in for a service, you may want to try out the burning tool method. I’ve seen it work flawlessly, but I’m not as familiar on the instructions. 

Share this comment


Link to comment
Share on other sites

Purchased a USB M to USB M cable. Sadly the notebook does not recognise the device and it does not appear in the AMLogic Burning Tool interface. I guess the unit is totally bricked.

Will be buying a replacement unit that supports the latest iteration of Android, but it will not be a MyGica product as this has been a less than pleasant experience.

Share this comment


Link to comment
Share on other sites
15 hours ago, Stickler said:

Purchased a USB M to USB M cable. Sadly the notebook does not recognise the device and it does not appear in the AMLogic Burning Tool interface. I guess the unit is totally bricked.

Will be buying a replacement unit that supports the latest iteration of Android, but it will not be a MyGica product as this has been a less than pleasant experience.

Hi Stickler:

For what it's worth, on my 495PRO, it only works if I use the USB port beside the SD card slot. Also my cable is USB 2 with two type A (4 pin) male connectors.  Previously, I tried out a "type A to micro" cable which did not work.

QV

Share this comment


Link to comment
Share on other sites
19 hours ago, MyGica Support said:

What image do you mean? There are multiple versions of android in the downloads section that each have an .img file in them. Sorry if I’m confused. 

 

Hi Support:

Your img file (update_MyGica_ATV495_Pro_1900_Pro_wv_5.1_20170324.img) will not load in USB Burning Tool. It is not a true image; it is simply a renamed zip file with the following contents:
02/28/2008  09:33 PM        10,631,168 boot.img
02/28/2008  09:33 PM         1,441,792 bootloader.img
02/28/2008  09:33 PM            69,225 dtb.img
02/28/2008  09:33 PM            14,008 file_contexts
02/28/2008  09:33 PM         5,049,760 logo.img
03/14/2019  09:46 PM    <DIR>          META-INF
02/28/2008  09:33 PM        13,248,512 recovery.img
03/14/2019  09:46 PM    <DIR>          system
02/28/2008  09:33 PM       953,790,464 system.new.dat
02/28/2008  09:33 PM                 0 system.patch.dat
02/28/2008  09:33 PM               282 system.transfer.list
               9 File(s)    984,245,211 bytes


The img files of many other Android vendors (which work with USB Burning Tool and other Android recovery tools) are quite different. Here's what it looks like when I burn a "proper" img to an SD card - it's only three files.
03/09/2019  10:23 AM               617 aml_sdc_burn.ini
03/09/2019  10:21 AM           754,176 aml_sdc_burn.UBOOT
03/09/2019  10:22 AM       823,394,368 M8SPRO_S905W_A95XR2_9377_2+16_20171122.img
               3 File(s)    824,149,161 bytes

In an earlier post above, you claim to have used the burning tool method. If that's the case, I'm guessing you have access to other img files that are not currently available via your download section.

QV

Share this comment


Link to comment
Share on other sites
1 hour ago, QVortex said:

Hi Stickler:

For what it's worth, on my 495PRO, it only works if I use the USB port beside the SD card slot. Also my cable is USB 2 with two type A (4 pin) male connectors.  Previously, I tried out a "type A to micro" cable which did not work.

QV

Hey QVortex, yep, the USB 2 Type A Male to Type A Male is the cable I got.

Made no difference which of the 2 ports I used unfortunately. Interestingly enough, the power button lit up when I inserted it.

As an aside, our local supporr is dismal as they are now no longer responding. So I am now done with MyGica.

Share this comment


Link to comment
Share on other sites

Hi Stickler:

In theory, you might still be able to get USB Burning Tool to recognize the 495PRO by shorting a couple of NAND pins with a small screwdriver.  Unfortunately, without some insider info, it's a trial and error process. Freaktab.com has a long thread dedicated to this topic but I couldn't find anything useful about our specific Samsung chip. For what it's worth, I attached a photo showing the pins.

QV

 

 

NAND.jpg

Share this comment


Link to comment
Share on other sites

Thanks QVortex. Will have a look see. I also came across a post stating that one would possibly need to disable driver signature verification. Have not tried any of this yet must be honest as all the images return a parse error in any event when loading in the USB Burning Tool.

Will give it all a bash before I bin the unit.

Share this comment


Link to comment
Share on other sites

So got it to recognise the device when connected by USB in the USB Burning Tool (did not have to short the NAND pins thankfully, but did have to disable the driver signature verification which requires a restart).

Same issue as you though QVortex in that the image files when attempting to load deliver a "Parse Burning Image Fail" error. So unless MyGica can provide a usable image with which to flash the unit, it is going the route of recycling.

Thanks for the help and advice :-)

Share this comment


Link to comment
Share on other sites
On 3/12/2019 at 12:35 AM, QVortex said:

Well Stickler, you're not alone. After waiting almost 2 years for a promised passthrough audio fix, I was absolutely shocked that MyGica actually came through with an Android upgrade. Unfortunately, despite carefully following the steps, my 495PRO promptly bricked. During the "upgrade" attempt (with a new SanDisk 32GB SD card), I saw absolutely no activity. There was no Android on screen, no flashing light, no menu - just black. I waited 30 minutes but it's dead. The only ray of hope is that the power light works and my PC recognizes the device when plugged in via USB. Normally, this would mean that I could attempt to recover the box with "USB Burning Tool", but it will not load MyGica's (non-standard?) img file. 

Support@mygica.com has been prompt but ABYSMAL. I asked if they had a method of unbricking and/or a proper recovery img file (containing 3 files: aml_sdc_burn.ini, aml_sdc_burn.UBOOT, and 495PRO.img). Their (shocking) response was "what Android 7.1 upgrade?" and they asked for the URL and a picture of the box. I sent both (as well as a photo of the NAND chip in case pins need to be shorted for flashing) and the response was:

Actually, this product does not support 7.1 system.
You can follow our latest products which support 7.1.

Obviously they have no idea what their own company is doing and they didn't even bother opening my link. I'll probably try to submit another request via their support ticket webpage, but I'm not hopeful.

You emailed support@mygica.com
This is handled by China Head Office
Our support in North America is support@mygica.tv

We paid for 7.1 Upgrade ourselves and did it separately from the China Office, so that is probably why they responded like that for 7.1

We we be releasing the required AML files for USB Burning tool for your device, so you can try to revive it
It will be posted on the forums within the next few days.

Quote

 

 

 

Share this comment


Link to comment
Share on other sites
On 3/14/2019 at 11:27 PM, QVortex said:

Hi Support:

Your img file (update_MyGica_ATV495_Pro_1900_Pro_wv_5.1_20170324.img) will not load in USB Burning Tool. It is not a true image; it is simply a renamed zip file with the following contents:
02/28/2008  09:33 PM        10,631,168 boot.img
02/28/2008  09:33 PM         1,441,792 bootloader.img
02/28/2008  09:33 PM            69,225 dtb.img
02/28/2008  09:33 PM            14,008 file_contexts
02/28/2008  09:33 PM         5,049,760 logo.img
03/14/2019  09:46 PM    <DIR>          META-INF
02/28/2008  09:33 PM        13,248,512 recovery.img
03/14/2019  09:46 PM    <DIR>          system
02/28/2008  09:33 PM       953,790,464 system.new.dat
02/28/2008  09:33 PM                 0 system.patch.dat
02/28/2008  09:33 PM               282 system.transfer.list
               9 File(s)    984,245,211 bytes


The img files of many other Android vendors (which work with USB Burning Tool and other Android recovery tools) are quite different. Here's what it looks like when I burn a "proper" img to an SD card - it's only three files.
03/09/2019  10:23 AM               617 aml_sdc_burn.ini
03/09/2019  10:21 AM           754,176 aml_sdc_burn.UBOOT
03/09/2019  10:22 AM       823,394,368 M8SPRO_S905W_A95XR2_9377_2+16_20171122.img
               3 File(s)    824,149,161 bytes

In an earlier post above, you claim to have used the burning tool method. If that's the case, I'm guessing you have access to other img files that are not currently available via your download section.

QV

We will release AML file for you guys to use on USB burning tool.
It will be up in the downloads section within a few days + instructions

Share this comment


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...