Related
Hi all,
I recently got hold of one of these OTT M8S boxes and have been banging my head against a wall ever since then. My ultimate objective is to load Openelec onto this and be done. The Android Firmware it comes with is flaky - especially on MPEG2 content (which is amazing considering how well the Pi Zero does with that content).
Trouble is the Firmware that mine came with has no functional recovery partition. Eventually I loaded a new firmware with a recovery using USB_Burning_tool using a stock .img . This image didn't have my WIFI support so I upgraded it using another zip file and the stock recovery method. This went fine, but really I was no nearer my goal since the new recovery firmware has built in signature checking and will only allow firmwares in the same series to be loaded. It seems that this has become a standard feature of all the firmware for these boxes now coming out. So there is no pathway to loading TWRP or Openelec using the standard Firmware - but it won't allow you to break out of the standard firmware signature checking. Deadend !!!
I attempted to dd a functioning TWRP onto the box using shell emulator, but this simply broke the recovery. This suggests that this issue is deeper than just the way the recovery is setup, it suggests that the issue is with the second bootloader (u-boot.ini) which seems to have signature checking built in as well. So no longer can you pick any functioning u-boot.ini file and make a bootable SD-card with Amlogics SDcardMaker.
Fairly locked down altogether, and it would seem that this feature is going to proliferate to all of these boxes since they are all using variants of the same basic Android ROM, which I suspect is issued by AMlogic themselves.
It seems to me that the only way forward is to create alternative ROMS such as Openelec as pure .img files which can be loaded at the raw NAND level using USB_Burning_Tool. None of the developers seem to be addressing this, simply repeating the old approaches which no longer work on these new generation boxes.
A lot of people are thrashing around and bricking their boxes and without a functioning recovery partition these become defacto hard bricks.
So I make a call out for the developers of the unofficial Openelec firmwares to package them as raw .img files rather than OTA zip files which can no longer be sideloaded.
Maybe someone reading this with a functioning Openelec M8S S812 box can do a dd dump and post up a .img file for me to burn into my box. Please.
Stephen
I attempted to use USB_Burning_Tool to burn an Openelec Wetek Core .img file and the program wouldn't pass it. So it seems that not even this is a suitable method of bypassing the bootloaders.
Stephen
However here is a heads up for anyone out there struggling to get a decent performance from their Kodi. I have just loaded up my box with the Wetek Core Kodi 15.2 and I can report that out of the box it solves almost all of the Amlogic codec issues people have been facing and runs all three hardware acceleration tabs. On Tvheadend PVR playback it occassionally does a black screen on channel switches and can be very slow to switch channels, but if you switch channels again and then back to the black screen channel it usually comes back. no stuttering or audio lag what so ever. Can be found here:
http://wetekforums.com/v/index.php?...-2-to-fix-23-976fps-video-sync-issues?p=23662
Here is an interesting quote from the users of this Kodi version, which suggests that the Kodi developers know what the issue are but refuse to address them, I suppose they hate these "pirate boxes" that much :
Blame Kodi for this. By default mpeg4 / divx is not Hardware accelerated. I'm not sure what WeTek did with this version, they may or may not have patched it to re-enable Hardware accelerated mpeg 4 / divx for the Core.
Try playing with the Video > Playback > Hardware acceleration options.
The Android Kodi devs know about this problem and refuse to change what is distributed by default.
Note other Kodi issues on AML.
mpeg2 in .vob files will not play in Kodi on ANY AMLogic platform, they stutter.
Click to expand...
Click to collapse
If I had to factor in my time to the cost of this box, the WETEK core starts to look a very cheap deal.
Stephen
I went back to this on a hunch and downgraded my Firmware to cyx_m8s_ap6330_8g2g_150728_SD.rar
this ROM has fully functioning recovery and it Flashes Openelec upgrade ROM by default with the toothpick method. So I tried as many different versions of Openelec for M8S as I could find and the sad news is that they all soft brick my box with the M8 v8_8 board. They all reproduce the same behaviour of preventing the box from booting and no Blue light on power up. Fortunately USB_Burning tool version 2.0.5.13 recovers the box without difficulty (though it usually takes two tries to get it past 3%).
It is my conclusion at this point in time that there is no functional Openelec available for this version of the board.
Stephen
Working TWRP?
Shoog03 said:
I went back to this on a hunch and downgraded my Firmware to cyx_m8s_ap6330_8g2g_150728_SD.rar
this ROM has fully functioning recovery and it Flashes Openelec upgrade ROM by default with the toothpick method. So I tried as many different versions of Openelec for M8S as I could find and the sad news is that they all soft brick my box with the M8 v8_8 board. They all reproduce the same behaviour of preventing the box from booting and no Blue light on power up. Fortunately USB_Burning tool version 2.0.5.13 recovers the box without difficulty (though it usually takes two tries to get it past 3%).
It is my conclusion at this point in time that there is no functional Openelec available for this version of the board.
Stephen
Click to expand...
Click to collapse
I worked with Abdul over on this forum and he was able to port a OTT S812 2G/8G M8 4335 TWRP which might work for your box. It was for my M8 v8_6 box. I tried all other TWRPs and they didn't work. I was his guinea pig and this result works great
If you go to the Freaktab dot com forum and look into the "TWRP for Amlogic devices" folder (which is under the "AMLogic based TV Players" folder, go to message 900 and you'll see a link to a TWRP recovery which may work on your machine.
I cannot post the URL due to rules in this website to prevent spam.
Hope it helps you.
Thanks a lot, that TWRP works very well off of a SD-Card.
It also successful boot into TWRP recovery on my box.
Finally some progress and the possibility of loading Openelec open's up.
Cheers.
Stephen
I attempted to use my new power of TWRP to flash a WETEK-Core Openelec development OTA. The result was a soft brick again.
However TWRP opens up new possibilities since I can now flash my Openelec image and then flash the bootloader from a stock rom - since I believe it is the bootloader packaged with Openelec which causes it to soft brick.
Will report back if I am successful.
Update: this strategy still produces a soft brick so the problem must run deeper than the Bootloader.
Maybe you could persuade Abdul to express an opinion on why Openelec soft bricks these boxes as I am sure he would have a good understanding of what was going wrong at the boot sequence.
Stephen
So good news folks. I have manged to get openelec loaded onto my box and its working fine.
My method was to use BootCardMaker and to load onto it the u boot.ini file from my second stock ROM.
I then placed the same u boot.ini file into the root of the same SD-card and then unzipped the image "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" into the SD-card root (which I believe I got from the WETEK site). All seem to work fine out of the box and HD works fine. It still has lip sink issues when handling streamed MPEG4 content - but it is definitely using the built in amcodec hardware decoding. Last thing to do is to replace the recovery with the working TWRP and make a full backup of the configured system.
So the issue with all the other builds of Openelec was an incompatible u boot.bin
Openelec is a lot more snappy in the interface than Kodi as an Android app, which is really noticeable when using the crappy remote it came bundled with.
Last thing to check is if the Amcodec has the same zoomed screen issue when outputting composite that exists in the Android version. Hope not.
I can now reload either the working Android or the Openelec using TWRP which is great.
Update: It appears at first glance that this build has no AV support at all.
Stephen
Hi firstly thank you i managed to get twrp on my OTT M8s following your instructions with the link to post 900~
Now i have made a complete backup of my rom but when i try to update a different rom it always reloads my original rom - It goes through the updating apps process but is always my stock rom
Now when i say stock rom that is a bit of a lie, i bricked this box within 20 mins of getting it and had to find a compatible rom, i ended up having to use the usb flashing tool and shorting out pins 28 and 29
there is a problem in the recovery/bootloader/u.boot bin somewhere that will not let me update the firmware
I am currently on a ap6330 but have had it on bcm4335 previously (go figure)
Also when i tried to update it to the latest acemax firmware last night it said 'this rom is for n200c and this box is k200 etc' but CPUZ clearly states my box is a n200c (again go figure)
I am by no means an expert on the file system of Android as a whole but am pretty experienced in flashing roms/cyanogenmod/xposed/twrp etc
Getting twrp running is a small achievement in itself....
It seems that the stock recovery process for installing OTA's checks signatures and will not allow "incompatible" ROM's to be flashed. The only way to get a ROM on there would be to find a full TWRP backup of that ROM and sidestep the standard recovery process.
I am still having issues with mine in that now that I have a working version of Openelec 6.0.0.2 it will not allow me to use the standard method of installing Openelec to downgrade to the 5.95.5 version. I am very happy with the way that Openelec performs, but without AV output it is a dead duck for me.
Looks like it was a wise move to do a full TWRP backup of the Android system as it seems that is the way I am going.
Stephen
Hi Stephen
Yes been trying to update and continually getting the E:error executing updater binary in zip
Could i take the meta-inf file from my working rom and swap it out?
I am not familiar with the more complicated stuff :/
See this comment by abdul in another forum:
On newer versions i have changed device id to k200. What device do you have ? I don't recall having made a TWRP for the MXQ.
That check is made by the update-script inside the flashable zip, I DID NOT MAKE IT CHECK. And "toggle signature verification" is there but it's not related to this.
Just delete the assert in update-script or use a newer version
I have been messing about with some roms and now i cannot restore my backup:/
E: unable to mount storage
Got a feeling i am going to have to start from scratch with usb burning tool
USB Burn tool will generally solve most issues. Only once or twice did it fail to find my Box and then the NAND shorting trick sorted that out.
Stephen
Shoog03 said:
So good news folks. I have manged to get openelec loaded onto my box and its working fine.
My method was to use BootCardMaker and to load onto it the u boot.ini file from my second stock ROM.
I then placed the same u boot.ini file into the root of the same SD-card and then unzipped the image "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" into the SD-card root (which I believe I got from the WETEK site). All seem to work fine out of the box and HD works fine. It still has lip sink issues when handling streamed MPEG4 content - but it is definitely using the built in amcodec hardware decoding. Last thing to do is to replace the recovery with the working TWRP and make a full backup of the configured system.
So the issue with all the other builds of Openelec was an incompatible u boot.bin
Openelec is a lot more snappy in the interface than Kodi as an Android app, which is really noticeable when using the crappy remote it came bundled with.
Last thing to check is if the Amcodec has the same zoomed screen issue when outputting composite that exists in the Android version. Hope not.
I can now reload either the working Android or the Openelec using TWRP which is great.
Update: It appears at first glance that this build has no AV support at all.
Stephen
Click to expand...
Click to collapse
I have the exact same PCB board M8 V8_8 and am also trying without success to get openelec running on it. Can you please explain the steps and firmwares you were using please and thank you - you are a god to me right now lol
I got the openelec file from the the VectorDroid website where i grabbed the file "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" from their download section.
I grabbed Amlogics Bootcard maker from Chinesegadget Reviews. This runs in Windows, but I had no problem using it in VirtualBox running Win7.
I extracted the file "u boot.bin" from the stock ROM "cyx_m8s_v8.6_bcm4335_8g2g_kodi_addons_151013_SD##.rar" (hash represent chinese letters). This is the most critical part since this is the layer which points Openelec to all of the available hardware. Use Bootcard maker to burn this file into a SD_card, and then for good measure add it into the root by a simple file transfer.
Copy the Openelec file into the SD cards root, and then extract it into the root.
The SD card should now be setup and ready to roll. However it will depend on the recovery setup that you have on your box. I cannot remember at this stage whether I used the stock ROM's "cyx_m8s_ap6330_8g2g_150728_SD升级.rar" or "cyx_m8s_v8.6_bcm4335_8g2g_kodi_addons_151013_SD升级.rar" to boot into recovery. My gut feeling at this stage is that the ap6330 has a less secure recovery partition and will recognise the Openelec card better than the bcm4335.
If you have the correct recovery img from the correct ROM it will boot into Openelec via Android stock Recovery and flash the files to you box. Give it at least 15mins as the screen is likely to go blank. Take out the SD card and reboot.
I used TWRP to back up my stock ROM and Kodi setup before I did all this, but if you decide to do this (a good idea) you will need to reload the STOCK ROMs recovery img using TWRP before you can get Openelec to boot since it uses a functional unlocked down version of Android recovery to do the flash.
If this fails to create a working box it will most likely brick your device, but its a simple matter to reflash the "cyx_m8s_ap6330_8g2g_150728_SD升级.rar" ROM using USB_Flash_Tool and start all over again !!
Hope that works for you.
Stephen
Good to know that a change to openelec can brick it because i tried to install
it. I like more the wetek stuff but my box is cheap chinese trash where the
ota-update have a failure.
Well, it's working but the pvr will not work (said no connection but 127.0.0.1
is already set and ports open in my modem...), and a settop box without the
ability to look tv or streams is useless.
any suggestions how to bring the pvr to work? Os is Kodi 15.2 bc jarvis
refused to run on this box.
Most of the versions of Kodi you get bundled with these packages have got no installed PVR support and no release candidates. They are sold purely as streaming candidates.
The only way to get round this is to completely remove the Kodi version and reinstall it from scratch. This will lose all the preconfigured Addons but most of them are useless anyway. Get a release candidate from the Google Play store or from Kodi Foundation and this should either have PVR support built in or should have a release candidate. Its important to get the right PVR support otherwise it will fail to load the dll of the addon and will report as broken. I had the self same problem with my Kodi version on my Opensuse Linux box and solved it by making sure that both the Kodi build and the PVR build came from the same source. Its not really a Kodi problem and you will get no help from their forums.
Stephen
"Most are useless anyway", so right. I tried to install the wetek firmware
(device is rooted) but it seems this chinese counterfeits miss a lot of
system settings ....change thru twrp and uboot-button also failed.
I'm clueless what to do.
Mine settled down quite nicely in the end. I could be running Openelec if it had AV plug support. As it is I settled for nothing fancy - but a version of KITKAT firmware with a fresh install of Kodi from the Google Playstore, has been working OK for months. Any of the WETEK ROMs are likely to be unsatisfactory. Go back to the post where I point out the specific two ROM's which worked for me and use the ROM burning tool from Amlogic. There is very little to be gained by trying to get anything more complex working.
Stephen
lost finding right firmware
please dont be mad if i did something wrong in this forum i have never post before or subscribe on any forum but here i am very confused with my box (sorry no picture) but here are the spec as a friend opened it once for me :
m8s box from ott (M8S on the top and the sticker on the bottom of the box)
inside amlogic s802b and wifi 6330
connect succes with usb burning tool
didnt find the right firmware, the only one that worked had no wifi no bluetooth and remote issue (with color button) i tried several firmware but invain, your are my last hope,
not looking for openlec, just an android rom sorry again and thanks in advance
Can some one point me in the right direction for the firmware for a t95z plus firmware it's a amlogic s912 chipset with 2gb ram
h t t p s://mega.nz/#F!Ix9zmZqC!LIVPa5zPR6XmcwODW42r7Q
Use this method to flash the box:
h t t p://androidpcreview.com/how-to-use-the-amlogic-usb-burning-tool-to-manually-update-firmware/3749/
You will need an usb to usb male cable. Connect to usb1 on the box. No power cable needed.
Worked for me.
are there newer images.. I bought one of these
https://www.aliexpress.com/item/2GB...73409096.html?spm=2114.search0104.8.57.YrpUy2
[Genuine] T95Z Plus 2GB 16GB 3GB 32GB Amlogic S912 Octa Core Android 7.1 OS Smart TV BOX 2.4G/5GHz WiFi BT4.0 4K pk X92 h96 pro+
I got the 3g/32g rom was fast and seemed ok android 7.1
until I upgraded or installed the superuser from chain DD said installed ok and asked to reboot which
I did for it only to hang on the boot animation... so very sad
I suspect its altered or written to the wrong partition?
now need to reflash
recovery works with toothpick
is there a image for this new update? and can it be flash from recovery from sd card so dont need a pc
as pc cable method is more a pain
Firmware for t95p ?
(3GB)
T95ZPLUS-7.1-912-3GB-17.3-v1072
https://goo.gl/RG92GR
by the way, who also want a 2GB or directly dl from their link are also welcome,
Below are the links from sunvell,
(2GB)
T95ZPLUS-7.1-912-2GB-17.3-v1013
http://pan.baidu.com/s/1jl7jLOU
Pw: 81uc
(3GB)
T95ZPLUS-7.1-912-3GB-17.3-v1072
http://pan.baidu.com/s/1hrPU5rY
Pw: gbrg
I add the info for others with bricked boxes or bad ram.. reformat reflash can bring them back
also try a new power pack.. often the voltage degrades over years and drops too low
I used the 3gb with the flashing tool usb to right sid port... leave power plug out.. and insert toothpick and
connect usb from pc.. should beep if pc detects device on USB and the tool should show finally
http://androidpcreview.com/how-to-use-the-amlogic-usb-burning-tool-to-manually-update-firmware/3749/
http://androidpcreview.com/wp-content/uploads/2015/12/USB_Burning_Tool_v2.0.6.2_build2.rar
---------- Post added at 12:49 AM ---------- Previous post was at 12:43 AM ----------
endera said:
Firmware for t95p ?
Click to expand...
Click to collapse
you could try asking these guys
http://freaktab.com/forum/tv-player...s/s905x/607678-sunvell-t95p-tv-box-2-8gb-wifi
I thought i read some 95z plus roms will work but not sure.
---------- Post added at 01:02 AM ---------- Previous post was at 12:49 AM ----------
endera said:
Firmware for t95p ?
Click to expand...
Click to collapse
similar cpu
http://chinagadgetsreviews.com/firmware-t95x-tv-box.html
(2GB)
T95ZPLUS-7.1-912-2GB-17.3-v1013
http://pan.baidu.com/s/1jl7jLOU
Pw: 81uc
The above link for 2GB is not working, also can you please clarify for which WiFi chip is the above firmware? There are three versions of T95Z Plus: WiFi 8830, WiFi 6330 and WiFi 6335. If one flashes the wrong version, then WiFi will not be working on his box...
Thanks for this thread. I am fighting with a T95z PLUS 3/32GB stuck on boot. I am going to try the above ROM (the one in gdrive is still available) as soon as I can get a USB cable, and report the results.
EDIT: Is there a way to flash from SD? I have no usb-to-usb cable to try right now, I am going to have to buy one and wait for it...
EDIT 2: Flashed through SD directly. Extracted the contents to a FAT32 formatted SD card and inserted it in the T95Z Plus. Booted normally and proceeded to "upgrade". The box is working right now. Sound are wifi are working - cannot say more than that so far. I don't know if the version is older than the original that came with the box, but I guess it should be possible to update if necessary (not sure how, though).
Thanks @kiwiman2000!
I can see from the boot screen that the firmware posted for the 3/32GB model by Kiwiman2000 with which I recovered my box is the 20170623 version. I know that the one my box had before rescuing it was 20170807, so it is possible that somewhere a newer version is available. The OTA updater is not finding anything online, though. In the meantime I will stick with this working version, and if I happen to find an update, I will post it here.
After playing around with the T95z Plus after installing the above firmware, I started noticing some bugs. First, the Play Store resets itself constantly. It seems every time it updates from the factory version to the current one, whenever you open it, it goes back to factory, asks for permissions again, and resets all settings.
I have tried to replace the system apk with an updated version. This works but only when starting it for the first time. It then fails to open, and will only open again after clearing the app data.
Does anyne know how to correctly fix a broken gapps?
Latest T95Z Plus Firmware. Android v7.1.1 For 2GB RAM/16GB S912 Chipset
Here is the latest firmware for the T95Z Plus Android tv box. Works on Sunvell, and also on Weily branded T95Z plus and probably all models with same chipset. Says android 7.1.2 but it’s actually 7.1.1. Latest firmware for this box tho. Runs great.
Google search “latest t95z plus firmware” and it’ll be the first site you see called entertainmentbox. I can’t post links here as I’m a new user.
You don’t need to use the male to male USB cable method to flash firmware. You can use Burn Card maker and update box using micro sd card. USB burn card maker can flash new firmware and also revive bricked Amlogic based android tv boxes.
search on YouTube for “t95z plus burn card maker” and there are many videos on how to use this method.
Hope this helps, it will get your box updated to Android v7.1.1 build T5ZP1013 kernel v3.14.29 android security patch level February 1, 2017 Model T95ZPLUS despite the build saying T5ZP1013. I assure you it’s the T95Z Plus firmware.
As for google play updating, then returning back to previous version and default settings every time I believe this is to keep the box running without breaking any apps or software for the current firmware. You really only need the version the firmware comes with. If you wish to update keep a lookout for future firmware releases. My box has the same issue as do others I have asked. I also like to have the latest version of everything too so this is what prompted me to check into the google play thing myself.
Happy Flashing!!! -~
T95z Plus will not flash
I have tried over 7 different roms, different usb, ect all the same result
UBOOT/Partition _aml_dtb/Verify patition/Error result can't pass 9%
What does that mean??
Hi friends, which application is responsible for display (LED) on the device?
victorsyt said:
Hi friends, which application is responsible for display (LED) on the device?
Click to expand...
Click to collapse
It's the WinS8Launcher system app. This also five the CEC options in the settings.
mr sharpey said:
It's the WinS8Launcher system app. This also five the CEC options in the settings.
Click to expand...
Click to collapse
Thanks. It's important.
I ran into this problem, since Kodi wasn't playing right. I used a script program universal init.d and supersu, and after supersu rebooted the device it hung on reboot. I have an easytone t95zplus but don't see any of their firmware posted online.
startreksuite said:
I ran into this problem, since Kodi wasn't playing right. I used a script program universal init.d and supersu, and after supersu rebooted the device it hung on reboot. I have an easytone t95zplus but don't see any of their firmware posted online.
Click to expand...
Click to collapse
You first need to determine the precise model to get the firmware:
1) Is it a 16 or 32 GB model?
2) Is it model q200 or q201?
You can check these by booting into recovery.
Need files for recovery
Hello guys, i need some dire help.
i have a 3G 32GB variant with AP6255.
my wifi was broken hence i browsed thru and was flashing the firmwares using tooth pick method.
1st attempt. - my recovery didnt boot at all. no HDMI signal was going to the TV
2nd attempt - managed to boot to recovery and flashed the firmware. wifi was not fixed.
3rd attempt onwards i could never get into recovery.
looks like my sd card marker is missing some boot files.
appreciate someone could guide me the extact steps and files i need for recovery to work.
archrival9 said:
looks like my sd card marker is missing some boot files.
appreciate someone could guide me the extact steps and files i need for recovery to work.
Click to expand...
Click to collapse
I am not sure of how to help you- but I will tell you this: I did not use a SD card maker. I just pasted the img file into the root of the SD card AND also included the extra files (which I believe are needed for proper boot and installing) from a different img file package I found somewhere else. So, tell me if this can make sense somehow:
Get the img file you tried to use in step 3 and put it in a SD along the extra files included in the package you used in the second attempt.
This is sort of the way I had to go to fix mine (although, for the sake of truth, my box is pretty unstable now - freeezes and hangs often). I hope an update would come out, but nothing so far.
Hi everybody, I'm just posting to let you know that I have very much upgraded my T95Z Plus 3/32 through the instructions in this thread, which includes firmware and recovery files.
Hopefully someone else can give it a try.
hello,
what / where is the last upgrade / custom rom for T95z plus 2/16gb S912 ?
World first recovery flashable ROM for android TV boxes!
WARNING: This rom is under heavy development. There are bugs, bootloops and internal issues.
STRICTLY A DEVELOPMENT THREAD.
For a stable rom check out PoisonRom
A lot of effort and research was put into this device and will be put into the Amlogic ROM tool(A tool for creating roms for Amlogic devices(any android version)) so consider making a donation to me or buying me a beer by clicking on my name a clicking the "Donate to me" button!
Our TV Boxes are finally treated like standard android devices from this point on!
So here it is, this ROM is for the T95Z Plus 2/16GB variant, its stock 7.1.2(not 7.1.1) ported from the 3/32GB variant!
MAKE SURE YOU HAVE THE TWRP RECOVERY!
Here are instructions to install TWRP if you havent already.
Recovery
So far we have a working recovery(TWRP) thanks to @rrvuhpg
You can download it from HERE for the 2/16GB T95Z variant(Mirrored and renamed custom-recovery.img for the sake of flashing instructions)
Flash instructions
1. Download ADB and install it on your pc(not explaining this, there are 5 second installers) then open a command prompt in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
ROM
Instructions:
1. Download the 2_16GB_7.1.2.zip from HERE
and put it on a usb stick.
2. Reboot into recovery(not explaining this)
3. Go to mount and mount USB-OTG
4. Go back to the main menu and select install, then choose the 2_16GB_7.1.2.zip and swipe to install!
Reboot and enjoy!
NOTE: Remember to make a backup in recovery before flashing!
XDA:DevDB Information
T95Z Plus Stock 7.1.2 2/16GB Ported from 3/32GB, ROM for the Android Stick & Console Computers
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2018-02-05
Last Updated 2018-02-19
So witch wifi module is support?.
Will be work on sunvell t95k pro 2/16gb and LTM8830 wifi module?
rumunn95 said:
So witch wifi module is support?.
Will be work on sunvell t95k pro 2/16gb and LTM8830 wifi module?
Click to expand...
Click to collapse
Wifi module is not a factor anymore.
Aslong as your device is 2/16GB this could possibly work.
great to hear this i will be testing
I had no PC around (at least not in the same ip-range
So, i installed the Flashify app and used that instead...works great! So now i have TWRP 'loaded' i will give it a go in a few minutes....#fingerscrossed #yeah
Well...no USB-stick or microsdcard laying around at the moment and i also use 1 usb port for power and the other for remote control. So I ended up downloading the ROM directly to my T95Zplus.....no errore during flashing, wiped cache/dalvik and rebooting right now and so far so good...!
ZeroZorro said:
I had no PC around (at least not in the same ip-range
So, i installed the Flashify app and used that instead...works great! So now i have TWRP 'loaded' i will give it a go in a few minutes....#fingerscrossed #yeah
Well...no USB-stick or microsdcard laying around at the moment and i also use 1 usb port for power and the other for remote control. So I ended up downloading the ROM directly to my T95Zplus.....no errore during flashing, wiped cache/dalvik and rebooting right now and so far so good...!
Click to expand...
Click to collapse
Well...that did not work....rebooted and after 15 minutes still nothing except the boot-screen (and before that animation)...so gonna try to figure out what went wrong...
So be warned if you are gonna try it like i did and not following OP to the letter!
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
Well...that did not work....rebooted and after 15 minutes still nothing except the boot-screen (and before that animation)...so gonna try to figure out what went wrong...
So be warned if you are gonna try it like i did and not following OP to the letter!
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
Quite odd, if you flashed the rom in recovery, it should have worked :/
I did find a bug though, endless reboot if you try connecting wifi
So it's canned now
Ricky Divjakovski said:
...I did find a bug though, endless reboot if you try connecting wifi
So it's canned now
Click to expand...
Click to collapse
I didn't get a boot loop; however, attempt to activate wifi resulted in wifi switch button moving to on position and after ~3 seconds returning to the off position. Is it possible this needs to be debugged on a per-wireless-chipset basis? I'm on 8830 q201_6255....
Please advise and let me know if I can help out with logs, etc.
Thanks
LAX_2_TLV said:
I didn't get a boot loop; however, attempt to activate wifi resulted in wifi switch button moving to on position and after ~3 seconds returning to the off position. Is it possible this needs to be debugged on a per-wireless-chipset basis? I'm on 8830....
Please advise and let me know if I can help out with logs, etc.
Thanks
Click to expand...
Click to collapse
From which firmware did you flash?
I don't know if partitions are different sizes and maybe that did trigger the bootloop? I come from goo.gl/hWrmxY (Android 7.1.1 with root, 1013) and that did not work so far...
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
From which firmware did you flash?
I don't know if partitions are different sizes and maybe that did trigger the bootloop? I come from goo.gl/hWrmxY (Android 7.1.1 with root, 1013) and that did not work so far...
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
I flashed on top of stock 1013 rooted with magisk
LAX_2_TLV said:
I flashed on top of stock 1013 rooted with magisk
Click to expand...
Click to collapse
Well...gave it another shot. Flashed 1013 ROM with USB Card Maker. Flashed TWRP and after that this ROM. Same issue....
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
Well...gave it another shot. Flashed 1013 ROM with USB Card Maker. Flashed TWRP and after that this ROM. Same issue....
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
Im gonna update it tonight, ill need someone to PM me, im gonna need someone to test as i dont have my TV box with me and im away on buisness, i think i have found the wifi bug, but as you can tell with the ROM ram usage is ALOT less, framework is much smoother and alot of apps have been updated from the manufacturer
Ill also be basing it on the newest build 1075(Or if anyone has a newer build PM me)
This rom will be pretty stock with more features implemented and possibly some apps i might make ffor the device
Ricky Divjakovski said:
Im gonna update it tonight, ill need someone to PM me, im gonna need someone to test as i dont have my TV box with me and im away on buisness, i think i have found the wifi bug, but as you can tell with the ROM ram usage is ALOT less, framework is much smoother and alot of apps have been updated from the manufacturer
Ill also be basing it on the newest build 1075(Or if anyone has a newer build PM me)
This rom will be pretty stock with more features implemented and possibly some apps i might make ffor the device
Click to expand...
Click to collapse
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
papla83 said:
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
Click to expand...
Click to collapse
yes thats a bug, this is mean for 2/16GB variants, this is exactly like stock 7.1.2, if you have 3/32GB variant flash stock 7.1.2(build 1075)
Ricky Divjakovski said:
yes thats a bug, this is mean for 2/16GB variants, this is exactly like stock 7.1.2, if you have 3/32GB variant flash stock 7.1.2(build 1075)
Click to expand...
Click to collapse
if i flash it with the 3gb/32gb rom version the box doesn't boot. the 1075 is for 32gb and i allready tried with no success.
papla83 said:
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
Click to expand...
Click to collapse
The CEC support is found under Droid Settings in apps mate.
whiteak said:
The CEC support is found under Droid Settings in apps mate.
Click to expand...
Click to collapse
OK. Thanks. I'm waiting for an solution about the connection trouble.
Maybe you can consider to bake a little reboot app (i use Simple Reboot) into the ROM cause it makes it much easier to test and restore/backup especially when there is no internet with this ROM at the moment.
For now I have some apk's ready on a sdcard so I will get there but would make things a little easier...
ZeroZorro said:
Maybe you can consider to bake a little reboot app (i use Simple Reboot) into the ROM cause it makes it much easier to test and restore/backup especially when there is no internet with this ROM at the moment.
For now I have some apk's ready on a sdcard so I will get there but would make things a little easier...
Click to expand...
Click to collapse
will do!
adb connect not working
Hi,
Thank you very much for all your effort Ricky. I have T95Z Plus 2/16 variatnt. I am unable to connect to my TV box using adb. I have USB debugging enabled on my TV box. The TV box and my Mac from where I am trying to run adb commands are on the same wifi network. I have tried connecting my TV box to my Mac using USB cable but still adb connection fails with error "Host is down" and sometimes "Operation timed out".
I cannot proceed further without this step. Any help is much appreciated.
Apart from adb, can I copy the files into SD card or USB drive and install it? If so, what will be the steps?
Thanks again!
Hello, I have this tv box (MXQ Pro+ S905) 2GB RAM / 16GB ROM
The stock firmware is horrible, can you help me to upgrade it?
Do you have some firmware?
I tried to flash some firmware, but i think they was incompatible, i got only errors
Originally bought two identical MXpro Android TV Boxes. Since one of them freezes at startup on Android logo (won't enter launcher). My question: is there any way to copy certain files & folders directly from the other identical box to get it to boot up correctly once again? *issue is that I have no use of any computer at the moment. Either this method or any other suggestions would be greatly appreciated! Thanks! -Dave.D.
LordMauryZ said:
Hello, I have this tv box (MXQ Pro+ S905) 2GB RAM / 16GB ROM
The stock firmware is horrible, can you help me to upgrade it?
Do you have some firmware?
I tried to flash some firmware, but i think they was incompatible, i got only errors
Click to expand...
Click to collapse
If you have s905X with blue board than try this one :
https://mega.nz/#!jQ8HWIoQ!ubMpueVYGPA_PtE9snE1buZXjLUeFJP-mOd6vX91wkw
what you need to do is procure the factory image. i may be wrong but there isn't a S905 with 2 gb ram and 16gb nand. the first ones were S905x (excluding capabilities of the S912). there are plenty of alternative roms available including linux based. search around and you will find your firmware. you can even contact the seller you bought it from including amazon and ebay. check chinagadgetreviews.com also. alot can be found there. theres other forums too. once you find your correct firmware, reflash it and see if that resolves your issues. if not. boot twrp on the other one and make a full backup. take this backup, and move it to an area on your sd where you can find it then restore it on the buggy box. make sure you keep a backup copy of everything that works, especially if you cannot find the original. if you look really really hard, you may even find some fully compatible generic images that some developers are kind enough to maintain. you may need to make friends with a ruski to get it tough. thats the best hint im willing to give without provoking any admins or mods (sorry guys if i broke any rules).
im going back under my rock now.
oh and another tip, not all devices are the same. even if they say the same brand. there are differences in wifi chips. you should be able to figure this out. usually theres some model or sticker on the bottom or on the box it came in
LordMauryZ said:
Hello, I have this tv box (MXQ Pro+ S905) 2GB RAM / 16GB ROM
The stock firmware is horrible, can you help me to upgrade it?
Do you have some firmware?
I tried to flash some firmware, but i think they was incompatible, i got only errors
Click to expand...
Click to collapse
I HAVE SAME PROBLEM HERE...JUST 1MONTH BACK I PURCHASED MXQ PRO 2GB 16GB ROM...S 605W BUT UNFORTUNATELY IT HAS STUCKED WITH A LOGO ....NOTHING MORE...
SEVERAL TRIED TILL UNABLE TO DETECT PC
I have android tv 7 roms for s905x and android tv 9 roms for s905x s905w and s912 based boxes https://aidansrom.wordpress.com
aidanmacgregor said:
I have android tv 7 roms for s905x and android tv 9 roms for s905x s905w and s912 based boxes https://aidansrom.wordpress.com
Click to expand...
Click to collapse
not detecting box by usb burning tool...
mbox55980 said:
not detecting box by usb burning tool...
Click to expand...
Click to collapse
ahh, you may need to figure out "Mask Rom Mode" to force your device to be detected by burn tool, assuming you have already tried different usb port on pc, reinstalling burn tool & Also tryed adding power at same time connecting the usb cable
Hello, I have Magicsee N5 Plus Android 9.0 TV Box Amlogic S905X3
But I cannot spread it the status-bar / notification bar..
I need messages from there.
If I change, I installed the Notification History app, I got message. Cannot access for notification, not implemented.
Do you have any idea, how can I hack?
Thanks;
That is because of the writeover of the cpu stats like speed and temp. No way around it. I just use a different firmware (Tanix TX3) and the only thing i lost was the clock display. Everything else worked fine. Hope this helps.
samsungmario said:
That is because of the writeover of the cpu stats like speed and temp. No way around it. I just use a different firmware (Tanix TX3) and the only thing i lost was the clock display. Everything else worked fine. Hope this helps.
Click to expand...
Click to collapse
hey bro.How you flashed this firmware?i consider buy this box among x96 air,tanix tx3,f3,gt1 mini 2.are there any problems with this box?
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
hey bro.How you flashed this firmware?i consider buy this box among x96 air,tanix tx3,f3,gt1 mini 2.are there any problems with this box?
kos25k said:
hey bro.How you flashed this firmware?i consider buy this box among x96 air,tanix tx3,f3,gt1 mini 2.are there any problems with this box?
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
hey bro.How you flashed this firmware?i consider buy this box among x96 air,tanix tx3,f3,gt1 mini 2.are there any problems with this box?
Click to expand...
Click to collapse
Just flash Tanix TX3 firmware (android 9) like you would any other - i used sdcard burn tool and hold reset button while powering on the box.
I would not recommend this box. It looks nice on the outside but the components are cheap on the inside. The ram is still DDR3 and my wifi wasn't working after a week. The main issue is heat. Although there are vents, the box gets very hot and the cpu does not have a big enough heatsink.
samsungmario said:
Just flash Tanix TX3 firmware (android 9) like you would any other - i used sdcard burn tool and hold reset button while powering on the box.
I would not recommend this box. It looks nice on the outside but the components are cheap on the inside. The ram is still DDR3 and my wifi wasn't working after a week. The main issue is heat. Although there are vents, the box gets very hot and the cpu does not have a big enough heatsink.
Click to expand...
Click to collapse
thanks for info bro!i liked this box because i thought it could give me plently space to install a mini fun (under ssd holes) but now i am thinking to go straight to an S922 box.Particularly Ugoos AM6 Pro!
Στάλθηκε από το Redmi 4 Prime μου χρησιμοποιώντας Tapatalk
Flashed the tx3 rom as suggested, after the usual stuffing around with the remote, I must say it runs great! A lot faster than with the crappo original firmware. Only thing I noticed was after fixing the remote (this is the first time I have had to stuff around to get a remote working, and I also edited the init.rc) everything works brilliantly however I lost root access, which to me isn't a big deal so I'm super happy with it now. After I emailed the seller about K*di not displaying correctly, they offered me a partial refund of $15 which I accepted, so extra bonus.
Have now flashed the BZ-TX3-20191130_ATV9_davietPDA ATV ROM from pda. (Android TV 9)
So far it works great!!! Very minimal and very fast.
https://4pda.ru/forum/index.php?showtopic=969245&st=940#entry92946437
I used the BZ version (same as the TX3 ROM I downloaded).
There is some mention that the Ethernet may not work, but I only use WiFi so haven't checked and the WiFi works great.
I copied the remote-0xfe01.tab file from my original factory ROM to /vendor/etc renamed the remote.tab1 to remote.tab1.old and renamed remote-0xfe01.tab to remote.tab1 rebooted and remote works perfectly and no issues with affecting anything else either.
Almost forgot... Language is set to Russian so go to settings and change first up. (Language is the icon that looks a bit like a globe).
So..... I may have been a bit hasty with the last, as soon as I moved my N5 from the office to the lounge room my WiFi went to crap.
I am now trying SLIMBOX N5MAX X3 ATV OTA
https://4pda.ru/forum/index.php?showtopic=973352&view=findpost&p=93085504
First install the N5MAX_X3_152_MGCTV15220191225_8822BS_100M_Magicsee firmware from the manufacturer site and let it load at least once and connect to your WiFi, then flash the SLIMBOX-N5MAX-X3-ATV-OTA zip with TWRP. It says can use stock recovery to do it as well, but I used TWRP.
So far so good.
After running for a couple of weeks I can say it works great! Hasn't crashed, WiFi great, Very responsive!
Only thing is when I went to pair my new BT keyboard II couldn't see the pairing key. Went into settings and turned on High Contrast and tried again and could see fine. Then disabled afterwards.
Definitely recommend Slimbox!
Hi,
I have a N5PLUS S905X3, but the stock firmware i constantly freezing.
Is SLIMBOX-system-ATV-ver5.1 the firmware that you talk about?
Can you also please give me detailed instructions on how to update? I am kind of new to this and I am afraid I am going to brick it.
Thanks in advance
r17019 said:
So..... I may have been a bit hasty with the last, as soon as I moved my N5 from the office to the lounge room my WiFi went to crap.
I am now trying SLIMBOX N5MAX X3 ATV OTA
https://4pda.ru/forum/index.php?showtopic=973352&view=findpost&p=93085504
First install the N5MAX_X3_152_MGCTV15220191225_8822BS_100M_Magicsee firmware from the manufacturer site and let it load at least once and connect to your WiFi, then flash the SLIMBOX-N5MAX-X3-ATV-OTA zip with TWRP. It says can use stock recovery to do it as well, but I used TWRP.
So far so good.
Click to expand...
Click to collapse
Hi, your experience is very interesting. I want to install Slimbox version, and maybe a linux later ... But I can't flash it !!! Where is the RESET Button ??? If I link the box to the PC, Box is started the system ... And PC didn't see the box ... So ... Burning tool too ....
==> OK ! I Find It !!! It is inside AV plug !!!
r17019 said:
So..... I may have been a bit hasty with the last, as soon as I moved my N5 from the office to the lounge room my WiFi went to crap.
I am now trying SLIMBOX N5MAX X3 ATV OTA
https://4pda.ru/forum/index.php?showtopic=973352&view=findpost&p=93085504
First install the N5MAX_X3_152_MGCTV15220191225_8822BS_100M_Magicsee firmware from the manufacturer site and let it load at least once and connect to your WiFi, then flash the SLIMBOX-N5MAX-X3-ATV-OTA zip with TWRP. It says can use stock recovery to do it as well, but I used TWRP.
So far so good.
Click to expand...
Click to collapse
I get the last SlimBox ATV 12.2 for N5 Max (sbx_n5max_x3_atv_v12_2.7z), and flash it with Burning Tools : It works perfectly !
Also I did successfully flash Slimbox TV v9.3 (for the Magicsee N5 Max X3) into a Magicsee N5 Plus. I almost forgot I had it and was about to throw it away. After some digging on the internet I decided to take the risk and flash it.
Another happy 'customer': Everything worked after flashing without any modification: the remote, internal hard disk, Bluetooth, WiFi and Ethernet.
I just did an overwrite of the original crappy Magicsee firmware with the USB flashing tool via the USB 2.0 port. Simple as that. It's like you have a brand new (and much, much snappier!) tv box.
Choose your flavor from this link (thanks to SlimboxTV!): https://disk.yandex.ru/d/dAgGXJ8GfBHdVA and flash it.
It's still on your own risk but it is definitely worth trying. The Magicsee firmware is (to put it mildly) total crap and a shame for the hardware it is running on. The N5 plus is in my opinion also somewhat unique with an option for an internal harddrive. Slimbox really revived my N5 plus!
Also very handy: the SMB app that also can be found on the slimbox site. This enables you to share the internal hard drive via SMB on your network. No top speeds, but still very convenient.