yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Questions & Answers] cstark27:
It's very strange. I've heard from 5 others it has worked so far. I am on a Windows machine though I don't think that should really matter. I simply flashed the debug vendor img over my January patched 4XL (using factory images).

I also unpacked the img files while trying to see if I could put together a Magisk module (which was unsuccessful) and can confirm in the build.prop, this property is definitely set to userdebug as well as 'build.tags':

ro.vendor.build.tags=dev-keys

ro.vendor.build.type=userdebug

Also in /vendor/etc/init/hw/init.sm8150.diag.rc should look like: https://android.googlesource.com/de.../heads/master/init.hardware.diag.rc.userdebug

Not like https://android.googlesource.com/device/google/coral/+/refs/heads/master/init.hardware.diag.rc.user

For setprop, resetprop should work but it still won't make NSG work unfortunately.
[Google Pixel 4 XL Questions & Answers] hongfa1380:
can not fastboot to my pixel4

D:\android rom\pixel4\platform-tools>fastboot flash vendor vendor.img

Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 1.190s]

Writing 'vendor_b' FAILED (remote: 'Partition should be flashed in fastbootd')

fastboot: error: Command failed

flame-qq1b.200105.004-factory-1ebb473b
[Google Pixel 4 XL Questions & Answers] cstark27:
You have to be in "fastbootD" which is a screen that has in red at the top, fastbootd. You can boot to the fastbootd from the bootloader screen by giving 'fastboot reboot fastboot'
[Google Pixel 4 XL Questions & Answers] hongfa1380:
Thank you for reply, I flash flame-qq1b.200105.004 both sloth 11. Set factory. Than fastboot vendor img and restart. It freez at Google logo.
[Google Pixel 4 XL Questions & Answers] cstark27:
You can fix most boot freezes by flashing the factory image. If you are not familiar with flashing commands and practices it best to avoid tinkering. Also, please make sure your fastboot tools are up to date as linked and mentioned in the "instructional" post. You need to double check with 'adb --version' and 'fastboot --version'

>Version 29.0.2-5738569

>Installed as C:\platform-tools\adb.exe
[Google Pixel 4 XL Questions & Answers] hongfa1380:
D:\android rom\pixel4\platform-tools_r29.0.5-windows>fastboot --version

fastboot version 29.0.5-5949299

Installed as D:\android rom\pixel4\platform-tools_r29.0.5-windows\fastboot.exe

---------- Post added at 06:16 PM ---------- Previous post was at 06:00 PM ----------

It must fastboot to sloth B？
[Google Pixel 4 XL Questions & Answers] loonix:
Ah coincidently I was reading about enabling diag mode (and this)and it requires the userdebug image to be flashed to vendor partition. Unfortunately flashing to either slots or both results in a corrupted boot and it hangs either at or before the Google logo. And this is after flashing factory images first (pre magisk). Anyone else running into problems flashing the vendor images?
[Google Pixel 4 XL Questions & Answers] cstark27:
What are the filenames of the driver binary package and the factory image you are flashing? Are your adb tools up to date?

---------- Post added at 06:14 PM ---------- Previous post was at 05:39 PM ----------

Also, make sure you're flashing the correct extracted image. To be sure, you can just drag the file to the window after you've typed 'fastboot flash vendor '.
[Google Pixel 4 XL Questions & Answers] loonix:
Yes we went over it in earlier post.

MacBook-Pro:proprietary $ shasum -a 256 vendor.img
32f5fa4ea6200dee0d12f2848f63fe4a76b2963fd10586a3eb1065781678c638 vendor.img
MacBook-Pro:proprietary $
[Google Pixel 4 XL Questions & Answers] cstark27:
And you're positive this is the image that is being flashed? Are you running other Magisk modules (perhaps disable all modules before flashing vendor)? I've reflashed stock and the userdebug vendor again and no issues still. I was on the January build, rooted, and just flashed the userdebug vendor from January binaries over it. I did not flash it to a certain or all slots, simply ran the command from the post on page 1.
[Google Pixel 4 XL Questions & Answers] loonix:
Quite positive and I have the latest platform-tools as well. I believe this is related to how I have flashed magisk, but I believe that flashing stock factory images wipes everything? In one of the attempts I tried disabling modules as well. I cannot afford to wipe data to get a really clean slate (too much work).

