Nexbox A95X Pro Android TV OS 2GB/16GB Netflix 720P YT4K S905W 4K Voice Remote 2.4G WiFi LAN

[clarkss12]

I also bricked my box and i want to make the same steps as you, first i will try to install with usb burning tool the m82 pro w firmware.
Then the Magendanz oem firmware, which one you used exactly, can you tell me the link of the rom and the name of the file,thanks a lot

perhaps is it this one from here? http://freaktab.com/forum/tv-player-...android-tv-7-1

Yes, I do believe that is the firmware that I used.

[tombraga]

Next, i found the original Mecool M8S Pro W firmware from this site ( https://chinagadgetsreviews.com/down...-w-tv-box.html), it was an older version of the firmware and not the ATV version, but was in an IMG format so I could burn it to my box using the USB Burning tool. After I got it installed on my box, it now thinks my box is an official Mecool box. Next, I downloaded a newer OEM firmware from Magendanz's page, copied the file to a USB pen drive. Inserted the Pen drive into my box and using the UPDATE app from Android, I wiped data and media. After box rebooted, took awhile for the firmware to setup, but now I have an ATV Andoid, ALMOST the same as the original firmware..

Now, Voice works, and I have my Widevine DRM level 1 back, so now I have Netflix in 1080p with DD+

I also bricked my box and i want to make the same steps as you, first i will try to install with usb burning tool the m82 pro w firmware.
Then the Magendanz oem firmware, which one you used exactly, can you tell me the link of the rom and the name of the file,thanks a lot

perhaps is it this one from here? http://freaktab.com/forum/tv-player-...android-tv-7-1

[tombraga]

how can i connecto to my usb burning tool? there is no hole to put it into recovery?

[mrpunch]

To be honest, I'm not really bothered about this update or even a new one that installs and "fixes" Netflix.

The last one lasted about 3 weeks before Netflix blocked it again.

Unless the developers officially license Android TV, it's only a matter of time until it's blocked.

Sent from my TA-1021 using Tapatalk

[krde]

Just out of interest, which directory was it downloaded to?

Sent from my SM-P555 using Tapatalk

Can't remember the full path, something like Android->data->a***fota or something like that, but, internal path was always empty even without install it, i only could get it downloading the update after plug an external usb storage and i took from same path in external usb

[mrpunch]

Same error here, seems like we all having this problem trying to install the new OTA update, very strange...

EDIT: i managed to upload the UPDATE.ZIP file here... https://we.tl/t-SqM3QI3Zl5 if somone else wants to try, but, it doesn't work, i've tried copying into the internal memory and into an external HDD and same problem always, even after a factory reset, but, nothing!!!

Just out of interest, which directory was it downloaded to?

Sent from my SM-P555 using Tapatalk

[krde]

Thanks, I'll try it then and let you know what happens.

Same error here, seems like we all having this problem trying to install the new OTA update, very strange...

EDIT: i managed to upload the UPDATE.ZIP file here... https://we.tl/t-SqM3QI3Zl5 if somone else wants to try, but, it doesn't work, i've tried copying into the internal memory and into an external HDD and same problem always, even after a factory reset, but, nothing!!!

[Knuistenbek]

The failed update hasn't bricked my box. It restarts normally after a power cycle but remains on the original firmware.

Thanks, I'll try it then and let you know what happens.

[mrpunch]

The failed update hasn't bricked my box. It restarts normally after a power cycle but remains on the original firmware.

[Knuistenbek]

Hi, because I’m very new at this and have no idea how to unbrick a bricked box I am very cautious.
Does this failing update affect everyone or only certain users?
I am curious if some people manage to do the update without any problems.

[rebelos]

how can we download the update in order to update our boxes manually ?

[mrpunch]

I have a theory (on my problem at least) after finding this info on another forum:

A non-rooted Android device only displays a Status 7 error when a system update is being flashed onto it and something is found to be out of place or, to be more precise, modified.

The Status 7 error only affects non-rooted devices that are not in complete stock condition, so the only way to fix the Status 7 error on a non-rooted Android device is to restore every bit of the device back to its stock condition.

I have disabled the leanback launcher on my box because I prefer to use a particular 3rd party one. When I get back home, I'll re-enable it and try the update again.

[rebelos]

I got the same error. If someone can give us the update like previous time in a zip file then our boxes will work again i believe.

[mrpunch]

I'm not sure.....Are the source and target reversed?

The update is also failing on my box which is running stock firmware...

This happened before the last update and they released a working one a couple of days later.

Sent from my SM-P555 using Tapatalk

[mrpunch]

The update is also failing on my box which is running stock firmware....

This happened before the last update and they released a working one a couple of days later.

Sent from my SM-P555 using Tapatalk