Network Signal Guru

Search This thread

Ingenium13

Senior Member
Dec 25, 2006
384
161
Pittsburgh, PA
So thinking of getting my Pixel rooted so I can run NSG. If I’m understanding this all right, currently I can get this done but will lose the squeeze thing?

If you're on the February OTA already, then yes, at least for now. If you're still on January, stay there and everything works. Or if you don't mind wiping (or if you have to wipe anyway to bootloader unlock), then revert to January and root that build.

Root itself won't cause you to lose squeeze though, it's just the vendor.img needed for NSG in February.

Hopefully it's fixed in the March OTA. It seems like Google broke a bunch of drivers in the February userdebug version of vendor.img
 
  • Like
Reactions: Jiggs82

cstark27

Senior Member
Jul 2, 2010
1,240
7,270
I can confirm the squeeze and DSDS issues on the February userdebug images. However, QPST is now working for me.

The driver is "Qualcomm HS-USB Diagnostics 903A" v2.1.2.2.
 
  • Like
Reactions: loonix and Jiggs82

cstark27

Senior Member
Jul 2, 2010
1,240
7,270
Does QPST work with DP1 ?

I didn't try (and probably not since NSG doesn't even work). Also to note, after flashing the DP1 radio image on my February Q system, I lost QPST access even after flashing the Q radio back. I can try to get it back by restoring all stock images but don't have much time right now.
 
Last edited:
  • Like
Reactions: loonix

ryaniskira

Senior Member
Mar 28, 2013
431
134
Chattanooga
I didn't try (and probably not since NSG doesn't even work). Also to note, after flashing the DP1 radio image on my February Q system, I lost QPST access even after flashing the Q radio back. I can try to get it back by restoring all stock images but don't have much time right now.

QPST? The Qualcomm flash tool?

---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------

Oh ok thx..dammit Google lol well hopefully it is fixed with official March images next month

Just flashed March yesterday, nope still does not work without the userdebug vendor image. On top of that custom kernels seem to cause issues with NSG. With Kirisakura flashed NSG refuses to work at all.
 

cstark27

Senior Member
Jul 2, 2010
1,240
7,270
Android 11 DP3, rooted with latest Magisk Canary (make sure you select Canary channel in settings before patching img), has NSG working without a "userdebug" vendor. Let's hope Google doesn't "fix" that. Also, if you need QPST, these steps seem to work reliably on A11 DP3 and April 2020 A10 patch:

adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst

Lastly, a couple people have verified that "Clear Forcings" is causing the loss of B71 after a reboot or airplane toggle (among some other bands potentially). So if you've done this already, then one of the fixes is to dial *#*#4636#*#*, Phone Information, and flip Enable DSDS, reboot. You might then revert this switch after the reboot, reboot again, then check your LTE bands in NSG to make sure they're all checkmarked.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.
 
Last edited:
  • Like
Reactions: loonix

vwp1

New member
Apr 26, 2020
1
0
I keep having to go to the Factory Image and grabbing the vendor.img from there. How did you get it from the Driver Binaries?
extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img
I can extract all the way to extract-google_devices-coral.sh, is there a tool or do i have to use linux?
With the vendor img i use i open up NSG and get N/A testing at the top and it does not pick up anything.
 
Aug 30, 2015
32
8
Is it possible with a customROM like pixel dust to make NSG to work? Since flashing the vendor doesn't work it gives me "Command not available on locked devices" error
 
Last edited:

tattoodv

New member
Jun 12, 2020
3
1
Android 11 DP3, rooted with latest Magisk Canary (make sure you select Canary channel in settings before patching img), has NSG working without a "userdebug" vendor. Let's hope Google doesn't "fix" that. Also, if you need QPST, these steps seem to work reliably on A11 DP3 and April 2020 A10 patch:

adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst

Lastly, a couple people have verified that "Clear Forcings" is causing the loss of B71 after a reboot or airplane toggle (among some other bands potentially). So if you've done this already, then one of the fixes is to dial *#*#4636#*#*, Phone Information, and flip Enable DSDS, reboot. You might then revert this switch after the reboot, reboot again, then check your LTE bands in NSG to make sure they're all checkmarked.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