MacBook-Pro:coral-qq1b.200105.004 $ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
Installed as /Users/x/Applications/platform-tools/adb
MacBook-Pro:coral-qq1b.200105.004 $
[Google Pixel 4 XL Questions & Answers] cstark27:
In the bat file equivalent for Mac should be a -w flag on one of the lines. This is what wipes data. Remove the -w and it won't wipe data but will flash all the stock images back. You will lose root at this time, but you will retain your apps and settings.
[Google Pixel 4 XL Questions & Answers] loonix:
Yes that is what I follow. I have flashed quite a few times now trying to get userdebug going.
[Google Pixel 4 XL Questions & Answers] Ingenium13:
The free version of NSG doesn't support dual SIM. Only the premium version supports dual SIM.
[Google Pixel 4 XL Questions & Answers] cstark27:
[MENTION=251096]loonix[/MENTION] [MENTION=7990588]hongfa1380[/MENTION]

It seems your issue may be related to 29.0.5 fastboot tools, I'm guessing. I had factory reset the other day, and followed my steps including updating my fastboot tools to 29.0.5 (I had 29.0.2 when I wrote my original post). The device did not boot anymore as you describe. I tried again with 29.0.2 fastboot tools but still no go. I also noticed new entries on my bootloader screen:

debug policy(a): enabled(not-in-list)

debug policy(b): enabled(not-in-list)

Never seen these before.

:\
[Google Pixel 4 XL Questions & Answers] loonix:
I think you mentioned that some others were successful? Maybe we can compare with their tools/environment.

.
[Google Pixel 4 XL Questions & Answers] rester555:
Has anyone got this working on 29.0.5 platform tools?
[Google Pixel 4 XL Questions & Answers] cstark27:
Try these steps. Just did it with adb tools 29.0.5 and it worked. I did not have Magisk installed yesterday when I was getting the failures.

remove -w flag from factory image bat/sh then re-flash factory image

adb reboot-bootloader

flash magisk boot

reboot

install Magisk apk and open it, allow additional setup, reboot

open Magisk, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF

adb reboot-bootloader

fastboot reboot-fastboot (wait for "fastbootd" screen)

fastboot flash vendor <location_of_vendor_image_here>

When "finished", reboot system

Upon boot, you can check if it's correct

adb shell
su
getprop ro.vendor.build.type

Should return 'userdebug'.
[Google Pixel 4 XL Questions & Answers] rester555:
So to understand this set of steps, you flash the magisk patched image, then install the APK, then turn off the dm verity option, repatch boot again, then install vendor image?

---------- Post added at 11:18 AM ---------- Previous post was at 10:48 AM ----------

When I follow these steps, and get to booting into fastboot from the bootloader screen, it bootloops and I need to reflash the factory image.

Essentially I follow these steps:

remove -w flag from factory image bat/sh then re-flash factory image

adb reboot-bootloader

boot into phone, patch my boot.img file to make magisk_patched.img with Preserve AVB 2.0/dm-verity is OFF

adb reboot-bootloader

flash magisk boot

boot into phone and Magisk, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF

adb reboot-bootloader

fastboot reboot-fastboot (wait for "fastbootd" screen)

bootloop for me at this point...
[Google Pixel 4 XL Questions & Answers] cstark27:
Can you describe your 'bootloop' after typing fastboot reboot-fastboot? It will look like it's booting normally, but then you'll see a new screen with red fastbootd at the top, then you can flash the modified vendor.

I did the steps exactly as laid out, only flashed the magisk boot image once, and dm-verity was already disabled in my Magisk Manager. I cannot guarantee that's the same for everyone but I am assuming.
[Google Pixel 4 XL Questions & Answers] rester555:
I am using windows 10 with latest platform tools. I have the latest canary build of magisk. When following your steps, I get the bootloop as described below. It just goes from the start up screen where it says I have an unlocked bootloader. Then goes to the Google logo and repeats over and over never getting into fastbootD.

remove -w flag from factory image bat/sh then re-flash factory image

adb reboot-bootloader

flash magisk boot

reboot

install Magisk apk and open it, allow additional setup, reboot

open Magisk, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF

adb reboot-bootloader

fastboot reboot-fastboot (wait for "fastbootd" screen) <------- THIS IS WHERE I GET THE BOOTLOOP

fastboot flash vendor <location_of_vendor_image_here>

When "finished", reboot system

Upon boot, you can check if it's correct

---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------

