Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell
And then type (for some reason if you combine the two commands it doesn't work):
settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.
MishaalRahman said:
Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.
Click to expand...
Click to collapse
It's also in the cust folder in the local.prop file you can change it to true to have the icon show 4GLTE.
ajsmsg78 said:
It's also in the cust folder in the local.prop file you can change it to true to have the icon show 4GLTE.
Click to expand...
Click to collapse
That requires root access doesn't it? This method doesn't.
Hey there thanks again! But when I try to enter your input I get /system/bin/sh: 220: not found and when I enter just adb shell settings get system hw_show_lte it shows 260.
hmm what could be the issue
Coolyou said:
Hey there thanks again! But when I try to enter your input I get /system/bin/sh: 220: not found and when I enter just adb shell settings get system hw_show_lte it shows 260.
hmm what could be the issue
Click to expand...
Click to collapse
Sorry, it's been awhile since I did this. Let me double check the syntax.
Edit: I double checked my syntax, and it is correct. Please double check you are entering it exactly as I wrote.
MishaalRahman said:
Sorry, it's been awhile since I did this. Let me double check the syntax.
Edit: I double checked my syntax, and it is correct. Please double check you are entering it exactly as I wrote.
Click to expand...
Click to collapse
I tried several times and also copied your text without any space here is the output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very interesting. For some reason when you combine "adb shell" and "settings put system hw_show_lte" it doesn't work. Do this instead and it will work:
Type
adb shell
to enter the shell. Then type
settings put system hw_show_lte "260;310"
This should work. I edited my OP to reflect this change.
MishaalRahman said:
Very interesting. For some reason when you combine "adb shell" and "settings put system hw_show_lte" it doesn't work. Do this instead and it will work:
Type
adb shell
to enter the shell. Then type
settings put system hw_show_lte "260;310"
This should work. I edited my OP to reflect this change.
Click to expand...
Click to collapse
it seems like it worked now, no errors shown, I restarted my phone but however still no 4G icon as shown below:
This change doesn't add a 4g LTE icon to the quick tiles. It adds the icon to the status bar.
MishaalRahman said:
This change doesn't add a 4g LTE icon to the quick tiles. It adds the icon to the status bar.
Click to expand...
Click to collapse
Oh, you misunderstood me then. Sorry for troubling you all the way. I was talking about that icon in notifications tile how you called it. I unlocked my phone from c66 to c432 on c66 I had it, now on c432 it's non-existant.
Oooo...will give this a try and get back to you. I am in US on AT&T network...I thought I would get LTE by default, but only showing 4G. I have the L29C185B138 international version...
MishaalRahman said:
Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell
And then type (for some reason if you combine the two commands it doesn't work):
settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.
Click to expand...
Click to collapse
Thank you!!! Worked like a charm!! I'm on AT&T and now I can see LTE instead of 4G in my status bar!! Great find!
I don't get people 4G and LTE is the same thing just different names.
albertobom said:
I don't get people 4G and LTE is the same thing just different names.
Click to expand...
Click to collapse
Agreed! But when you're used to seeing 'LTE' instead of '4G', it helps that there's a way to bring it back... [emoji12] [emoji12]
Sent from my MHA-L29 using Tapatalk
baddison said:
Agreed! But when you're used to seeing 'LTE' instead of '4G', it helps that there's a way to bring it back... [emoji12] [emoji12]
Click to expand...
Click to collapse
I know just teasing you guys.
baddison said:
Thank you!!! Worked like a charm!! I'm on AT&T and now I can see LTE instead of 4G in my status bar!! Great find!
Click to expand...
Click to collapse
Glad it worked for you. This trick makes 0 difference in functionality, but for some people the lack of an LTE icon is jarring.
When I run "adb shell settings get system hw_show_lte" I just got the answer "null".
Is it save to continue and run the next command? In my case will be something like:
settings put system hw_show_lte "226"
dancrow said:
When I run "adb shell settings get system hw_show_lte" I just got the answer "null".
Is it save to continue and run the next command? In my case will be something like:
settings put system hw_show_lte "226"
Click to expand...
Click to collapse
Yes, be all good . Im using c636 got null , then change to 302 and 310
How does it work with the MHA-L29C432B182?
MishaalRahman said:
Glad it worked for you. This trick makes 0 difference in functionality, but for some people the lack of an LTE icon is jarring.
Click to expand...
Click to collapse
Hey Mishaal I sent you a PM but I don't think you are reading those so I'll ask here
I spoke with your about LTE shell and I'm aware that you are very good with adb shell commands. So wanted to ask is it possible to change this option without rooting with adb shell?
The correct path is /system/emui/lite/prop/local.prop and you have to set ro.build.hw_emui_lite.enable=false
I tried with adb shell settings put system hw_emui_lite false via cmd but it doesn't work :/ If someone has experience with ADB write here
EDIT 1: adb shell settings put system hw_emui_lite.enable false - doesn't wor
Related
hello everyone, I'm new to the forum as I can not post in the area of development so I decided to post here ... when I started the rom arbayong of guy saw that the wi-fi did not work, there started looking on the internet and found the error and remediation for him ... follow the tutorial below ...
One. Enter the settings menu of Android
2nd. Settings Wireless and network
3rd. WiFi Settings
4th. Connect the antenna desired (or publishing house)
5th. Will show the famous message (Getting IP address) only if it's because they do not think well ever ...
6th. Now click on the Menu android (which is one of the triangle on the top bar)
7th. Click the "Advanced"
Eight. Select Fixed IP
9th. Now enter IP, Gateway, and DNS Maskara.
10. Go back and try to navigate if the addresses are correct your internet browsing will normally
Tip you can test the addresses below:
configuration 1
IP 192.168.1.150
Gateway 192.168.1.1
mask 255.255.255.0
DNS1 8.8.4.4
8.8.8.8 DNS2
configuration 2
IP 192.168.0.150
Gateway 192.168.0.1
mask 255.255.255.0
DNS 8.8.4.4
configuration 3
IP 192.168.2.150
Gateway 192.168.2.1
mask 255.255.255.0
DNS 8.8.4.4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got here and I'm with the upgrade 1.1 and wi-fi is working 100%
I have helped ..
hug
Good work bro.. I will let them know about your thread in dev thread.. nice find..
Sent from the MUST have app!
Thanks for confirming this work around works.
I could not test this procedure 2 days ago myself as I had no wifi. Can you change "fixed ip" ip to "static ip" and (DNS maskara" to "dns mask"? The are more correct terms
Sent from my GT-B5512 using Tapatalk 2
Its this working?
Sent from my GT-S5360 using xda premium
salvaje0886 said:
Its this working?
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Why not try as it will never harm your phone?
Sent from my GT-B5512 using Tapatalk 2
arbayong said:
Thanks for confirming this work around works.
I could not test this procedure 2 days ago myself as I had no wifi. Can you change "fixed ip" ip to "static ip" and (DNS maskara" to "dns mask"? The are more correct terms
Sent from my GT-B5512 using Tapatalk 2
Click to expand...
Click to collapse
sorry, is that I have a few posts then I'm secure in what I can do, I can not even edit my topic ... but do what patience ... sorry for the english, I'm from Brazil ...
I can confirm that this solution with static address does work but it make no sense for people who uses many Wi-Fi networks.
I've made some research after googling around and the reason being is permission problem. I'm not Linux guru and ask people and ROM makers to please correct me.
The error is the following
Code:
Error dhcpcd 1082 /system/etc/dhcpcd/dhcpcd-run-hooks: Permission denied
I've set permissions to this file to allow execute and write. I know it's a bit to much and additional test needs to be done to find out what exact permissions should be set. But it worked for me!! I was able to connect to wi-fi network at work. Will test it again at home.
Hope it helps someone.
myafik said:
I can confirm that this solution with static address does work but it make no sense for people who uses many Wi-Fi networks.
I've made some research after googling around and the reason being is permission problem. I'm not Linux guru and ask people and ROM makers to please correct me.
The error is the following
Code:
Error dhcpcd 1082 /system/etc/dhcpcd/dhcpcd-run-hooks: Permission denied
I've set permissions to this file to allow execute and write. I know it's a bit to much and additional test needs to be done to find out what exact permissions should be set. But it worked for me!! I was able to connect to wi-fi network at work. Will test it again at home.
Hope it helps someone.
Click to expand...
Click to collapse
permissions for that file are r-xr-x--- in mine which is working fine in my rom.. which is 550 if you want to add it in updater-script
myafik said:
I can confirm that this solution with static address does work but it make no sense for people who uses many Wi-Fi networks.
I've made some research after googling around and the reason being is permission problem. I'm not Linux guru and ask people and ROM makers to please correct me.
The error is the following
Code:
Error dhcpcd 1082 /system/etc/dhcpcd/dhcpcd-run-hooks: Permission denied
I've set permissions to this file to allow execute and write. I know it's a bit to much and additional test needs to be done to find out what exact permissions should be set. But it worked for me!! I was able to connect to wi-fi network at work. Will test it again at home.
Hope it helps someone.
Click to expand...
Click to collapse
Thanks man. U saved the day. Will test it and make a fix in an hour or two. Unpardonable that I did not notice it was perm issue.
Sent from my GT-B5512 using Tapatalk 2
I confirm that this method fixes problem. Since this thread arose from use of hatyon rom 1.1, I will assume you are using it. Here is how to go about it:
Method 1
Code:
1. Open terminal
2. Type 'su' without quotes and hit enter
3. Type 'chmod 755 /system/etc/dhcpcd/dhcp-run-hooks' without the quotes and hit enter on keyboard
4. Type 'exit' + enter key
5. Repeat step 4 to exit terminal
6. If wifi is on, turn it off and on again
7. It should work. Remember to type command as you see it here
8. Report here or hatonrom thread if works or not
Method 2
Code:
1. Open root file explorer/browser
2. Browse to /system/etc/dhcpcd
3. Long press on the file 'dhcpcd-run-hooks'
4. Scroll down to and select permissions.
5. Give owner 'rwx' permissions and also give group and others 'r-x' and exit app. See attached screenies.
6. Same as 6 in method 1
SCREENIES
see attached screenies in their correct order.
NB: in the screennies i gave all three users 'rwx' permissions. i recommend you untick the 'w' permission for 'group' and 'other'
Sent from my GT-B5512 using Tapatalk 2
arbayong said:
I confirm that this method fixes problem. Since this thread arose from use of hatyon rom 1.1, I will assume you are using it. Here is how to go about it:
Method 1
Code:
1. Open terminal
2. Type 'su' without quotes and hit enter
3. Type 'chmod 755 /system/etc/dhcpcd/dhcp-run-hooks' without the quotes and hit enter on keyboard
4. Type 'exit' + enter key
5. Repeat step 4 to exit terminal
6. If wifi is on, turn it off and on again
7. It should work. Remember to type command as you see it here
8. Report here or hatonrom thread if works or not
Method 2
Code:
1. Open root file explorer/browser
2. Browse to /system/etc/dhcpcd
3. Long press on the file 'dhcpcd-run-hooks'
4. Scroll down to and select permissions.
5. Give owner 'rwx' permissions and also give group and others 'r-x' and exit app. See attached screenies.
6. Same as 6 in method 1
SCREENIES
see attached screenies in their correct order.
NB: in the screennies i gave all three users 'rwx' permissions. i recommend you untick the 'w' permission for 'group' and 'other'
Sent from my GT-B5512 using Tapatalk 2
Click to expand...
Click to collapse
Well done Mate.
The first one does work.
+1 from me for the fix
Well, for the convenience of other users, can you release a zip update for it?
anyways, its your call.
In mu phone change permission is not suceesful.
Sent from my GT-B5512 using Tapatalk 2
Darshan Modi said:
In mu phone change permission is not suceesful.
Sent from my GT-B5512 using Tapatalk 2
Click to expand...
Click to collapse
what do you mean? you can't change permission or you mean after changing permissions, wifi still did not work?
i hope you are not on stock unrooted rom.
@Modi, if after successfully changing permissions wifi is not fixed, then give us logcat. look at Nitubhaskar's signature for his latest thread as it has instructions on how to take logcat.
@Smartxtreme. will try making update.zip tomorrow. i though it was much easier to just change the permissions manually instead of going into cwm recovery, flashing and rebooting.
op should mark the thread as solved.
arbayong said:
op sure mark the thread as solved.
Click to expand...
Click to collapse
it wasnt a question thread to begin with.. so solved is inappropriate... [solution] would be more proper i feel
nitubhaskar said:
it wasnt a question thread to begin with.. so solved is inappropriate... [solution] would be more proper i feel
Click to expand...
Click to collapse
i get your point Nitu. op should use correct tag as you suggested. seems you are addicted to the forum and can't even stay away for a day to concentrate on your exam. did i say good luck in your exams?
arbayong said:
i get your point Nitu. op should use correct tag as you suggested. seems you are addicted to the forum and can't even stay away for a day to concentrate on your exam. did i say good luck in your exams?
Click to expand...
Click to collapse
Ya you did.. thanks..
Yup.. checking xda every half an hour is bad habit...
Or you could say addiction.. I don't want to though
**Nothing is True... Everything is Permitted**
Muffins.. muffins everywhere!
help on wifi fix for Samsung Galaxy Y pro duos b5512
i tried using the methods that were posted here http://forum.xda-developers.com/showpost.php?p=34105560&postcount=10
the first method didnt work because the terminal force closes.
i did the second method and ticked the right boxes that were indicated and pressed apply. i turned wifi on and off and on but it still cant connect.
when i checked the permissions for dhcpcd-run-hooks it went back to its original like this
are there more methods? or can you send me a working terminal so i can try method 1
im using hatyonrom 1.1 and my phone is rooted
arbayong said:
I confirm that this method fixes problem. Since this thread arose from use of hatyon rom 1.1, I will assume you are using it. Here is how to go about it:
Method 1
Code:
1. Open terminal
2. Type 'su' without quotes and hit enter
3. Type 'chmod 755 /system/etc/dhcpcd/dhcp-run-hooks' without the quotes and hit enter on keyboard
4. Type 'exit' + enter key
5. Repeat step 4 to exit terminal
6. If wifi is on, turn it off and on again
7. It should work. Remember to type command as you see it here
8. Report here or hatonrom thread if works or not
Method 2
Code:
1. Open root file explorer/browser
2. Browse to /system/etc/dhcpcd
3. Long press on the file 'dhcpcd-run-hooks'
4. Scroll down to and select permissions.
5. Give owner 'rwx' permissions and also give group and others 'r-x' and exit app. See attached screenies.
6. Same as 6 in method 1
SCREENIES
see attached screenies in their correct order.
NB: in the screennies i gave all three users 'rwx' permissions. i recommend you untick the 'w' permission for 'group' and 'other'
Sent from my GT-B5512 using Tapatalk 2
Click to expand...
Click to collapse
hello arbayong
i have a little problem,i did all steps for the rom exactly as you say but when i reached the point to fix the wi-fi for 1.1 my phone didn't have root permission and1) the terminal app crashes 2)the file explorer doesn't contain any /system.is there any way to fix it?or is it possible to go back to hayton 1 version?
thanks for your understanding
wankel13 said:
hello arbayong
i have a little problem,i did all steps for the rom exactly as you say but when i reached the point to fix the wi-fi for 1.1 my phone didn't have root permission and1) the terminal app crashes 2)the file explorer doesn't contain any /system.is there any way to fix it?or is it possible to go back to hayton 1 version?
thanks for your understanding
Click to expand...
Click to collapse
you did not follow my instructions well so go back and read at least the first three posts in Hatyon rom thread and you should get your problem solved as i have explained how to get root access via file explorer there (seee the additional instructions part). the rom is rooted. you just have to tell superuser.apk which apps should be given root previledge. on the issue of terminal app, you can install your own from android market.
when you encounter a problem, the first thing you should do is to ask yourself if you have followed all tips well.
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]
[SIZE=+2]Specific to[/SIZE]
[AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
Click link here>> http://forum.xda-developers.com/showthread.php?t=2502789 <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP
Please use this thread to assist each other and help provide useful tips and tricks you have implemented to modify and suite PA 4.4+ to your needs. Please, be polite, courteous, and helpful.
Finally, if you have a useful link, PM it to me and I can try to consolidate anything that will help others in the OP here for easy finding.
ParanoidAndroid Website and changelogs
ParanoidAndroid Github
Official TWRP Recoveries: Download here and select your model in the top right dropdown
D802 is somehow missing from their webpage. Broken link on page or some other error, here it is: Download
KK basebands/modems: thanks to @Cloudyfa for this nicely Consolidated download list.
http://www.androidfilehost.com/?w=files&flid=12880
Troubleshooting and Pulling LogCats
For anyone who isn't really comfortable pulling dmsg or last_kmsg logs from their phones needs to download and use this app: SysLog
https://play.google.com/store/apps/details?id=com.tortel.syslog
One button click and it will pull 4 logs for you and zip them all up in one small package:
dmsg
last_kmsg
logcat
Modem log
You can then get that to the dev to go through and look for errors.
Known issues for each variant:
Reported Issues:
All Variants:
- All games should be working fine, even touch based games
D800:
-
D801:
D802:
D803:
LS980 & VS980
- a few report issues with in-call volume (echo bug fixed)
Links:
Gravity Box 2.7.5
Xposed Beta for 4.4
LG Camera
For USB/OTG, try root Stickmount @Alex0901 pointed to this app from Chainfire
Screen Off App - If you're missing the knock off functionality, @bhc112 highlighted this app
Quick Remote IR Blaster - Thanks @sefnap
Signature Banner can be downloaded here:
https://db.tt/yM8N3UfQ
Bootanimation Attachments Below: (If you have any to add, send them to me and I'll include them)
- The one I made, Houston converted to a flashable zip so no need to push to system / media, just flash in recovery: Here's a video so you can see it first: http://youtu.be/DBbYnDLRauI
[Q&AT] - [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
FAQ's....coming soon!
I need some time (after work) to try to review the most common and recent issues/resolutions. Stay tuned, thanks for your patience!
[Q&AT] - [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2
Judgment Passed....
The Xposed link isn't working
Link Xposed
D801: wireless display isn't working. The WiFi module seems to flip out half way through the connection process.
crazy talk said:
D801: wireless display isn't working. The WiFi module seems to flip out half way through the connection process.
Click to expand...
Click to collapse
try to collect logcat and post it in the dev thread please
D800
- Dialer screen wont tag on instantly when removing from face during call (ie dialed into Voicemail, and moved phone away to bring up dialer to delete message)
I am now getting an issue with WiFi saint "failed to connect to network". It was working fine earlier.
Sent from my LG-G2 using Tapatalk
BlackHoleSlam said:
I am now getting an issue with WiFi saint "failed to connect to network". It was working fine earlier.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.
Jank4AU said:
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.
Click to expand...
Click to collapse
What I am seeing is the MAC address is getting changed every reboot. I have verified this. This may be causing other issues as well with Wifi related modules.
I wonder if this would work?
http://forum.xda-developers.com/show....php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Jank4AU said:
What have you done to try to fix? Have you reset your router at all? Are there any other networks you can try to connect to in order to rule out some issues? Are you still able to get Network Data if you turn off wifi? We need more info when you post these issues in order to help you.
Click to expand...
Click to collapse
I have forgot the connection reconnected to the ssid. No change has taken place WiFi seems borked now. Will try a restart. Network data is working fine.
Sent from my LG-G2 using Tapatalk
sublimejosh2000 said:
What I am seeing is the MAC address is getting changed every reboot. I have verified this. This may be causing other issues as well with Wifi related modules.
I wonder if this would work?
http://forum.xda-developers.com/show....php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
What model G2 do you have? I'll throw this in the OP until resolved
BlackHoleSlam said:
I have forgot the connection reconnected to the ssid. No change has taken place WiFi seems borked now. Will try a restart. Network data is working fine.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
Update: WiFi is back after rebooting.
Sent from my LG-G2 using Tapatalk
Jank4AU said:
What model G2 do you have? I'll throw this in the OP until resolved
Click to expand...
Click to collapse
It is D800 AT&T. I remember Nexus 4 having a similar issue. The link I posted was a fix for that. I doubt I will get my Origional MAC back, but I did backup my EFS. So, once a fix is in place, I should be able to restore.
Oh, Thank Goodness for Reserved MAC address in my router, I was able to get my old MAC from there. So, if need be, I can change it back.
D800 mute not functioning?
Hi, thanks to everyone involved in developing this custom ROM. It generally works really well.
I wondered if someone that has an AT&T G2 and has the ROM installed could verify whether the phone mute works?
It currently highlights and acts as if it works, but doesn't actually mute the microphone.
Thanks!
AT&T D800 - GPS not working either...
Couldn't get a location in Google Maps.
sublimejosh2000 said:
Couldn't get a location in Google Maps.
Click to expand...
Click to collapse
FWIW, I'm able to get one without a problem.
Since I have no desire to clog the enormous Dev thread, I will ask here:
Anyone know if there will be any plans to port this work over to CM11?
sublimejosh2000 said:
Couldn't get a location in Google Maps.
Click to expand...
Click to collapse
Mine is flawless...I had this one time on an earlier build. Flashed back to a stock nandroid, got GPS lock, then reflashed the ROM with clean install. Been perfect, accurate and fast since.
dawkpaul said:
Hi, thanks to everyone involved in developing this custom ROM. It generally works really well.
I wondered if someone that has an AT&T G2 and has the ROM installed could verify whether the phone mute works?
It currently highlights and acts as if it works, but doesn't actually mute the microphone.
Thanks!
Click to expand...
Click to collapse
Mute button works fine for me. Just cussed out a fellow employee who heard none of it and I'm still gainfully employed!
You do everything here at your own risk. I take no responsibility for any broken devices/sdcards/your house going down on fire and everything else.
PLEASE DO NOT MIRROR THESE FILES!
Requirements:
root
ability to use mouse and keyboard
terminal emulator on your phone
What do you get for doing this?
Propably you'll be able to use a lot more bands than before. Most likely your phone will work on every place in the world now.
Check the third post for a link to OPO guide
C6903
before
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after
1. Download this zip Google it as it's banned from xda for the ability of imei change
2. Extract it and install QPST from that zip
3. Open the caller app and type in *#*#8778#*#* (it should go off the screen after you type in the last symbol "*"
3.5 Those on custom roms (tested on cyanogen 11 with s4 mini) can use the efs professional toolkit to change the mode to enable the diag port.(Thanks @blackburn !)
4. Connect your phone to your PC
5. Open ADB console
6. Type in these commands:
Code:
adb shell
su
setprop persist.usb.eng 1
7. Turn off USB Debugging, Disconnect your phone from the PC
8. Wait about 10 seconds (don't have to be exact, just let it all disconnect in the PC) and turn USB Debugging back on
10. Connect it back to the PC. It should try to install drivers. Wait until it fails to install all of them.
11. Open device manager - you will see your device model a few times. Go to details tab. Scroll down a single time on that tab. You will see MI_0x there.
12. Go through those devices until you find MI_04 under the second drop down position.
13. Select "update driver" for this device and install the htc driver from the zip.
14. Press start button and navigate to QPST -> QPST Configuration
15. Go back to device manager -> modems -> HTC
16. Find "COM*" in my case it was "COM3". It might be different for you.
17. In QPST Configuration click on "Add new port" and in "Port" type in your "COM*". In my case It's "COM3" in there. In Port label it could be anyting u want. In my case I used a Z1 so I typed IN "Z1".
18. It should look like this now.
19. Navigate to QPST/bin and open RV_NV_Manager.exe
20. press on settings -> Comport and choose your COM port.
21. Press on file -> read from phone
22. Wait patiently until it is finished. Now pay attention!
23. Go to line 1877, click it and copy the decimal number on the right side of a programme. right click - copy
24. Go to the place where you extracted the zip from the first step and start mzTool
25. On the left side you will see "Input radix" - press decimal there.
26. On the right side you will see "RF BC CONFIG" paste your previously copied number from the RV_NV_Manager.exe there.
27. You will see now what bands are you able to use on the bottom of the app in "Bit information"
28. Switch tab to "Band Preference (NV Value)"
29. In there select all GSM bands and WCDMA bands. This place is really a field of testing. In my case (C6903 LTE) I selected all of GSM and WCDMA. I wouldn't suggest you to do anyting else in here unless you know what your'e doing. Let me know if you got something interesting in there.
30. After you're done choosing what bands do you want - copy decimal number from the bottom right
31. Remove all commas from that number ( "," ) so it would be just a bunch of numbers without anything else.
32. Open RV_NV_Manager.exe from the point you left it (step 23) and paste your new number without commas "," there.
33. Press on write NV and then press on file ->write changed NV to the phone.
34. Open up the terminal emulator on your phone and write there this:
Code:
su
setprop persist.usb.eng 0
35. Reboot the device and hope you'll have the reception. If you do, hooray!
36. Type in *#*#SERVICE#*#* (*#*#7378423#*#*) to see your new bands that your phone can use!
If your phone can't boot then flash stock FTF to your device and you should have your reception back!
Enjoy!
I wanted to mention that I'm just the guy that was interested in this and the person that actually made it possible is @BlackSoulxxx all thanks go to him! He's the guy that did it! Please thank him in the second post!
PLEASE DO NOT ASK ME IF IT WORKS ON YOUR DEVICE! I DON'T KNOW. YOU HAVE TO TRY IT YOURSELF.
If you have any problems or issues here's some help from other users http://forum.xda-developers.com/showpost.php?p=55321344&postcount=3
Tested on: ZU, Z1,SP,Xperia TL,Sharp-DOCOMO Aquos Zeta SH-04F
Dangerous stuff to experiment with. Already lost 2 phone (2 expensive paper-weight with OmniBalance design -_- )
But ENJOY!
And remember to check out *#*#4636*#*# to select band (I dont advice to do that, because to revert it you will have to reflash baseband)
And the setting
@olokos
BlackSoulxxx said:
Hey, for everyone with error "execptionthrow" error pls use QXDM and search for nv 1877 and change it
Click to expand...
Click to collapse
Nexus connection
1. Remove all installed drivers.
2. Install LG United Mobile Driver
3. Enable debugging and install adb driver if it's not automatically installed.
4. Using adb issue the following commands on a separate line
Code:
adb shell
su
setprop sys.usb.config diag, adb
5. Your phone should start installing drivers, once installed under Ports in device manager there should be (* indicates a number):
LGE AndroidNet for Diagnostics Port (COM*)
LGE AndroidNet USB Serial Port (COM*)
Thanks for that @CHAMAVELI !
kevin3688 said:
For GSM HTC Phones.
Use "setprop sys.usb.diag.config diagon" instead of "setprop persist.usb.eng 1"
Click to expand...
Click to collapse
One Plus One guide
Moto Droid RAZR Guide
XIAOMI MI2 Guide
LG G3 D852 Guide
Device-specific drivers and Z2 LTE unlock here:
http://forum.xda-developers.com/showthread.php?p=55394190
LTE Unlock guide based on OPO
http://forum.xda-developers.com/showpost.php?p=56577252&postcount=455
olokos said:
Massive stuff. I'm writing it down right now. wait for it.
Click to expand...
Click to collapse
Haha ok, we all waiting ^^
Send from my XZ With My Own Personal Modified MoonWalker SuperB !
What about this thread,I don't understand. You will open a port or an app thread,right?
Mazellat said:
What about this thread,I don't understand. You will open a port or an app thread,right?
Click to expand...
Click to collapse
Much bigger than that. Look at @BlackSoulxxx signature. I'm almost done writing it all down. Hang tight
Finally did it
olokos said:
Much bigger than that. Look at @BlackSoulxxx signature. I'm almost done writing it all down. Hang tight
Click to expand...
Click to collapse
I don't see anything his sign. and waiting for you
Mazellat said:
I don't see anything his sign. and waiting for you
Click to expand...
Click to collapse
Already did it! Try it by yourself!
I forget to tell you that this can works with UB and LB If you want to unlock for non-Xperia device that power by SD PM me....
Is it also supposed to work on the LTE bands, or just GSM and WCDMA? For instance, would it reveal any 'hidden' LTE bands on LT30AT?
ArtDC said:
Is it also supposed to work on the LTE bands, or just GSM and WCDMA? For instance, would it reveal any 'hidden' LTE bands on LT30AT?
Click to expand...
Click to collapse
Yes, works with GSM/WCDMA/LTE, even with CDMA if you phone supporting them. About hidden band, just give it a try
But if your phone is 3G variant, it will unlock wcdma/gsm band only. Using LTE version, result like OP screenshot
Tempted to try this out but what happens if we mess up something? Just do a nandroid and everything is fine?
Ahki767 said:
Tempted to try this out but what happens if we mess up something? Just do a nandroid and everything is fine?
Click to expand...
Click to collapse
Reflash baseband from full ftf
BlackSoulxxx said:
Reflash baseband from full ftf
Click to expand...
Click to collapse
When i disconnect and reconnect, it just worked normally without trying to install drivers
Ahki767 said:
When i disconnect and reconnect, it just worked normally without trying to install drivers
Click to expand...
Click to collapse
Repeat the step
1. Dial *#*#8778#*#*
2. open adb
adb shell
su
setprop persist.usb.eng 1
Click to expand...
Click to collapse
3. turnoff usb debugging and unplug the phone
4. wait 10s, turn on usb debug and connect it again to pc
1. Dial *#*#8778#*#* ---> I try several times and will not turn off
erick_shadow said:
1. Dial *#*#8778#*#* ---> I try several times and will not turn off
Click to expand...
Click to collapse
When you dial it, it will dissappear right? If so, that's ok. Stay on the guide and olokos guide have some place wrong, I have correct it in #2 post
the mark is left on the keyboard and does nothing
How to get into Diag mode:
1) open dialer
2) enter: *#*#717717#*#*
3) you'll see a toast "diag mode enabled"
To disable diag-mode enter the same code again.
How to install drivers in Windows:
1) download and extract xiaomi_mi2_diag_driver.zip
2) after you've connected your phone in diag mode you'll see very much devices
3) choose custom source to search for driver and select the extracted folder.
4) only 3 of the devices will install it doesn't matter we don't need the others.
How to configure QPST:
1) open QPST configuration from start menu
2) on tab "ports" click on "Add new Port"
3) you should see two qualcom ports in the list. choose one and click OK.
4) if displayed phone name is SURF9615, you've selected the correct one. otherwise add the second device, too
But why?
Hello M1cha,
I'm sorry if this is obvious but what exactly can I use this for
Is it changing my IMEI?
And if so, why would I want to change it?
Again, I'm sorry if the answer is obvious and I'm just asking a stupid question.
Unrelated question:
Do you know if Xiaomi.eu will really shut down or not? I can't seem to get straight answers on the Q&A forum
Redme Note LTE TD
Hello
I used your guide and http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
to unlock the WCDMA frequencies on my Redmi NOTE LTE TD ... bought in china .... everything OK ... but the phone works on GPRS ... I have also tried using the menu * # * # 4636 # * # * .. but nothing ..
do you have same idea ??
thank you !
Gobbenobber said:
Hello M1cha,
I'm sorry if this is obvious but what exactly can I use this for
Is it changing my IMEI?
And if so, why would I want to change it?
Again, I'm sorry if the answer is obvious and I'm just asking a stupid question.
Unrelated question:
Do you know if Xiaomi.eu will really shut down or not? I can't seem to get straight answers on the Q&A forum
Click to expand...
Click to collapse
On mi2 u can't change the IMEI because it's locked.
But you can change several settings and unlock bands.
I don't think MA shuts down soon but Marks ups and downs are very annoying.
mzz75 said:
Hello
I used your guide and http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
to unlock the WCDMA frequencies on my Redmi NOTE LTE TD ... bought in china .... everything OK ... but the phone works on GPRS ... I have also tried using the menu * # * # 4636 # * # * .. but nothing ..
do you have same idea ??
thank you !
Click to expand...
Click to collapse
Maybe these bands really aren't supported by hardware?
m11kkaa said:
On mi2 u can't change the IMEI because it's locked.
But you can change several settings and unlock bands.
I don't think MA shuts down soon but Marks ups and downs are very annoying.
Maybe these bands really aren't supported by hardware?
Click to expand...
Click to collapse
but when I enable WCDMA ..i can see the network [0]=CellInfoWcdma ..... but the type of network is still GPRS ... maybe some setting?
I don't think so. That's the normal behavior if a band isn't supported.
You can even enabled LTE but it won't work because the hw doesn't support it.
Modem Dead
I'm sorry to bother you again, but I have a big problem ..... with Qualcomm QPST I have a modified live parameters for the WCDMA network, but now the modem does not work anymore (2g, 3g, lte) and I can not connect the phone with QPST (say NO pHONE) .... I can do something ??
thanks
Well you have to restore the parameters to the original ones. I hope you made a backup.
m11kkaa said:
Well you have to restore the parameters to the original ones. I hope you made a backup.
Click to expand...
Click to collapse
I can not do the restore ... QPST Configurator does not see the phone ... or is there another method ??
Is it possible to enable wcdma band 900 MHz on mi2s?
orlanddon said:
Is it possible to enable wcdma band 900 MHz on mi2s?
Click to expand...
Click to collapse
I'd like to know that, too
i have one of the first batch of mi2 without wcdma 900 and it's very important to my operator so you know if it's hw supported or not? If i mess up with miflash i will restore everything or not? After a wipe i must repeat all the procedure?
Does somebody know which code it is for Redmi2? *#*#717717#*#* doesn't work... I want to try to unlock LTE band 20 (800Mhz), do you think any chance?
Any of you have got unlock 900MHz 3G on MI2 with this ?
Very interested in.
regards
I tried the tips but something's wrong :
QPST is ok i see my phone MI2 : APQ8064
With RF NV manager i got the error when i read from phone :
NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)
Again when i tried to make a backup :
"Memory Backup failed"
"Disk Error while writing to file"
Really stange... any advise ?
m11kkaa said:
How to get into Diag mode:
1) open dialer
2) enter: *#*#717717#*#*
3) you'll see a toast "diag mode enabled"
To disable diag-mode enter the same code again.
How to install drivers in Windows:
1) download and extract xiaomi_mi2_diag_driver.zip
2) after you've connected your phone in diag mode you'll see very much devices
3) choose custom source to search for driver and select the extracted folder.
4) only 3 of the devices will install it doesn't matter we don't need the others.
How to configure QPST:
1) open QPST configuration from start menu
2) on tab "ports" click on "Add new Port"
3) you should see two qualcom ports in the list. choose one and click OK.
4) if displayed phone name is SURF9615, you've selected the correct one. otherwise add the second device, too
Click to expand...
Click to collapse
Hi M1cha, I'd like to so a backup, but I can't let it work.
My problems start from the biginning: when I enter the code I got no toast message. I tried to connect anyway the phone (when is on, with and without debug option), but I don't see much devices, only the usual MI2 MTP.
Suggestions? Could be ROM releated?
Fortinho said:
Hi M1cha, I'd like to so a backup, but I can't let it work.
My problems start from the biginning: when I enter the code I got no toast message. I tried to connect anyway the phone (when is on, with and without debug option), but I don't see much devices, only the usual MI2 MTP.
Suggestions? Could be ROM releated?
Click to expand...
Click to collapse
yes, this works in MIUI only
m11kkaa said:
yes, this works in MIUI only
Click to expand...
Click to collapse
Still problems :/
I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And If I try to update drivers individually, only one will successfull install. It's normal?
Anyway, after that, I don't know how to open QPST configuration from start menu. What start menu?
Thank you.
Fortinho said:
Still problems :/
I got this:
And If I try to update drivers individually, only one will successfull install. It's normal?
Anyway, after that, I don't know how to open QPST configuration from start menu. What start menu?
Thank you.
Click to expand...
Click to collapse
Up.
Fortinho said:
If I try to update drivers individually, only one will successfull install. It's normal?
Click to expand...
Click to collapse
I don't know but you will see after with qpst if it works.
Fortinho said:
I don't know how to open QPST configuration from start menu. What start menu?
Click to expand...
Click to collapse
What windows do you've got?
With Seven : Start menu is bottom left on your screen
With 8 : go on the mosaic screen (where you have all your program) and type QPST. You will find QPST configuration
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2. run the following commands (note that you MUST be rooted to enable this. The mod survives returning to stock unrooted, and even survives OTA so you can unroot when finished if you want.):
'''
adb shell
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
'''
3. once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
4. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
5. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
6. click the load button and select the mcfg_sw.mbn you downloaded earlier.
7. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
8. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
9. on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
10. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can this phone work on Metro PCS network
I tried and tried, but i cannot get PST to see my phone. I loaded qualcomm drivers and ADB drivers, nothing. Any suggestions?
Daha3ker said:
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2.once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
3. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
4. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
5. click the load button and select the mcfg_sw.mbn you downloaded earlier.
6. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
7. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
8.on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
9. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
Click to expand...
Click to collapse
This sounds scary. I thought volte works on band 12. If the band is missing how would it work. How can you confirm it actually works.
Hi!
I am running into the same issue of two computers (Win 7 and Win 10) that cannot see the phone. Anyone willing to help in getting PDC to see the phone? Thanks!
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
mymeatb18 said:
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
Click to expand...
Click to collapse
I would like to know this as well.
Ulver said:
I would like to know this as well.
Click to expand...
Click to collapse
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config diag,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Hi Daha3ker,
I tried to enable with the mentioned commands and still PDC cannot see my phone.
Daha3ker said:
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config acm,diag,mtp,adb
setprop persist.sys.usb.config acm,diag,mtp,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Click to expand...
Click to collapse
Can't seem to make the phone appear in PDC as well, I've rooted the device with magisk and have tried to input the commands as suggested but it is still not being detected...
This is what I have
Any word on this?
Update, with stock you need to enter the command
setprop sys.usb.config diag,adb
While the phone is plugged in to the computer for it to work. I was using a different set of debug tools.
I had to use the following command to get PDC to work.
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Im running Pixel Experience 20190320 rom with Magisk 18.1.
QPST 2.7.460
I used the QUD.WIN.1.1 Installer-10040.5 drivers on Windows 10 x64.
Could you unroot and relock bootloader and have this continue working and survive OTA updates?
---------- Post added at 11:18 PM ---------- Previous post was at 10:25 PM ----------
Looks like this survives a complete fastboot flash/relock. How would you reverse this and go back to stock?
---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------
I want to switch back because sometimes when I make calls, it's high pitched and quiet. I can turn off voLTE to go back to the way it was, but would be nice to be stock again.
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
joaomiguelsm said:
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
Click to expand...
Click to collapse
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Ulver said:
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Click to expand...
Click to collapse
Oh, sad
This is the worst thin of Xiaomi in Brazil
PDC not recognizing phone
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
mtrohan said:
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
Click to expand...
Click to collapse
im getting same problem... can solve??
pleaaaase... need help.