Related
Hi Guys,
As I have a really opportunity to get me a Nexus 9 32GB + Google dedicated keyboard for a stunning price, I was wondering if it is possible to cast/mirror it's display to a VP be it wired or wireless.
I will root it and I am also almost sure to install a custom ROM to it...
I intend to use it to display my .ppt slides on the University/School VP.
Those usually have a Wi-Fi network, but it's sometimes a real nightmare to get the L/P to connect and, even when I have those, it's sometimes difficult to get a reliable connection to that Wi-Fi network.
Given these considerations, I would like to know if it is possible to cast/mirror the Nexus 9 display to a VP.
It seems that when it came out, the Nexus 9 could not output anything via it's USB port (no SlimPort nor MHL support). Is this still correct or has this been addressed by Google ?
Will I be able to cast/mirror with a Chromecast ? I had the "old" Chromcast but that required to be connected to the internet permanently, so I could not use it... Does the "new" Chromecast allow to cast/mirror directly from the Wi-Fi ?
Will I be able to cast/mirror with Miracast ? It seems that does not require an external netwark as it provides it's own network, but when it was released, it seems the Nexus 9 wasn't compatible with Miracast... There have been some workarounds, but those are for Android LP. Has this been adressed by Google or are the tricks reported here and there also working on Android MM ?
I would really appreciate you answers... and yes, I have done some research, but the results seem to be old (more or less when the N9 was released).
Regards.
NexusPenguin
I think Google doesnt support Miracast tech in their new products. It wants to sell Crapcast to everyone. I read somewhere on xda thats possible to enable Miracast trough root and editing some files.
Found on reddit
If you're rooted, add this to your build.prop. It will re-enable wireless display
persist.debug.wfd.enable=1
Or non root method not confirmed
Grim-Sleeper5d,
You don't even technically need to be rooted. All you need is an unlocked boot loader. You can then use "fastboot boot twrp-2.8.7.2-angler.img" to start TWRP recovery mode.
And from there use "adb shell" to access your device. You can edit either "vi /system/build.prop", or "vi /vendor/build.prop". Make sure you told TWRP to mount these partitions.
Wysłane z mojego GT-I9295 przy użyciu Tapatalka
Hi Ewa12321,
Thanks for your reply.
I have seen the link, but that is for Android LP isn't it ?
Do you if it's going to work with Android MM ?
Regards.
Enable Mircacast feature on Nexus 9
Has anyone tried successfully to enable this feature?
Renate NST said:
You don't need to modify /system/build.prop
You only need to add that property as persistent and you can do that in /data/property with setprop.
Code:
C:\>adb shell
[email protected]:/ $ su
[email protected]:/ # setprop persist.debug.wfd.enable 1
[email protected]:/ # reboot
On the Nexus 9, after you reboot you need to click the enable Wifi Direct box on the Screen Mirroring setup.
Click to expand...
Click to collapse
SGH-i200 said:
Has anyone tried successfully to enable this feature?
Click to expand...
Click to collapse
it enables it but then crashes as soon as i try and connect to my firetv stick
Hello Everyone,
This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...
the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.
all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.
Bug reporting.
if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)
Updated on January 6th 2018:
- 3 Magisk Modules added Description bellow for each.
- all 3 modules are based on the latest 1500 (15.0) Magisk template.
- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.
should Works On All Oreo Roms.
Requirement:
-Root
-Root file manager
-Recovery (TWRP) for flashable Zip
A- Manual Installation:
1- download & extract the zip attached. ( APTX-enabler)
2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.
2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.
3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.
Code:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
5- reboot
B- Flashable Zip Installation
1- reboot to TWRP
2- flash APTX-enabler.zip
3- reboot
C-Magisk Module
1- Download one of the 3 modules (discretion bellow)
2- install through Magisk manager
3- reboot
Modules Description:
A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.
B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.
C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.
Old lib Files and modules can still be found on the following folder
https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry
Credits to
@Riku Azhurlar for initial flashable zip
@simonsmh for the Initial Magisk Module
@bmg1001 & @ossito2012 for initial aptx files
OnePlus for Current aptX lib files
theduke7 said:
Hello Everyone,
The latest beta of Android Oreo doesn't have AptX support like the previous bet a builds (because of compatibility Issue)
It only plays on SBC, so until OnePlus brings it back, i found a work around but it requires ROOT.
The files provided, are from a Magisk module port to Nexus 6P ...thanks to @ossito2012 for providing the file
Click to expand...
Click to collapse
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
ossito2012 said:
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
Click to expand...
Click to collapse
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
If you go into developers options under Bluetooth audio codec and enable optional codecs it turns on apt hd and ldac turns on aptx without this.
Edit: I see what you're saying now when I actually connected the Bluetooth headphones I saw you can't change those options so I'm going to use the instructions thanks.
Thanks.. It worked.. You. Are Awesome...
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
info2shail2010 said:
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
Click to expand...
Click to collapse
yes i tested that too, it's an old port but it has N API files, so they wouldn'e work...
i was lucky i found the Oreo files
Glad it helped
Yes.. I know.. Thats y i said i tried on openbeta 24.. OB24 was on Android N 7.1.1 and even after that didnt worked for me.. But manually doing with your zip worked for me.. Thanks again
theduke7 said:
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
Click to expand...
Click to collapse
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
beeree7 said:
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
Click to expand...
Click to collapse
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
jokerpappu said:
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
Click to expand...
Click to collapse
it's not working, OnePlus disabled the codec itself , that's why when you add those files to the lib folder, they don't over right anything... there's bug reports about it
https://forums.oneplus.net/threads/open-beta-25-bluetooth-aptx-is-not-working.656630/
so OnePlus said they temporarily disabled the codec, before adding those files, download a log app and see if it enables Aptx while pairing.
and i personally assisted the OnePlus BugHunters team collecting Logs for the issue...
your theory is right, in the future it should work automatically or with forced selection, at it's current state if you play any file it defaults to SBC only (try it)
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
You need to learn a lot more... Your screenshot missing bluetooth connected icon...
sorry wrong reply, never-mind this
B4oE said:
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
Click to expand...
Click to collapse
the files are Oreo specific, if you search the forums, you'll find ones for Nougat and i think there's also a magisk module
jokerpappu said:
When i connected my aptx enabled device
Click to expand...
Click to collapse
Could you reveal what's your aptx enabled device?
Flashable Zip
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Riku Azhurlar said:
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Click to expand...
Click to collapse
thanks m8, added to OP with credit
i want to report that it works in nexus 6
using oreo rom
cDroid v4 had aptx working for nexus 6
so when i move to another rom it was not working
after flashing this it works again
can someone make magisk version for this
and'' call it aptx enabler for oreo '' for example
If aptx works for you you will see 4 options
If it's not working you will see 3 only
In the Bluetooth settings
Hello all,
Mirroring through miracast works fine now! I managed to fix the issue I faced with trying to mirror the phone with miracast.
The phone I bought from China came with apparently some manually altered rom. It didn't have much of the bloatware of the Nubia stock firmware. Also, it did not come with the "screen projection" app of Nubia. This app seems to be integrated into the phone. I couldn't find any .apk of it online. I tried a bunch of different apps, none worked. Also, factory resets, did not reinstall that app either.
The solution was simple. I used TWRP to wipe the phone and install the latest (v2.23) rom from the official nubia website: http://ui.nubia.cn/rom/detail/56
After installing it, the app was there and worked instantly.
At the moment now I have some issues with TWRP. I will fix it and see if the build.prop presisted through all of this, I doubt it.
If it did, and any changes are still required, I will update the post.
Kind regards,
Rup7ur3
---- initial post ----
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). Currently when I try mirror with the use of wi-fi direct, it doesn't show the miracast dongle I use (anycast).
I've not any experience in this and am trying to google for solutions. Online I have found some answers, but it's not yet working.
Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.adb.notify=0
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=0
Click to expand...
Click to collapse
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
Miracast is available on Android devices with Android 4.2 Jelly Bean
Click to expand...
Click to collapse
and
no more supported by Android since 6.0
Click to expand...
Click to collapse
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
#property to enable VDS WFD solution
persist.hwc.enable_vds=1
# Add by ztemt for ZWfd begin
#property to set wfd output resolution is 1080P(0) / 720P(1) / 960*540(2) / 800*480(3)
persist.sys.wfd.zte_resolution=0
#property to show wfd sink false(0) / true(1)
persist.sys.wfd.zsink_support=1
#property this is device support wfd 1080p output support(true) not support(false)
persist.sys.wfd.1080p_support=false
# Add by ztemt for ZWfd end
Click to expand...
Click to collapse
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
rup7ur3 said:
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). I've not any experience in this and am trying to google for solutions.
I have found some answers, but it's not yet working. Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
and
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
Click to expand...
Click to collapse
Never try downgrading this phone. It's a nightmare because it's using AVB2.0 which was introduced with Android 8 I think. So getting that to work would be extremely difficult. What I'm not sure about is if nubia is doing anything different from other vendors as, judging by the source code, it looks the same as Sony for example (actually that's no wonder since they got 70% of their code from Sony).
What's difficult about this is that they define custom, vendor and device specific values as you can see with the Z9 build.prop. I'm not that well versed in Android actually and mostly just learning all this stuff by experimenting right now, but I would say your best bet would be some tool that scans a system for possible values in build.prop. However I'm unsure if such a tool exists unfortunately..
Sorry I can't be of more help as of now. I think Lineage is supporting Miracast though? So once I got that to work, it might be an option for you
Nubia z18 support screen cast without internet.
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
jagdishgeb said:
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
Click to expand...
Click to collapse
Thank you for the response, great to hear that it is possible! Did it work immediately?
Also, if you don't mind me asking. Could you maybe check if there are any default screen projection / sink apps pre-installed on your z18?
Mine came without any. I will try reinstall stock to see if that helps. All apps I use go to this screen: https://imgur.com/a/Otf1YO0
Online I read there are supposed to be options to enable wireless display in there. However, I think Nubia disabled it in their UI.
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
Q1 FIRMWARE #1
666.25 MB file on MEGA
mega.nz
Q1 FIRMWARE #2
683.48 MB file on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk, an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
##Edit## Updated 13/02/2021
Bertonumber1 said:
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
File on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
Click to expand...
Click to collapse
The file you posted is no longer available. Could you post it again? Thanks a lot!
lchang.atsoft said:
The file you posted is no longer available. Could you post it again? Thanks a lot!
Click to expand...
Click to collapse
OP updated, 2 newer firmwares, also check out Vasily' site
Bertonumber1 said:
OP updated, 2 newer firmwares, also check out Vasily' site
Click to expand...
Click to collapse
Thank you for posting the files again. Do you know firmware for it that is rooted?
Will this firmware work on the older X96max Plus models?
delucai7 said:
Will this firmware work on the older X96max Plus models?
Click to expand...
Click to collapse
No there is a firmwares for that model. Search for vasily-ts vasikh shevchuk and slimhouse have great firmwares for amlogic boxes.
Regards
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
wonzay said:
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
Click to expand...
Click to collapse
Hello, I was talking to someone on YouTube about this earlier too.
There maybe a rooted firmware from Vasily Shevchuk :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
scroll to near bottom of page.
I'm afraid TWRP only works via USB and won't give you root privileges on this System as Root device.
You're best bet is to install slimbox rom and patch magisk to boot. At least that way you will have a root and manager app to control it.
Here is a link to slimhouse slimbox firmwares :
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
You will also find more help and guidance in that amlogic thread with regards to what you want.
Regards
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
wonzay said:
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
Click to expand...
Click to collapse
Hmm I can't remember if it was this box that had the su file in the xbin folder but it needed chmod permissions to work.
By far the easiest way is to just connect via USB, get rid of stock rom an use slim, then patch the boot. Save yourself the headache
Regards
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
:/ $ ls -lh /system/xbin/su
-rwsr-x--- 1 root shell 16K 2008-12-31 17:00 /system/xbin/su
Click to expand...
Click to collapse
wonzay said:
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
Click to expand...
Click to collapse
Ah.. So it was that box.. Then maybe change permissions and make it executable.
You may not have proper root but it should get you a root shell at least
Regards
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
wonzay said:
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
Click to expand...
Click to collapse
You'll only have twrp with a custom rom installed, stock firmware = stock recovery slimbox or one of vasilys roms and it will be a recovery.img via USB flash drive that boots from the update menu.
Have you tried installing a soft keyboard such as SwiftKey, Leanmey or some other that will change default settings?
I was using Leanmey without issues with a Rii mini USB keyboard/mouse.
Again, you're best bet is to flash the slimhouse firmware. These boxes are pretty indestructible and have a built in auto mask rom mode that kicks in after 5 minutes during brick and will accept stock firmware again regardless (so don't worry) .
Hope this helps
Regards
Do you mean in this way?
Bertonumber1 said:
I was using Leanmey without issues with a Rii mini USB keyboard/mouse
Click to expand...
Click to collapse
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
wonzay said:
Do you mean in this way?
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
Click to expand...
Click to collapse
Your box sounds identical to all my devices app wise ( you missed Newpipe for downloading though )
How did you get on with this? There is three options, you may try inserting the lines for the key into the file or you may try flashing another firmware... If that fails try another keyboard.
I don't know if you've done this already though
Regards
I have left this subject alone (for a time). "Enter" key works via AOSP stock software keyboard - it has option to set default key. The only disadvantage of this "method" is that the AOSP keyboard is visible on the screen.
Ok, I figured it out, enter key works properly on my hardware bt keyboard. X96 MAX+ Q1 gains superuser powers when is connected via adb (root) over wifi. I remounted "read-write" /vendor partition, went to file "/vendor/usr/keylayout/Generic.kl" (make a backup!) and changed the line "key 28 DPAD_CENTER" to "key 28 ENTER". Don't forget to mount back /vendor as "read-only". At the end reboot your box.
Useful commands:
adb:
Code:
adb root
adb connect [ip address of the box]
(backup Generic.kl)
adb pull /vendor/usr/keylayout/Generic.kl
adb shell
re-mount, read write & read only:
Code:
mount -o rw,remount /vendor
mount -o ro,remount /vendor
Shell text editor - only vi is avaliable on my box:
Code:
busybox vi /vendor/usr/keylayout/Generic.kl
On the other hand you can pull "Generic.kl" to your computer, edit it locally, then push to "/vendor/usr/keylayout/" and chmod it correctly. The funny thing is that the "Generic.kl" in "/system/usr/keylayout" has right value for the key 28, but "vendor" path has a higher priority (I think).
ADB can be run directly from the box too, just use app called "termux" (get the latest version from "fdroid") and install in it "android-tools" package via the command:
Code:
apt update && apt install android-tools
Bertonumber1 said:
you missed Newpipe for downloading though
Click to expand...
Click to collapse
Similar tool for this purpose is "youtube-dl". I use it in termux (requires python3), but works anywhere python is installed (linux, windows, macos and so on).
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you.Only works for Allwinner H3 models with 5G support!
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SV6256P (Most stable)
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but WiFi not working
-Go and activate developer options and enable USB debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-WiFi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-WiFi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the "SV6256P" WiFi chipset.
XR819 Devices are not supported!
This ROM will still boot without the following WiFi modules but Wi-Fi function will not work, Hope you will find the right one soon though GL on your next Google search
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app (No need to go to some dodgy websites just go to the built in rooted store to get the latest updates)
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
4. A driver is required for Phoenix Suit to detect the box when plugged in please download a working driver before doing so, if the box is detected you can continue the steps without downloading the driver.
5. To flash the box use the USB port 4 (Located at the back side of the box or the rear panel where the rear ports are located) your PC will not detect the box if you use USB port 1-3!
Downloads:
Phoenix Suit V1.10 Flash Tool Download
Download all files Here
ROM INFO:
ROM OS Version: Android 7.0-7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Klein61967 said:
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SC6256P, SV6256P and SV5256P
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but wifi not working
-Go and activate developer options and enable usb debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-wifi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-wifi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the following WiFi modules below:
SC6256P
SV6256P
SV5256P
(It is possible that this firmware will work without the following WiFi modules just make sure you have the 5G model or else success rate is very low)
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
Download files Here
ROM INFO:
ROM OS Version: Android 7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Click to expand...
Click to collapse
From where can I download this Rom
Klein61967 said:
MXQ PRO 4K 5G OFFICIAL STOCK FIRMWARE (ROOTED)If you have an MXQ PRO 4K 5G that it's bricked or a firmware that doesn't support your current WiFi module then this is for you
SPECS WITH THE BOX THAT I TESTED:
CPU: Allwinner Tech H3 @1.1Ghz
RAM MODULES: SEC 246 (4 Chips) and ELPIDA J2104ECSE (4Chips)
RAM Space: 4GB (1GB Actual)
ROM: 64GB (8GB Actual)
WiFi: SC6256P, SV6256P and SV5256P
Board ID: QL2039 - Q44_V4.0_20200602
Things to prepare:
A full sized USB to USB cable (You can make your own using your old charging cables)
A computer that is running Windows 7 or later
A toothpick or anything that would fit on the AV port
USB Mouse to interact with TWRP Recovery
5G only:
-Flash box with the firmware H3-R69-MXQ-S-MXQ4K-8PD3-1.1.4 using phoenix suite
The Box will boot, but wifi not working
-Go and activate developer options and enable usb debugging and USB0 device mode
-Copy twrp.zip (from archive in link bellow) to flash drive
-Connect Phoenix suite to box using the USB to USB cable and press recovery and the box will boot into recovery mode
-Press install update from external and choose twrp.zip (executable only) DO NOT TRY to install just run it!
-Make full backup of "no-wifi" rom (check all boxes) and save it to external flash drive
-When is done, disconnect flash drive from box and connect to pc. Replace only files ( from backup in link bellow ) to folder in flash drive. DO NOT rename folder!
-Boot box to "no-wifi" rom and connect to phoenix suite and press recovery again.
- From stock recovery load twrp.zip again, point where backup is, mark again all boxes, and choose restore.
- Wait to finish and press reboot when is done.
Box will now boot to stock firmware with working Wi-Fi
This firmware is tested with the following WiFi modules below:
SC6256P
SV6256P
SV5256P
(It is possible that this firmware will work without the following WiFi modules just make sure you have the 5G model or else success rate is very low)
Tips:
1. If you've noticed the display output resolution is not 4K
Go to Settings>Display>HDMI output mode>4K_30Hz (Refresh rate is limited to 30Hz/FPS due to hardware limitations)
2. If you accidentally deleted Netflix app or you want to update YouTube just go to GetApps app
3. It's really hard to find a custom ROM that is fully working for this Box but you can actually customize it on your own like the attached image below
Download files Here
ROM INFO:
ROM OS Version: Android 7.1 Actual
ROM Kernel: Linux 4.4.55
Android Security patch level: (Located in Settings>TV Status)
Click to expand...
Click to collapse
josejosemanoel said:
From where can I download this Rom
Click to expand...
Click to collapse
Download files Here
Anyone knows for a custom rom for this Cortex version? The stock rom really s*x
will this work on rockchip 3299 version?
_harley said:
will this work on rockchip 3299 version?
Click to expand...
Click to collapse
This ROM is tested for Allwinner only but you could try, if you have TWRP recovery...
Just tested this firmware on my box with exact same board ID
Board ID: QL2039 - Q44_V4.0_20200602
The box is bricked, only the red light light on and no blue light when I press power on.
Press the reset once and blue popped up for 2 sec and then again red.
Really no hard feelings here, this box is a trash and I got "cheated" by Banggood selling this as a 4+64 Android 10 device.
It is a modified 7.1 version that looked like 10, so I wanted to get rid of it because lagged or crashed randomly.
@Klein61967 if you have any suggestion happy to hear it. Box still accepts flashing.
Kamui_ said:
Just tested this firmware on my box with exact same board ID
Board ID: QL2039 - Q44_V4.0_20200602
The box is bricked, only and the red light stays on. Tried to press the reset and blue popped up for 2 sec and then again red.
Really no hard feeling here, this box is a trash and I got "cheated" by Banggood selling this as a 4+64 Android 10 device. It was a modified 7.1 version that looked like 10, so I wanted to get rid of it because lagged or crashed randomly.
@Klein61967 if you have any suggestion happy to here them. Box still accepts flashing.
Click to expand...
Click to collapse
Honestly, I really don't know what I can suggest for you to flash. I made this thread to help troubleshoot this box cause I've seen a lot of people complaining about the box like Netflix not working keeps crashing, unwanted UI and Corrupted Roms etc. and yes those specs advertised is obviously fake but this ROM I posted only works with Allwinner H3 Processors it doesn't work on Rockchip, S905W etc. make sure you have Allwinner H3 processor by (carefully) removing the heatsink on top.
Klein61967 said:
Honestly, I really don't know what I can suggest for you to flash. I made this thread to help troubleshoot this box cause I've seen a lot of people complaining about the box like Netflix not working keeps crashing, unwanted UI and Corrupted Roms etc. and yes those specs advertised is obviously fake but this ROM I posted only works with Allwinner H3 Processors it doesn't work on Rockchip, S905W etc. make sure you have Allwinner H3 processor by (carefully) removing the heatsink on top.
Click to expand...
Click to collapse
Yeah I did that months ago when I got the box and understood that its a fake one. Its an Allwinner H3
Maybe the flash messed up the bootloader or maybe your model use a different one because of the different ROM. Do you include bootloader in your img file? I will try once more (already flashed 3 times)
P.S. It's a good reason for me to buy a new "good" one this time
Some extra news. I found and flashed this one https://mega.nz/folder/y4ZSkbDL#5KLc5vKUWOyBAMmJXfGQZw from this video
.
The TV box is alive again
thanks for this. it worked, but i want to tell you that the rom android version is 7.0(sdk24) and not android 7.1 as mentioned.
SreyasXd said:
thanks for this. it worked, but i want to tell you that the rom android version is 7.0(sdk24) and not android 7.1 as mentioned.
Click to expand...
Click to collapse
I'm pretty sure this rom is Android 7.1.2 with API Level of 24 (CPU-Z), also what software did you use?
Klein61967 said:
I'm pretty sure this rom is Android 7.1.2 with API Level of 24 (CPU-Z), also what software did you use?
Click to expand...
Click to collapse
yeah, API level 24 means Android 7.0, and API level 25 is android 7.1, i am going to post my modded tv rom thread for this soc by tomorrow
SreyasXd said:
yeah, API level 24 means Android 7.0, and API level 25 is android 7.1, i am going to post my modded tv rom thread for this soc by tomorrow
Click to expand...
Click to collapse
Oh ok, my apologies...
Hi, this rom work with QL-2036 board?
CPU: ALLWINNER H3 L3064BA
BOARD ID: QL-2036 - Q44_V4.0_20200602
29F64G08CBABA FLASH MEMORY
SV6256P WIFI CHIP TAC 2032 19U68B
sixtoja said:
Hi, this rom work with QL-2036 board?
CPU: ALLWINNER H3 L3064BA
BOARD ID: QL-2036 - Q44_V4.0_20200602
29F64G08CBABA FLASH MEMORY
SV6256P WIFI CHIP TAC 2032 19U68B
Click to expand...
Click to collapse
As long as you have the Allwinner H3 chip and this following onboard WiFi chips:
WiFi: SC6256P, SV6256P and SV5256P
then yes it will work.
My board is this. The PC doesn't recognize it and not the card, it doesn't recover from the SD card either.
Kamui_ said:
Some extra news. I found and flashed this one https://mega.nz/folder/y4ZSkbDL#5KLc5vKUWOyBAMmJXfGQZw from this video
.
The TV box is alive again
Click to expand...
Click to collapse
Hi, I did the installation of that rom and it remains in the ALLWINER logo. Does not start. any ideas to fix it?
I attach images of the board
Klein61967 said:
As long as you have the Allwinner H3 chip and this following onboard WiFi chips:
WiFi: SC6256P, SV6256P and SV5256P
then yes it will work.
Click to expand...
Click to collapse
Hi, @Klein61967 , the system boots fine after (+-) 15 tries (I remove and insert the power cable several times because in those times it is frozen). what is happening with my board, why is that happening?
When the system is running it has no problems, it connects to the wifi well, and it executes the applications perfectly.
any ideas please.
sixtoja said:
Hi, @Klein61967 , the system boots fine after (+-) 15 tries (I remove and insert the power cable several times because in those times it is frozen). what is happening with my board, why is that happening?
When the system is running it has no problems, it connects to the wifi well, and it executes the applications perfectly.
any ideas please.
Click to expand...
Click to collapse
Sorry I don't, I haven't encounter this type of problem before maybe your CPU is overheating make sure you reapplied your heatsink properly after checking it's model or if the motherboard is outside the case don't touch it you're probably shorting the contacts on your motherboard tried it before and sure enough it did freeze.