I have been able to get QPST connected but when trying to download the QCN file or do anything with the Software Download (Start Client->Software Download) tool it crashes/doesnt work. It does not seem to read the phones information, and the window closes when pressing start.
 
Last edited:

Eiad Ajam

Senior Member
Jul 24, 2012
405
116
Homs
Android 11 DP3, rooted with latest Magisk Canary (make sure you select Canary channel in settings before patching img), has NSG working without a "userdebug" vendor. Let's hope Google doesn't "fix" that. Also, if you need QPST, these steps seem to work reliably on A11 DP3 and April 2020 A10 patch:

adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst

Lastly, a couple people have verified that "Clear Forcings" is causing the loss of B71 after a reboot or airplane toggle (among some other bands potentially). So if you've done this already, then one of the fixes is to dial *#*#4636#*#*, Phone Information, and flip Enable DSDS, reboot. You might then revert this switch after the reboot, reboot again, then check your LTE bands in NSG to make sure they're all checkmarked.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

Is there any chance to get volte working with mentioned steps on Android 11 beta 3?
I was trying to apply those codes with Magisk Canary installed but there is no luck with getting PDC recognizing my pixel 4 XL ....
Help pixel community please !
 

cstark27

Senior Member
Jul 2, 2010
1,240
7,270
Is there any chance to get volte working with mentioned steps on Android 11 beta 3?
I was trying to apply those codes with Magisk Canary installed but there is no luck with getting PDC recognizing my pixel 4 XL ....
Help pixel community please !

On A11 Beta 3 I know QPST works with the given ADB commands at the bottom of the quoted post, but I couldn't get QXDM to show anything but it's a pretty old version. I do not know about PDC. NSG also doesn't work as of Beta 3.
 

cstark27

Senior Member
Jul 2, 2010
1,240
7,270
Android 11

Updated instructions for Android 11 release + Magisk Canary. Much simpler this time around, thankfully. You might even get Band Locking back.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

If you encounter an issue where LTE Band 71 (and/or others) does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then switch 'Enable DSDS' then reboot.

  1. If you have NSG version under 3.7 then install the "nsg_sepolicy" Magisk Module which is attached to this post (credit: @xian1243)
  2. Install the "MagiskHide Props Config" from the Magisk repo then reboot
  3. Open a su terminal and type props
  4. Input the choice for "Add/edit custom props"
  5. Input the choice for "new custom prop"
  6. Type in ro.vendor.build.type then press enter
  7. Type in userdebug then press enter
  8. The default boot stage is fine
  9. Reboot
  10. If you get a driver error still (Pixel 4a 5G/Pixel 5) then go into Settings>Experiment and enable the "SELinux Policy" then close the app and Force Stop it

If you want to mess with QPST, then you need to enable DIAG with these steps:
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst
 

Attachments

  • nsg_sepolicy_v1.1.zip
    5.2 KB · Views: 984
Last edited:

mulencja

Member
Jan 10, 2013
30
6
@cstark27 how to get NSG 3.7 or above? Cause latest google play version is 2.12, and I'd like to get the SA/NSA force going on, and 5G RAT to choose, is NSG 3.7.X pro version only? Thanks!
 

ashu.nift

Member
Nov 12, 2009
10
2
Wow !!! Worked for me on OnePlus 5, Android 11 build (YAAP Alpha) just when I had given up all hopes on my pathetic operator keeping me stuck to the most congested band.
Thank you :)

Updated instructions for Android 11 release + Magisk Canary. Much simpler this time around, thankfully. You might even get Band Locking back.

Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.
If you encounter an issue where LTE Band 71 (and/or others) does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then switch 'Enable DSDS' then reboot.

  1. If you have NSG version under 3.7 then install the "nsg_sepolicy" Magisk Module which is attached to this post (credit: @xian1243)
  2. Install the "MagiskHide Props Config" from the Magisk repo then reboot
  3. Open a su terminal and type props
  4. Input the choice for "Add/edit custom props"
  5. Input the choice for "new custom prop"
  6. Type in ro.vendor.build.type then press enter
  7. Type in userdebug then press enter
  8. The default boot stage is fine
  9. Reboot

If you want to mess with QPST:
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket 
change usb config (file transfer, no file transfer)
wait
qpst
 
  • Like
