hi guys,
a tried to update this box, and i used one rom "T95" with the same processor, now i dont have wifi and bluetooth any more.
i seaching a rom 32Gb_4Gb ram "T95" WiFi 2.4G/5G WiFi Bluetooth 5.0 like this for this box or QPLOVE Q6
some "T95" have only wifi 2.4 and bluetooth 4.0 please dont post it
thanks for help
i found -> Transpeed-H616_4-32_20200812.img
now i have bluetooth and wifi, but not cotrol remote
but this rom use AOSP, good for me :angel:
@ch... a link to that firmware might interest a few people
was it this?
https://chinagadgetsreviews.com/download-android-10-stock-firmware-for-transpeed-h40-tv-box.html
Is there a way to backup a USB driver from another ROM?
Original ROM but i have same problems https://www.turewell.com/pages/tvbox-document
hmm, with the amount of links related to android TV that lead to taken down pages or outright scam links, a company that sells dental flossing machines and android TV boxes from a fake HTTPS link doesn't inspire confidence.
I got a browser warning about the links from that page too.
may be is more easy to install remote driver.
some body know?
watching IMG files, i saw many files different like
88x2cs.ko, 8821cs.ko, uwe5622_bsp_sdio.ko, on -> /vendo/modules/
subtypes.xml on -> data/system/inputmethod/
android.hardware.wifi.passpoint.xml on-> /vendor/etc/permissions
bcm4335.hcd, fw_bcmdhd_ag.bin, on -> /vendor/etc/firmware/
wifi_2355b001_1ant.ini, wifi_board_config.ini, fw_bcmdhd_ag.bin, on -> /vendor/etc/
android.hardware.wifi.passpoint.xml on -> system/vendor/etc/permissions/
and impossible to copy, to push some ones cause they are read only,
but i can edit prop.defaults and some others with
adb shell and adb shell sed
Here: https://chinagadgetsreviews.com/dow...r-sunvell-t95-tv-box-with-dual-band-wifi.html
Chinagadgets firmware website
Hey guys,
Most of these Chinese boxes are copycat clones of other better made models. A lot have really high thermals out of the box, so users then revert to trying to install root and custom roms in order to sort out overheating, bugs and poor performance.
The only downfall here is most of the manufacturers of these boxes do not disclose what drivers, go with what firmware and so on, so forth.
This result being that mere guesswork ensues when trying to find suitable firmware for these clone boxes. Most of the time people end up losing WiFi and/or Ethernet/Bluetooth or they lose the function of the stock remote control.
This has happened to me god knows many times.
I am currently using an Aeromedia Nanomax Android 9 here
https://www.amazon.co.uk/JUSTOP-Android-Marshmallow-Amlogic-Miracast/dp/B06XB13G9Y
The Aeromedia is a carbon copy of the T95max and when I tried to root it from magisk app (like a proper newbie) I bricked it and was sent T95max stock firmware from the supplier.
This caused me to start experimenting and trying out other roms. Turns out this Allwinner H6 box is highly customisable.
I have had Ports from Amlogic devices running on this, Pendoo and Tanix TX 6 roms TX Pro roms
Just now I have downgraded it to an android 7.1. 2 Nougat rom Rooted with Magisk and Have got rid of the dreaded AlicUX and replaced with nova launcher.
There was a slight Thermal problem which I fixed by adding active cooling. Please see photos.
Overall, I'm happy with this knock off box now because I've modded it to the hilt. Netflix, prime etc also work as does my IPTV.
Just be careful if you've spent some money on an android box, this one only 35 gbp so I was prepared to take a loss.
4pda Russia is also great for modding tips, as is freaktab.
@3mel, @Bertonumber1 and friends.
I am using the Transpeed-H616_4-32_20200812.img firmware on my Tanix TX6S box with relative success.
REASONS:
TX6S with stock firmware 90ºC / 95 ° C.
TX6S with Transpeed-H616_4-32_20200812.img firmware 70ºC / 75ºC.
But without root I can't use some applications.
Is it possible to root the firmware?
If so, please how should I do it?
Grateful for the attention.
webipsum said:
@3mel, @Bertonumber1 and friends.
I am using the Transpeed-H616_4-32_20200812.img firmware on my Tanix TX6S box with relative success.
REASONS:
TX6S with stock firmware 90ºC / 95 ° C.
TX6S with Transpeed-H616_4-32_20200812.img firmware 70ºC / 75ºC.
But without root I can't use some applications.
Is it possible to root the firmware?
If so, please how should I do it?
Grateful for the attention.
Click to expand...
Click to collapse
Hello mate, yeah the tanix is prone to overheat.
Same chipset as my other box, temperature dropped around 40 degrees when I flashed this firmware.
Modified and rooted (with switch)
T95 TX6S H616 Rom
https://drive.google.com/file/d/1h2MCPxSzkIC1MebgkNlj709yndOhkt5p/view
Try that one mate and see how it goes
@webipsum, if you can find a version of TWRP that can be temporarily flashed as your recovery you might be able to flash magisk.
that's a lot of 'ifs' though, you could just easily be unlucky and brick your device.
@Bertonumber1
I installed the firmware (T95-H616-XR819-10.1.X18.img) you provided. It worked correctly.
Regarding root, the behavior is the same as for Transpeed-H616_4-32_20200812.img.
Applications that check for root say yes, but it is not possible to assign the permissions that some applications request.
Once the firmware (T95-H616-XR819-10.1.X18.img) is applied, it is possible to see that it has an update (OTA). I can download but despite the update app going ahead, restarting the box and etc., the update is not applied.
I found the newest firmware (T95-H616-XR819-10.1.X19.img), but when I apply in the TX6S, it freezes at startup.
I returned the firmware: T95-H616-XR819-10.1.X18.img
My tests in the TX6S:
1) Stock firmware: TX6s_android10_20200730 OK!
Note 1: Temperatura 90ºC/95°C.
2) Transpeed-H616_4-32_20200812.img OK!
Note 1: Stock firmware root is more complete.
Note 2: Temperature 70ºC / 75ºC.
3) T95-H616-XR819-10.1.X18.img OK!
Note 1: Stock firmware root is more complete.
Note 2: Temperature 70ºC / 75ºC.
4) T95-H616-XR819-10.1.X19.img Not work!
Note 1: TX6S freezes at startup. Freeze in the T95 screen.
5) YDS-VONTAR-X1-10.1.A19.img Not work!
Note 1: TX6S freezes at startup. Freeze in the T95 screen.
6) T95-H616-AW859A-10.1.A19.img Not work!
Note 1: TX6S freezes at startup. Freeze in the T95 screen.
@3mel
I will try to install Magisk.
But information and tools like TWRP, Magisk and root are few for boxes with Allwinner H616. Unlike Amlogic.
Thankful
@webipsum use @Bertonumber1's firmware but instead of looking for TWRP install magisk manager from the official thread here on xda. because that firmware is rooted you can install magisk manager and use it to install magisk systemless root. also download the APK file for magisk (from within the manager app) and then you'll have a superuser app to control permissions. after you've completed that turn off the built in root via the root switch in settings about.
EDIT: magisk manager IS the APK file needed to manage superuser and other things so just get that and install magisk root from there.
@3mel
I was able to install Magisk on the TX6S with the T95 alternative firmware (T95-H616-XR819-10.1.X18.img).
However, this firmware, without or with Magisk is presenting the following problem:
All apps that request accessibility permission, when the box is restarted, those apps are without accessibility permission.
I have to grant the permissions again, but just restart and the permissions are disabled.
Friends.
You who have the T95 with stock firmware:
Is it possible to use application widgets? Here(*) I can't.
Here(*), apps that grant accessibility permission, every time the box is restarted, have to grant permission again.
Remote control with voice. To use, I need to remove and replace the CR dongle with the box(*) on.
Does it work on your T95 with stock firmware?
Tks.
(*) Tanix TX6S with T95 firmware (T95-H616-XR819-10.1.X18.img)
widgets do not work for me.
apps do keep their root permission after a reboot
I have microphones all denied permission, I don't want devices listening to the room / I've not tried it.
@3mel and @Bertonumber1
Here is not the specific topic of TX6S, but as TX6, TransTrans and T95, seem to be clones, I thank you for your attention and I present below my experience in relation to the topic:
My experience with the Tanix TX6S box with the firmwares:
TX6S with STOCK FIRMWARE:
Tanix-Box_com-TX6s_android10_20200730.img
Temperature (board inside the case): 90 ° C / 100 ° C
Temperature (board removed from the case and heatsinks placed on the CPU and RAM (both sides of the plate)): 75 ° C / 85 ° C
Clock: OK!
widget: DOES NOT work. When configuring - without success - a widget, the message (tosted) returns: “Please turn off the" Don't keep activities "option in developer options.” I checked that in the developer options this option is OFF by default.
Magisk: Installation success. SuperUser working OK!
MagiskHide does not work. HBO GO identifies root. HBO GO does NOT work.
Accessibility permission: Accessibility permissions granted to apps are maintained, even when the box is reset.
TX6S with TRANSPEED ALTERNATIVE FIRMWARE:
Transpeed-H616_4-32_20200812.img
Temperature (board inside the case): not tested.
Temperature (board removed from the case and heatsinks placed on the CPU and RAM (both sides of the plate)): 75 ° C / 85 ° C
Clock: CRAZY! Display of numbers inverted vertically and some numbers, also inverted horizontally.
widget: DOES NOT work. When configuring - without success - a widget, the message (tosted) returns: “Please turn off the" Don't keep activities "option in developer options.” I checked that in the developer options this option is OFF by default.
Magisk: I was unable to install..
MagiskHide: I was unable to install.
Accessibility permission: Accessibility permissions granted to apps are NOT maintained when the box is reset. It is necessary to grant permissions every time the box is reset.
TX6S with T95 ALTERNATIVE FIRMWARE:
T95-H616-XR819-10.1.X18.img
Temperature (board inside the case): not tested.
Temperature (board removed from the case and heatsinks placed on the CPU and RAM (both sides of the plate)): 75 ° C / 85 ° C
Magisk: Installation success. SuperUser working OK!
MagiskHide WORKS. HBO GO does NOT identify root. HBO GO works.
Clock: OFF. Does not work!
widget: DOES NOT work. When configuring - without success - a widget, the message (tosted) returns: “Please turn off the" Don't keep activities "option in developer options.” I checked that in the developer options this option is OFF by default.
Accessibility permission: Accessibility permissions granted to apps are NOT maintained when the box is reset. It is necessary to grant permissions every time the box is reset.
CONCLUSION:
I am using the STOCK FIRMWARE.
REASON: The correct functioning of the accessibility permission is more important to me, at the moment, than HBO GO.
webipsum said:
@3mel and @Bertonumber1
Here is not the specific topic of TX6S, but as TX6, TransTrans and T95, seem to be clones, I thank you for your attention and I present below my experience in relation to the topic:
My experience with the Tanix TX6S box with the firmwares: ...
Click to expand...
Click to collapse
Remote control with voice: the voice (CR) does not work in all 3 cases. To use voice (CR) it is necessary to remove the CR dongle from the USB and put again (with the box power on).
3mel said:
widgets do not work for me.
apps do keep their root permission after a reboot
I have microphones all denied permission, I don't want devices listening to the room / I've tried it.
Click to expand...
Click to collapse
@3mel
Please: Can you open the list of recent apps to clear everything or close one by one?
Tks.
Related
Hello,
I have an external USB camera(endoscope) that I'd like to use with my Huawei Mediapad tablet. I've been googling and its possible, there is no hardware restrictions since USB OTG is working(tested with thumb drive). I'm not sure about UVC drivers but there are a few other problems that might be causing the problem.
Reading a blog i discovered that since KitKat(this tablet has 4.4.4) the SELinux policy is set to "enforced" and therefore apps can't access external USB camera feeds like they used to straight out of the box. There are 3 workarounds which all require rooting.
1. Start the app with superuser rights
2. Configure SELinux to allow USB cam feed
3. Custrom rom
Blog link: htt ps://droidperception.wordpress. com/2013/12/01/webcams-on-android-4-4/
So it all comes down to this - I need to have this device rooted but I haven't even found a single thread about this model in this forum.
NB! I don't have room for experimentation(read: bricking the device) since the device is not mine.
Thanks for you attention,
Pask
You ask quite a while ago and I see no answer. So, just in case, I did root mine in a way I not necessary would recommend, but ... KingRoot latest version can do a trick, but it definitely not kind of software I would keep on my tablet. So after that I install SuperSU, Link2SD ( using it to get rid of applications I do not like) and RootExplorer + Terminal. Give all of them root access using KingRoot manager and with help of Super-Sume App (will cost you some money) start a process of getting read of all related to KingRoot and Co. It is more tricky that one may think but by freezing and killing some processes in "write" time I manage to install SupeSU binaries and remove left overs. I still have problems to get su requests, so just copy config files from my phone with access rights already given to specific applications and deny access to anything else. So far do not see anything I cannot identify running, so my hope KingRoot is completly gone.
So far I did not fine any other tools/methods to get root
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable. Instead, I was greeted with the same Error 40 that everyone with a rooted device got. It took me a couple of days of researching and playing and reflashing and..., but I've finally figured out the simple(r) method to bypass this stupid root check for DirectTV Now (AKA Error 40, QP1005)
This applies to the TX5Pro, but it should work on any s905x based AMLogic SoC running Marshmallow 6.0 (A95X, CQ9, TX5, TX3, X96, NEXBOX, +many more.) As I understand it, they all have similar Android builds using the p212 board and firmware. I also have a M8S s812 running Kit-Kat 4.4.2 that I'll work on breaking, next.
First things, first: If possible, find your firmware and do a clean flash. Not a requirement, but if you've been playing with this for a while and you've ended up here, you've probably mucked up your /system files in some way or another. I managed to screw up my su binary location a few times and couldn't get it back without a lot of work. Reflashing was a three-minute, headache-free task.
That said, you'll want to adb over tcp/ip as these devices don't like to play the USB cable game.
Code:
adb connect deviceipaddress:5555
Follow up with
Code:
adb shell
and
Code:
su
to get into a root shell (if you don't get one by default.) Mine came with SuperUser from ClockworkMod preinstalled as a system app. Mount your system folder
Code:
mount -o rw,remount,rw /system
and edit your build.prop file with Vim.
Code:
vi /system/build.prop
If Vim is new to you, search the interwebs for a Vim cheat sheet.
Here's the trick with this... DirecTV Now's shared object file in lib/armeabi/libdrmagent_downloadable_jni.so looks for a few keywords within a few properties. Those properties are:
Code:
ro.build.product
ro.build.tags
ro.build.type
ro.build.display.id
...and the keywords are:
Code:
"release-keys, OnePlus2, OnePlus, Z26CL, STUDIO_C, user" are keywords that it favors, while "cm, cyanogen, cyanogenmod, debug, userdebug, A0001" are disqualifying keywords. Supposedly, "test-keys" is a bad word, too.
In my case, I needed to edit my build.prop to eliminate any sign of the bad words. Example:
Code:
ro.build.display.id=p212-userdebug 6.0.1 MHC19J 20160909 test-keys
to
ro.build.display.id=p212-user 6.0.1 MHC19J 20160909 release-keys
Run through the file and replace anything that says userdebug with user and test-keys with release-keys until you get to "#end build properties" Then save and reboot.
After reboot, install Hide My Root (I used the one from Amphoras) and hide the Su binary. This is where things might be getting tricky for some of you... on the TX5Pro, the SuperUser app is a system installed app, meaning it can't be uninstalled (it can, but it's not exactly a simple task for everyone) so you'll need to go into settings -> apps -> superuser and disable the app from there. Reboot again. Now, with the su binary hidden and the app's manifest not showing up in the system, the error 40 message should go away. This option will allow you to quickly restore su and SuperUser without needing a bunch of additional steps. You'll still need to set the device location service to "battery saving" (or use mock locations) but that's a simple task anyone can figure out.
The app is a choppy on high def feeds for some reason. I can't tell if this is processing/memory issue or a feed (wifi) issue. By default, the app doesn't work on ethernet, meaning you'll have to use wifi until you can fix that issue. But hey, one thing at a time, right? Anyway, I hope this helps anyone with this particular headache.
Thanks for pointing me in the right direction...
Got DirecTV NOW working on my nexus 6 running pure nexus ROM... I just did the edits with super su root and root explorer. Then disabled super su and rebooted.
Now to update the the build.prop files on the lineage os 13.0 nexus 10, and my wife's kltevzw (on ting gsm network) running lineage os 14.1
hi please help i flashed wrong twrp recovery i think now my amlogic smartbox failed to boot in recovery mode and the main problem is my smartbox Encryption Unsuccessful Factory reset, when i click factory reset nothing happend please guide how to solve this
Sent from my SM-N910G using Tapatalk
jameson.donaghy said:
I downloaded the DirecTV Now app on New Year's Eve hoping for $35/cable.
Click to expand...
Click to collapse
Any chance that you tried this out with Data Free TV/"Sponsored Data" with an AT&T wireless account? i.e. running the box through a Cellular Hotspot or tethered to your phone. I've been looking at if one could use one of therse Android TV Boxes to basically get Data Free TV.
my live tv app detect root try with magisk also but no success in my s905x help me guys
Sent from my SM-N910G using Tapatalk
is anyone help me out
Sent from my SM-N910G using Tapatalk
I edited my build.prop files to try and "hide" the root and I still get the error. I also tried root cloak with xposed and still nothing
Thanks so much
This really helped. I used Xposed module to hide those keywords. Worked a charm!
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.
Hi,
I want to root my xiaomi mi box 3
Do you have a tutorial to do this?
I don't find it....
No you can't. Xiaomi does not provide the bootloader private key unlock. As referenced here: https://forum.xda-developers.com/an.../to-root-xiaomi-mi-box-s-info-please-t3876822
Sent from my Moto Z Play using Tapatalk.
Yes
I've done it before , but it was more of a tethered root for say , I used a raspberry pi to get around the selinux , make sure adb was on , downgraded to the userdebug rooted , got the pi to disable selinux when it detected the box over adb , then after you have that accomplished update the box and there you go , I'd have to do it again and wipey box if you wanted me to try it again , and get another pi for it to bypass that little annoyance of a bootloop (caused by selinux) your not changing the ROM just modding your current system and getting around your selinux so no your bootloader doesn't need to be unlocked , like someone else said but it's tethered for say
coffenat said:
I've done it before , but it was more of a tethered root for say , I used a raspberry pi to get around the selinux , make sure adb was on , downgraded to the userdebug rooted , got the pi to disable selinux when it detected the box over adb , then after you have that accomplished update the box and there you go , I'd have to do it again and wipey box if you wanted me to try it again , and get another pi for it to bypass that little annoyance of a bootloop (caused by selinux) your not changing the ROM just modding your current system and getting around your selinux so no your bootloader doesn't need to be unlocked , like someone else said but it's tethered for say
Click to expand...
Click to collapse
You are playing with semantics. What you described is a system that allows temporary admin access via userdebug firmware. This will not allow you to install any apk that requires administrative access and goes away on reboot.
Unfortunately, there has been no userdebug version for either Android 8 or Android 8.1, so none of the international official AndroidTV boxes can support this method.
Only hope is to find a factory fresh MiBox 3 (MDZ16AB) that is still running MM version, 4.54 then flash a Nougat userdebug firmware, build 1028.
Had apks supersu installed
Had super su installed the only thing wrong with the set up was after I updated the firmware , it was still rooted but if I didnt tether something to it to disable selinux on boot itd hit a boot loop , but if you downgraded with the update.zip file , did the adb root , uploaded su , installed supersu , set up the outside device with adb to disable selinux, upgraded, youd have an updated mibox 3 , I'd have to go through google but I used a modified version of someone's script for the root and some udev rules on a rpi0 , and posted somewhere the instructions I'd just have to find it again if I do I'll share the link or re duplicate and share
Just read a tool exploiting a new 0-day exploit may be able to root and disable the selinux (making it untethered) called quickr00t if anybody wants to give it a shot thinking I will my next day off it's a poc code right now you'll have to compile it yourself , thinking I may try my next day off , so Friday I may give it a shot
---------- Post added at 07:43 AM ---------- Previous post was at 07:40 AM ----------
https://www-zdnet-com.cdn.ampprojec...-of-concept-code-for-recent-android-zero-day/
Since this comes up first in google when searching for mi bix 3 root. I would like to inform all that the mi box 3 source code has been released by xiaomi as claimed by this link https://piunikaweb.com/2019/02/28/x...bal-kernel-source-codes-3-years-after-launch/
I have MI Box 3, with pre installed Netflix TV application i can play upto 1080p resolution. Problem is when i install mobile apk to MI Box 3 i can only play upto 540p (960×540) resolution. (Checked with the test pattern episode in Netflix). MI Box is DRM L1 certified. I wanted to play mobile Netflix Application since i want to play US contents using smartdns and use my netflix content based internet package ( With latest version of netflix tv app doesn't support smartdns properly, when i enable smartdns with Netflix TV Application it start to bypass my content based internet plan). All things work fine with Netflix mobile application except the resolution. How can i fix that? Any ideas?
Maduwantha said:
I have MI Box 3, with pre installed Netflix TV application i can play upto 1080p resolution. Problem is when i install mobile apk to MI Box 3 i can only play upto 540p (960×540) resolution. (Checked with the test pattern episode in Netflix). MI Box is DRM L1 certified. I wanted to play mobile Netflix Application since i want to play US contents using smartdns and use my netflix content based internet package ( With latest version of netflix tv app doesn't support smartdns properly, when i enable smartdns with Netflix TV Application it start to bypass my content based internet plan). All things work fine with Netflix mobile application except the resolution. How can i fix that? Any ideas?
Click to expand...
Click to collapse
Mobile apk is not designed to validate presence of DRM as it is not allowed to exceed 480/540 resolution.
You could search for earlier versions of Netflix Ninja (AndroidTV version) which may be more tolerant of VPN trickery...
You may be able to extract it from some of the older Nougat or MM builds here or in /r/Androidtv on Reddit.
Good luck
bigtalker said:
Mobile apk is not designed to validate presence of DRM as it is not allowed to exceed 480/540 resolution.
You could search for earlier versions of Netflix Ninja (AndroidTV version) which may be more tolerant of VPN trickery...
You may be able to extract it from some of the older Nougat or MM builds here or in /r/Androidtv on Reddit.
Good luck
Click to expand...
Click to collapse
I had to downgrade the MI Box 3 to old Oreo update and it works. But don't know how long i can use Netflix Ninja 5.4.1 version in there. Even when we have paid for Netflix UHD Subscription and Pay for Data bills why Netflix bother to give us 1080p support? I do not see reason behind it.
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).