[ROM] Magicsee N5 - atvXperience v2 N5 Edition

[Nayam]

Good evening everyone.
Today I checked the authentication when using a wired connection, the effect is the same - an incorrect username or password.

I think it has something to do with build.prop file.
We got the same problem in v2A a year ago and I think I fixed it by using a standard build.prop file.

[SrWladimir]

[mention]Nayam[/mention] What improvements have this ROM/Firmware?

[Nayam]

[mention]Nayam[/mention] What improvements have this ROM/Firmware?

It's the build from HD84 that I modded. I removed/added some files and build.prop tweaks and also some apps and stuff. The google play doesn't work probably because of buildprop but everything else works great.
Even played a game on it, works just fine.

[Aston]

Good day! When do you plan to restore google play on this build?

[Nayam]

Good day! When do you plan to restore google play on this build?

I don't have the device with me so cannot test. I'll need you guys to test things for me.

[Aston]

I'm ready to help, but the image of the Magicsee N5 Edition - v2
Final release is not installed on my Magicsee N5 console.
Upgrading error

[Nayam]

I'm ready to help, but the image of the Magicsee N5 Edition - v2
Final release is not installed on my Magicsee N5 console.
Upgrading error

Use USB Burning tool

[NuPogodi]

Hi! I'm not totally sure that it was the reason, yet by simple replacing the description & fingerprint lines in the v2-version of build.prop by corresponding info taken from the stock firmware

# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=p212-userdebug 7.1.2 NHG47L 20180321 test-keys
ro.build.fingerprint=Amlogic/p212/p212:7.1.2/NHG47L/20180321:userdebug/test-keys
ro.build.characteristics=tv
# end build properties

I've succeeded to eliminate boring warnings by google services as well as problems by login to my google account (both the androidtv.com/setup and the mail & password methods work properly). Now everything looks much better than my first naive attempt to install atvXv2 via microSD (with the crash and following reinstalling atvXv2 via USB Burning Tool). Thanks a lot, dear membera of atvX-team, for excellent product

[Nayam]

Hi! I'm not totally sure that it was the reason, yet by simple replacing the description & fingerprint lines in the v2-version of build.prop by corresponding info taken from the stock firmware

# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=p212-userdebug 7.1.2 NHG47L 20180321 test-keys
ro.build.fingerprint=Amlogic/p212/p212:7.1.2/NHG47L/20180321:userdebug/test-keys
ro.build.characteristics=tv
# end build properties

I've succeeded to eliminate boring warnings by google services as well as problems by login to my google account (both the androidtv.com/setup and the mail & password methods work properly). Now everything looks much better than my first naive attempt to install atvXv2 via microSD (with the crash and following reinstalling atvXv2 via USB Burning Tool). Thanks a lot, dear membera of atvX-team, for excellent product

Thanks, I knew it had something to do with the build.prop codes. Thanks for finding the exact line, I didn't notice I changed the fingerprint lol.
Thanks again, I'll push an update online after I'm done with my exams

[Nayam]

Can anybody please upload a build with the build.prop fix? I cannot use my computer and that's why I'm asking you guys