Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/
requirements:
adb for PC
QPST
latest EFS Tools from JohnBel: https://github.com/JohnBel/EfsTools/releases/tag/v.0.14
Qualcomm-Driver
mbn file for your carrier- I used Google Pixel 4a from @swangjang : https://github.com/swangjang/Pixel-...pss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
1. settings props:adb shellsusetprop persist.vendor.dbg.ims_volte_enable 1setprop persist.vendor.dbg.volte_avail_ovr 1setprop persist.vendor.dbg.vt_avail_ovr 1setprop persist.vendor.dbg.wfc_avail_ovr 1
2. go into diag mode for X55 modem:adb shellsusetprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adbMake sure to install the drivers for it manually, especially the Diag Drivers.
3. find the correct com portgo to QPST configuration and find the X55 Modem com port in active phones. After it stop the QPST server.
4. EfsToolsGo to the EFSTools folder and find the EfsTools.dll config file. Open and change from autoport:
efstool port="yourcomport" (e.g. efstool port="com8")
5. Flash the mbn fileNow its' the same procedure like in the guide from Homersp. So I copy it from there:
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Thank you! Going to try this for T-Mobile.
Trying this but I can never get my wife's phone to show up in QPST and notice connecting her phone vs my G8 behaves differently in Device Manager. My G8 I'm able to see my Com Port number via Device Manager. The Zenfore only shows up as ASUS Android Composite ADB Interface and under Portable Devices. Weird.
wud_e said:
Trying this but I can never get my wife's phone to show up in QPST and notice connecting her phone vs my G8 behaves differently in Device Manager. My G8 I'm able to see my Com Port number via Device Manager. The Zenfore only shows up as ASUS Android Composite ADB Interface and under Portable Devices. Weird.
Click to expand...
Click to collapse
That's strange. What happens in the "normal" diag mode: setprop sys.usb.config rndis,diag,adb ?
Which firmware your wife's has?
Seosam said:
That's strange. What happens in the "normal" diag mode: setprop sys.usb.config rndis,diag,adb ?
Which firmware your wife's has?
Click to expand...
Click to collapse
Sorry long day at work. It's WW_30.40.30.93.
Doing adb shell, su then setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
It doesn't error or report anything.
Seosam said:
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/
requirements:
adb for PC
QPST
latest EFS Tools from JohnBel: https://github.com/JohnBel/EfsTools/releases/tag/v.0.14
Qualcomm-Driver
mbn file for your carrier- I used Google Pixel 4a from @swangjang : https://github.com/swangjang/Pixel-...pss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
1. settings props (I don`t know if we need this):adb shellsetprop persist.vendor.dbg.ims_volte_enable 1setprop persist.vendor.dbg.volte_avail_ovr 1setprop persist.vendor.dbg.vt_avail_ovr 1setprop persist.vendor.dbg.wfc_avail_ovr 1
2. go into diag mode for X55 modem:adb shellsusetprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adbMake sure to install the drivers for it manually, especially the Diag Drivers.
3. find the correct com portgo to QPST configuration and find the X55 Modem com port in active phones. After it stop the QPST server.
4. EfsToolsGo to the EFSTools folder and find the EfsTools.dll config file. Open and change from autoport:
efstool port="yourcomport" (e.g. efstool port="com8")
5. Flash the mbn fileNow its' the same procedure like in the guide from Homersp. So I copy it from there:
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Click to expand...
Click to collapse
Do you have a link for the qualcomm drivers to download? I'm trying to get this to work on T-mobile in the U.S.
juanappleseed said:
Do you have a link for the qualcomm drivers to download? I'm trying to get this to work on T-mobile in the U.S.
Click to expand...
Click to collapse
I'm not sure, too long ago. But I believe I used the driver of https://qpsttool.com/qpst-tool-v2-7-496 .
The is an extra folder for driver install.
wud_e said:
Sorry long day at work. It's WW_30.40.30.93.
Doing adb shell, su then setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
It doesn't error or report anything.
Click to expand...
Click to collapse
It should work :/
What happens when you use the setprop sys.usb.config rndis,diag,adb ?
Do you got a question from magsik first time after adb shell -> SU?
edit: Tipp: update to 30.40.30.96- it's the official ww Update, the 30.40.30.93 was just test for a few phones
My wife is far too busy and has no time for my nerdy ways! Even though she is gonna miss it (shoot I am too) she is gonna return the phone. She gets way too many business calls and it keeps dropping service sporadically due to being on T-Mobile. Thank you and I hope your tutorial is helpful to others!
I Got Volte VoWifi working on Tmobile in the US for the zenfone 7 pro! Read on below for easy instructions that worked for me.
Ok guys I was obsessing over all this, (as someone who doesn't program at all), how to get volte working on tmobile for the zenfone 7 pro on android 11, version (30.40.30.96), that I have in the U.S. And I ended up giving up on it late last night accepting I don't know what I'm doing in my life in general lol. Then randomly, I restarted my phone today for an unrelated reason and then I saw the volte letters at the top of my phone! I was like WTF!
So I THINK it's fully working now. Though I'm open to someone here helping me verify if I'm truly right or wrong about that. In fact I welcome it because I did it kind of on accident in an easier way than this guide or other guides have taught how to do it.
For more potential proof that I fully got it working:
The settings to enable volte, ("4G calling" as it's called in the menu) off and on are now present in the 'Settings>Network & Internet>Mobile Network' page, which seemingly indicates volte as an option to turn on and off has been enabled on the phone. Also Wifi Voice Calling as an option to enable is also there as well if you click the "Advanced" Menu Option on that same page under 4G calling and 5G Network Options.
BUT, when I check Settings>System>About Phone>Status>Sim Status it still doesn't say Volte or LTE under data or voice, it still says 4G which one might think would be an indicator against volte being truly enabled. Though I think it just means that officially my carrier tmobile doesn't have it activated on my sim even though it is activated on my phone? Could someone correct me on if I have this right?
BUT if i dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings it shows LTE under Both data network type and VOICE NETWORK TYPE, which IS an indicator that I got volte working.
I also downloaded two volte status checker apps from the play store and they both said it is connected so I suppose at this point I am sold unless someone here tells me how wrong I am.
Also when I called my voicemail, aka placed a phone call, it said "HD voice" on my phone and it kept 4G data enabled instead of downshifting to 3G or H+ which is another strong indicator I got it working.
Ok So here's how I think I got it working easily for those who may get it to work doing the same method that's the easiest way I have found.
So I wasn't able to do any of the complicated stuff, (to me it's complicated), in any of the guides above because I just couldn't get my phone to connect right with qspt or anything else for whatever reason. Nor could I get a shell on my computer to even recognize the setprop commands. I didn't even get to the later steps because I couldn't complete the first ones.
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone!
It seems like instead of having to use qspt and all that other stuff to enter the commands through a computer that then connect to a phone I just entered them on the phone itself through the terminal emulator app and it worked?
Other than that I'm not sure how else I got it working because when I tried to enter those setprop commands from my computer to the phone I couldn't even get it to work and the computer kept telling me setprop wasn't a recognized command, whereas when I entered those commands into the terminal emulator app on the phone itself, it DID recognize setprop as a valid command, even though when I entered the block of setprop commands through manual typing it didn't say anything once I entered them to verify that they did anything.
But I think the results say that they in fact DID do something.
I know my explanation is long but it seems I got it working a lot simpler than anyone else has just using the terminal emulator app on the phone itself after having it rooted on android 11 so wanted to share in case someone else can get it to work this way as well because man was it a pain in my ass to figure it out lol.
And please if someone is more knowledgeable let me know if I got it wrong or if there was something else I did to make it work that I'm not aware of at the moment or if I haven't FULLY got it enabled or it's only saying I did or something. But there seems to be a lot more evidence it is working that evidence that it isn't. Called my mom and she said my voice was clearer and richer as well so I think I got it.
I'm looking forward to using this phone in the U.S. and seeing if this radically improves my call quality and connection dependability! Cuz this phone's hardware is awesome it's just the software that is whack and incomplete because Asus cheaped out on the licensing this time. They did it for the bluetooth audio quality also. But Viper for android has solved that as well.
juanappleseed said:
Ok guys I was obsessing over all this, (as someone who doesn't program at all), how to get volte working on tmobile for the zenfone 7 pro on android 11, version (30.40.30.96), that I have in the U.S. And I ended up giving up on it late last night accepting I don't know what I'm doing in my life in general lol. Then randomly, I restarted my phone today for an unrelated reason and then I saw the volte letters at the top of my phone! I was like WTF!
So I THINK it's fully working now. Though I'm open to someone here helping me verify if I'm truly right or wrong about that. In fact I welcome it because I did it kind of on accident in an easier way than this guide or other guides have taught how to do it.
For more potential proof that I fully got it working:
The settings to enable volte, ("4G calling" as it's called in the menu) off and on are now present in the 'Settings>Network & Internet>Mobile Network' page, which seemingly indicates volte as an option to turn on and off has been enabled on the phone. Also Wifi Voice Calling as an option to enable is also there as well if you click the "Advanced" Menu Option on that same page under 4G calling and 5G Network Options.
BUT, when I check Settings>System>About Phone>Status>Sim Status it still doesn't say Volte or LTE under data or voice, it still says 4G which one might think would be an indicator against volte being truly enabled. Though I think it just means that officially my carrier tmobile doesn't have it activated on my sim even though it is activated on my phone? Could someone correct me on if I have this right?
BUT if i dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings it shows LTE under Both data network type and VOICE NETWORK TYPE, which IS an indicator that I got volte working.
I also downloaded two volte status checker apps from the play store and they both said it is connected so I suppose at this point I am sold unless someone here tells me how wrong I am.
Also when I called my voicemail, aka placed a phone call, it said "HD voice" on my phone and it kept 4G data enabled instead of downshifting to 3G or H+ which is another strong indicator I got it working.
Ok So here's how I think I got it working easily for those who may get it to work doing the same method that's the easiest way I have found.
So I wasn't able to do any of the complicated stuff, (to me it's complicated), in any of the guides above because I just couldn't get my phone to connect right with qspt or anything else for whatever reason. Nor could I get a shell on my computer to even recognize the setprop commands. I didn't even get to the later steps because I couldn't complete the first ones.
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone!
It seems like instead of having to use qspt and all that other stuff to enter the commands through a computer that then connect to a phone I just entered them on the phone itself through the terminal emulator app and it worked?
Other than that I'm not sure how else I got it working because when I tried to enter those setprop commands from my computer to the phone I couldn't even get it to work and the computer kept telling me setprop wasn't a recognized command, whereas when I entered those commands into the terminal emulator app on the phone itself, it DID recognize setprop as a valid command, even though when I entered the block of setprop commands through manual typing it didn't say anything once I entered them to verify that they did anything.
But I think the results say that they in fact DID do something.
I know my explanation is long but it seems I got it working a lot simpler than anyone else has just using the terminal emulator app on the phone itself after having it rooted on android 11 so wanted to share in case someone else can get it to work this way as well because man was it a pain in my ass to figure it out lol.
And please if someone is more knowledgeable let me know if I got it wrong or if there was something else I did to make it work that I'm not aware of at the moment or if I haven't FULLY got it enabled or it's only saying I did or something. But there seems to be a lot more evidence it is working that evidence that it isn't. Called my mom and she said my voice was clearer and richer as well so I think I got it.
I'm looking forward to using this phone in the U.S. and seeing if this radically improves my call quality and connection dependability! Cuz this phone's hardware is awesome it's just the software that is whack and incomplete because Asus cheaped out on the licensing this time. They did it for the bluetooth audio quality also. But Viper for android has solved that as well.
Click to expand...
Click to collapse
For some U.S. carriers may it work so. I have read in ROG 2 or 3 forum about it. Maybe because Asus has build in these carriers but not activated. For other you need whole procedure....
Tip: you can check your setptop status with getprop e.g. getprop persist.vendor.dbg.ims.volte If you get a "1" back it's activatetd.
Seosam said:
For some U.S. carriers may it work so. I have read in ROG 2 or 3 forum about it. Maybe because Asus has build in these carriers but not activated. For other you need whole procedure....
Tip: you can check your setptop status with getprop e.g. getprop persist.vendor.dbg.ims.volte If you get a "1" back it's activatetd.
Click to expand...
Click to collapse
Hey there, thank you for the response. I'm glad I didn't have to do anything else because I'm woefully underskilled at understanding the rest of the procedures though with enough time could have figured it out of course.
My image attached below shows what I got when I wrote in getprop to the terminal emulator.
When I wrote the command you gave me specifically it didn't return anything, though there are 1s returning for all the other setprop commands previously entered which is the same thing yes?
wud_e said:
My wife is far too busy and has no time for my nerdy ways! Even though she is gonna miss it (shoot I am too) she is gonna return the phone. She gets way too many business calls and it keeps dropping service sporadically due to being on T-Mobile. Thank you and I hope your tutorial is helpful to others!
Click to expand...
Click to collapse
I figured out how to enable volte on tmobile pretty easily if you still have the phone to try it out on! My guide on how to do it is posted in this thread.
juanappleseed said:
I figured out how to enable volte on tmobile pretty easily if you still have the phone to try it out on! My guide on how to do it is posted in this thread.
Click to expand...
Click to collapse
Hey, awesome to see. She got a new Samsung phone and took her number back to Cricket. Howerver, I haven't had a chance to unroot and relock the bootloader so I could verify this for you on the phone. At least see if the settings stick using an on phone terminal like you did.
Also I do have a Mint Sim I'm test driving for a Mi 10 Ultra. I'll see what happens adding that Sim in since it is T-Mobile after all.
----------
Unrelated sort of. Something happened last night that I didn't think was needed and made me question if any of this is needed at all when trying to get these phones to work on Cricket. So the Samsung my wife bought is the S20 Ultra which is 5G, AT&T variant. I was doing a speed test with my Mi10 and then randomly asked my wife to do it on the S20. Her speed never got over 4G speeds. I mentioned that and she said Cricket charges extra for 5G. Interesting! So I wonder if popping your SIM in a 5G phone no matter what triggers their alarm system and they shut it down because they want the "cost" of 5G. I'm going to take my Mi 10 ultra to the Cricket store and since Amazon has like a 30 day window of needing merchandise back after making a return claim I'll take the Zenfone 7 also. Maybe in store asking to upgrade to 5G nets a different result than popping in the SIM which they recommend anyway, but it shouldn't be this hard.
wud_e said:
Hey, awesome to see. She got a new Samsung phone and took her number back to Cricket. Howerver, I haven't had a chance to unroot and relock the bootloader so I could verify this for you on the phone. At least see if the settings stick using an on phone terminal like you did.
Also I do have a Mint Sim I'm test driving for a Mi 10 Ultra. I'll see what happens adding that Sim in since it is T-Mobile after all.
----------
Unrelated sort of. Something happened last night that I didn't think was needed and made me question if any of this is needed at all when trying to get these phones to work on Cricket. So the Samsung my wife bought is the S20 Ultra which is 5G, AT&T variant. I was doing a speed test with my Mi10 and then randomly asked my wife to do it on the S20. Her speed never got over 4G speeds. I mentioned that and she said Cricket charges extra for 5G. Interesting! So I wonder if popping your SIM in a 5G phone no matter what triggers their alarm system and they shut it down because they want the "cost" of 5G. I'm going to take my Mi 10 ultra to the Cricket store and since Amazon has like a 30 day window of needing merchandise back after making a return claim I'll take the Zenfone 7 also. Maybe in store asking to upgrade to 5G nets a different result than popping in the SIM which they recommend anyway, but it shouldn't be this hard.
Click to expand...
Click to collapse
Update!!! It works and it makes me sad that it worked this easily! Only because we are returning it. Before using Termux as su and entering the commands, my Mint Sim did not show Volte and VoWifi was not an option. Changing the settings Volte shows up in the top of the screen next to the connection icons and going into the Sim options you are able to flip VoWifi on and then that worked as well. Also verified in *#*#4636#*#* Great work both of yall!!! This is a legit option. Will verify taking my MI 10 to Cricket in case that helps further.
wud_e said:
Update!!! It works and it makes me sad that it worked this easily! Only because we are returning it. Before using Termux as su and entering the commands, my Mint Sim did not show Volte and VoWifi was not an option. Changing the settings Volte shows up in the top of the screen next to the connection icons and going into the Sim options you are able to flip VoWifi on and then that worked as well. Also verified in *#*#4636#*#* Great work both of yall!!! This is a legit option. Will verify taking my MI 10 to Cricket in case that helps further.
Click to expand...
Click to collapse
I'd be interested for sure and glad you verified a super easy solution that at least works for us tmobile users in the USA. As for 5G on zenfone 7 from what I understand it doesn't have the bands to work on tmobile. I believe ATT has one 5G band available.
Yeah Cricket wouldn't touch either phone. So I'm going to switch to Mint for MI 10.
Můj operátor nemá v seznamu podporovaných telefonů telefon 4a. Nevíte, kde najít MBN pro:
My carrier does not have phone 4a in the list of supported phones. Don't know where to find mbn for:
My operator is 02 telefonica CZ
Related
So obtaining the MSL on a samsung device is pretty straight forward most of the time..on Sprint devices we usually use the getprop ril.MSL command..this method works by entering the MSL incorrectly 1st....Verizon is normally all zero's..but its not on the VZW S4..and the big problem is the device doesnt require an MSL to access data menu's..soooo I cant use the getprop ril.MSL command
The MSL is used to reprogram NAM settings
Im trying to figure out how to get the phone to ask for the MSL so I can then enter it wrong so I can then use the getprop ril.MSL command to retrieve the correct MSL
Any ideas?
Sent from my SPH-L720 using Tapatalk 2
12manytimes said:
So obtaining the MSL on a samsung device is pretty straight forward most of the time..on Sprint devices we usually use the getprop ril.MSL command..this method works by entering the MSL incorrectly 1st....Verizon is normally all zero's..but its not on the VZW S4..and the big problem is the device doesnt require an MSL to access data menu's..soooo I cant use the getprop ril.MSL command
The MSL is used to reprogram NAM settings
Im trying to figure out how to get the phone to ask for the MSL so I can then enter it wrong so I can then use the getprop ril.MSL command to retrieve the correct MSL
Any ideas?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
How do you get to the data menus in the first place? I've tried the usual codes and I don't see any of them working.
vacaloca said:
How do you get to the data menus in the first place? I've tried the usual codes and I don't see any of them working.
Click to expand...
Click to collapse
+1 I can't get to the data menus either. How do you do it.
Okay, so I did a little digging and found this:
http://galaxys4root.com/galaxy-s4-t...aws-bands-on-att-galaxy-s4-sgh-i337sgh-i337m/
Now, the kicker is that since our hidden menus aren't enabled, and the enabler code isn't the same as the Galaxy S3 as posted below, dialing the code won't pull up the screen as on the tutorial above:
http://androidforums.com/samsung-ga...unlocking-jelly-bean-service-modes-found.html
However, we can resort to some additional trickery. I installed the Market app called QuickShortcutMaker. With that app, one can create a shortcut to an activity, specifically for the phoneutil.apk listed in the first tutorial after it is installed. The activity we want to make a shortcut to that is equivalent to the menu shown by dialing *#7284# is:
Code:
com.sec.android.app.phoneutil.SetPortUartUsbMSM8960
With that, it should give access to the Samsung COM Port we can use with whatever utility can read the MSL on Samsung phones. If I find one that works, I will post again.
Edit 1: It seems that the mode should be set to DM + Modem + ADB to get the modem working under QPST. The RNDIS + DM + MODEM mode errors out in QPST.
---------- Post added at 10:05 PM ---------- Previous post was at 09:47 PM ----------
Okay, so I used CDMA Workshop v2.7.0 (google it) and I input SPC 000000 and it worked fine for me on my Verizon Galaxy S4, so either OP is on Sprint or another carrier or someone else set the SPC on his phone.
It seems like OP posted using a Sprint phone, but he seems to think Verizon S4's have a different SPC/MSL other than 000000, which doesn't seem to be the case.
Edit 2: I retried the RNDIS + DM + MODEM mode and it seems to load fine on QPST also, might've been that I needed to unplug/replug the phone USB cable. For that matter, QPST also acknowledges SPC/MSL code as 000000 on VZW GS4. The version I found (QPST 2.7 build 402) detects the chipset, but stops responding when reading the Service Programming data.
Thanks for the reply, I do have a sprint s4 and I already flashed it 2 vzw prepaid..my brother in LA has the vzw s4 and based on what u said I think what happend is he changed the MEID 1st and restarted l the phone and I think it changed his MSL..maybe he can revert back to the original and get the stock MSL..ill comfirm when he responds back to me..but for my original question lets assume he's stuck with the new MSL..how would we go about getting the MSL? on all the devices ive used the getprop ril.MSL command on, Ive always had to 1st enter the MSL wrong but since the programming menus on this phone dont ask for it im stuck as to how to get the getprop ril.MSL command to work?
Edit: just got my hands on it and thats exactly what it was..SPC changes once u tamper with the MEID, reverted back 2 stock and reset the phone and voila, back 2 zeros, full flash in no time
Sent from my SPH-L720 using Tapatalk 2
12manytimes said:
Thanks for the reply, I do have a sprint s4 and I already flashed it 2 vzw prepaid..my brother in LA has the vzw s4 and based on what u said I think what happend is he changed the MEID 1st and restarted l the phone and I think it changed his MSL..maybe he can revert back to the original and get the stock MSL..ill comfirm when he responds back to me..but for my original question lets assume he's stuck with the new MSL..how would we go about getting the MSL? on all the devices ive used the getprop ril.MSL command on, Ive always had to 1st enter the MSL wrong but since the programming menus on this phone dont ask for it im stuck as to how to get the getprop ril.MSL command to work?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I knew something funky was up I was going to try a memory dump in QPST to see if it was visible like on an LG Optimus Elite I tinked with a while ago, but QPST insists the phone isn't in download mode, and when it prompts to switch it over, it hangs and says the phone stopped responding to commands, or just reboots the phone and does not place it in download mode.
Edit 1: You can read NV item 85 using CDMA Workshop v.2.7.0 -- that contains the MSL, however, you'll also need to know the 16 digit password to be able to read it.
Edit 2: A bit more googling found a 16 digit password that works for my Verizon Samsung Galaxy S4 -- it is: 2009031920090615 (it is also the password for the i535) You can retrieve protected NVM items after inputting this password AND the SPC code.
Edit 3: Nice, once I had input the 16 digit code into CDMA workshop and opened up QPST service programming, it enables reading of the service information there too! Seems like the lack of a correct 16 digit password being sent is what was 'locking' it. Presumably newer versions of QPST will ask for the 16 digit code in addition to the SPC.
Unfortunately, because you don't know the SPC code, even knowing the 16 digit password is not enough to get the SPC from NVM item 85, as I said earlier, you have to know both. Presumably there is another way of getting it... I tried to read the memory from the S4 with just the 16 digit code set and it doesn't seem to work.
Because it is relevant to the discussion, I figured out how to enable the hidden menus on the Verizon Samsung Galaxy S4. See here for details:
http://forum.xda-developers.com/showthread.php?t=2303905
This makes it a bit easier... no shortcut trickery needed to get to the *#7284# menu. After enabling the hidden menus, just dialing the code will work.
I'm still not aware of a way to get the MSL/SPC if it is unknown, however. Perhaps someone else can figure this out.
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
I ended up being able to read the LTE bands with DFS and write them with QXDM. The only thing is that there is no LTE/GSM/UMTS mode on the phone, so it's either LTE/CDMA or GSM/UMTS for now until I figure out if I can flash some other ROM to it to let it use the other bands, cause right now it only wants to look at band 25.
So I've been trying to flash the N900T MI7 modem/baseband on my N900P but I can never get it to flash in Odin. I've been able to put the modem and non-hlos in flash able zips and flash those but it never shows up. I've also tried to dd the files directly but that doesn't work either. Ideas?
I am impressed it's not bricked yet.
Sent from my SM-G935F using XDA-Developers mobile app
Same issue
BlockOfDynamite said:
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
Click to expand...
Click to collapse
I am facing same issue regarding back up nv at 12%
vipsy6 said:
I am facing same issue regarding back up nv at 12%
Click to expand...
Click to collapse
So basically what happened was I found a couple other tools to do what I wanted. First was DFS tool. This works well, because it can both read and write bands to the nv of the phone. I forget what the second was, but it could both read and write the raw value of any given value in the nvram. I'll have to dig through my stuff again if you want to know what the second program was. The fact of the matter is that I was never able to get it working right. The phone always looked at band 25 LTE no matter what bands I turned on/off of the phone.
another ?
BlockOfDynamite said:
So basically what happened was I found a couple other tools to do what I wanted. First was DFS tool. This works well, because it can both read and write bands to the nv of the phone. I forget what the second was, but it could both read and write the raw value of any given value in the nvram. I'll have to dig through my stuff again if you want to know what the second program was. The fact of the matter is that I was never able to get it working right. The phone always looked at band 25 LTE no matter what bands I turned on/off of the phone.
Click to expand...
Click to collapse
Please let me know second program
BlockOfDynamite said:
First off, thanks for tolerating this somewhat noobish post, but I've searched through almost the whole internet trying to find answers.
Alright, so here's the dealio.
Sprint Galaxy Note 3. UICC unlocked via idoneapp, then used on domestic T-Mobile through GCF settings. I want to enable more bands as described in the following links: here and here.
I get as far as Step 9 in the second link. Then, I go to select a port, and it's not there. OK, so I uncheck the "diagnostic port only" check box, and select COM12 which is what my phone is on. No big deal, right? So I go to read/backup my NV and I start it; it only gets to 12% and says "Could not Communicate in Diagnostic Mode"
That's it. I've tried different USB ports, different USB cables, other USB modes on the phone, I even have a custom kernel. I really hope it's something obvious that I'm doing wrong instead of something that's a niche error.
Thanks, guys.
Click to expand...
Click to collapse
hi
how did you connect QPST to your phone? i can't do it,
installed QPST under windows 7, QDXM and kies, but in QPST configuration i get "No Phone" when added new port
walidham said:
hi
how did you connect QPST to your phone? i can't do it,
installed QPST under windows 7, QDXM and kies, but in QPST configuration i get "No Phone" when added new port
Click to expand...
Click to collapse
I never did get QPST to connect to my phone. I think I was able to get it to see the phone at some point, but it would never read anything from it or write anything to it. The program always froze up or something when I tried that. If I could remember the second program I used, I'd share it with you all, but for the life of me, I can't think of it.
Edit: Oh hey, the two programs I used are RIGHT IN MY SECOND POST. lol. Yeah, use DFS tool to read the NV and QXDM to write the NV. It'll save you a whole lot of trouble over doing stuff with QPST.
BlockOfDynamite said:
I never did get QPST to connect to my phone. I think I was able to get it to see the phone at some point, but it would never read anything from it or write anything to it. The program always froze up or something when I tried that. If I could remember the second program I used, I'd share it with you all, but for the life of me, I can't think of it.
Edit: Oh hey, the two programs I used are RIGHT IN MY SECOND POST. lol. Yeah, use DFS tool to read the NV and QXDM to write the NV. It'll save you a whole lot of trouble over doing stuff with QPST.
Click to expand...
Click to collapse
Hi
Yes i used only DFS tools and it work fine, also and changed my Bands 4G and 3G to work in Europe with Spint N900P phone,
3G work fine but not 4G, i will install custom Rom and see if it will work.
walidham said:
Hi
Yes i used only DFS tools and it work fine, also and changed my Bands 4G and 3G to work in Europe with Spint N900P phone,
3G work fine but not 4G, i will install custom Rom and see if it will work.
Click to expand...
Click to collapse
Well, 3G will work fine without changing anything anyway. All of the bands are already enabled. 4G is the issue.
BlockOfDynamite said:
Well, 3G will work fine without changing anything anyway. All of the bands are already enabled. 4G is the issue.
Click to expand...
Click to collapse
Yes 4G is the big pb, i found that DFS Tools write 3G bands but for LTE, the issue is in BC Config Div, need SPC code
i tried to find SPC /MSL code but no chance
I will install SPR-N900PVPUBMJ4 rom and after SPR-N900PVPUBMJ3 modem and use DSF tools to set it 000000
hope i will work
walidham said:
Yes 4G is the big pb, i found that DFS Tools write 3G bands but for LTE, the issue is in BC Config Div, need SPC code
i tried to find SPC /MSL code but no chance
I will install SPR-N900PVPUBMJ4 rom and after SPR-N900PVPUBMJ3 modem and use DSF tools to set it 000000
hope i will work
Click to expand...
Click to collapse
Flash the MI3 (that's emm eye three) modem and then use the app included in the zip file to find the MSL code. Here's a link to the zip file: http://bit.ly/1oZDO9t
I was not aware that you could change the MSL code with DFS tools. At least I have a Verizon Note 3 now, so I have a lot more LTE bands than the Sprint version does (although I don't care all that much; I think I may switch to the Nexus 6 soon). But yeah, try the stuff in the zip file from the link, and you should be able to
Find your MSL code
Unlock your phone internationally
Use hidden menus
Most of all, have fun! I know for sure this can be very very frustrating a lot of the time, but if you don't have fun, then I don't think there's much profit in trying stuff like this. Good luck!
BlockOfDynamite said:
Flash the MI3 (that's emm eye three) modem and then use the app included in the zip file to find the MSL code. Here's a link to the zip file: http://bit.ly/1oZDO9t
I was not aware that you could change the MSL code with DFS tools. At least I have a Verizon Note 3 now, so I have a lot more LTE bands than the Sprint version does (although I don't care all that much; I think I may switch to the Nexus 6 soon). But yeah, try the stuff in the zip file from the link, and you should be able to
Find your MSL code
Unlock your phone internationally
Use hidden menus
Most of all, have fun! I know for sure this can be very very frustrating a lot of the time, but if you don't have fun, then I don't think there's much profit in trying stuff like this. Good luck!
Click to expand...
Click to collapse
After many try, finaly i get my MSL code (24 hours).
I have downgrad my phone to 4.4.2, and install custom rom Galaxy-Note-fre3-2.26,
and after using adb and logcat i got my code.
Now how can i activate it for internationally ? i have added all LTE band (3,7,20) but still H+
I will try with QXDM, but i have windows 10 and give me error acces denied.
walidham said:
After many try, finaly i get my MSL code (24 hours).
I have downgrad my phone to 4.4.2, and install custom rom Galaxy-Note-fre3-2.26,
and after using adb and logcat i got my code.
Now how can i activate it for internationally ? i have added all LTE band (3,7,20) but still H+
I will try with QXDM, but i have windows 10 and give me error acces denied.
Click to expand...
Click to collapse
I just did it with my Verizon Note 3 on Windows 10, so I know it's not a Windows 10 issue. Also, QPST seemed to work with my Verizon phone but not my Sprint phone. Weird. Make sure you're running QXDM as administrator. Also, I unlocked all of the LTE bands in this way but I can't seem to get LTE from my GSM sim card, even by going into the service mode and enabling all LTE bands.
BlockOfDynamite said:
I just did it with my Verizon Note 3 on Windows 10, so I know it's not a Windows 10 issue. Also, QPST seemed to work with my Verizon phone but not my Sprint phone. Weird. Make sure you're running QXDM as administrator. Also, I unlocked all of the LTE bands in this way but I can't seem to get LTE from my GSM sim card, even by going into the service mode and enabling all LTE bands.
Click to expand...
Click to collapse
Yes; for LTE i found in hiddn menu, that they use Tri Bands (25, 26 & 41), so for others bands will not work.
I don't know how i can disable this and force it to use bands 3, 7 20.
walidham said:
Yes; for LTE i found in hiddn menu, that they use Tri Bands (25, 26 & 41), so for others bands will not work.
I don't know how i can disable this and force it to use bands 3, 7 20.
Click to expand...
Click to collapse
I honestly couldn't tell you, and I'm not sure how much help I'm going to be in general. I've tried it on both of my Note 3 phones but have had no confirmed success. Sprint especially is the one carrier that sticks out like a sore thumb, and by association, so do their phones. I've had plenty of frustration on that front, that's for sure.
BlockOfDynamite said:
I honestly couldn't tell you, and I'm not sure how much help I'm going to be in general. I've tried it on both of my Note 3 phones but have had no confirmed success. Sprint especially is the one carrier that sticks out like a sore thumb, and by association, so do their phones. I've had plenty of frustration on that front, that's for sure.
Click to expand...
Click to collapse
Thanks for your help,
Just one question if have any idea for it
can i install Firmware N9005 using PIT file for N90005 in N900P?
Because when i received my phone(from china) , the first time i see that BaseBand version is for n9005 and phone name n900 but in download mode i see n900p
i think chines have a method to do it
walidham said:
Thanks for your help,
Just one question if have any idea for it
can i install Firmware N9005 using PIT file for N90005 in N900P?
Because when i received my phone(from china) , the first time i see that BaseBand version is for n9005 and phone name n900 but in download mode i see n900p
i think chines have a method to do it
Click to expand...
Click to collapse
Maybe. Really they have a method to do anything I would advise against trying to do that, although I'm not sure what harm it could do if you can still get back into download mode. I've tried flashing different versions' firmware to the N900P with no success.
I'm on the latest global stable ROM 7.3.2, I'm not sure why it's so unstable. It'll show HSPA+ and 3G and switch between the two but randomly it'll just drop signal altogether.
You could try the Qualcomm bands unlock procedure. It's really complicated though and might not even work. I think if you do it right it works. I have no way to test it yet even though I've successfully done the procedure.
LiQuiD_FeAR said:
You could try the Qualcomm bands unlock procedure. It's really complicated though and might not even work. I think if you do it right it works. I have no way to test it yet even though I've successfully done the procedure.
Click to expand...
Click to collapse
Can you point me in the right direction?
You need root. After you put the phone in dev options usb debugging and installer mode go to command prompt in adb folder and type:
adb shell
Su
Setprop sys.usb.config diag,adb
That sets the drivers on your pc right for QPST
I used qxdm for the nv edits, i had to dig deep for a link. Then check out these threads:
http://forum.xda-developers.com/showpost.php?p=64675180&postcount=11
http://www.usoftsmartphone.com/t264374.html
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
Save yourself the headache of messing this up and see if you can find the copy of twrp that someone made to backup the efs and other odd partitions. Before you try to change anything also go to QPST, start clients menu, software download, backup tab, and backup your phones nv to a qcn file. Don't share the backup file with anyone until you null out the imei and other unique values.
If anyone has the best qcn file with the most bands unlocked that would be convenient. Another tip is don't add any cdma bands or you won't get any signal.
Hi!
So I bought a HTC 10 from Amazon back in May and, even though the product description said it was the US version which had LTE bands for US carriers (specifically 4-AWS), they sent me a M10h, which is the international/asian version that doesn't support band 4. I can't return the phone though, since I'm from Argentina and with the insane customs ruling here, sending the phone to the US and back would cost me almost as much as just buying selling mine (at a highly reduced pricepoint since it doesn't support LTE in my country) and buying a new one.
After a lot of reading here in XDA, paying 25$ to be S-Off, flashing radios, changing roms and kernels, and a bunch of other stuff, I've come to the conclusion that my only alternative left is to change the 06828 NV value (which determinates what LTE bands are activated) with QXDM/DFS tools/whatever program. I've managed to put the phone in diag mode (for those who don't know how, I'll leave a little tutorial in the end of the thread), but when I write the value and then read it again it's back to its original state. I guess this is some kind of protection Qualcomm/HTC/whoever put in place to avoid users messing around with this stuff.
I read in the HTC One M9 forums that users with CDMA phones could change the 06828 value, while I, using a GSM phone, have been able to change 06829. I tried using a Verizon radio, which turns on and off the diag mode for some reason, and a Sprint radio, which gives me a "diag error response" in QXDM when I try to read/write any NV value.
Maybe a custom kernel can help avoid the write protection for NV values? I don't know a lot about that kind of stuff, so it's the only thing that I believe could change my situation
Phone info:
White HTC 10 M10h model
LeeDroid 10 v2.4.1-stable rom with CleanSlate kernel
S-Off and root
Baseband version [email protected]_51.01_F
---------------------------------------------------------------------------
For those who can't make it to Diag Mode:
1) Install the HTC Diag Drivers in your PC
2) Install a terminal emulator in your phone (in my case I used SManager)
3) Connect the phone to the computer with the USB cable
4) In the terminal emulator use:
Code:
su
and then
Code:
setprop sys.usb.config diag
5) Now touch on the "Use USB for" notification.
6) If everything worked, the phone should block you from choosing any option in the list besides Charging and USB tethering
7) Choose USB tethering
8) Your phone should appear in the Windows Device Manager as HTC Diagnostic Interface, which means the phone is in Diag Mode
9) To return to the default USB mode, repeat step 4, but replacing setprop sys.usb.config diag for
Code:
setprop sys.usb.config mtp
--------------------------------------------------------------------------
Does anyone know any way to make my phone work? Any kernel made from scratch I can try? I'm really desperate.
Thank you all for reading!
Up!
Bump... has anyone figured this out? The M8 and M9 guys have reported flashing a Verizon RUU/Firmware to allow the LTE NV values to stick, but this does not seem to work on the HTC 10. I've tried everything and have gone this far, but I just cant seem to write the NV values. I've tried QPST + QXDM, as well as DFS. I am not sure if it's the actual firmware/radio itself (though I've also tried them ALL), or just the actual Kernel.
I am stopped on the same spot. I used ElementalX-HTC10-1.06 as kernel without success. Were you able to get anything?
After reading through the OPO thread and someone confirming they saw bands unlocked for their OP2, but could not test if they are working as well as reading through the OP3 and similar threads with our processor I finally delved into trying this. Here is the quick guide of how to do it. Sorry if there is any confusion I will try my best to make it concise as possible. This is my first time writing a guide up for XDA.
I have not been able to test each band to confirm it's working, but it is showing up in Network Guru. I am on AT&T so I only unlocked AT&T bands (bc that's all I care about currently and it makes it easier for me to test)
I WILL NOT BE HELD RESPONSIBLE IF SOMETHING WRONG HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE!
Credit: All my fellow XDA'rs who have been diligently testing, experimenting, bricking/unbricking, creating ROMs, FLASH, Root ability, and Bootloader unlocking. You are the heart and soul of XDA!
[URL="https://forum.xda-developers.com/member.php?u=4066277" @otonieru[/URL] for the concise guide
[URL="https://forum.xda-developers.com/member.php?u=7846474" @baskaflyfer[/URL] Rmt Storage Patch Zip
Here is the OP3 thread I based this guide off of and credit to all those mentioned in there as getting this far would have been impossible without them: https://forum.xda-developers.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
OKAY:
PreReq's:
1. Rooted
2. TWRP or like
3. RMT Storage patch from OP3 forums: SEE POST BELOW!
4. DFS Explorer - Find via searching XDA, again checking OP3 thread or OPO
5. ADB installed (whether that be minimal ADB or like from other toolboxes out there)
6. QPST - Check forums for download
Guide:
1. Put phone in MTP mode if not default (Some default to charge mode) Just go to status bar and press the charging mode to change to file transfer
2. Place file from PRE-REQ #3 in a folder you'll remember
3. Reboot phone (or shut down) and when coming on hold Vol Down+Power for a few seconds and let go
4. Boot into TWRP
5. Backup (If you don't have a backup of EVERYTHING at this point, probably a good idea to do so)
---If you do take only EFS
And install file from #3
6. Restart into System
7. Open up your CMD and run this ADB command :
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your OP3 diagnostic port)
Click to expand...
Click to collapse
This forces it into DIAG mode, check your Device Manager to see if you see a port connection displaying a COM PORT.. IF NOT, you need to install drivers--Search thread for drivers, likely will be find in original OPO or OP3 thread.
***********THIS SECTION IS PURELY PRECAUTIONARY*********************** SKIP TO 11 IF YOU WANT
Purely precautionary we did not have to restore any QCN as they do in OP3 due to encryption:
8. Install QPST, open QPST
Now fire up QPST and go to "Port" tab, and choose "Add New Port" ,
9. On "Serial/USB Port" tab, unchecked the option of "Show Serial & USB...bl bla bla" option, you will see your phone listed there as a "COM#" (# is a number depending on your PC) choose it, and click "OK"
10. Now choose "Start Clients" from the Menu tab above, and choose "Software Download"
**********************************************************************************
11. CLOSE QPST. Open up DFS Explorer, when the signup option comes up it is up to you whether or not you want to register for an account (Good to support them since it's a good application) If not, press the X and the app will be there
12. You should see your PORT listed as you did on QPST. Double click on it (If you can't; confirm QPST is closed otherwise you won't be able to connect to the port) You should see it turn green and highlighted ONLINE if you successfully connected
13. Go to the "Band" option then click on "LTE"
14. Press READ; Give it a second and you should see all currently enabled bands listed; If you want to compare you can go to "Network Guru" and press the 3 dots on the top right and press Band Locking and then press LTE.. Should list the same ones
15. Check the additional bands (Just because it says it's enabled, doesn't mean hardware wise it will work due to chipset hardware limitations; This is why as you all do this if you can confirm which bands for you connected and/or didn't connect we can keep a running list.)
16. Press "Write"
17. Since we're in Demo mode it will count down and then in the LOG box you'll see operation successful
18. Restart the phone at this point and disconnect the cable
19. Wait until it boots up again and go to "Network Guru" press the 3 dots again and go to Band Locking and you should see the new bands listed
*If you don't press the 3 dots and press Clear forcings and it'll prompt that a power cycle may occur; That's okay, let it, mine did, wait until the phone comes back up and repeat 19 and the new bands should be listed.
20. LET US KNOW ON THIS THREAD what bands are working, what aren't. It will allow us to further play with the device to discover if there's limitations or if further editing is required like in the OP3.
*Please press THANK YOU if this guide was helpful.
**Sorry for the missing of some info in the guide! Seems when I added the HYPERLINK it removed most of the other text before it so it started at #4 instead of the remainder of #1-3
Direct link to RMT STORAGE PATCH:
Rmt Storage Patch Zip
usb debugging should be enabled i think, you didn't mentioned that. " (this will open your OP3 diagnostic port)" and here should be op2 i think. thanks for thread, i have a2005 and want to unlock 20 band(800mhz), will try asap, now i have exams running out of time. btw, so the risk of breaking phone is low right, this steps only modify EFS partition only? so hybrid recovery and flashfire can backup/restore if enything goes wrong
What is the benefit from this? Better reception?
Sent from my ONE A2005 using Tapatalk
So... Are your at&t bands working now? Which bands specifically?
我從使用 Tapatalk 的 Nexus 9 發送
Still something is missing
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
haroldgv said:
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
Click to expand...
Click to collapse
what and where is PRE-REQ #3?
haroldgv said:
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
Click to expand...
Click to collapse
In Network Signal Guru, choose clear forcing. And check the LTE bands again,
or, install Network Signal Guru after you done unlocking, else it will show what it remember on previous set up
---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------
chxei said:
what and where is PRE-REQ #3?
Click to expand...
Click to collapse
the guide forget to mention that u need to flash rmt storage patch before do any modification,
else no mod will be saved (will revert upon boot)
the patch is in my OP3 thread
Thanks! So today's update:
1- I connected the phone again, ran adb commands, reviewed the bands again on DFS tool and settings stayed. I'm pursuing to enable Band 3
2- I uninstalled Network Signal Guru
3- On Recovery, flashed again the patched rmt_storage, boot the phone, wrote the values again on DFS tool. Reboot phone
4- I installed Network Signal Guru and now it's showing up on the bands lists. I unchecked the bands default on A2005 and used the ones from Eruper/Asia Model as FDD-LTE: Bands 1/3/5/7/8/20 and TDD-LTE: Bands 38/40/41. My provider in Costa Rica (Movistar) uses Band 3 (1800) for their LTE. I clicked on Band locking, clicked on GSM and WDCMA and removed all checks. Then clicked on LTE and left all LTE bands in hopes that it will connect to that frequency. The list shows:
B1: 2100
B3: 1800+
B5: 850
B7: 2600
B8: 900 GSM
B20: 800 DD
B38: TDD2600
B40: TDD 2300
B41: TDD 2500
When I only picked LTE bands as checked, it never resovled to get connected to any cell base.
5- I dialed *#*#4636#*#* to access the information about the phone and monitored the signal setting it up to "LTE Only". No signal on that either
Top of my head, I will restore the qcn backup I made and restore the backup I made for EFS and start again. Now it's saving values after reboot, which is great, but not identifying anything.
Is there any log worth posting here? I read on the OP3 guide that they were restoring a qcn file with bands enabled. Is it worth trying the same?
Anyone that has LTE band 3 enabled would be very appreciated if they post their qcn backup
t99220475 said:
So... Are your at&t bands working now? Which bands specifically?
我從使用 Tapatalk 的 Nexus 9 發送
Click to expand...
Click to collapse
I have not been able to further test as all the phones I compare to that are also AT&T ie: AT&T S6 are connected to the same Bands as me so cannot test til I get to an area where other bands are available currently. Will report back as I can test, but was hoping others can test in the mean time as well.
haroldgv said:
Thanks! So today's update:
Click to expand...
Click to collapse
You shouldn't need to restore any QCN or EFS, just re-check the bands you unchecked and it should pickup all the bands again. Also, confirm your APN is correct to be used with LTE?
Did you get ANY LTE Bands before this mod? Or you only have LTE on Band3?
You can use RAT locking to enable LTE Only rather than unchecking all the WCDMA and GSM bands. that way it'll force LTE, if it doesn't go to the Cellular Network tab and press the Preferred NETWORK to go to LTE ONLY.
sadly for me nothing happened, i have a2005 and want to add band 3 and band 20, did everything 2-3 times whats in a guide, everything went well, write process was comlete but bands didn't added
When you say didn't add, you don't see them in network guru or you see then, but unable to catch signal on them?
aurfawce said:
When you say didn't add, you don't see them in network guru or you see then, but unable to catch signal on them?
Click to expand...
Click to collapse
both, not shown in neywork guru, nor lte signal
chxei said:
both, not shown in neywork guru, nor lte signal
Click to expand...
Click to collapse
You tried to force clear in network guru? If so, when you reconnect and enter diag mode and go to DFS, press bands and LTE, press read, did the changes you made stick?
Just so ppl around here know... there is old forum about band OPT band unlocking with various trials of changing bands, which failed, due to missing RMT patch OR BUT it got MANY juicy info !!!
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
gps3dx said:
Just so ppl around here know... there is old forum about band OPT band unlocking.
( un-successful of course due to missing RMT patch OR modem ( on A2005=US) ) with juicy info.
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
Click to expand...
Click to collapse
Have you tried what we said here? And tried to see if you can band lock on 3?
I'm going to see the qcn based off of the op3 guide as well as they had to do qcn restoring.
aurfawce said:
Have you tried what we said here? And tried to see if you can band lock on 3?
I'm going to see the qcn based off of the op3 guide as well as they had to do qcn restoring.
Click to expand...
Click to collapse
not yet...it will take me some time, i'm a master's student in exam period.
nontheless, as you can see from the old forum, i'm really interested in opening LTE band 3 on my A2005.
Thanks guys! I live in Venezuela and we use band 3 for LTE and I have the EU version. I'll try this guide today
EDIT: I tried without success, I did all the process but i do not have LTE signal on Band 3. On Network Guru, Band 3 appears as supported. I tried RAT locking but It keeps without signal.
gps3dx said:
Just so ppl around here know... there is old forum about band OPT band unlocking with various trials of changing bands, which failed, due to missing RMT patch OR BUT it got MANY juicy info !!!
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
Click to expand...
Click to collapse
Thank you for the qcn files. I've tried it, and it overwrites my imei, which is expected. Then I tried to replace the imei with mine by hex editor, but flashing the modified qcn still overwrites my imei. We may get into the same trouble with op3, which is the imei encryption.