Related
Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.
I own a rooted Asus Transformer Prime TF201 table with JB 4.1.1 (original), and have probably done something stupid... please help this Noob, as I've read so much when looking for answers the last 2 days -- now I'm thoroughly confused! (To tell the truth, wasn't that great of a root user before...)
My tablet won't get beyond "Launcher has stopped" error when booting.
I rooted several months ago, installed a custom bootloader graphic (still works), SuperSU, ROM Manager and some other rooted apps. I had flashed cyanogen rom "9" (I think) -- the stable one for Asus -- and was running fine. I thought I had done a nandroid backup (file on SD card).
Then I created my problem: I had messed around with the LED settings via ROM Manager, and then I think I changed the build.prop file value for VM heap stack from 256 to 512 ("governor" settings?). (I know, I know -- used to mess around a little with PCs and I should have known better what I was doing!)
Now I can't get homescreens or launch apps, or anything. "Launcher has stopped"
I can power off and power on (using power + volume buttons). My custom bootloader image comes into view after the ASUS logo -- but next I get the "Asus Keyboard is not installed" message with the "Unfortunately, Launcher has stopped" message on top of that. Pressing the OK buttom just blinks and back to the errors.
I *can* get get to the settings, though.
Is a new tablet in my future?
Can anyone help me undo this mess I've made?? Help for the Noobs! Oh, and THANK YOU in advance for the trouble!
Hey!
Can you access the recovery mode? If yes:
1. Download the zip file attached to this post;
2. Put the holo.zip file in your sdcard;
3. Enter in recovery mode and flash the zip;
4. Reboot system;
5. Now you get Holo Launcher in your tablet!
Can't See Asus tablet from PC
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Ellie92 said:
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Click to expand...
Click to collapse
Sorry, I didn't see your post before.
Why don't you flash the ROM again?
I mean the custom one.
Sent from my mind using super powers.
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
Hi folks, first up, apologies for starting a new thread, but i am completely lost and couldn't find any solution online and wasn't sure which thread to post this in. So here is my situation
So, i upgraded my mediapad x1 to 7D-501u a week ago, and it was working well. While on it, i rooted it and did the following tweaks
1. to install google apps i did the tweak at the following link http://forum.xda-developers.com/showthread.php?t=2757537 (which is 1. Go to the following folder 2. / cust / channel / charm_china_u / xml / 3. You will find the file UNSTALL_APK.XML 4. Rename it to : UNSTALL_APK.XML.OLD)
2. I changed the DPI to 400 by changing build.prop
Then, i wanted to give the phone to my sister and did a full factory reset (without undoing the changes above). Now, none of the keyboards work after the reboot, (Huwaei keyboard is all messed up resolution wise, if i choose any of the other keyboards they FC). I tried reinstalling the rom itself, but it give me an error saying unable to mount update.app
Any ideas on how to proceed? I am stuck right now.
Install https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
this keyboard usually works on all dpi settings.
ashish1607 said:
Install https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
this keyboard usually works on all dpi settings.
Click to expand...
Click to collapse
Hi Ashish, thanks for that, but currently i am unable to type anything on the phone that has been factory reset, so i havent been able to setup my google id, havent been able to download anything in the play store etc. I was just wondering if there was a way to overcome that problem of the update.app not being mounted.
When i try to update, it gives me a message saying update file found, but cannot mount update.app
Hi,
Try to connect your x1 to your PC with Hisuite software installed on your PC. If your x1 can connect with Hisuite, you can then reflash your firmware again (I hope).
boysha8 said:
Hi Ashish, thanks for that, but currently i am unable to type anything on the phone that has been factory reset, so i havent been able to setup my google id, havent been able to download anything in the play store etc. I was just wondering if there was a way to overcome that problem of the update.app not being mounted.
When i try to update, it gives me a message saying update file found, but cannot mount update.app
Click to expand...
Click to collapse
Are you trying to reflash the firmware from within the OS? If yes, you are getting the error because you have rooted.
You will need to put update.app into a folder named 'dload' then put the folder at the root directory of your SD card, switch off the phone and force flash.
You can force flash by holding both the vol up and down, and the power on buttons concurrently, when you see the screen lit up, do not release the buttons yet, only let go of them when flashing starts.
At the end of the flash, you will / may be asked to removed the SD card (if you were not asked, pull the card out when the phone reboots, else it will attempt to flash again).
bthoven said:
Hi,
Try to connect your x1 to your PC with Hisuite software installed on your PC. If your x1 can connect with Hisuite, you can then reflash your firmware again (I hope).
Click to expand...
Click to collapse
Thanks a lot. I managed to install a new keyboard and adjust the resolution and stuff. But i am now not able to upgrade or install a different rom version. Once it enters recovery mode i keep getting this same message below.
ERROR:update_package_exist, /sdcard/dload/update.app not mounted
i tried updating using the sd card, i tried using the hisuite software etc. I undid the unstall_apk xml thing, and changed the resolution back, but still no luck. Any pointers will help
boysha8 said:
Thanks a lot. I managed to install a new keyboard and adjust the resolution and stuff. But i am now not able to upgrade or install a different rom version. Once it enters recovery mode i keep getting this same message below.
ERROR:update_package_exist, /sdcard/dload/update.app not mounted
i tried updating using the sd card, i tried using the hisuite software etc. I undid the unstall_apk xml thing, and changed the resolution back, but still no luck. Any pointers will help
Click to expand...
Click to collapse
Please Format your SD card as NTFS.AT unzip your ROM from Huawei website.(B010 version recommaded).and gointo systemupdate and selcet local
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.