Related
KitKat for the Omate TrueSmart
Congratulations, you made it this far and managed to keep your unit alive long enough to upgrade it to the next level!
4.4.2 Changelog:
================
Fixed glitch in boot animation to make it smoother
BTLE profile and PAN profiles added
Full Settings Menu
Functional Accessibility Menu
Updated Wi-Fi Drivers, now supports ip6, ip4, and low-power mode
Updated GPS Drivers, lock-on after initial lock and AGPS update should be quicker
Kernel updated from 3.4.5 to 3.4.67, supports SELinux
Unlocked bootloader and insecure kernel allows for root access through SU
Google Play Services included
Google Talkback/Voice Search integrated
Fixed glitch where Voice Search would not complete spoken sentences
TWRP updated to 2.8.3.0 with full features and MTP support
Camera now operates at 5MP/720P without force closing
Security holes have been closed
MALI 400 drivers updated
Battery management integrated; after first boot battery readings should be accurate
Sound issues fixed; microphone should no longer sound muffled
Soft reset implemented, holding both buttons for 10-15 seconds should power down or reset unit
ART mode implemented, allowing for faster and more efficient performance
Known Issues:
=============
Sensors are non-functional until updated drivers are available (if they become available)
Settings is not accessible from status bar icon
1900MHz units are unable to access 3G data currently (if a modem becomes available this should change)
Bluetooth connectivity may occasionally drop out depending on data load
APNs are not automatically added
IMEI may be lost or corrupted after installation
Instructions:
=============
REQUIRED PROGRAMS:
1) SP FLASH TOOL
2) MTK DROID TOOL
3) WINDOWS OS XP or HIGHER
The All Tools suite for MTK devices can be found here:
MTK All Tools Suite
****** You must install the preloader drivers for your device using the 32-bit or 64-bit installer (dpinst) for your operating system before you continue. ******
I suggest making a full backup of your device either in TWRP or in MTK DROID TOOLS (1:1) to preserve valuable data or in case of a failed upgrade. You should always back up your IMEI/NVRAM in DROID TOOLS for safe-keeping and this is no different.
Download the full set of factory images here:
Omate 4.4.2 Factory Image RAR
Extract the contents of the ZIP file to a known directory and proceed to the next step.
Next, navigate to the Settings menu on your Omate TrueSmart and, under Accessibility, disable Quick Boot. This is the only way to enter Download mode reliably. With that completed, power down your watch.
Finally, open the scatter file (mt6572_scatter_emmc.txt) found in the directory you extracted the ZIP file to in SP FLASH TOOL and check to make sure each file is present. You may need to manually add the system.img and recovery.img. To do this, double click on the empty box and select the file.
Once you've made sure each file matches, go to the drop-down menu where it says "Download" and select "Firmware Upgrade". Take one last look to make sure every file is selected and press the Download button on the top left of the screen.
With the watch powered off, go ahead and plug it in. THEN WAIT. It will take between 5-10 minutes to fully upgrade your unit. You should see a red bar, then green, then purple, then yellow. If you get any error that says "BROM DLL ERROR" note down the error number and send me a message. If it gives you a green checkbox, you're done with this step.
Now you're ready to boot the watch. Press and hold the power button until it powers on. The first boot will take approximately 5 minutes to complete while it assembles all of the information. Once it finishes, power down the watch. Hold the home (bottom) button and press and hold the power (top) button simultaneously (at the same time). You'll see a recovery menu. Press the power button to boot into TWRP. From there, select "Wipe" followed by "Factory Reset". You will want to reset the watch to factory settings. You can either make a backup or go ahead and reboot the system.
Congratulations! You should now be on Android 4.4.2 for your Omate TrueSmart.
NOTES
=====
If you're missing APN information I suggest you either restore previously saved APNs or add them manually if they disappear. Currently 3G data will not work on 1900MHz units.
This firmware was designed for UMEOX smart watches operating on the x201-series MT6572 chipset. I am not responsible if you damage your watch because you flashed the firmware incorrectly or to the incorrect watch.
If you have any questions as to whether your watch is compatible, please message me.
It is IMPOSSIBLE to brick your watch if you are flashing this firmware. If for some reason you think your watch is bricked or you feel uncomfortable flashing this firmware you are welcome to send your unit to me (if you pay shipping) or I am available to help over Chrome Remote Desktop to flash it for you.
If you are having issues getting the firmware to work, please send the following information to me:
Watch Manufacturer
Date Received
Last Known Firmware
Case Material
And I will answer on a case-by-case basis to help you troubleshoot. I never make guarantees but I promise to help as much as I am able.
Finally, please take the time to thank the brave soul who voided his warranty to get me the prototype firmware for this. I won't reveal his name for security's sake, but he obtained a developer unit from another company who uses the x201 chipset and was kind enough to upload the system dump in September of last year. I would have presented this sooner to you guys, but until the method for flashing the S8 firmware was released I had no idea why I couldn't get it to work.
SPECIAL THANKS
==============
Laurent LePen, for giving me the tools from UNOVA to make this possible
@Dees_Troy, for having the patience to flash the firmware, assemble a system image, and update TWRP
Derek Serianni, for flashing his watch 42 times to test the firmware
Christos Vorkas, for testing SIM functions and the early firmware
@AdamOutler, for advice operating Linux and troubleshooting errors
The Anonymous Firmware donor, who voided his warranty and bravely e-mailed me about 1.5GB worth of files
XDA, for always having that clinch moment where someone has a breakthrough that helps the rest of us
KNOWN COMPATIBLE UNITS:
IconBit:
Callisto 100, 300
SimValley:
Pearl AW414, AW420/1
UMEOX
X201
Omate
TS-1/TrueSmart 512MB/4GB Edition
TS-1/1900MHz 1GB/8GB Extreme Edition
TS-1/2100MHz 1GB/8GB Extreme Edition
For Root, download Chainfire's latest SuperSU package and flash in TWRP:
SuperSU 2.44
Derek Serianni, for flashing his watch 42 times to test the firmware
Click to expand...
Click to collapse
I think that number is a lot higher actually..... but, 42 is quite fitting as this is now the answer to the ultimate question...
It has been an exciting couple of days testing and flashing.
Despite all the trial and errors, not once did the watch become unrecoverable.
If you load Google Now Launcher and the latest Google Search APK (and setting it up properly) you can use the "Ok Google" feature from the lock menu as well as in the OS.
I stopped wearing my LG G and am now wearing the TS daily....
Kudos for all the hard work!
I knew there was light at the end of the tunnel!
D.
Great job!
hi dan,
i have tried to flash this to my EU 1/8G Pre May Omate TS.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Steel
A few questions:
1) the downloaded KK Omate rar file does not include UBOOT.BIN or a BOOT.IMG file. Am I supposed to leave it blank or use the UBOOT / BOOT IMG from my current Omate's backup?
EDIT: I have tried using the UBOOT.bin and BOOT.IMG from another KK thread but still run into the same "CheckSum Failed" error i mentioned below: http://forum.xda-developers.com/showpost.php?p=57433563&postcount=189.
2) under FLash Tool: the ANDROID file is usually blank - i have selected system.img from the rar file for the file to be flashed for this. Is this correct?
3) When flashing via FlashTool, about 27 seconds into the flash (i see a RED Bar, then it changes to a couple of BLUE "Read Back" bars), I keeping getting a error saying "CheckSum Failed". I have tried redownloading the KK Omate rar file and trying again but to no avail.
EDIT: I have tried with different ports, different cables, including cleaning the Omate TS's ports with no luck. Just prior to the flash, i was able to do a full backup so it does seem strange and does not seem specific to the cables/ports/contacts on the TS.
UPDATE: Seems to be working - TRY Flash Tool v3.1332 instead of the latest V5.1352. It is now flashing fine as mentioned by Dan.
FINAL: My TS boots up fine with KK now! If you face the checksum error as i did, try using SP Flash Tool v3.1332 instead! - LINK HERE: http://androidxda.com/smart-phone-flash-tool
Any advice on the above?
NO UBOOT
Trying to flash this on my Omate 2100 unit but the UBOOT is missing for me? Got the system.img and recovery.img added but no uboot.
I am also not sure what to select as "BOOTIMG".
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Caboose1979 said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
Mike? hehe did you get the same error i had? with the CheckSum failed as well?
Isn't the baseband included under "0 Needed files -> NA/World Baseband"?
I can not check if valid files. My TS is not booting/reacting to Flash tool anymore...
Not sure if I did it correctly but because I could not find the boot.img within the supplied files I took the boot.img from the other kitkat rom here on xda. Have at least a working TS now .
Only problem right now is that the home button is not functioning as the home button. It sets the volume to max.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
I had the same issue as well!
Thanks. Works well like the other early ROMs and is a bit better prepared including Google Play etc. Can we remove the extra apps like QQ etc from the image for a future release? Edit that might have been my fault from not wiping after flashing although I was pretty sure I had already removed them from the ROM whilst creating a flashable zip.
When turning on Wifi I do get an NVRAM error initially in the list of Wifi items. It fairly quickly finds real ones and it connects fine to my AP.
I have the issue with the second button turning up the volume too. There is a fix in the other thread for this.
Also I had to manually select system.img, the recovery, uboot.img and boot.img (the latter two weren't in the archive so I took from the X202 image in the original KK thread).
Glad to see Omate somewhat taking credit on Facebook. It seems I'm banned on Facebook from recently posting after commenting that they probably shouldn't be taking credit for this. The initial announcement a few days back has 14 missing/hidden comments. Oh so childish LLP - I'm sure you're reading.
I'd like the sensors if possible, mainly for a shake/rotate to wake up function..
---------- Post added at 11:43 PM ---------- Previous post was at 11:38 PM ----------
Caboose1979 said:
could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
I'm going to take a look at doing this when I get a chance in the next couple of days. I had a basic one working with just system and boot images of the KK ROMs. It should be possible but I'm kinda new to this so not sure if there are any limitations when flashing everything like this. I do need to make sure I know all of the device names to flash.
Hi Guys,
Not sure where I am going wrong, can't make head nor tails so far.
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
On from that i am also missing the .img files that the others are.
sorry to be a hassle, i will do my best to work it out, but just need a bit of help getting off in the right direction please,
also i haven't done any other flashing etc with my truesmart, is there anything i should be doing prior for brick protection?
it is a 2100mhz model
Cheers
burlyoaf said:
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
Click to expand...
Click to collapse
MTKDroidTools is different to SP Flash Tool. They are 1 and 2 respectively in the All Tools folder.
Follow the instructions exactly particularly the order. Turn the watch completely off (disable Quick boot), click download and *then* plug the cable in.
Quick Update:
My EU 1/8G Omate TS-1 Pre-May is up and running fine (see my earlier post for some tips / advice based on the issues i had).
1 major issue as below:
However, under Baseband - it shows unknown, and similarly in IMEI - it also shows unknown.
i tried to flash the old 2100 World Baseband.zip in TWRP, but no luck,
tried to use MKT Tools to restore my NVRAM but no luck either (just shows install\data\nvram) and then nada.
minor issue: home button is defaulting to UP Volume instead of HOME function. I will try to flash the FIX_HOME.zip in the other thread and report back.
any advice Dan or anyone else who has theirs working?
If it says uboot, that's the lk.bin.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
Stop with the attentions. The baseband is included. I've had at least 5 people flash it with no issues.
IF you are missing a baseband, sit tight. Try flashing the UNOVA system image, then flash this again.
IF you are having checksum issues, either use an older version of flash tool OR format and flash the stock firmware.
The LK and Kernel must have been a goof on my part. I'll fix that.
Team Win Recovery Project
for Huawei Mediapad s7-301u
What's new in 2.8.4.0:
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
SS:
Download
https://drive.google.com/file/d/0B-JwjbrlsO9CbUpyOHQtSGs4ak0/view?usp=sharing
Installation :
It's automatic
- Be sure that you have checked this points :
- on you computer : install huawei usb driver
- on your phone : enabled USB Debuging in
- Settings-Developer options-USB debugging on your tablet
credit : Dees_Troy, TheMasterMindGT
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
pvdeejay said:
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
Click to expand...
Click to collapse
Done, Link Update
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Someone has tested the Huawei Mediapad S7-302u
TheMasterMindGT said:
Someone has tested the Huawei Mediapad S7-302u
Click to expand...
Click to collapse
according to this http://forum.xda-developers.com/showthread.php?t=1743025, there is no difference between those two versions, except the radio freq, so i think you can safely flash the recovery
Hello,
I have flashed this hoping I will be finally able to control TWRP using commandline. That's a new feature added in TWRP 2.8. However most likelly because of the core MTP support ADB is not turned on as this version of TWRP boots up.
I am unable to use TWRP GUI because I'm blind, so I had to revert back to TWRP 2.7.1 in order to get ADB functional in the recovery by default.
This is my strange use case only I think you will have no issues with this. You should safelly flash this using fastboot or flashify if you have got rooted your tablet.
install this recovery to Huawei MediaPad 7 S7-302u but shows no navigation buttons, so it does not work for the model Huawei MediaPad 7 S7-302u.
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Hi @ary12282,
I this TWRP still available? Seems the link to google drive requires permission?
Thank you!
Edit:
Hi @pvdeejay and @TheMasterMindGT,
any chance one of you still have a copy of the TWRP 2.8.4.0 for the S7-301u on hand, which you can share?
Thank you!
This is Directly related to the Mseries boxes.
The M8s+ device inperticular but its widely cloned and comes under many names.
MXIII, M8, M8s, M8s Plus etc. The chipset and storage are the important factors here.
Amlogic S8xx series devices, like the S802, S812 etc.
This will be used for Q/A
Troubbleshooting
and helping direct traffic to the right devices.
Freaktab.com has the Android Tv box section laid out well compared to Xda.
The Android phone section on XDA is perfect and im hoping we can get the Tv boxes organized and supported more!
To enter the recovery stock or not, there are multiple methods.
Using a toothpick and pushing the reset button inside the AV port ( Harder/nonrooted )
1.) At the bottom of the AV jack hole is the reset button.
Using a tooth pick hold this button in. You know you have pressed it if you feel the click.
2.) Now plug in the power cord.
3.) While holding the reset button down, wait until you see the logo and you can then release the reset button.
done: The recovery menu should now be shown and the device should update.
ALT For rooted devices:
1.) Install romtoolbox lite and Give romtoolbox superuser permissions
2.) Use the rebooter function inside the app to enter recovery mode. (easier)
Rooted how to Install Custom Recovery or Return to Stock Recovery:
To install the custom recovery I used [Root] Rashr - Flashingtool app to install the custom TWRP recovery, this also can be used to install the image files like boot.img or return to stock recovery.img
Notes:
The boot img needs to match the rom version you are running.
IE: 4.0 needs the 4.0 boot.img. 5.0 needs the matching 5.0
in most cases the device will not boot or bootloop when using mismatched images. in some cases you can use the LATEST image and run older software behind it. Furthermore, if you choose to not listen your support will be to listen and try it this way first.
The recovery images should be used the same way, ive attatched the links on my main page for convienece.
The manufactures and sources post the rom and the img together in a combined zip, ive broken them apart to reduce size and to avoid loosing your custom recovery evey time you flash a rom! This makes updates etc sooo much easier!
Would you know if you're able to flash the m8s+ rom on an ACEMAX M8S Amlogic S812 Quad Core box? From what I can see they have the same hardware specs however the + is a lollipop rom?!
Thanks in advance. I realise this says to only post 'answers' but your first post says this will be the Q&A section...
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.