Related
Hello everyone. I just started selling these at my job. I was wondering if anyone knows what is under the hood of this thing. Also if its common enough hardware, are there any roms on this forum that it will work with?
I'm most interested because there is no play store. This is an amazon app store device
Thanks for your help!
http://www.craigelectronics.com/site/pdetails.php?id=420
for details
Processing Speed 1.5GHz
Operating System : Powered By Google Android 4.1
4 GB Built-in Flash Memory
Built-in 1GB DDR III RAM
Built-in WiFi (802.11b/g/n)
Support Video Format : MKV/AVI/RM/RMVB/FLV/WMV/MP4/MPG/VOB (Up to 1080p)
Support Audio Format : MP3/WMA/WAV
Support Photo Format : JPEG/BMP/GIF/PNG
Support e-Reader Format : PDF/PDF/DRM/TXT/EPUB/EPUB DRM/HTML/FB2
Supports 3D Gaming Accelerometer
Built-In Full Size USB Port for Input Device Connection
Support Wireless Keyboard and Mouse
HDMI Interface to connect to Any HDTV
Micro USB port for power Supply
Micro SD Card Slot (Supports Max. 32GB)
Supports Amazon App Store, Dropbox, Soc.io. Mall, Opera, Netflix, Browser, e-Book Reader, e-Mail, Photos, Maps, Video, YouTube, Facebook, Twitter, Music,Clock
I finally have this craig CVD601 figured out 100%.
after days of playing and searching around here is all the info.
there are customs roms.
mainly the hardware is a tvdongle_8277-aihua figured this out by click on the model number multiple times (under setting about device. a few easter eggs like this in the android world)
uses a wondermedia wm8850 cpu
custom roms for many devices, the one i used on my craig is good for 200 other devices.
rom i used works great so far
WM8850_Universal_Uberoid_v1.0_JB_4.1.1_01MAR2013_[TechKnowForum.net]
http://www.techknow.me/forum/index.php?board=121.0
I am very happy with this device after finding this rom.
Total nube. I was gonna pick up a minix G4 for tv streaming, but this was $10 !!
It was on clearance at Rideaid.
So, I quick googled on my phone and saw this post.
Based on that I bought two.
It automatically updated to Jelly bean, but what ROMs do y'all recommend to get this think cookin?
As it is it is not impressing me.
I really just want it to watch Game of Thrones and Walking Dead.
Many thanks and yes I searched and yes I watched that Noob video on registration.
$10 really? I paid $70
from my other post.
rom i used works great so far
WM8850_Universal_Uberoid_v1.0_JB_4.1.1_01MAR2013_[TechKnowForum.net]
http://www.techknow.me/forum/index.php?board=121.0
Yes. $10.
Sorry. I actually bought two for $10. Each. they were on Uber clearance at the rite-aid.
Can I run ubuntu on this?
I looked at those links and there was none.
acem77 said:
$10 really? I paid $70
from my other post.
rom i used works great so far
WM8850_Universal_Uberoid_v1.0_JB_4.1.1_01MAR2013_[TechKnowForum.net]
http://www.techknow.me/forum/index.php?board=121.0
Click to expand...
Click to collapse
Does HDMI-CEC work with this unit and rom combo?
I'm holding out trying to find a device that will integrate with my remote control and tv.
DPI
Anybody figure out a way to change the DPI without being stuck in a boot loop? I'm having to completely re-install everything after attempting to change the DPI.
Need drivers
Ok, so my unit is dead. It's flashing a green light and it won't start. If someone could dropbox a driver package for the device, it would totally make my day.
CVD601 Rooted with GAPPS!
So I picked one of these things up on eBay cheap and decided to mess around with it. Out of the box it had ICS on it and was very unstable. Fortunately it began doing an OTA upgrade to Jelly Bean almost immediately after I got a WiFi connection. Unfortunately I was at my parents house and they have DSL with a top download speed of about 1.5Mbps so the whole JB image took like 4 hours to download. Once it finally downloaded I was able to apply the update and BAM, a CVD601 running JB 4.1.1. My initial enthusiasm was soon crushed when I realized there was no Google Play store however. Not being one to give up easily I began a week long quest to get GAPPS working properly on this device. I'm happy to say that after much trial and error I now have a CVD601 running JB which is rooted and has a fully functional Google Play App.
The Craig website which is linked in the top post now has a new 4.1 image that can be downloaded, it appears to contain GAPPS but I have not tried applying it for fear of destroying everything I have worked all week to accomplish. If someone would like to apply it, or has, and can report back on here whether or not GAPPS actually works that would be great. This image appears to be slightly older than the one that downloads OTA (from Taiwan) but if it has functional GAPPS it is probably the better choice.
As for rooting this device I was able to get version 1 of RootBurner for the WM8850 to work, the OTA image has su in /sbin so it must have been rooted at some point. RootBurner appears to do nothing when you boot the device with the SD card inserted but you should notice that the device does not boot properly but instead appears to be in a boot loop going from the JB logo to a seemingly blank black screen. I think this is because the boot files in RootBurner were made for a tablet rather than an HDMI device. If you let it go through the boot process a couple times and then power off, remove the SD card, and power back up your device should boot normally. If it worked you will see a Android is Updating message before the boot completes.
Feel free to post any questions and I will try to answer them as best I can.
Heiligkuh said:
So I picked one of these things up on eBay cheap and decided to mess around with it. Out of the box it had ICS on it and was very unstable. Fortunately it began doing an OTA upgrade to Jelly Bean almost immediately after I got a WiFi connection. Unfortunately I was at my parents house and they have DSL with a top download speed of about 1.5Mbps so the whole JB image took like 4 hours to download. Once it finally downloaded I was able to apply the update and BAM, a CVD601 running JB 4.1.1. My initial enthusiasm was soon crushed when I realized there was no Google Play store however. Not being one to give up easily I began a week long quest to get GAPPS working properly on this device. I'm happy to say that after much trial and error I now have a CVD601 running JB which is rooted and has a fully functional Google Play App.
The Craig website which is linked in the top post now has a new 4.1 image that can be downloaded, it appears to contain GAPPS but I have not tried applying it for fear of destroying everything I have worked all week to accomplish. If someone would like to apply it, or has, and can report back on here whether or not GAPPS actually works that would be great. This image appears to be slightly older than the one that downloads OTA (from Taiwan) but if it has functional GAPPS it is probably the better choice.
As for rooting this device I was able to get version 1 of RootBurner for the WM8850 to work, the OTA image has su in /sbin so it must have been rooted at some point. RootBurner appears to do nothing when you boot the device with the SD card inserted but you should notice that the device does not boot properly but instead appears to be in a boot loop going from the JB logo to a seemingly blank black screen. I think this is because the boot files in RootBurner were made for a tablet rather than an HDMI device. If you let it go through the boot process a couple times and then power off, remove the SD card, and power back up your device should boot normally. If it worked you will see a Android is Updating message before the boot completes.
Feel free to post any questions and I will try to answer them as best I can.
Click to expand...
Click to collapse
Hey there, just got the device myself the other day. I'm going to try your method as the Uberoid ROM wont boot for me no matter what I seem to do and Uberizer doesnt work because for the life of me I can't get the Developer Options to show no matter how many times I click the build number!
---------- Post added at 11:43 AM ---------- Previous post was at 11:28 AM ----------
Okay so just tried RootBurner with no luck. No matter what I do this thing will not boot from the SD Card. Any ideas?
acem77 said:
I finally have this craig CVD601 figured out 100%.
after days of playing and searching around here is all the info.
there are customs roms.
mainly the hardware is a tvdongle_8277-aihua figured this out by click on the model number multiple times (under setting about device. a few easter eggs like this in the android world)
uses a wondermedia wm8850 cpu
custom roms for many devices, the one i used on my craig is good for 200 other devices.
rom i used works great so far
WM8850_Universal_Uberoid_v1.0_JB_4.1.1_01MAR2013_[TechKnowForum.net]
http://www.techknow.me/forum/index.php?board=121.0
I am very happy with this device after finding this rom.
Click to expand...
Click to collapse
When doing this method did you open TVDongle_8277-AiHua.fwc in Notepad and remove everything and replace it with
Code:
#--BEGIN OF FILE
<?xml version="1.0" ?>
<!--????FMaker????,????????-->
<!--This file is generated by FMaker, don't modify it manually.-->
<!--???:?? SimenXie Tel-6786.-->
<product>
<editor>Last edited by RubbitXiao on 2012-10-08 12:04:26</editor>
<modules>
<DDR_TYPE name="??????" />
<BOOTDEV name="NAND" />
<TOUCH name="FT5406_AS1220" />
<KEY_PAD name="??" />
<VIBRATE name="??" />
<SENSOR name="??" />
<CODEC name="??" />
<SPEAKER name="??" />
<BATTERY name="??" />
</modules>
<ext>
<cmd>setenv wmt.camera.param 1:12:0:0:0:0:0:0:0:0</cmd>
<cmd>setenv wmt.io.touch 1:SSD253X_pyd7a1ctphole1:9:480:800:4:0:1:1:1:1</cmd>
<cmd>setenv wmt.io.ts.2dcal 23775 492 206136 -155 24362 1259 25156</cmd>
</ext>
<auto />
</product>
#--END OF FILE
Or did you append that code to the rest of the code? I'm a lil lost in this root/flashing method.
_
Have you tried Uberoid 2.0 on it yet? http://www.techknow.me/forum/index.php?topic=5356.0
Okay so I just added the lines from that file I didn't see in it already...
My next question is has anybody tried hooking up a webcam to one of these and got it working as the system's camera?
So I ran into a problem, I think... On Uberoid 2.0 my 16Gb microSD card only shows up as 80Mb's or somewhere around that size.
drivers with a improperly flashed unit
Will someone on here please share their Windows drivers for this device? I'm doing everything I can to fix my device so it will boot. I loaded the wrong firmware and now the device will not boot with the accurate fwc. Any thoughts or suggestions? I'm stumped.
Anybody find a way to reset the the display resolution? I let my friend use it who has a tube flat panel tv with a hdmi port and I had it set to the largest and he said it was way to big on his tv so he changed it back and then it was all pixelated.
Fun with Craig
I bought one of these (for a lot more than $10, sadly) and have been playing with it for the past few weeks.
I bought it to play video files and stream Youtube. I plugged it into a USB hub and it plays a bunch of formats that my Samsung home theatre doesn't like, but the wifi is unreliable and it can't read my 2 TB hard drive (it's FAT32, not NTFS), though it reads USB memory sticks OK.
I am past the store's return date, so I'm going to play with it and hack it as much as possible.
It came with JB 4.1.1 installed, no Google Play access, just Amazon.
It was not rooted and there is no developer options. (See below.)
I tried the image from the Craig web site and it's the same.
Clicking three times on the device info where it says Craig CVD 601 does switch to tvdongle_8277-aihua, as acem777 says.
I managed to root it with RootBurner, as per Heiligkuh's post. I used RootBurner_v0.1_MaPan on an SD card and it booted and rooted in a few seconds. I pulled the card and it rebooted into JB 4.1.1 with Superuser in the apps list. Hooray! Now I can run the techknow toolkit.
And I have the original Craig ROM so I can always go back to square one.
The TVDongle_8277-AiHua.fwc file from the Craig ROM is identical to the Uberoid version except it includes a name in the "<product>" and it turns off "developer options":
Code:
<?xml version="1.0" ?>
<!--本文件由FMaker自动生成，手动修改需谨慎。-->
<!--This file is generated by FMaker, don't modify it manually.-->
<!--Created by aksenxu on 2012-08-16 16:06:19.-->
<product model="CVD601" manufacture="Aihua">
<editor>Last edited by heng on 2012-12-25 15:15:09</editor>
<modules>
<DDR_TYPE name="参考板载信息" />
<BOOTDEV name="NAND" />
<TOUCH name="无" />
<KEY_PAD name="默认" />
<VIBRATE name="无" />
<SENSOR name="无" />
<CODEC name="HW DAC-板上没有声卡" />
<SPEAKER name="默认" />
<BATTERY name="无" />
<MODEM name="无" />
</modules>
<ext>
<cmd>+setenv wmt.td.param 1</cmd>
<cmd>+setenv wmt.display.param 8:0:0:1280:720:60</cmd>
<cmd>+setenv wmt.display.dual 1</cmd>
<cmd>+setenv wmt.pmc.param 1:0:0</cmd>
<cmd>+setenv wmt.audio.i2s hwdac</cmd>
<cmd>setenv wmt.display.chargeanim 0</cmd>
<cmd>setenv wmt.camera.i2c_gpio</cmd>
<cmd>setenv wmt.camera.param 2:12:1:0:0:0:0:0:0:0</cmd>
<cmd>setprop ro.wmt.drv.remove gsensor_kxte9_md,wmt_battery_md</cmd>
<cmd>setprop ro.wmt.usbcamera.probe 1</cmd>
<cmd>setprop ro.wmt.audio.hardware MONOMIX=[0,0],USBMIC=[1],AMPCTRL=[0,0,0,0],HSMICCTRL=[0,0,0,0]</cmd>
<cmd>setprop ro.wmt.launcher2.power_reboot true</cmd>
<cmd>setprop ro.wmt.launcher2.power_off true</cmd>
<cmd>setprop ro.wmt.poweroff_to_hdmi true</cmd>
<cmd>setprop ro.wmt.shutdown_to_wifi true</cmd>
<cmd>setprop ro.mouse.sbutton 4</cmd>
<cmd>setprop ro.wmt.f7f8 volume</cmd>
<cmd>setprop ro.wmt.ui.settings_remove ethernet,3g,gps,pppoe,battery,brightness,airmode,camera,developer_options</cmd>
<cmd>setprop ro.product.model CVD601</cmd>
<cmd>setprop ro.wmt.wizard.hdmi 1</cmd>
<cmd>setprop allow.system.3rdapk 1</cmd>
<cmd>setprop ro.wmt.rmtctrl.enable 0</cmd>
<cmd>setprop ro.wmt.disable_video_thumbnail true</cmd>
<cmd>setprop wmt.HLS.support 0</cmd>
<cmd>cp -v wmtAirShow/MyAirShow.apk ${instenv_fs_data}/app/</cmd>
<cmd>cp -v wmtAirShow/MyAirShow.apk ${instenv_fs_system}/.restore/data_app/</cmd>
</ext>
<auto>
<cmd>setprop ro.wmt.product aihua-cvd601</cmd>
</auto>
</product>
I'm going to try the Uberoid ROM and if that fails I will reinstall the Craig ROM after I manually edit the file to allow developer options. Manual edit? Oh no! I've voided the warranty!
Fun Toy So Far
I got one on clearance at rite aid for $25, but they're gone from there now.
I added a powered usb hub and connected usb mouse, keyboard and memory stick. They're all working. With a TV, they make a very small pc setup.
I rooted it via method posted above, RootBurner_v0.1_MapPan.zip .
Then I pulled Play Store from my rooted phone, an LG LS970, and installed it on the stick using adb. I also installed any apks I found that seemed necessary.
At first Play Store didn't really work -- it threw errors and died -- but then it updated and it has worked since.
I'd like to find a recovery for it.
I'm also going to try hooking up a USB camera. I have my doubts about whether that will work, but it'll be cool if it does.
eyesquash said:
I'm also going to try hooking up a USB camera. I have my doubts about whether that will work, but it'll be cool if it does.
Click to expand...
Click to collapse
No luck with Uberoid. I get an error part way through the install, but as I said, I have the Craig img file so I started over and rooted it again.
I'd like to figure out how to get bluetooth working. I have a $2 BT dongle and it would be nice to have it recognized when I plug it in to the hub.
Update
I got Google Play installed and working, thanks for mentioning it, eyesquash!
I have an Amazon account so I can download apps from there, as well.
I have a 32Gig SDHC card which gives me lots of room for junk.
More expensive than Chromecast, but fewer limitations.
Cheaper than Apple TV, but more fun to tinker with.
I am trying to sideload cyanogen mod. Whenever I boot the phone into TWRP, Windows 7 (64 bit) tries to install MTB USB Device drivers and fails.
Driver Software Installation:
Device driver software was not successfully installed
Please consult with your device manufacturer for
assitance getting this device installed.
MTB USB Device X Failed
I already uninstalled Android SDK Tools and re-installed, making sure that Google USB Drivers are installed. I also installed Motorola drivers, but that was at the start of my journey and I didn't take notes on the details.
I have no problems accessing the phone via USB when the phone is booted up normally. I also have no problems using fastboot when the phone is is bootloader mode.
I originally tried a number of ways to use CWM instead of TWRP, but was unsuccessful. I've posted those efforts in this forum and abandoned CWM after a while.
Has anyone who owns a Moto G actually been able to install CWM or install CyanogenMod using TWRP? I want to use adb rather than non-mainstream tools, and I'm not interested in rooting at the moment (though rooters are more likely to be familiar with issues at this level).
From further web search, this is the last news that I can find about MTP USB drivers when booted up in TWRP: <<erroneous URL removed (I can't re-find the correct webpage)>>
I'll continue sleuthing a bit more before looking at how to install cyanogenMode without sideload. But for now, it seems that the MTP issue remains (though I admit, I'm new to the whole smartphone thing and I could be wrong about that).
Afternote: I chose sideload so that I wouldn't have to worry about where the cyanogenMod zip file goes. From using adb shell to "ls" around, it seemed a bit confusing, and it wasn't obvious how the directory structure from "ls"ing around matched the 5-7 partitions that are on most Android file systems. In fact, entire subtrees seemed to repeat themselves at different parts of the tree.
I followed a suggestion on another forum and used the push method. I followed wiki.cyanogenmod.org/w/Install_CM_for_falcon. I found that I needed to bookend sdcard with slashes: "/sdcard/".
I am now facing the (apparently commonplace) problem of being in an endless loop with the popup "Unfortunately, the process com.android.systemui has stopped. [OK]". I'm one step further, though. There seem to be many causes for this problem, with varying degrees of similarity in the symptom. I've not yet run across a case with exactly the same symptom, where the loop occurs at the language selection screen. Of the various circumstances that I've read about, the one that seems that it might be most relevant is the association of this error with an Italian keyboard app. In my case, the English (Canada) language seems to be selected, if I'm interpretting the graphics properly. I will try replacing the keyboard apk with one from a nightly. New territory.
The other causes are flipboard app, ART vs. Dalvik, and possibly a few others.
Someone suggested that I might try clearing data and cache on Google Play Framework. I googled how-to-clear-data-and-cache-on-Google-Play-Framework, and read www.androidpit.com/google-play-not-working. It seems that you have to be able to get the OS working before you can actually clear those Google Play data. I haven't been able to get beyond the language screen. I can't access the device via adb, either.
Afternote: I was able to press Next a few times in between the error message popups, and I got the the home screen. The devices shows as XT1032 in the Windows Explorer, but there's nothing in that "folder".
Update: I don't have any app beginning with the word "Google", so it seems that none of the above measures having to do with Google Play apply in my case. I suspect that this may be because I'm working with a virgin install of CyanogenMod. Looks like I'm still on search for a way ahead. I also tried switching the language from English (Canada) to English (US), based on the info I found online that the problem was due to a keyboard apk. No joy.....
Update: Another user had the same problem and solved it by reverting to CM 10 (www.reddit.com/r/cyanogenmod/comments/2gvmqu/cm11moto_g_comandroidsystemui_is_crashing_after). Looks like I have a way ahead.
Hi everyone,
I'm new on xda and I come here because I struggle to install this app on my rooted Galaxy S4 with CyanogenMod 11: "Paiement mobile (pour Orange)" (sorry, I'm new, so I cannot post urls).
In fact, this app has not been declared by the devs (on the Google Play) to be compatible with my phone, despite the fact that I have the specs to run it (NFC payment).
I asked a friend who was able to download the app to upload it on Aptoide, giving me the opportunity to download the apk on my phone (this apk is available in this thread). I tried to install it, but I get the following the error: "app not installed".
I would like to force the installation of the app. I tried many ways, like using apps that use root access on the phone, without success (for example, I tried with "System Apps Installer" on the Google Play, but I get a problem with mounting /system). I also tried to install it with the command line tool, but I get the error "[install_failed_invalid_uri]". I tried to change the permission of the /data/local directory and /data/local/tmp with ES file explorer, but it did not change anything.
In addition to this, I'm not able to enable usb debugging in the developper options (to install the apk with adb), because every time I activate the option, it becomes disabled in the following seconds.
It seems to be a little bit complicated, because I seem to have different problems, but I hope that someone here will be able to help me !
Thanks for your help,
Aquignis.
The issue is most likely Cm. They alter things so some that normally work no longer work
I suceeded to solve the "[install_failed_invalid_uri]" error in the command line tool by also changing the permissions of /data.
After that, I got another error (yes, one more, but the last) that made me discovering what's the real problem in this situation: "install_failed_missing_shared_library". By doing some researches on the web and exploring the apk, I understood that the app use a library called "org.simalliance.openmobileapi" that corresponds to the work of SIMalliance, who developped an API called "Open Mobile API", which notably enables communication with NFC sim cards and must be integrated to the build of the ROM. This system is used by many banks in Europe and has been integrated in the stock ROM of many NFC devices by the important manufacturers, but not by Cyanogenmod devs in the last stable release of CM 11 for the Galaxy S4.
Like you said it, the problem was CM
I asked them if it has been integrated in CM 12, because that is why the app is said to be incompatible with my device by Google Play which automatically checks which libraries are installed on your device (I'm waiting for their answer). The other solution would be to add the library to the CM build by myself, because it seems not to be very complicated, but I'm not qualified enough to do this !
If it is not part of aosp I wouldn't count on it being added to be honest. Not to mention most banking apps refuse to work if the Rom has root as it can cause security issues.
Yes, the root seems to be a problem with some apps according to the work of this man.
On the other hand, I think that this API is important enough to make CM devs pay attention to it, because it is used in many countries (except the USA which use only HCE, I believe). If only I was able to build it myself !
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.
I published a script that can automatically resign GrapheneOS OTAs with your own keys, and also optionally apply a few modifications like enabling ADB root (without turning on ro.debuggable), ignoring allowbackup and changing the update URL.
You can use it if you like GrapheneOS (I think it's the Android OS with the best engineering, security and privacy), but would also like to have full control of your device, by controlling the verified boot keys of your device and applying modifications that make the OS do what you want regardless of what upstream OS developers, app developers, or anyone else might want.
Note that, on the other hand, GrapheneOS follows the Google Android security model which says that the OS will not perform an action you want it to perform if it may result in something that "application developers, content producers, service providers, and employers" do not consent to (which means not letting you have root, or ignore app wishes regarding backups and other settings, or send arbitrary responses to app requests, etc.), while this script will let you do what you want with your own device regardless of whether it's in anyone else's interest or not, including things that this script does not itself support since you control the verified boot keys of the device and can thus sign anything; all this while still taking advantage of all the security and privacy features in GrapheneOS, including verified boot.
You can find it at https://github.com/chriswoope/resign-android-image
Currently it's intended for people with good technical knowledge, although once you set it up (if you run Qubes a lot of steps are automated) it should continue working with no or minimal intervention.
Thank you very much for this
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
pmatj said:
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
Click to expand...
Click to collapse
I was not able to get this working myself unfortunately
but using a different script called AVBRoot and using it on a self built build of GrapheneOS I am able to lock the bootloader with Magisk Root
I have created this guide to help people https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
pmatj said:
Hi, do you still update your tools? I've changed quite some things while traing to get this running for a Pixel 7....
I had to adept quite some changes (e.g. for init_boot on A13 shipped device, incresed HeapSize for Java, as SmailPatcher crashes, problems while generating keys with signify-openbsd and also missing tools like zip and unzip on a fresh installed debian), but in the end I received a nice zip which I've flahsed to the device, but I ended up in a Bootloop (Google Logo, Graphene Logo, some seconds and then.. reboot).
So, did someone got this running with A13 (and at best also on a Pixel 7)?
Click to expand...
Click to collapse
Hey, did you ever get this working on Pixel 7?
User.Hemlock said:
Hey, did you ever get this working on Pixel 7?
Click to expand...
Click to collapse
You can use AVBRoot to patch and sign roms to get root with a locked boot loader using GrapheneOS
I wrote a guide here https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
FireRattus said:
You can use AVBRoot to patch and sign roms
Click to expand...
Click to collapse
Thanks! Haven't had a chance to dig into AVBroot yet, but I'm guessing the patching capability would include things like ignoring allowbackup? (that was one of OP's features that I was interested in)
User.Hemlock said:
Thanks! Haven't had a chance to dig into AVBroot yet, but I'm guessing the patching capability would include things like ignoring allowbackup? (that was one of OP's features that I was interested in)
Click to expand...
Click to collapse
The main purpose of AVBRoot is to root and sign an image so that with pixel devices for example you can lock the bootloader and have root
With root you can achieve ignoring the allowbackup, I believe you could do this with xposed
I also just use root apps like Swift Backup to backup everything on my device