hmm, i might have a bad cable on my setup... What version of magisk are you using?
[Google Pixel 4 XL Questions & Answers] cstark27:
Magisk Manager 7.5.1 and the image was patched with Magisk 20.2. You can try 'adb reboot-fastboot' it would directly reboot into the fastbootd from the OS. It is odd you are not getting to the fastbootd though.
[Google Pixel 4 XL Questions & Answers] rester555:
Ok, got it to work using Windows 10 with latest platform tools 29.0.5. I followed the steps you described as follows with some changes shown below:

Remove -w flag from factory image bat/sh then re-flash factory image

booted into phone installed latest magisk STABLE apk

flash magisk boot (I created a magisk patched image with Preserve AVB 2.0/dm-verity OFF at this point. Seems to only work using Magisk STABLE build, latest canary does not work)

reboot

open Magisk, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF

adb reboot-fastboot (wait for "fastbootd" screen)

fastboot flash vendor <location_of_vendor_image_here>

When "finished", reboot system

Upon boot, you can check if it's correct

---------- Post added at 01:29 PM ---------- Previous post was at 12:52 PM ----------

So now that I got network signal guru to work, is there a way to shut off or turn on certain cellular bands with Verizon on the free version?

Looking at NSG's paperwork, it seems like the Pixel 2 XL has the radio locked. So my guess is, you can't turn off certain bands or lock to certain bands?
[Google Pixel 4 XL Questions & Answers] cstark27:
Thanks [MENTION=3108304]rester555[/MENTION]. I've updated my original post. Hope that fixes it up for everyone else that it's failed for.
[Google Pixel 4 XL Questions & Answers] rester555:
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.
[Google Pixel 4 XL Questions & Answers] cstark27:
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.
[Google Pixel 4 XL Questions & Answers] loonix:
I can confirm that the revised steps worked for me as well. Thanks [MENTION=2712580]cstark27[/MENTION] and [MENTION=3108304]rester555[/MENTION]. I know this is outside the scope of this thread but are you also able to set it to show diag port?
[Google Pixel 4 XL Questions & Answers] loonix:
I can confirm that the revised steps worked for me as well. Thanks [MENTION=2712580]cstark27[/MENTION] and [MENTION=3108304]rester555[/MENTION]. I know this is outside the scope of this thread but are you also able to set it to show diag port?

.
[Google Pixel 4 XL Questions & Answers] cstark27:
I was able to get the COM port/modem to show but it didn't register in QPST (maybe wrong driver). I didn't explore this more.

su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug

After doing the commands you might need to switch USB mode between File Transfer and Charging.
[Google Pixel 4 XL Questions & Answers] loonix:
You are on fire in this thread :) This is awesome information. A search for Pixel USB Diag mode leads to a lot of informative threads like Pixel XL - USB diag mode and {Guide} QXDM Port activation on Pixel 2 XL, (VoLTE,WoWIFI,CA) but I see that they have developed magisk modules /ran other commands to enable diag etc but never saw these commands discussed before when related to QPST/EFS/QXDM etc. I have never tried these tools before but I downloaded the latest QPST_2.7.480 and installed the driver that comes inside the package (It is called Qualcomm USB Driver V1.0). I also installed Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup that is linked in one of these threads (but it may be redundant). Now I do see COM port show up according to different USB connection selection on the phone.

File Transfer -> Qualcomm HS-USB Diagnostics 903A (COM4). In driver properties It shows version as 2.1.2.2 and is dated 3/25/2016

No Data Transfer -> Qualcomm HS-USB Android DIAG 901D (COM3). Same driver properties.

A modem device doesn't show up, but I bet it is another command that needs to be run to setprop. I will see if some of the tools work on coral but some really great findings in this thread !

Also ran this and in edl mode the COM port shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)"

adb reboot edl

I'm not sure if anything can be done in edl mode as none of the known tools detect the phone even though the COM port does show up.
[Google Pixel 4 XL Questions & Answers] loonix:
[MENTION=2712580]cstark27[/MENTION] Are there other commands needed for the Modem to show up as a device in Device Manager? Looking at all the older screenshots, it seems all of these get added in Device Manager

1)Android Device

2)Modem (should be Qualcomm HS-USB Modem 903A)

3)Network Interface (Qualcomm Wireless HS-USB Ethernet Adapter)

4) The COM ports (this one is showing successfully with those commands)

Edit:

I think there could be a bug with the usbradio bootmode. I read how this is supposed to enable all diagnostic ports, but the values are not changing for some of the key variables