Reactions: android-utelias

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Updated instructions for Android 11

    Old instructions:
    Here are instructions to get NSG working. You need to download the newest and re-apply the "userdebug" vendor.img every month. These instructions are given with the assumption you know that this app requires root, an unlocked bootloader, and that you know how to recover your device in case of flashing failures by using the factory images.

    Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

    • To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab. Make sure your correct device variant is chosen.
    • 2. Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
    • 3. Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
    • 4. If already rooted with stable Magisk, open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF. (Canary builds may not work.)
    • If OFF, skip to #13.
    • If ON, then uncheck Preserve AVB 2.0/dm-verity then press Install>Direct Install, reboot. Skip to #13.
    • 5. If you are already rooted with Canary builds, or are having bootloop issues, remove -w flag from factory image bat/sh then re-flash factory image
    • 6. Boot into OS, install latest stable Magisk APK
    • 7. Open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF
    • 8. Patch stock boot.img
    • 9. adb reboot-bootloader
    • 10. fastboot flash boot <magisk_patched.img>
    • 11. Reboot
    • 12. Open Magisk Manager, make sure dm-verity option is still off
    • 13. Reboot to fastboot (adb reboot-fastboot) - you should see "fastbootd" in red at the top
    • 14. Flash the vendor.img you extracted (fastboot flash vendor location/of/vendor.img)
    • 15. When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
    • 16. If you cannot boot or get a corrupted boot message, start over at #5

    If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app a couple times as needed, or clear app data as a last resort.

    If you encounter an issue where LTE Band 71 does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then turn on Enable DSDS then reboot.

    As of April 2020 patch or Android 11 DP3, you might be able to see your device in QPST with these commands:
    Code:
    adb shell
    su
    resetprop ro.bootmode usbradio
    resetprop ro.build.type userdebug
    setprop sys.usb.config diag,diag_mdm,adb
    diag_mdlog
    cancel (ctrl+c) once it starts to "hang" at failed to open diag socket 
    change usb config (file transfer, no file transfer)
    wait
    qpst
    7
    Android 11

    Updated instructions for Android 11 release + Magisk Canary. Much simpler this time around, thankfully. You might even get Band Locking back.

    Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.

    If you encounter an issue where LTE Band 71 (and/or others) does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then switch 'Enable DSDS' then reboot.

    1. If you have NSG version under 3.7 then install the "nsg_sepolicy" Magisk Module which is attached to this post (credit: @xian1243)
    2. Install the "MagiskHide Props Config" from the Magisk repo then reboot
    3. Open a su terminal and type props
    4. Input the choice for "Add/edit custom props"
    5. Input the choice for "new custom prop"
    6. Type in ro.vendor.build.type then press enter
    7. Type in userdebug then press enter
    8. The default boot stage is fine
    9. Reboot
    10. If you get a driver error still (Pixel 4a 5G/Pixel 5) then go into Settings>Experiment and enable the "SELinux Policy" then close the app and Force Stop it

    If you want to mess with QPST, then you need to enable DIAG with these steps:
    Code:
    adb shell
    su
    resetprop ro.bootmode usbradio
    resetprop ro.build.type userdebug
    setprop sys.usb.config diag,diag_mdm,adb
    diag_mdlog
    cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
    change usb config (file transfer, no file transfer)
    wait
    qpst
    2
    Do any of the kernels properly support NSG's unreasonable requirements?

    Haven't been able to get it working on any Pixel phone for months. What changed?

    Edit: Dev says it's not supported yet.
    2
    What is the main benefit to using this app for everyone trying to get it to work? There is an app called network cell phone info lite that is similar to this tool.

    Display of actual bands/cells being used for carrier aggregation, MIMO (4x4, 2x2, etc) status along with actual RANK, band/EARFCN/RAT/cell locking, access to event signalling to see what the phone is reporting as far as capabilities, etc. It reads directly from the modem, not the Android API's which has more limited access to the data.
    2
    Technically, it can support such combos. But again, I can't confirm that it does it out of the box since I don't have an active Sprint sim.



    You might reach out to the developers and see if they can help you out. I only use a single sim.

    It was actually the devs who told me about this thread in an email. I did reply back to them with the issue though.