Hi everyone, I have finally figured out how to get proper diag support on our device. This will allow us to use QPST and such.
It will be a pretty short guide as it's quite simple, but it does enable us to do a whole lot of things we couldn't do before.
Downloads
* QPST
* AsusVoLTE app
Prerequsities
* Both methods require root, at least initially. There are several threads on how to do that, so look those up if you need help.
USB method
Downloads
* Qualcomm USB drivers
Step 1
Install the drivers and QPST from above. If you've already done this from my VoLTE/VoWiFi guide there's no need to reinstall them.
Step 2
When you've done that, install the AsusVoLTE app and connect the phone to the computer and open up it up. Press the Enable DIAG button, and you should hear/see a new device attaching. This should hopefully be enough, but if not, try rebooting the phone. If that still doesn't work try the Remote method below.
Remote method
Prerequsities
* Both your computer and phone have to be connected to the same network. You may also need to allow port 2500 in your firewall.
Step 1
Start by downloading and installing QPST from the link above, no drivers or such required. If you've already done this from following my VoLTE/VoWiFi guide you can safely skip this step.
Step 2
Now run QPSTConfig.exe from the bin folder of the QPST install and wait for it to open up. Head to the IP Server tab and tick the Accept client connections box - we need to do this as we will be connecting to QPST remotely. Take a note of the Server IP Address (this should simply be the ip address of your computer), and potentially the Server Port below if you have changed it from the default value of 2500.
Step 3
Open up the AsusVoLTE app on the phone, and enter the IP address from the Server IP Address in the field, and optionally, change the port number.
After this you can simply press the Start button.
Now that you have done this, you should, momentarily, see a new port appear in QPST Configuration under the Ports tab with a Port number like COM30001 and the Phone column should hopefully say SDM855 (0). If you do see this you are good to go! You can now start exploring EFS and such.
Troubleshooting
Some people have had issues connecting to the diag port, with EfsTools from the VoLTE guide returning BadCmd and QPST not working either. If you have this problem, try restoring modem settings by running this in bootloader (adb reboot bootloader, or press volume up while rebooting):
Warning: This may cause issues with no service for some, do not run this without a full backup of all of the partitions (in particular, modemst1, modemst2, fsg and fsc) on the device!
Code:
REDACTED because people still run these commands without taking a backup
Do note that this will reset any changes you may have done (like enabling VoLTE through PDC).
Thanks to @xbamaris1` for troubleshooting this with me, and for confirming this worked!
Let me know if this has worked for you, and if you have any questions!
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
dennis96411 said:
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
Click to expand...
Click to collapse
I had this problem to until I realized that its network based and your phone should be connected to your WIFI (at least thats what fixed it for me).
However, Despite this, i am still not getting data from it. COM30001 from an IP of 192.168.1.211 (which is my phone) and it is still not able to browse data from QPST
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
{
"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"
}
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update 2: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
xbamaris1` said:
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
Click to expand...
Click to collapse
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
dennis96411 said:
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
Click to expand...
Click to collapse
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
xbamaris1` said:
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
Click to expand...
Click to collapse
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
dennis96411 said:
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
Click to expand...
Click to collapse
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
xbamaris1` said:
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
Click to expand...
Click to collapse
Which version of QPST Configuration do you have? This is mine.
dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
It's not necessary, no - if you get it to show up in usb you won't need to do any of this. I could, however, never get the phone to connect in usb mode - it just shows as No phone.
I will try those drivers you posted and update the guide.
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
Oh did those drivers make a difference for you?
HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
How to change imei with EFS
QPST via remote using your guide worked for me. I am able to use EFS Explorer. Thank you @HomerSp!
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
XavierBK said:
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
Click to expand...
Click to collapse
Magisk (the root method) hides itself from bank apps and such, but you can do a SafetyNet check in the magisk manager app, and if that passes so you should be good to go.
Only thing you won't be able to get with the bootloader unlocked is HD video in Netflix and Amazon video.
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
ChronoReverse said:
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
Click to expand...
Click to collapse
Yes indeed, but we have yet to find a way to enable additional bands. We are working on it though, so hopefully we'll have something soon.
Hi, can we use QPST to unlock LTE band on 8G/128G version?
Related
I'm using burnt-droid 2.6.32.25 kernal rom rooted and vpn connections and i can't get vpn to work.
http://code.google.com/p/get-a-robo...=Filename+Summary+Uploaded+Size+DownloadCount
it downloaded kun.to fine and i setup my connection
ipsec gateway - ip
ipsec id = group name
ipsec secret = secret
username = username
password = password
tried pass+token digits checked and unchecked
can't seem to connect. has anyone gotten this to work on their evo?
Does it say that it connects? When I tried VPN Connections, it would connect but not send any traffic over the VPN.
There's a couple of patches on the website for vpnc-script Here for example that fixes that problem. Otherwise can you give more details? What error messages do you get, any debugging information available (logcat, etc)?
noxipoo said:
I'm using burnt-droid 2.6.32.25 kernal rom rooted and vpn connections and i can't get vpn to work.
http://code.google.com/p/get-a-robo...=Filename+Summary+Uploaded+Size+DownloadCount
it downloaded kun.to fine and i setup my connection
ipsec gateway - ip
ipsec id = group name
ipsec secret = secret
username = username
password = password
tried pass+token digits checked and unchecked
can't seem to connect. has anyone gotten this to work on their evo?
Click to expand...
Click to collapse
Hi,
I am having this issue as well, but could not find the path to install this script nivron referred to, on the evo.
I am connecting and I can see that I have the tun0 interface and an IP address assigned, but I cannot get applications to use the tunnel.
I even tried to pass the --script flag to the script on the sdcard, but would not connect then.
Any info would be appreciated.
-- Ray
Running :
MikFroYo-v4.4
netarchy-toastmod-4.3.2-cfs-nosbc-havs-less-universal
I asked about this month ago and I would like to see this working.
It seems to work as far as making connections but I cannot get the traffic to use the tunnel.
I did see a post about clearing the ip tables, but not really sure how.
-Ray
Well first you need to make sure you have a kernel that has the correct tun.ko file (its kernel specific) Netarchy has it, I think Ziggy has it. Its in the /system/lib/modules
Second you need to decrypt your group password. Check google for cisco decrypt group password.
Enter all your info in. You should be able to connect.
Once you are connected you maybe able to log in your computer once but then it may not pop up the computer after. you need to run these scripts
I use scripter
to reset 3g connection
busybox ip rule del from all lookup gprs
to reset wifi
busybox ip rule del table wifi
Hope that works, if not pm me
Well I don't have tun.ko ? How ?
{
"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"
}
erik077 said:
Well I don't have tun.ko ? How ?
Click to expand...
Click to collapse
Have you tried another Kernel?
No. I am beginner and didn't play with that
erik077 said:
No. I am beginner and didn't play with that
Click to expand...
Click to collapse
nand backup, then try a netarchy http://forum.xda-developers.com/showthread.php?t=719763
Make sure you wipe dalvik and cache before installing
I just removed amon_ra because nandroid backup does not work for me. Working for hour + and screen gets full of dots but no backups are made. Anyway software info says : Karnel version: 2.6.32.17-ck2CFS and [email protected] #011011
I am running Calkulin ROM ... should I try with ROM Manager backup?
so I got it to work by running the commands to clear the gprs and wifi tables (thanks!).
But only the first of my two connections is working. I just disconnected and tried the other of my VPN connections and I keep getting an error when running the script now.
RTNETLINK answers: No such file or directory
I can reconnect to the first, but not the other.
Going to try a reboot and try the second connection.
-Ray
erik077 said:
I just removed amon_ra because nandroid backup does not work for me. Working for hour + and screen gets full of dots but no backups are made. Anyway software info says : Karnel version: 2.6.32.17-ck2CFS and [email protected] #011011
I am running Calkulin ROM ... should I try with ROM Manager backup?
Click to expand...
Click to collapse
When using nand backup, wipe the dalvik cache before the backup.
Ziggys should work for you
It seems like it is still pretty buggy to make connections with VPNC.
I can connect and disconnect, but I need to cycle either 3G or WiFi in order to reset. That is not too bad on its own, but I was having issues accessing the local LAN on another of my connections, so not very consistent.
I also tried the WiFi hotspot on 3G while vpn'd and could not get my laptop to connect to the internal website that I could connect to on the phone browser.
Thanks for the help.
I don't think that OpenVPN can connect to a cisco ipsec vpn that uses group names yet, or can it?
-Ray A.
ultra74 said:
It seems like it is still pretty buggy to make connections with VPNC.
I can connect and disconnect, but I need to cycle either 3G or WiFi in order to reset. That is not too bad on its own, but I was having issues accessing the local LAN on another of my connections, so not very consistent.
I also tried the WiFi hotspot on 3G while vpn'd and could not get my laptop to connect to the internal website that I could connect to on the phone browser.
Thanks for the help.
I don't think that OpenVPN can connect to a cisco ipsec vpn that uses group names yet, or can it?
-Ray A.
Click to expand...
Click to collapse
Correct, I dont believe OpenVPN will connect to Cisco VPN using IPSec.
I am not sure I understood what you are saying but instead of cycling through Wifi and 3g, run the script. Using the scriptor I just click it.
The easiest way to connect to a Cisco VPN is to use a kernel that has the module built in. I've tried a lot of kernels and only Netarchy's had it built-in. Flash whatever ROM you like, then flash one of Net's kernels. Install the VPN connections app and configure it for your VPN.
I admin a Cisco VPN at work, and this has worked for me.
Sent from my PC36100 using XDA App
dwertz,
when I run the script the first time with scriptor, it goes fine. I make my connection and go.
Because I do work between two separate networks, I need to disconnect and connect to the other network. This does not work after I have connected to another network already. I can disconnect, disable/enable VPN, etc. The other connection says connection failed.
Running your commands again, gives me the error "RTNETLINK answers: No such file or directory".
The only thing that works, is to turn off then on 3G or WiFi then the scrips will not fail and I can then connect to the other network fine. It is like cycling the radio recreates a file and the script can clear it.
jerich007,
Yes, I tried the install and configure, and was able to connect, but was not able to get the traffic to use the tunnel, until I ran the script from dwertz, but with mixed results as I stated above.
I saw an entry from the second post by nivron that mentioned the vpnc-script was modified to fix this problem, but I was unable to find the location on android where I could replace the script for the modified one.
ultra74 said:
dwertz,
when I run the script the first time with scriptor, it goes fine. I make my connection and go.
Because I do work between two separate networks, I need to disconnect and connect to the other network. This does not work after I have connected to another network already. I can disconnect, disable/enable VPN, etc. The other connection says connection failed.
Running your commands again, gives me the error "RTNETLINK answers: No such file or directory".
The only thing that works, is to turn off then on 3G or WiFi then the scrips will not fail and I can then connect to the other network fine. It is like cycling the radio recreates a file and the script can clear it.
jerich007,
Yes, I tried the install and configure, and was able to connect, but was not able to get the traffic to use the tunnel, until I ran the script from dwertz, but with mixed results as I stated above.
I saw an entry from the second post by nivron that mentioned the vpnc-script was modified to fix this problem, but I was unable to find the location on android where I could replace the script for the modified one.
Click to expand...
Click to collapse
Did you try running the script before connecting to the different network? When you connect to a network it gets the ip table. When you try to connect to another network you need to clear the ip tables thus running the script.
Also I dont think DNS works so you might need to hard type the internal web address.
dwertz,
Yes, it seems to work correctly when connecting to the newer ASA, but the older vpn concentrator is not letting me access the remote lan intranet. Not sure exactly where the problem with that one is.
I do get dns resolution for the ASA network, but we did configure the dns settings in the vpn group in the asa, so that might be why. I will try the direct IP address for the other network.
I know that the cisco vpnclient for my laptop has an option for "Allow Local LAN Access", but not sure how that changes the client configuration.
Are you able to use wireless tether or the "modified" hotspot app while connected to the vpn?
-Ray
ultra74 said:
dwertz,
Yes, it seems to work correctly when connecting to the newer ASA, but the older vpn concentrator is not letting me access the remote lan intranet. Not sure exactly where the problem with that one is.
I know that the cisco vpnclient for my laptop has an option for "Allow Local LAN Access", but not sure how that changes the client configuration.
Are you able to use wireless tether or the "modified" hotspot app while connected to the vpn?
-Ray
Click to expand...
Click to collapse
I have never have tried to use wireless tether and vpn to get to my network. I wireless tether and VPN through my Mac but not the phone
Any one know how to use adb over bluetooth in this device ??
I tried 'pand' command from terminal and this doesn't work.
impossible...
try this, for linux pc.
http://fomori.org/blog/blog/2011/12/05/android-adb-over-bluetooth/
nfs1mw said:
try this, for linux pc.
http://fomori.org/blog/blog/2011/12/05/android-adb-over-bluetooth/
Click to expand...
Click to collapse
I already tried this but didn't work
pand gave some error "Failed to open control socket: Address family not supported.........."
then I thought this error may be due to lack of bluetooth module.so I compiled "bluetooth.ko" and loaded.
then the error disappeared but the thing didn't worked..
I think my bluetooth device is not detected by the module because '/sys/class/bluetooth' directory was empty
So still now i am seeking for a solution....
harish2704 said:
I already tried this but didn't work
pand gave some error "Failed to open control socket: Address family not supported.........."
then I thought this error may be due to lack of bluetooth module.so I compiled "bluetooth.ko" and loaded.
then the error disappeared but the thing didn't worked..
I think my bluetooth device is not detected by the module because '/sys/class/bluetooth' directory was empty
So still now i am seeking for a solution....
Click to expand...
Click to collapse
Well it actually is not impossible. I already had it working.
But your phone shouldn't have any issues with BLUETOOTH PAN profile. If having any issues maybe don't expect this to work. And it need not have mobile internet for both phone or PC. Its just phone-to-pc direct connection, no need for internet access point. Lets think there is no mobile internet enabled for the below HOW-to.
Ok here u go. Pair your phone and PC. Initiate BT PAN connection from PC to phone (right click on bluetooth device and select connect-via-access-point). This creates a local connection. Now u need to know local IP address on phone side. Install terminal emulator application and issue the command "netcfg" which lists all connections active. Note the IP address of the connection bnep0 (say ww.xx.yy.zz)
Now open your PC Command prompt and type the command
adb connect ww.xx.yy.zz:5555
it says connected. Enjoy.
Same goes for wireless connection through LOCAL WIFI (WLAN) without internet access point.
Lets think mobile internet is off.
Turn on the portable Wifi Hotspot on the android device and make ur PC to connect to that hotspot. Note down the local ip address of the connection. Then open pc command prompt and type same command as above
adb connect ww.xx.yy.zz:5555
connected . enjoy.
IMPORTANT: First of all u need to enable ADB OVER NETWORK option in phone. This option is present in latest roms like cm7.2 or cm9 or ics roms. If this option is not available u need to find terminal alternatives for this.
Noob here.
Is there any detail guide to do this ???
Here is what I’ve done to manually update the PRL on my new G2. I don’t want to debate the reasons for this. But here’s one way to do it without rooting.
NOTE: This method, to obtain your MSL, only works on the the ZV8 and ZCA software versions. They changed something in ZVC and later versions.
Note: The easiest way to get MSL/SPC code is to just dial ##443336772# on your dial pad and you don't even have to be rooted.
Note: SPC is your MSL. They are the same things.
Note: All this was done on Windows 7-64 bit.
Part 1, Connecting the phone in diagnostics mode:
Install USB drivers. http://www.lg.com/us/support-mobile/lg-LGD801BK. Use the Tmobile D801 USB drivers since it is the same as the AT&T drivers and the LS980 page only had directions to update drivers via the LG Mobile Tools.
On the phone, enable USB debugging in developer options (tap the build # in Settings > About Phone > Software Information, 7 times to enable developer options).
Dial ##Diag# (##3424#) enable diagnostics mode.
Connect phone, select "charge only"
Check windows device manager to see if you have a com port. It should be listed as “LGE AndroidNet USB Serial Port (COMxx) (xx=port #).
Part II, Get your SPC/MSL:
Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
Open Basic Flasher, password is oriax123.
In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)” and ensure the COM port on the drop down menu next to the "Scan" button matches the COM port listed in the display section (see attached screen shot). If it does not, manually select the correct COM port in the drop down menu that matches the LGE device.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG"
F. Click “Read SPC”. The SPC field should populate with your SPC.Note: Stop here and disable the DIAG mode (dial ##3424# and select disabled) if all you want is your SPC/MSL.
Part III, Update your PRL:
Click the “…” next to the PRL field and browse to the file location of the PRL you want to load, select the PRL. In Basic Flasher:
A. Click the “Send SPC” button. The dialog will show “Device Unlocked”.
B. Click the “Provision” button. The dialog will show that the MDN, MIN and SID have been written and the phone will reset.
C. On the phone, go to Settings > About Phone > Status and see if it shows you new PRL number.
D. On thee phone dial ##3424# and disable the DIAG mode.
I was also able to connect the phone to DFS (after getting my MSL with Basic Flasher). But didn’t have success writing the PRL in DFS. I used this 16 digit password EBB4EDB0B8B8C2BD in DFS. It reported “Device Unlocked” but if I tried to write anything in DFS the com port would lock up. Not sure what the issue there is, perhaps it would work if rooted.
Listing of Sprint PRLs along with descriptions http://forum.xda-developers.com/showthread.php?t=1880781.
rich_e said:
Listing of Sprint PRLs along with descriptions http://forum.xda-developers.com/showthread.php?t=1880781.
Click to expand...
Click to collapse
Thanks for sharing the steps. Did you have any problems enabling diagnostics mode prompting for SPC?
Dial ##Diag# enable diagnostics mode. * Newbie Post. If phone is not activated first, SPC will be prompted.*
dryw00d said:
Thanks for sharing the steps. Did you have any problems enabling diagnostics mode prompting for SPC?
Dial ##Diag# enable diagnostics mode.
Click to expand...
Click to collapse
Nope, no problem with accessing the menu.
When i first tried, it was showing the COM in basic flasher, now adb has installed and now i can't get COM showing so i can't access the info for my MSL
I can't get this thing to scan for my device. I have the adb drivers installed already but when I try to Scan in Basic Flasher tool, it keeps telling me "No Device Found". I even opened up a command prompt with adb and did a "adb devices" query and my device shows up.
Anyone else having issues or advice or what to do?
Slightly off-topic, is there a good way with ROOT to get your MSL? For some reason, getprop ril.MSL doesn't work in Terminal...
droidjosh said:
When i first tried, it was showing the COM in basic flasher, now adb has installed and now i can't get COM showing so i can't access the info for my MSL
Click to expand...
Click to collapse
Mine shows the ADB interface and the com port in device manager too but not having any issue finding the com port in Basic Flasher. Maybe uninstalling and re-installing the drivers would help.
WhiteZero said:
Slightly off-topic, is there a good way with ROOT to get your MSL? For some reason, getprop ril.MSL doesn't work in Terminal...
Click to expand...
Click to collapse
I added a step to set method field to "LG" before clicking the Read SPC button. I just noticed that I forgot that step when I repeated the process for the screen shot and got an SPC error with it set to "NV". Try reading it again, can think of any reason why it wouldn't work with root.
ericdabbs said:
I can't get this thing to scan for my device. I have the adb drivers installed already but when I try to Scan in Basic Flasher tool, it keeps telling me "No Device Found". I even opened up a command prompt with adb and did a "adb devices" query and my device shows up.
Anyone else having issues or advice or what to do?
Click to expand...
Click to collapse
If you don't have the com port listed under device manager it won't work. You have to be in diagnostics mode (dial ##3424#) and have the USB connection on the phone set to "Charge only" for the ports to show up.
rich_e said:
Mine shows the ADB interface and the com port in device manager too but not having any issue finding the com port in Basic Flasher. Maybe uninstalling and re-installing the drivers would help.
Click to expand...
Click to collapse
I've uninstalled and reinstalled multiple times. still won't show it. It did the first time, before windows downloaded drivers when i plugged the phone in.
rich_e said:
If you don't have the com port listed under device manager it won't work. You have to be in diagnostics mode (dial ##3424#) and have the USB connection on the phone set to "Charge only" for the ports to show up.
Click to expand...
Click to collapse
I finally got it to work. I didn't have Diag mode enabled. I guess I totally skipped Part 1. However for Part II your procedure needs some additional steps. Suggested revision of your steps. Let me know if you like and if so maybe add that to the OP.
Part 2, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)”.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
ericdabbs said:
I finally got it to work. I didn't have Diag mode enabled. I guess I totally skipped Part 1. However for Part II your procedure needs some additional steps. Suggested revision of your steps. Let me know if you like and if so maybe add that to the OP.
Part 2, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/showthread.php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)”.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
Click to expand...
Click to collapse
I made the changes to the OP as recommend. Thanks!
rich_e said:
I made the changes to the OP as recommend. Thanks!
Click to expand...
Click to collapse
A few more slight changes in bold based on feedback from people that had some difficulty when trying out this procedure in Part 2.
In part 1, I updated the link and reference to the USB drivers to use the AT&T/Tmobile LG G2 drivers since they are made for the LG G2 vs. referencing Sprint Optimus G LS970 drivers. I personally use the Tmobile D801 LG G2 USB drivers for the LG G2 and it works fine on the Sprint model.
Part 1, Connecting the phone in diagnostics mode:
1. Install USB drivers. http://www.lg.com/us/support-mobile/lg-LGD801BK. I used the Tmobile D801 USB drivers since it is the same as the AT&T drivers and the LS980 page only had directions to update drivers via the LG Mobile Tools.
2. On the phone, enable USB debugging in developer options (tap the build # in Settings > About Phone > Software Information, 7 times to enable developer options).
3. Dial ##DIAG# (##3424#) enable diagnostics mode.
4. Connect phone, select "charge only"
5. Check windows device manager to see if you have a com port. It should be listed as “LGE AndroidNet USB Serial Port (COMxx) (xx=port #).
Part II, Get your MSL:
1. Get Basic Flasher http://forum.xda-developers.com/show....php?t=2394499. (Great tool! Please thank the poster "bigfdaddy2” and make a donation at tiny.cc/oriax123donate if you like it.)
2. Open Basic Flasher, password is oriax123.
3. In Basic Flasher:
A. Click the “Scan” button.
B. Select the “LGE AndroidNet USB Serial Port (COMxx)” and ensure the COM port on the drop down menu next to the "Scan" button matches the COM port listed in the display section. If it does not, manually select the correct COM port in the drop down menu that matches the LGE device.
C. Click the "Connect" button.
D. Click the “Read Device” button. The screen should populate with you MDN, MIN and SID.
E. Under Method, select "LG".
F. Click “Read SPC”. The SPC field should populate with your SPC.
ericdabbs said:
A few more slight changes in bold based on feedback from people that had some difficulty when trying out this procedure in Part 2.
Click to expand...
Click to collapse
Thanks again! I've seen people having problems with the drivers and the default behavior of the program to start with the lowest numbered com port. I hope these changes will make it easier for people to get their MSLs.
rich_e said:
Thanks again! I've seen people having problems with the drivers and the default behavior of the program to start with the lowest numbered com port. I hope these changes will make it easier for people to get their MSLs.
Click to expand...
Click to collapse
Thanks for updating the OP. Although I notice it says in the OP ##Diag# (##3434#) instead of (##3424#).
Btw I took your guide and made a sticky on another forum but made the instructions more generalized.
http://s4gru.com/index.php?/topic/5022-easy-method-to-obtain-your-msl/
ericdabbs said:
Thanks for updating the OP. Although I notice it says in the OP ##Diag# (##3434#) instead of (##3424#).
Btw I took your guide and made a sticky on another forum but made the instructions more generalized.
http://s4gru.com/index.php?/topic/5022-easy-method-to-obtain-your-msl/
Click to expand...
Click to collapse
I fixed the typo. Thanks for the cross-post and credit too!
rich_e said:
I fixed the typo. Thanks for the cross-post and credit too!
Click to expand...
Click to collapse
No problem since your guide has helped many folks obtain their MSL and I was able to verify that this method works to get my MSL. I am all for helping my Sprint brothers and sisters access their MSL to triband LTE testing.
If you are curious I did some B41 LTE testing last night and posted some screenshots in this thread below:
http://forum.xda-developers.com/showthread.php?t=2524824
I also did some further B41 LTE testing today on another tower and I almost hit 60 Mbps!!!!! Talk about making use of that Clearwire 2.5 GHz spectrum.
Deleted, found out you have to turn off anti virus to let this through, boy is this easy to use :good:
It is a very newbie question, what is the advantage of updating PRL, will I get more signal and speed on the different Roaming, at work I don't have any signal if update it to verizon Roming PRL, will I get good signal, please help me to find out.
thanks for your help.
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.
Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Bluetooth appears already fixed/correct. (Also I haven't noticed my paired bluetooth devices loosing pairing..)
FunkiBluDawg said:
Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Click to expand...
Click to collapse
Great! Also good that Bluetooth is correct. Did not pair anything yet but good to know there won't be similar problems.
Idakis said:
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.
Click to expand...
Click to collapse
thanks a lot, worked like a charm. I really needed that fix as i put mac control on my router
Meta_maui_db_inconsistent
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?
66krieger said:
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?
Click to expand...
Click to collapse
Sorry for my late answer.
Double check step 3) you need the correct file from the correct stock rom for your device.
If that still doesn't work I would try reflashing the bootloader preloader (only) from stock ROM and try again.
It should work.
I'm not having any luck with my device on windows 10.
Whenever I try to connect my device to windows via usb, a pop appears - (USB device not recognized-the last USB device you connected to this computer malfunctioned ,and Windows does not recognize it) .
I've also tried to clean up my usb drivers and re-install MTK preloader.
Any advice how I might fix this?
File APDB_MT6797_S01_alps-mp-m0.mp9_W16.48?
Hi,
Where do I find the file "APDB_MT6797_S01_alps-mp-m0.mp9_W16.48"?
It's not available on Google.
Thanks!
Thank q so much .. Fix it.
Hi everyone
i my friend gave me his firestick 4k the other day because he has managed to mess it up big time
He said that he followed a tech docter youtube video to sideload an app to remove bloatware, after being successful at this, he then used an app that clears your cache and closes all the apps for you, from what i can understand it sounded like the app "cleanmaster"
after doing that he immediately lost his internet connection, he said that there wasnt even a network section anymore, just a troubleshooting option, he then factory reset his stick but this didnt solve anything
ive got the stick setup now, ive looked in the network section and he was right, theres nothing, even in the my fire tv section where you can see the ip/mac/ssid etc, they all say "not connected"
ill attach pictures
Im willing to flash this somehow, or root it, install cfw anything, please help!
Try:
Select Settings > Network from the Fire TV menu, then Play/Pause on your remote, and follow the recommended steps.
If that doesn't work maybe reset the stick again.
I know one of the settings in the debloat tool turns off the ability to see new networks, resetting should have reenabled that switch.
carpenter940 said:
Try:
Select Settings > Network from the Fire TV menu, then Play/Pause on your remote, and follow the recommended steps.
If that doesn't work maybe reset the stick again.
I know one of the settings in the debloat tool turns off the ability to see new networks, resetting should have reenabled that switch.
Click to expand...
Click to collapse
Thanks for replying, pressing play/pause does nothing, as you can see there is nothing on the network page at all except the troubleshoot option
Factory reset doesn't work at all, doing a factory reset from the my fire tv section just makes you go back to the settings menu, using the back and right button combo does nothing either, even if you wait for the countdown to end
When he gave me the stick he had already factory reset it so there are no apps on here at all including this bloatware one you mentioned, nothing
stickpirate77 said:
Doing a factory reset
there are no apps on here at all including this bloatware one you mentioned, nothing
Click to expand...
Click to collapse
Head to the unlock, root, twrp, unbrick thread here :
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
If you have a stick that is from 2019 you can fix it by unlocking it and installing another firmware. This will also give you root privileges.
Regards
Bertonumber1 said:
Head to the unlock, root, twrp, unbrick thread here :
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
If you have a stick that is from 2019 you can fix it by unlocking it and installing another firmware. This will also give you root privileges.
Regards
Click to expand...
Click to collapse
How can I do this please? Keep in mind the stick doesn't display an IP address
stickpirate77 said:
How can I do this please? Keep in mind the stick doesn't display an IP address
Click to expand...
Click to collapse
This post may explain better mate :
[NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS)...
forum.xda-developers.com
It doesn't have to show ip address, follow the thread carefully. It involves opening up the stick, connecting it to pc (via the power cable) and shorting a resistor.
This will unlock the stick and let you flash brand new firmware. It's the only way to do it if your factory reset isn't working I'm afraid.
Regards
Thankyou for this fantastic response, when I've got spare time and the balls to try it I'll dive in, seems complicated but I'll give it a good go
stickpirate77 said:
Thankyou for this fantastic response, when I've got spare time and the balls to try it I'll dive in, seems complicated but I'll give it a good go
Click to expand...
Click to collapse
don't unlock your stick, use any of the method
Method 1:
reinstall the app again and turn on wifi, the wifi on the stick is disabled.
Method 2:
take out your stick, connect to your pc
wait for it boot
enter
adb devices
if it says "unauthorized"
press "Down" on remote two timesand press "select" to authorize your pcwhen it says "device"
enteradb shellsvc wifi enable
if you get "killed" error then go for method 3
Unplug your stick from PC and connect to your TV.
Method 3
Install the apk on your stick, then click on "Enable"
It will also tell you if your Wifi is disabled or not.
This app can TURN ON and TURN OFF the WIFI
Here's a proof
Hi I'm trying method 2 at the moment, but if it doesn't work how do I install the WiFi enabler APK without having WiFi?
stickpirate77 said:
Hi I'm trying method 2 at the moment, but if it doesn't work how do I install the WiFi enabler APK without having WiFi?
Click to expand...
Click to collapse
you can install the apk using adb
adb install "Wifi Enabler.apk"
Legendary! It worked! Thankyou so much, how do I mark this thread as solved? I'm new to this forum
stickpirate77 said:
Legendary! It worked! Thankyou so much, how do I mark this thread as solved? I'm new to this forum
Click to expand...
Click to collapse
You can close the thread but you'll have to contact the forum maintainer, which isn't necessary, just click the under post #8.
SweenWolf said:
You can close the thread but you'll have to contact the forum maintainer, which isn't necessary, just click the under post #8.
Click to expand...
Click to collapse
I've run into the next problem, I've installed the debloat tool, I've re enabled everything to try and clean up the mess my friend made, but when I try and deregister the stick it just goes straight back to settings, is there anything else I can do here? (he said I can have the stick now as he has a new one)
stickpirate77 said:
I've run into the next problem, I've installed the debloat tool, I've re enabled everything to try and clean up the mess my friend made, but when I try and deregister the stick it just goes straight back to settings, is there anything else I can do here? (he said I can have the stick now as he has a new one)
Click to expand...
Click to collapse
What do you mean be goes back to settings?
SweenWolf said:
What do you mean be goes back to settings?
Click to expand...
Click to collapse
I click on settings, my account, Amazon account, deregister, deregister.....
Nothing happens and I'm kicked back to the settings bar highlighting my account again
stickpirate77 said:
I click on settings, my account, Amazon account, deregister, deregister.....
Nothing happens and I'm kicked back to the settings bar highlighting my account again
Click to expand...
Click to collapse
Look, sorry for the issues, you have to do some steps.
Connect your pc to stick (using wifi)
adb connect IP:5555
then adb shell
then enter
pm list packages -d
And send me the output
SweenWolf said:
Look, sorry for the issues, you have to do some steps.
Connect your pc to stick (using wifi)
adb connect IP:5555
then adb shell
then enter
pm list packages -d
And send me the output
Click to expand...
Click to collapse
I typed ADB connect IP:5555
it said unable to connect
stickpirate77 said:
I typed ADB connect IP:5555
it said unable to connect
Click to expand...
Click to collapse
Reboot your stick (Long press "Play/Pause + Select" for few seconds)
Try deregistering, is result is same, go to developers options, turn it off and then on again.
Go to network section of the stick copy the ip address.
Then go to your pc, (make sure your Stick and PC are on same wifi network)
Enter
adb disconnect
adb connect ip:5555
Here ip is the ip address of your stick
Eg adb connect 192.168.43.123:5555
It should connect
stickpirate77 said:
I typed ADB connect IP:5555
it said unable to connect
Click to expand...
Click to collapse
Got it to connect
stickpirate77 said:
Got it to connect
Click to expand...
Click to collapse
In the shell
Enter
pm enable com.amazon.tv.oobe
pm enable com.amazon.aria
Then reboot and you will be able to deregister
Main one is oobe but enable both of them