coral:/config/usb_gadget/g1/configs/b.1/strings/0x409 # getprop |grep -i usb
[init.svc.usbd]: [stopped]
[init.svc.vendor.usb-hal-1-2]: [running]
[persist.data.df.dev_name]: [rmnet_usb0]
[persist.sys.usb.config]: [adb]
[persist.vendor.usb.usbradio.config]: [diag]
[ro.boot.usbcontroller]: [a600000.dwc3]
[ro.bootmode]: [usbradio]
[ro.boottime.usbd]: [3925450596]
[ro.boottime.vendor.usb-hal-1-2]: [3817537356]
[sys.usb.config]: [adb]
[sys.usb.configfs]: [2]
[sys.usb.controller]: [a600000.dwc3]
[sys.usb.ffs.ready]: [1]
[sys.usb.mtp.device_type]: [3]
[vendor.audio.feature.usb_offload.enable]: [true]
[vendor.usb.config]: [diag]
coral:/config/usb_gadget/g1/configs/b.1/strings/0x409 #

init.msm.usb.configfs.rc gives some valid combinations that can open the modem diagnostic port (I think!)

.
[Google Pixel 4 XL Questions & Answers] rester555:
[MENTION=251096]loonix[/MENTION] what is the benefit of having the diag tools and access?
[Google Pixel 4 XL Questions & Answers] loonix:
For me it is pure experimentation, as I have never known these kind of tools even existed. From Network Signal Guru I am still having issues understanding the CA matrix, but in one of the windows it said QPSK/64QAM for download and upload. I started reading about how it is possible to set 256QAM for better speeds etc as well, all of this after reading about userdebug etc. So the research areas sort of overlapped with trying to get NSG working via userdebug, and see what else were being done in earlier pixels via userdebug/diagnostic modes. I think the NSG team is also aware of this thread and I would love for some discoveries that can help us get officially supported.

After doing the steps you and [MENTION=2712580]cstark27[/MENTION] posted, at least NSG somewhat works. Other times it complains about the driver at boot but goes on to load the screens, but often misses detecting dual SIM. Sometimes clearing cache seems to help as well. NSG has been helpful in terms of band locking, that is a big plus so far. I went to purchase the pro version but it is $50/month ! (very expensive). But ideally I just want to learn how to detect CA combinations near my home and lock them. The pro version can lock PCIs too I believe but maybe if we learn what happens underneath, it can be enabled via diag tools I'm sure. It's disappointing to see some of the "open" nature of the Pixels are being stripped off with newer hardware and factory images.
[Google Pixel 4 XL Questions & Answers] rester555:
What did you learn about band locking on the Pixel 4 XL? [MENTION=251096]loonix[/MENTION] Is it able to lock bands on 4G LTE through NSG?
[Google Pixel 4 XL Questions & Answers] loonix:
Yes it can lock to specific band(s). Also i rarely am seeing CA near my home :( I had to go to various places around town to see what kind of CA combos are possible (I want to add them to my ATT Nighthawk). I was also able to see that my phone favors B2 at home which runs pretty saturated. Also available are B4, B12, B17, B30 and B66. For some reason B17 is not enabled by default on this phone, but through NSG you can lock it just B17 or B66 etc which provide great speeds for me.

Edit: But the implementation might be buggy. Even when I don't have B2 selected, I see that NSG is still reporting the phone receiving signal from the B2 towers.

I tried this also just to see, but the point about MPSS missing etc. could be related. This is from a magisk module that supposedly did everything diag in the older Pixels.

setenforce 0
resetprop sys.usb.configfs 1
resetprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
resetprop sys.usb.config diag,serial_cdev,rmnet,adb
resetprop sys.usb.ffs.ready 1
[Google Pixel 4 XL Questions & Answers] Ingenium13:
I installed the February update on my Pixel 4 XL and the matching userdebug vendor.img, and when the phone boots it says No SIM. Reverting to stock vendor.img allows the SIM to work. I tried downgrading to January without wiping data, but I get stuck at the G logo.

With the No SIM issue, I can still run NSG, and it shows WCDMA data that the phone is using to be able to place emergency calls. So the modem is working, it's just that the SIMs are disabled. My guess is it's some sort of Google security measure getting tripped.

I found some people who had this issue with the Nexus 6P, and they said removing lockscreen security and setting it to none or swipe, which disables device protection, and rebooting solves the issue (then you can re-enable the pin). I tried this but it didn't work.

I flashed everything at once without rebooting (factory image with --skip-reboot, followed by magisk_patched.img, followed by vendor.img), so maybe that has something to do with it. Maybe it would have worked if I booted once with the stock vendor.img.

Does anyone have any other ideas on how to solve the No SIM issue?
[Google Pixel 4 XL Questions & Answers] Ingenium13:
I was eventually able to get it working. The February userdebug vendor.img breaks dual SIM. You can't enable or disable it with that image flashed, and if it's enabled when flashed then you get "No SIM".

Flashing stock vendor.img, disabling DSDS, then flashing the userdebug version works. You can still switch between eSIM and physical SIM, but you can't enable it (it says it has to reboot to enable it, then just hangs at a grey screen. If you manually reboot, it's not enabled).

