Related
I have an rooted Android (4.4.2 Ugoos UG802 mini PC) device, mini PC (without screen or buttons) with Rockchip RK3066.
I was trying to create an image of its ROM using ROM manager (on Google Play), but when I tried to backup current ROM, it turned off and then said 'No command' with resting android.
MiniPC doesn't have volume buttons so I was unable to go through this problem.
After that, I tried romdump using tutorial, but although I have many files now, (f.e. boot.img or system.tar) I do not clearly understand what should I do with all those files. My intention is to get update.img which I can flash to other device.
Any help would be appreciated.
P.S.: I would like to add some links, but I cannot do that.
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
My Chinese Android car head unit is stuck in a bootloop (the home screen shows but the unit reboots after a few seconds). I got a firmware zip file from the manufacturer (the zip contains files like scatter.txt, ramdisk2.img, boot.img and so on). However, I'm unable how to find out how on earth I can install this firmware and get out of my bootloop.
I have no access to Android itself (the system reboots too soon). There are no physical buttons to activate recovery mode. When I use a USB keyboard I can get into recovery by pressing ALT GR and PRT SCR but after a reset "no command" shows up and I'm stuck again...
Any help please?
Flashing instructions
[Apologies for the lengthy reply, I have to assume that you have no experience in flashing MTK SoC]
Sorry to hear that! I am also contemplating t buy a Chinese Android headunit with GPS but I am still contemplating. Reason being which model to buy? I am an avid Lenovo devices fan because in my part of the world models from Lenovo uses a lot of MTK SoC. (Any other other brand I buy is also a must to be on MTK SoC)
Ok! Now based on your short description I saw "scatter.txt" file mentioned so it is definitely an MTK devices, 100%.. When you boot loop you definitely will not be able to access any function, more so with a head unit that dont provide hardware buttons. I can only help you understand the method to reflash the firmware on MTK devices the rest you have to figure it out yourself.
The USB port is your key here. If the manufacturer did not provide you with USB "IN" (female) port which is not normal and only provide you with USB connectors you will have to decode/or just connect the wiring from the connectors to a USB female Port (which what China manufacturers do at the back of the head unit). There are also head units that provide ready to use USB port on the facia.
Whatever it is I cant tell you which port to use. This where you will have to experiment yourself.
Download MTK flashing tool "SP Flashtool" (find the ones that is suitable upto MTK device 6592 because it should be back ward compatible with older devices) The Chinese dont use the latest MTK SoC for their head units, that is only reserved for the high end heads.
Read up on how to install SP Flashtool on your PC and other accompanying Drivers you have to install, (if you only have a Mac go borrow somebodys Win7 or Win10 PC) there are no Mac SPFlashtool.
Once you have install according to SPFlashtool instructions you read. (It has to follow a certain sequence) e.g "1- ADB Driver" so on and so forth because if you dont follow the sequence it might fail to start the flashing operation. (You will not know it but I am pretty damn sure you will be cussing me).
First read up on how to install ADB driver for MTK devices correctly. Confident? Now try connecting your device to the PC experimenting to identify the correct USB port to use. If the ADB is installed correctly and you got the right USB from the device connected your PC wil give an audible sound( it should unconnected to condition evreytime you test). OK good connection! Only then try installing SP Flash tool and try a dry running the SPFT. If your installation is correct there should be either color changes to the SPFT window because it doesnt detect any devices.
You are good to go! Your MTK Android device should be in the "OFF" condition (after every shutdown there are still some operation running in the background,so it is a good practice to wait at least 5 seconds for it to be 100% OFF.) Run the SPFT fully loaded with the firmware dislayed in the SPFT window. Then initiate "Download" (make sure all indicators is at "download only" do not change this option or you are gonna have a really dead duck.) At this point the SPFT is active and waiting for you to attach the device to PC (before running make sure the PC and device is not connected yet!). If everything is per instructed ADB, USB Cables/Ports, SPFlashTool (download only) you will see color lines in the SPFT Window, wait till the end of process it will display notificatio. If the firmware is correct and you have attached and 12V DC source to the device it should boot up as fresh as new.(provided that the supplier gave you the correct firmware).
A word of advise these cheap head units normally bluff their actual Android version e.g actual KitKat advertised and displayed as Marshmallow. Best of luck!
The zip file attached are screenshots of the flashing process.
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
wimpie3 said:
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
Click to expand...
Click to collapse
Doesnt the seller provide you with the original firmware? He only gave you an OTA?? Oh $#it! The OTA file is small probably a few Mb? The full firmware in your case should be around 800Mb upwards. You are right an OTA cannot use SPFT it can only be flash through the original recovery (not custom recovery). If its a popular Chinese model ML-CK1018 or Joying brand ( I assume you bought a Joying? Thats the only brand that release an OTA not long ago) There is remote possibility of getting the firmware.Anyway just give your brand and model number. I will try to look on Russian or Chinese site but no promises! Will try.
But I am pretty sure it is an MTK SoC since you can unzipped and it shows "scatter.txt" file. Most other SoC arent normally in zip format and have scatter file.
Sent from my HT70 using Tapatalk
The OTA ZIP file is about 900MB.
It's a NAVITOPIA 9 inch 4G LTE WIFI Head Unit with Android 6.0 2G + 32G.
I'm in the same boat, have a plastic bookend at the moment, will not connect to the PC because flashed and formatted my device with the update firmware!!!
T95 MAX - AEROMEDIA NANOMAX (T95 MAX Clone) ALLWINNER H6 CHIPSET EXCELLENT REPLACEMENT CUSTOM FIRMWARE BY [email protected]/FREAKTAB ANDROID 7.1.2 NOUGAT
When flashing your box with firmware there is always risks and these risks are to be understood solely by the user. Please understand that neither I or anyone at xda can be held liable for what you decide to do to your box.
I have seen many struggle to get a replacement firmware for the T95Max/ Nanomax box from Justopuk.
I am posting this for anyone who wants it and will link to instructions on how to replace the horrible stock firmware on the above boxes..
what's in it? This rom has been tweaked for better performance, much better kernel tuning and thermals, comes with magisk 19 which can be updated. Nova Launcher which can also be updated.
wht doesn't work? some lose ability of stock remote, this can be replaced via airmouse/keyboard and there is built in "advanced power menu! Quick reboot app to power off/on boot to recovery etc
T95MAX_SCV2.img Rom here :
https://mega.nz/file/iIsymLoD#UjQ6kp4UoTQus4XaUgujrsKX7Wd0tIT5KKZN9q0uk1g
Unofficial TWRP : This needs to be placed on USB and once you have flashed the rom, boot into recovery, apply update from external. This will USB boot to TWRP and let you back/up restore either from ext/int sdcard.
TWRP_TX6. IMG https://mega.nz/file/bZlmmZJC#-0mwsuzImK25aPWRaXFWCgiO-CzfI3ma-W01VOC90y8
Phoenix USB 4.0 :
https://mega.nz/folder/jd0GEZJQ#7_GRu5o9Ll3AygdetcdPNQ
T95max Instructions for flashing :
Download and extract from the archive Phoenix USB Pro 4.0
Download and Install USB_android driver
Install the driver by specifying the path via device driver in Windows (you may need to disable the driver's digital signature verification )
Restart the PC (although the driver is signed and everything went well without it).
Launch PHOENIX USB PRO , select THE T95MAX_SCV2. IMG File.
We will need a USB-A to USB-A cable
Then connect the cable to the PC,
Take a toothpick or something like that and insert it into the jack 3.5 (sound output) and press the button hidden there.
Connect the USB-USB cable to the set-top box to the USB 2.0 connector in the centre (T95Max)
Keep the button pressed, Until you see a green tick on screen (phoenix usb Pro gui)
You will see the progress as Phoenix begins preparation of the Flash
after the computer has identified the set-top box, release the button and connect the power cable.
Wait until it displays end/finish firmware then Unplug USB to USB and plug the dc power back in for first boot.
Enjoy
Rom twrp courtesy of beny and 4pda
@Bertonumber1, saw your question on freaktab and just wanted to say to the best of my knowledge you can't make TWRP the permanent recovery. you've gotta load it up each time you wanna use it on other boxes too.
3mel said:
@Bertonumber1, saw your question on freaktab and just wanted to say to the best of my knowledge you can't make TWRP the permanent recovery. you've gotta load it up each time you wanna use it on other boxes too.
Click to expand...
Click to collapse
Yeah mate, needs to be booted rom the USB. I figured that a while ago after messing aournd with this box and another couple I had. But thanks anyway for letting me know. :good: cheers
if I get another box in the future I'll make sure it's a pre android 10 AMLogic chipset box. that forum is buzzing with roms and mods.
3mel said:
if I get another box in the future I'll make sure it's a pre android 10 AMLogic chipset box. that forum is buzzing with roms and mods.
Click to expand...
Click to collapse
Yeah, this box I have is okay, It works better on nougat than it did on pie, I'm happy with it.
I lost the stock remote but always use the rii keyboard / airmouse anyway and use advanced reboot app to turn off so its not too much of a loss.
I prefer Allwinner devices to Amlogic and have tried allsorts of different devices and roms.
IMO after all the modding and tweaking over the years. I think it's best just to update your stock rom to the latest security patch etc, root, debloat and get a custom launcher.
Unless your running a stable rom, the bugs and problems just ain't worth the hassle.
@deano2011 here's example of active cooling, it don't need to be perfect m8 just make sure it's sealed so the air flows to the board :good:
Aeromedia (Justopuk) Nanomax (T95max Clone) - Shipped with Android 9 stock Unrooted.
Flashed with [email protected] build T95Max_SCV2.IMG via Phoenix USB Pro 4.0 (windows 10)
Rooted Android 7, WiFi Bt chromecast all working,
Stock remote don't work but Airmouse does.
Strip all unnecessary apps, replace webview with bromite and Adaway.
Result : heats up a little under heavy usage but fan takes care of that, expect 32 degrees when active cooling (raspberry pi 4b case fan) is activated.
Bertonumber1 said:
@deano2011 here's example of active cooling, it don't need to be perfect m8 just make sure it's sealed so the air flows to the board :good:
Aeromedia (Justopuk) Nanomax (T95max Clone) - Shipped with Android 9 stock Unrooted.
Flashed with [email protected] build T95Max_SCV2.IMG via Phoenix USB Pro 4.0 (windows 10)
Rooted Android 7, WiFi Bt chromecast all working,
Stock remote don't work but Airmouse does.
Strip all unnecessary apps, replace webview with bromite and Adaway.
Result : heats up a little under heavy usage but fan takes care of that, expect 32 degrees when active cooling (raspberry pi 4b case fan) is activated.
Click to expand...
Click to collapse
many thanks Berton' i will most likely give it a shot bud' at least the cpu/gpu won't be throttled under load with active cooling as the allwinner H6 chipset does get rather hot anyways with the manufacturer process of the chip being 28nm vs S905X2/X3 12nm process :good:
Bertonumber1 said:
Yeah, this box I have is okay, It works better on nougat than it did on pie, I'm happy with it.
I lost the stock remote but always use the rii keyboard / airmouse anyway and use advanced reboot app to turn off so its not too much of a loss.
I prefer Allwinner devices to Amlogic and have tried allsorts of different devices and roms.
IMO after all the modding and tweaking over the years. I think it's best just to update your stock rom to the latest security patch etc, root, debloat and get a custom launcher.
Unless your running a stable rom, the bugs and problems just ain't worth the hassle.
Click to expand...
Click to collapse
I agree with you about stability (and with phones, optimisation) being better on stock roms but I want a recents menu and notification bar. I don't think these fly by night brands put in the effort to create a good product.
3mel said:
I agree with you about stability (and with phones, optimisation) being better on stock roms but I want a recents menu and notification bar. I don't think these fly by night brands put in the effort to create a good product.
Click to expand...
Click to collapse
Definitely, I think these roms have just been thrown together to get ppl up and running quickly with regard to movies etc, you're right, no thought has been put into settings menu, I noticed the only way you can access developer menu is to search for a setting lol.
But hats off to the guy beny he did make good progress on what was already a shockingly bad Chinese stock firmware
hello, can you help me. I can't flash image files on Phoenix USB 4.0 and can't figure out why.
mmh any recommended Android 9 image with root? Kidn regards
Hi, this firmware, is a normal android firmware, not an android TV, is this?
Bertonumber1 said:
T95 MAX - AEROMEDIA NANOMAX (T95 MAX Clone) ALLWINNER H6 CHIPSET EXCELLENT REPLACEMENT CUSTOM FIRMWARE BY [email protected]/FREAKTAB ANDROID 7.1.2 NOUGAT
When flashing your box with firmware there is always risks and these risks are to be understood solely by the user. Please understand that neither I or anyone at xda can be held liable for what you decide to do to your box.
I have seen many struggle to get a replacement firmware for the T95Max/ Nanomax box from Justopuk.
I am posting this for anyone who wants it and will link to instructions on how to replace the horrible stock firmware on the above boxes..
what's in it? This rom has been tweaked for better performance, much better kernel tuning and thermals, comes with magisk 19 which can be updated. Nova Launcher which can also be updated.
wht doesn't work? some lose ability of stock remote, this can be replaced via airmouse/keyboard and there is built in "advanced power menu! Quick reboot app to power off/on boot to recovery etc
T95MAX_SCV2.img Rom here :
https://mega.nz/file/iIsymLoD#UjQ6kp4UoTQus4XaUgujrsKX7Wd0tIT5KKZN9q0uk1g
Unofficial TWRP : This needs to be placed on USB and once you have flashed the rom, boot into recovery, apply update from external. This will USB boot to TWRP and let you back/up restore either from ext/int sdcard.
TWRP_TX6. IMG https://mega.nz/file/bZlmmZJC#-0mwsuzImK25aPWRaXFWCgiO-CzfI3ma-W01VOC90y8
Phoenix USB 4.0 :
https://mega.nz/folder/jd0GEZJQ#7_GRu5o9Ll3AygdetcdPNQ
T95max Instructions for flashing :
Download and extract from the archive Phoenix USB Pro 4.0
Download and Install USB_android driver
Install the driver by specifying the path via device driver in Windows (you may need to disable the driver's digital signature verification )
Restart the PC (although the driver is signed and everything went well without it).
Launch PHOENIX USB PRO , select THE T95MAX_SCV2. IMG File.
We will need a USB-A to USB-A cable
Then connect the cable to the PC,
Take a toothpick or something like that and insert it into the jack 3.5 (sound output) and press the button hidden there.
Connect the USB-USB cable to the set-top box to the USB 2.0 connector in the centre (T95Max)
Keep the button pressed, Until you see a green tick on screen (phoenix usb Pro gui)
You will see the progress as Phoenix begins preparation of the Flash
after the computer has identified the set-top box, release the button and connect the power cable.
Wait until it displays end/finish firmware then Unplug USB to USB and plug the dc power back in for first boot.
Enjoy
Rom twrp courtesy of beny and 4pda
Click to expand...
Click to collapse
I have a problem.I can not unlock bootloader. In developer opcion I enabled OEM but when I type "fastboot oem unlock" I get "ability is 0. Premission denied. Vontar X1 Tv box
Igor twrp said:
I have a problem.I can not unlock bootloader. In developer opcion I enabled OEM but when I type "fastboot oem unlock" I get "ability is 0. Premission denied. Vontar X1 Tv box
Click to expand...
Click to collapse
Just plug the cable in and insert a toothpick on the reset button the usual way.
Flash firmware. I don't know this box.
Some more info please
Regards
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Reserved for future shenanigans.
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
effgee said:
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Click to expand...
Click to collapse
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
reza0511 said:
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
Click to expand...
Click to collapse
Regular Air firmware's do not work.
P1-P3 don't work for sure, P4 I don't know but I think not.
I haven't found a photo yet of the P4 hardware.
Try USB Flashtool 4/64 image for X96Max_Plus_Q2 to get your recovery back if such a firmware exists, otherwise try the 4/32. X96 Max Plus Q2 firmware (X96Max_Plus_Q2_20201209-1446.img)
You should be able to get recovery back via flashing one of those images.
X96 Max Plus Q2 firmware is compatible, but if you use the 4/32 image you will only see the half of your storage.
Restoring your TWRP full backup again once you get the max firmware (for twrp) installed will not work unfortunately. Already went through this.
reza0511 said:
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
Click to expand...
Click to collapse
You have a Conceptum box or just the same motherboard?
If you have a Conceptum, you are pretty much ****ed. They wont release the original firmware. You will have to buy a second box and get the image via dd.
I had to buy a second box and get the disk image via dd, and then restore the dd image using dd from within TWRP, overwriting the entire storage with the image. This was using the terminal built into TWRP.
In general, restoring from TWRP doesn't work well on these boxes, especially going from rom to rom as the partition layouts are different and TWRP doesn't handle it correct.
Conversion of the dd image to usb flashable is tricky and I haven't done it.
The person that MAY be able to do such a thing is Ricky ( https://forum.xda-developers.com/t/...w-milestone-donate-version-available.3786991/ ) but I dont know and I don't think there is any point as my dd image has partition layout for 32 gb version, you will lose half your storage unless he can also expand the partition.
Even if you manage to get TWRP back, there will probably be a partition layout difference from the firmware you use to get TWRP on the box, and the TWRP image backup you did. It probably will not work.
You need to get your original firmware, or a dd image of the same box.
You can also use the Slimbox for x96max_plus_q2. I did NOT like Slimbox 12 because it was missing google play and a lot of other things. But it will restore recovery.
solved !!
i save my box by below two steps
1- burning veitnami atv version of x96air img file (google for link )
2- restoring my full twrp via recovery
reza0511 said:
решено !!
Я сохраняю свою коробку, выполнив следующие два шага
1- сжигание veitnami atv версии файла img x96air (гугл для ссылки)
2- восстановление моего полного twrp через рекавери
Click to expand...
Click to collapse
is there a link?
Я уже решил свой вопрос. Спасибо за ваш сайт. Меня интересовало восстановление кирпича x96air_100. Я из Украины.
I have already solved my question. Thank you for your site. I was interested in the restoration of the brick x96air_100. I am from Ukraine.
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Soldiaz said:
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Click to expand...
Click to collapse
Hi.
To get Magisk working, its a bit of a difficult process.
Essentially, Amlogic released / built their kernels with a kernel boot option "skip_initramfs" which magisk needs "want_initramfs" for this to work.
The process is complicated as you must hex edit your boot.img after you have patched it with the Magisk Manager patching method called "Recovery Mode"
4pda where this was discovered - https://4pda.to/forum/index.php?showtopic=774072&st=25020#entry91068157
Video from 4PDA that shows the hex editing process - https://mega.nz/file/pJ1RTChR#b5rLNs-4GF2qlZXKzbL0P5lmAeLLYObJ_w3_Yf8h16U
You can also get the video from the above thread but if I recall you must register to download and unless you know russian its difficult to register there.
A guide I wrote that you can follow along with the video to understand the process - https://rentry.co/wgu9u
Every detail matters, I studied the video for many hours to understand the process, good luck.
My thread about this process here: https://forum.xda-developers.com/t/...ide-to-accompany-video.4320923/#post-85493037
Thanks!!!! Dam looking not that easy .
The Boot img from x96 Air you edited, is it Stock?
Sorry i dont check my mesages here very often.
I don't know which boot image you are talking about, it would be very helpful for you to link me which one specifically I need to answer the question for..
If you are talking about the image for my Air Extreme, it is stock and patched by magisk, and then hex edited for magisk. But I dont know its compatibility for any of the other Air versions.
effgee, just wanted to let you know there is a lot of information and multiple versions of the X96 Air TV Box Firmware available at...
Original Google link... (Vietnamese)
https://www.google.com/url? sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiDtPO9yZj0AhUOXM0KHYnzCIUQFnoECA8QAQ&url=https %3A%2F%2Ftinhte.vn%2Fthread%2Ftong-hop-cac-ban-firmware-cua-android-tv-box-x96- air.3050996%2F&usg=AOvVaw1it1QO7hR_e5XsrdSZH-Rj
Google Translated (English) link...
https://tinhte-vn.translate.goog/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/? _x_tr_sl=vi&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=nui,sc
Direct link... (Vietnamese)
https://tinhte.vn/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/
"X96 Air" search via direct link... (Vietnamese)
https://tinhte.vn/search/333184298/?q=x96+air&o=relevance
Hope they help!
Mr350
Ps... If you have trouble with the Google translation links not working try a Google search for... x96 air tinhte.vn ... that might work then click Translate this page.