Related
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.
Hello, Sony xzperia 1 users.
I'm writing this because I have something really urgent to do.
xperia 1 ii dual shim product.
Unable to modify build.prop
Sony has blocked it, or it's blocked.
Unable to open the Qualcomm diag port.
eFS Explorer is not accessible
So, in the countries that haven't released this product,
Volte is not available.
Sony users!:crying:
Help me.
adb shell
su
Set setprop sys.usb.config rndis,eng_mode,adb.
Applied to Xperia 1.
The command above is not possible.
If you help me, I'll make it up to you.
htcmage said:
Hello, Sony xzperia 1 users.
I'm writing this because I have something really urgent to do.
xperia 1 ii dual shim product.
Unable to modify build.prop
Sony has blocked it, or it's blocked.
Unable to open the Qualcomm diag port.
eFS Explorer is not accessible
So, in the countries that haven't released this product,
Volte is not available.
Sony users!:crying:
Help me.
adb shell
su
Set setprop sys.usb.config rndis,eng_mode,adb.
Applied to Xperia 1.
The command above is not possible.
If you help me, I'll make it up to you.
Click to expand...
Click to collapse
Sony has disabled DIAG access so the ADB command doesn't do anything.
Are you trying to load a Custom MBN file to enable VoLTE?
MeltdownSpectre said:
Sony has disabled DIAG access so the ADB command doesn't do anything.
Are you trying to load a Custom MBN file to enable VoLTE?
Click to expand...
Click to collapse
Yes, unlike xperia 1, this command is not possible in xperia1 ii
*#*#86583#* #*
Or
*#*#869434#*#*
doesn't work for you?
htcmage said:
Yes, unlike xperia 1, this command is not possible in xperia1 ii
Click to expand...
Click to collapse
Even if you got DIAG access, loading an MBN file wouldn't work unless it was signed for the Xperia 1 Mk II platform.
If the Xperia 1 Mk II is not sold in your region and there is no MBN file for your carrier included in the modem, there is no way to get VoLTE support.
MeltdownSpectre said:
Even if you got DIAG access, loading an MBN file wouldn't work unless it was signed for the Xperia 1 Mk II platform.
If the Xperia 1 Mk II is not sold in your region and there is no MBN file for your carrier included in the modem, there is no way to get VoLTE support.
Click to expand...
Click to collapse
If only the diag command is known, I can directly put a more powerful volte profile than mbn in the Qualcomm eFS Explorer. That way, Koreans are now using Xperia 1,5. I will share the way if I know the diag open command
TrustAugustus said:
*#*#86583#* #*
Or
*#*#869434#*#*
doesn't work for you?
Click to expand...
Click to collapse
Isn't that a volte activation command for Chinese products like Xiaomi? xperia is not able to do that, I am looking for the adb command to enable the Qualcomm diag port
htcmage said:
If only the diag command is known, I can directly put a more powerful volte profile than mbn in the Qualcomm eFS Explorer. That way, Koreans are now using Xperia 1,5. I will share the way if I know the diag open command
Click to expand...
Click to collapse
Commands won't be able to do anything. You'll have to create a patched kernel that allows DIAG access on the USB port to allow you to load custom MBN files.
MeltdownSpectre said:
Commands won't be able to do anything. You'll have to create a patched kernel that allows DIAG access on the USB port to allow you to load custom MBN files.
Click to expand...
Click to collapse
Unlike xperia 1&5, Sony (xperia 1 II) blocked the opening order of diag from the kernel itself? Oh, my God. This is driving me crazy.
htcmage said:
Unlike xperia 1&5, Sony (xperia 1 II) blocked the opening order of diag from the kernel itself? Oh, my God. This is driving me crazy.
Click to expand...
Click to collapse
As far as I know, DIAG access is disabled for the first gen Xperia 1 as well.
I was unable to get the phone detected for PDC tool to load custom MBNs.
Only engineering mode was functional through the command you mentioned in your first post and I've been using that since March to change band support through QPST on my first gen Xperia 1.
MeltdownSpectre said:
As far as I know, DIAG access is disabled for the first gen Xperia 1 as well.
I was unable to get the phone detected for PDC tool to load custom MBNs.
Only engineering mode was functional through the command you mentioned in your first post and I've been using that since March to change band support through QPST on my first gen Xperia 1.
Click to expand...
Click to collapse
No I don't have enough English, so the meaning seems to be different. Please refer to the attached picture. The xperia1 is open to the diag port, so you can access qpst efs explorer, but the xperia 1 ii device doesn't have access to the commands.
MeltdownSpectre said:
As far as I know, DIAG access is disabled for the first gen Xperia 1 as well.
I was unable to get the phone detected for PDC tool to load custom MBNs.
Only engineering mode was functional through the command you mentioned in your first post and I've been using that since March to change band support through QPST on my first gen Xperia 1.
Click to expand...
Click to collapse
I know the xperia1 &5 diag port opening command, but it does not apply in xperia1 ii. unlock I'm only one in the world who hasn't come to xperia1ii, so I can't get help anywhere else. I'd like to put a bounty on what these commands are. I'm so sad. Help me.:crying:
MeltdownSpectre said:
As far as I know, DIAG access is disabled for the first gen Xperia 1 as well.
I was unable to get the phone detected for PDC tool to load custom MBNs.
Only engineering mode was functional through the command you mentioned in your first post and I've been using that since March to change band support through QPST on my first gen Xperia 1.
Click to expand...
Click to collapse
I made an xperia1&5 volte possible in Android 10 by using the efs file extracted from xperia1firmware as the first mbn powerlessing method in a country that hasn't been released. If you only know the command to open xperia 1 ii digport, I will help you.
htcmage said:
I made an xperia1&5 volte possible in Android 10 by using the efs file extracted from xperia1firmware as the first mbn powerlessing method in a country that hasn't been released. If you only know the command to open xperia 1 ii digport, I will help you.
Click to expand...
Click to collapse
As mentioned earlier, there is no command to unlock DIAG access.
It's disabled in the kernel, you'll have to rebuild it and make the necessary changes to allow DIAG access.
Sony signs MBN files for each device platform, how did you manage to write custom MBNs on the first gen Xperia 1?
MeltdownSpectre said:
As mentioned earlier, there is no command to unlock DIAG access.
It's disabled in the kernel, you'll have to rebuild it and make the necessary changes to allow DIAG access.
Sony signs MBN files for each device platform, how did you manage to write custom MBNs on the first gen Xperia 1?
Click to expand...
Click to collapse
Need a Qualcomm port Open adb command, not a lock.
htcmage said:
Isn't that a volte activation command for Chinese products like Xiaomi? xperia is not able to do that, I am looking for the adb command to enable the Qualcomm diag port
Click to expand...
Click to collapse
I have script which I used for an old phone but I'm believing similar configuration need to be done for activating diag port, look for example:
Code:
echo 0 > /sys/class/android_usb/android0/enable
echo "0FCE" > /sys/class/android_usb/android0/idVendor
echo "diag" > /sys/class/android_usb/android0/f_diag/clients
echo "smd,tty" > /sys/class/android_usb/android0/f_serial/transports
echo "smd,bam" > /sys/class/android_usb/android0/f_rmnet/transports
echo 5416 > /sys/class/android_usb/android0/idProduct
echo "mtp,adb,serial,diag,rmnet" > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Better idea search in .rc files in ramdisk for idea!
Edit:
One question trought, does xperia 1 have kernel 4.4.xxx by default?
munjeni said:
I have script which I used for an old phone but I'm believing similar configuration need to be done for activating diag port, look for example:
Code:
echo 0 > /sys/class/android_usb/android0/enable
echo "0FCE" > /sys/class/android_usb/android0/idVendor
echo "diag" > /sys/class/android_usb/android0/f_diag/clients
echo "smd,tty" > /sys/class/android_usb/android0/f_serial/transports
echo "smd,bam" > /sys/class/android_usb/android0/f_rmnet/transports
echo 5416 > /sys/class/android_usb/android0/idProduct
echo "mtp,adb,serial,diag,rmnet" > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Better idea search in .rc files in ramdisk for idea!
Edit:
One question trought, does xperia 1 have kernel 4.4.xxx by default?
Click to expand...
Click to collapse
:fingers-crossed:
Thank you so much for the user's answer. The question is, where should I apply that code? If you do that, can you open Qualcomm diag?
I haven't been able to check the kernel version. I think it is the Sony basic kernel.
htcmage said:
:fingers-crossed:
Thank you so much for the user's answer. The question is, where should I apply that code? If you do that, can you open Qualcomm diag?
I haven't been able to check the kernel version. I think it is the Sony basic kernel.
Click to expand...
Click to collapse
Do not use those command on your phone since its soo old, instead decompile your kernel ramdisk and search in .rc script for similar definitions, use it as a reference and to get idea. Yes, I had qcom diag enabled using that file which I have created after I figured it in .rc files inside ramdisk, it was if I'm not wrong for Sony Xperia XZ1 Compact.
Kernel version you can see inside "about phone" in your android setings! My hope you get kernel version and post it here, I need to know that/
@op, use single sim firmwares, you will be good to go.
hello
munjeni said:
Do not use those command on your phone since its soo old, instead decompile your kernel ramdisk and search in .rc script for similar definitions, use it as a reference and to get idea. Yes, I had qcom diag enabled using that file which I have created after I figured it in .rc files inside ramdisk, it was if I'm not wrong for Sony Xperia XZ1 Compact.
Kernel version you can see inside "about phone" in your android setings! My hope you get kernel version and post it here, I need to know that/
Click to expand...
Click to collapse
The user who gave us the big idea! Thank you for your answer. I am checking the script file using the kernel-editable app. But it's hard, too. What should the kernel extract?
To use volte in unreleased countries where Sony has not released the product, unlock and magisk must be used regardless of firmware.
There is no menu to use VOLTE, but you can force it by modifying the build prop. After that, you can open the Qualcomm Diagnostic Port (qpst, EFS Explorer) and replace the EFS file to use VOLTE.
Unlike xperia 1&5, the corresponding adb shell-su (setprop sys.usb.config rndis,eng_mode,adb) does not work on xperia 1 ii. I'm frustrated. Is the build prop USB item wrong? Does anyone know of a command to activate the Qualcomm Diagnostic Port? :crying:
This guide is from: https://www.gizdev.com/repair-imei-snapdragon-device/
WARNING: Changing your IMEI to a value that corresponds to a different handset is a CRIMINAL OFFENCE. Use this guide only to restore your ORIGINAL IMEI where it is overwritten.
This guide CANNOT HELP YOU if your ESN and MEID are blank. If you know these values, you may be able to restore them with the QPST toolkit - use the diag steps in this guide to allow your handset to communicate with the QPST tools.
Background:
It is possible to accidentally wipe your IMEI information - either through a misconfigured ROM/Radio, or through wiping modemst1/2 for whatever reason. Wiping your IMEI ensures that your phone will never connect to an operator network (or ISP), meaning phone calls, text messages, and mobile data are inaccessible.
Good news! All is not lost. The Axon 7 is a Snapdragon device, with two sim slots. This means it falls into the family of devices that are easily fixed.
You will need:
All downloads, apart from LineageOS SuperSU, are also available at the bottom of this post
I have not tested these downloads. You are responsible for their contents. Keep your system up to date and protected.
- The addon/fastboot tools contained within this post. Download here - you may have other tools, but this version is confirmed to be working.
- The "WriteDualIMEI" tool. Download here
- The Qualcomm ADB drivers - you probably already have these installed, but here is a driver anyway. I BEAR NO RESPONSIBILITY FOR THIS DRIVER. Download here
- A rooted device. If you're on LineageOS, use the LineageOS extras here. Remember, the Axon 7 is an ARM64 device.
Process:
- Make sure you have at least your primary IMEI to hand. Copy it into notepad and check it for errors.
- Connect your phone to your PC. Ensure Android Debugging is enabled.
- Open the folder in which you extracted the ADB toolkit. On Windows, shift+rightclick, and select "Open Cmd Here"
- Type the following into the opened command prompt. Take note of the .exe - this ensures we use the ADB executable in the folder, and not the one in your $PATH.
Code:
adb.exe shell
su
setprop sys.usb.config diag,adb
Note also that between diag and adb exists a comma, not a period
- Now is the time, if you have not already done so, to install the Qualcomm driver.
- Open device manager, and ensure that you have, under COM ports, a ZTE device in Diag mode.
- Open the WriteDualIMEI application and make sure that the COM entry matches what you have in Device Manager. If it is blank, something has gone wrong and you should start again - including disconnecting and reconnecting your phone.
- Copy and paste the IMEI numbers you wrote down earlier into the IMEI1 and IMEI2 fields respectively.
- Click "Start". The process shoudl take no more than a millisecond. Success is delineated by a green square on the right hand side fo the window, with "PASS" in black font in the centre.
- Restart your handset. Check your IMEI values by visiting settings, or entering *#06# in the dialler.
RMX3363
How can i erase imei fastboot way?
Bootloader is unlocked & phone is rooted.
Do you know if this method is applicable for Asus Zenfone 8 Flip which has
Qualcomm SM8350 Snapdragon 888 5G?
I tested it on my mi note 10 pro, everything went well and at the end I got green PASS. But the imei number was not updated after the restart.
So didn't worked for me
At first, thank you for the great work, you did most of it and I only would like to add a small but necessary thing at the end. I could see most persons here couldn't make this work on their devices. I was one of them for the first few hours but then it struck me and I solved it. I am penning down the process as much in detail as possible as to where it went wrong for most of us and of course the fix:
In the adb shell after you put the command - setprop sys.usb.config diag,adb, ideally a ZTE device in Diag mode should have appeared under COM Ports in windows Device Manager. But, for most of us it was an unknown android device with an yellow exclamation showing something is wrong with the driver. Windows wouldn't update the driver and it is not available from the internet i.e., not easily. And hence without the driver the connection failed every time.
The Fix: Download Snappy Driver Updater for windows. I am running windows 11 Pro and it worked fine with mine, so I am guessing it would work fine for everyone. After you've downloaded it, run the updater after you have given all commands through the adb shell i.e, setprop sys.usb.config diag,adb and now scan through Snappy. If your device is uptodate in all other areas, snappy will find the missing driver which is causing the yellow exclamation android entry, and install it in a few minutes. After that just follow the above guide. It should be a success. The IMEI would be written and every functionality would be restored. I could verify the same on my ZTE Blade S7. Worked like a charm. Thank you again. All the best
Is there anyway to get Snapchat to work on these phones? I know there has to be android version 4.4. I think i have 4.3 in my Sony Xperia V. I also know there is a problem with snapchat locking rooted devices so this can be a problem. Is there any official releases that can handle snapchat?
I have Windows 8.1 does it works the same? https://forum.xda-developers.com/t/...y-xperia-s-stock-to-android-8-1-oreo.4222141/
I think i go for Android 7.1.2/nAOSP instead of Oreo. Something tells me Oreo will gets to laggy.
I got to: Seems like me phone is Desimlocked. How to easy lock it up. It stand 5 after all, i guess 5 attemps
5) MAKE SURE PHONE IS NOT SIMLOCKED
We need to check phone is not SIMlocked.
Open dialer, enter code again
Code:
*#*#7378423#*#*
Go to Service info > SIM lock. If everything is blank/unchecked ( [] ), phone is Desimlocked.
If not, you must contact your network provider for an unlock code.
### Don't move further until phone is simlocked. You cannot debrand/desimlock it using a custom ROM.
Should i copy the Android 7.1.2/nAOSP rar to the flash folder?
In Windows, copy the path to the "flash" folder you unziped earlier.
Open a Windows command prompt : Start menu > Command prompt > Start as administrator
Then type
What to type cd /d thePathToFlashFolder should cd be the moved files to d? destination?
I guess even if i get it to work snapchat will detect my rooted phone?
I have it like this C:\root\djibe\flash what path should i move to this folder the oreo 8.1?
Oldschool297 said:
I guess even if i get it to work snapchat will detect my rooted phone?
Click to expand...
Click to collapse
Correct.
Snapchat is performing a few tests and if at least one of them is positive, the application kills itself when Superuser is found in the system.
I know some xposed modules can prevent that. I guess you cannot root the phone and install custom rom and then unroot?
Oldschool297 said:
I know some xposed modules can prevent that.
Click to expand...
Click to collapse
Great you know this.
IMO it's a widespread misconception that a rooted Android can be hidden to apps: don't think the developers of banking / payment / other apps are dumber than then people who root their device's Android, this due to fact that all rooting methods ( e.g. SuperSu, MagiskSU, KernelSU, MTK-SU ) are based on open-source-code which everybody can look into to find out how Android gets rooted, i.e. where to search in filessystem for the SU-binary.
Thanks, so it is very hard to use snapchat on rooted phones? I need that so then a custom rom can't be so good for me. Official releases can be installed without rooting?
FYI:
Latest Snapchat v12.32.0.35 ( April 26, 2023 ) only runs on Android 5.0 and up.