The Feb userdebug vendor also breaks active edge. It doesn't respond at all to squeezing. Reverting to stock brings it back.

For squeeze, nothing at all shows in logcat when I squeeze it. For DSDS, only the following shows up:

2020-02-07 19:29:58.947 1278-1821/? E/InputDispatcher: Window handle Window{14a323 u0 com.google.android.euicc/com.android.euicc.ui.dialog.PrivilegedActionDialogActivity} has no registered input channel
2020-02-07 19:30:05.764 1278-3427/? E/InputDispatcher: Window handle Window{efa935a u0 com.google.android.euicc/com.android.euicc.ui.dialog.PrivilegedActionDialogActivity} has no registered input channel
2020-02-07 19:30:05.879 2442-14787/? E/ClearcutLoggerApiImpl: derived ClearcutLogger.MessageProducer
java.lang.RuntimeException: Field zzabul for c.b.a.c.j.Wc not found. Known fields are [public int c.b.a.c.j.Wc.h, public long c.b.a.c.j.Wc.i, public int c.b.a.c.j.Wc.j, public c.b.a.c.j.Ea c.b.a.c.j.Wc.k, public c.b.a.c.j.Ea c.b.a.c.j.Wc.l, public byte c.b.a.c.j.Wc.m, public static final c.b.a.c.j.Wc c.b.a.c.j.Wc.f, public static volatile c.b.a.c.j.wa c.b.a.c.j.Wc.g]
at c.b.a.c.j.Qb.a(SourceFile:88)
at c.b.a.c.j.Qb.a(SourceFile:55)
at c.b.a.c.j.Cb.a(SourceFile:21)
at c.b.a.c.j.Zb.a(SourceFile:3)
at c.b.a.c.j.Zb.a(SourceFile:7)
at c.b.a.c.j.gb.f(SourceFile:2)
at c.b.a.c.j.gb$c.d(SourceFile:6)
at c.b.a.c.j.gb$a.e(SourceFile:1)
at c.b.a.c.b.a$b.a(SourceFile:5)
at c.b.a.c.b.a.d.a(SourceFile:20)
at c.b.a.c.c.a.a.c.b(SourceFile:2)
at c.b.a.c.c.a.a.Da.a(SourceFile:3)
at c.b.a.c.c.a.a.e$a.c(SourceFile:18)
at c.b.a.c.c.a.a.e$a.b(SourceFile:15)
at c.b.a.c.c.a.a.e$a.a(SourceFile:42)
at c.b.a.c.c.a.a.e.handleMessage(SourceFile:121)
at android.os.Handler.dispatchMessage(Handler.java:103)
at c.b.a.c.j.l.dispatchMessage(SourceFile:1)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)

So Google seemingly broke a bunch of drivers in the Feb userdebug vendor.img. Hopefully they fix it in March....
[Google Pixel 4 XL Questions & Answers] sprke:
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?
[Google Pixel 4 XL Questions & Answers] Ingenium13:
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
[Google Pixel 4 XL Questions & Answers] cstark27:
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.
[Google Pixel 4 XL Questions & Answers] Jiggs82:
So probably a noob question lol but just curious it should be fixed/working in Android 11 dp since it has March security images already?
[Google Pixel 4 XL Questions & Answers] cstark27:
I tried DP1 with a pre-rooted kernel and the issue of NSG not working without a userdebug vendor image was still present.
[Google Pixel 4 XL Questions & Answers] Jiggs82:
Oh ok thx..dammit Google lol well hopefully it is fixed with official March images next month
[Google Pixel 4 XL Questions & Answers] loonix:
Does QPST work with DP1 ?
[Google Pixel 4 XL Questions & Answers] cstark27:
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.
[Google Pixel 4 XL Questions & Answers] ryaniskira:
QPST? The Qualcomm flash tool?

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

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.