Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Cibor said:
Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Click to expand...
Click to collapse
This will only work if the ramdisk has the appropriate configs:
su
setprop sys.usb.config diag,adb
to revert:
setprop sys.usb.config mtp
The 3xl and 3 can also enter edl (emergency download mode) by issuing:
adb reboot edl (exit by hardware buttons)
AnierinB said:
This will only work if the ramdisk has the appropriate configs:
su
setprop sys.usb.config diag,adb
to revert:
setprop sys.usb.config mtp
The 3xl and 3 can also enter edl (emergency download mode) by issuing:
adb reboot edl (exit by hardware buttons)
Click to expand...
Click to collapse
Are the ramdisk configs done at kernel level?
Cibor said:
Hi,
I need to use Pixel 3 with QXDM to debug some LAA issues. But I cannot connect Pixel 3 with QXDM. Probably it requires to enter to diagnostic mode on Pixel but I have no idea how to do it. Probably userdebug ROM is required, but I cannot find any info about it on Pixel 3.
Has anyone tried to use Pixel 3 with QXDM?
Click to expand...
Click to collapse
Usually on pixel 2 I had to flash a debug vendor image , which are available from Google site. Make sure adb is setup properly and issue commands given by Friday response.
I was looking to enable WiFi calling but this phones files are really.locked down:-/
Related
To continue this process you need to unlock your bootloader.
Read the full thread before doing anything.
1. Download Platform Tools & Extract it: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Copy the twrp file for your device into the extracted folder.
Latest Twrp for RN5Pro(Whyred): https://dl.twrp.me/whyred/
after downloading twrp rename it to twrp.img
3. Turn on Usb Debugging on your device and Connect the phone to the usb cable
4. Now open the platform tools folder and in the address section type cmd & hit enter
5. Type commands:
(a) adb reboot bootloader & hit enter(phone is now in fastboot mode)
(b) fastboot boot twrp.img
twrp mode is now open....just touch on keep read only(don't do anything you still now in twrp mode)
(c) adb devices (check your device is connected or not)
(d) adb shell
(e) setprop persist.camera.HAL3.enabled 1 ( be careful while typing or copy paste this line)
(f) exit
(g) adb reboot( your phone will Reboot now)
If gcam force closes then reboot your phone manually.
Done.I am not responsible if you brick your device.
#Now download GCam from below the link and install it.
In this method we doesn't flash twrp we are just boot into twrp to enable camera 2 api
Download GCam :
https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.apk
Official GCam Link : https://www.celsoazevedo.com/files/android/google-camera/
If you're not sure how this process is done then contact me in my email address : [email protected]
Thank You
I don't see the point in booting to twrp. All you need to do is to boot into fastboot and apply the adb commands.
anon768 said:
I don't see the point in booting to twrp. All you need to do is to boot into fastboot and apply the adb commands.
Click to expand...
Click to collapse
I think you can't access ADB in fastboot.
anon768 said:
I don't see the point in booting to twrp. All you need to do is to boot into fastboot and apply the adb commands.
Click to expand...
Click to collapse
try this method then you will see how it works.
Hosssain said:
I think you can't access ADB in fastboot.
Click to expand...
Click to collapse
Bro try the method,I am using GCam through this process.
hmmmn
I'm kinda lost here, what i have to do?
imgu r. com/a/FTfelHt
Rumcyk said:
I'm kinda lost here, what i have to do?
imgu r. com/a/FTfelHt
Click to expand...
Click to collapse
email me bro..my email id is already is given... follow the thread
is it work for redmi note 5 AI
does not work. It says "The system has been destroyed" and reboot into system after few seconds.
[email protected] said:
does not work. It says "The system has been destroyed" and reboot into system after few seconds.
Click to expand...
Click to collapse
)))))))))
Worked for me
I had to unlock the bootloader to follow this method.
First I got the system destroyed message, when I did with the bootloader locked.
Gcam that you suggested didn't work well for me. Then I used another one instead. Now everything is functioning properly.
Not working on my friends locked phone. It is showing "system destroyed".
You'll need to root and set Selinux to permissive because this will make your stock camera lag like hell
Work or not work?
Is the quality of the photos the same thing that happens with the other methods?
is it true that with this method, the quality of the camera gets worse?
the photo quality good better than stock app.
but the issue use gcam cant save front camera with hdr+ active
even with the miui 10 okay?
help
RSubha said:
Bro try the method,I am using GCam through this process.
Click to expand...
Click to collapse
I have heard that in miui10 global stable rom,after enabling camera2api without rooting,front camera is broken in third party apps like whatsapp...Is it true???
RSubha said:
To continue this process you need to unlock your bootloader.
Read the full thread before doing anything.
1. Download Platform Tools & Extract it: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Copy the twrp file for your device into the extracted folder.
Latest Twrp for RN5Pro(Whyred): https://dl.twrp.me/whyred/
after downloading twrp rename it to twrp.img
3. Turn on Usb Debugging on your device and Connect the phone to the usb cable
4. Now open the platform tools folder and in the address section type cmd & hit enter
5. Type commands:
(a) adb reboot bootloader & hit enter(phone is now in fastboot mode)
(b) fastboot boot twrp.img
twrp mode is now open....just touch on keep read only(don't do anything you still now in twrp mode)
(c) adb devices (check your device is connected or not)
(d) adb shell
(e) setprop persist.camera.HAL3.enabled 1 ( be careful while typing or copy paste this line)
(f) exit
(g) adb reboot( your phone will Reboot now)
If gcam force closes then reboot your phone manually.
Done.I am not responsible if you brick your device.
#Now download GCam from below the link and install it.
In this method we doesn't flash twrp we are just boot into twrp to enable camera 2 api
Download GCam :
https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.apk
Official GCam Link : https://www.celsoazevedo.com/files/android/google-camera/
If you're not sure how this process is done then contact me in my email address : [email protected]
Thank You
Click to expand...
Click to collapse
Which gcam should i use to front camera work correctly without patches on ai dual camera version ?
Front camera doesnt work with hdr on, or portreit mod, on any gcam i tried on rn5 whyred, sorry.
I enabled usb debugging and unlocked the bootloader. I downloaded the lates twrp daisy for mi A2 lite. I use the following commands in command prompt:
adb devices
adb reboot bootloader
fastboot boot twrp.img
When in enters the twrp I tried two things:
1. press do not change anything
2. swipe the arrow to the right
Next commands:
adb devices
adb shell
setprop persist.camera.HAL3.enabled 1
setprop persist.camera.eis.enabled 1
exit
adb reboot
I read somewhere that I need to write su after adb shell, but it doesn't recognize that command.
Does anyone know what I'm doing wrong?
I want to enable google camera without rooting my phone. Build number 10.0.4.0.
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
any usfull info here? https://gist.github.com/julian-alarcon/53f9a782008b5d5f879bf6fa878f87f3
Hello sir i lost my physical sim card on pixel 3a only shows esim option please help
luqman.mirza said:
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
Click to expand...
Click to collapse
Can you share the XQCN file with me??
I was able to use QPST and PDC on my OnePlus Nord (AC2003) when it was running Android 10 / Oxygen 10.5
After this weekends update to Android 11 / Oxygen 11 my phone is no longer recognised. I've tried all sorts of USB drivers I could find using some Google Fu, but none of them recognises it anymore.
Does anyone have USB drivers for the OnePlus Nord (AC2003) that works with Android 11?
Thank you
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
No need to root?
Thanks
ippo18 said:
No need to root?
Thanks
Click to expand...
Click to collapse
Nope, no need
Jaansburger said:
Nope, no need
Click to expand...
Click to collapse
Thanks, I got blocked at the PDC step: no options available in the devices list.
Do I need a special version of PDC?
Tks
Thanks, it worked in the end, good job!
sorfat said:
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Click to expand...
Click to collapse
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
ippo18 said:
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
Click to expand...
Click to collapse
Done
Since Android 11 - VOLTE fails to work my carrier (Telstra AU) which worked perfectly on AOSP and MIUI with codes.
These below setprop commands require root.
And require these drivers or the qualcomm one atleast.
Xiaomi Poco F2 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Xiaomi Poco F2 Pro USB Driver for your Xiaomi Mobile. We also provide all other Xiaomi Mobile drivers for free.
gsmusbdriver.com
Instructions for setting up EFS tools - this modded version is the only one that writes the mbn files correctly.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
And uploading the mbn instructions are in this post.
It took me ages to find the right setprop command to open the diag port. The below setprop commands work on MIUI or AOSP.
setprop sys.usb.config diag,diag_mdm,adb
This will open two com ports in device manage. You can only use the MDM one.
Then it will work with QPST, EFS Expolorer by selecting that port.
To use PDC you must use a different setprop command.
setprop sys.usb.config diag,diag_mdm,serial_cdev,rmnet,adb
adb shell
su
then setprop command.
Unplugging the USB cable will reset the setprop.
I have written the required mbn to /nv in the EFS however the ims_user_agent (/nv/item_files/ims) won't stick after a reboot which reverts to default. My carrier requires that file to have a header in it or it fails to register with their IMS server therefore no VOLTE on Android 11. The below link describes what's happening best.
https://c.mi.com/thread-3571499-1-0.html
I accomplished this task with efstools in the above link - it can be done with EFS Explorer but it doesn't write the files with the correct mode permissions.
I know there's a fair bit of info here, I share this incase anyone figures out a work around to fix this issue. I have tried all 4 Android 11 firmware's and they all do the same thing. Let me know if there's any questions.
I suggest to join the MIUI bugs telegram channel and complain that VOLTE isn't working.
https://c.mi.com/thread-2413060-1-0.html
Thank you. I recently bought a Mi 11 Ultra running EU ROM. Currently on Android 11 MIUI 12.5.12 and no VoLTE or VoWiFi. I am going to join the Telegram bug group to report the issue.
Edit: couldn't figure out the Telegram stuff so deleted the app. How else can I contact Xiaomi?