Restore IMEI of a SM-A705FN/DS - Samsung Galaxy A70 Questions & Answers

Hello! I have a Samsung A70, where I managed to ruin the SIM1 IMEI somehow, and I want to restore it to the original state. About the phone:
Stock ROM
Magisk installed, rooted -TWRP up and running -ADB connection works, OEM unlocked
I installed all the required drivers, both adb, fastboot and Qualcomm
I am able to put the phone into Qualcomm mode with adb setprop sys.usb.config diag,adb; when I do this it shows up both in QPST and QFIL as a device. But here the problems starts:
with QPST I was unable to download the .qcn of the phone, as when I start the download process it dropped me an error (even before the IMEI error) and completely killed my QUALCOMM port connection.
with QFIL I was able to download the phones .qcn file ( I have the valid .qcn of my phone), and I have it. buth when I try to flash it back to the phone, just nothing happens, the IMEI1 stays nulled out.
Others things I tried: -try to put the phone into EDP mode, but Qualcomm port never recognized it -#9900# - upload mode enable - When I booted into that weird menu, my computer never recognized it as a Qualcomm device. The phone is not bricked, I have access to everything! Any help is highly appreciated!
TLDR: I have a valid .qcn backup of my phone I can't seem to put back to the phone

Related

Fixed: No Phone showing in QPST

This assumes you DO have the drivers installed correctly and the phone configured right. Those two things aren't that hard to do - if you've done them and still get "No Phone" this may help.
I spent a lot of time on this the last few days, searched and searched and all I found was that a lot of people ran into this problem but I never saw much of a solution other than "get the drivers installed correctly." After going through the whole driver process on a 2nd PC and running into the same issue, I looked back at the phone itself and what fixed the issue for me (on both PCs now) was sort of odd.
I had flashed from ParanoidAndroid 03-07 release back to UVALJ1 - I chose to go this far back because that old stock is where I was able to do the free unlock via dialer code menus. I was still on baseband UVALL4.
I got the most recent Samsung drivers directly from Samsung and I'm working with QPST 2.7.378. The drivers were installed, the phone was in PDA mode on USB & UART and Qualcomm USB settings were DM + Modem + ADB. A COM port was showing up in device manager with a working driver (no unhappy devices at all in my device manager, all working.)
Given all of that, when I'd go into QPST I could add the port that showed up in device manager but it always said "No Phone".
It dawned on me when I had flashed all the way back to UVALJ1 to do the unlock, I did it with Odin and it put the modem on the came with that old stock. I downloaded just the modem for UVALJ1 and installed it via TWRP. That fixed my "No Phone" problem. Whats even more strange is that I've since gone back to UVALL4 baseband (installed via TWRP) and...the "No Phone" is still fixed.
I have no clue what flashing the modem did but it kicked something into communicating with QPST. I figured I'd get the problem back when I went back to UVALL4 but apparently not. Working fine now on that modem with the older stock ROM on top of it.
Hope this helps someone and saves them the many hours it took me to try this - flashing the modem only took a few seconds. Installing and removing and rebooting and trying different drivers on two different PCs took a good long time!
I have de same problem with my Samsung Galaxy Light and my Samsung Galaxy Note 3.
Can someone help us please?
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.

[HARDBRICK] D855; Boarddiag & flashtool not working

I'm fixing a D855 model which I hardbricked by accident. This is what I tried so far but still unsuccessful:
1. I used the method which involved shorting the pins in order for my PC to detect it as Qualcomm USB QDloader (something). I used the BOARDDIAG v2.99c as it's the only version that could detect my phone connected. Newer versions doesn't seem to work. I flashed all the partitions, even the userdata and system (which the tutorial doesn't recommend as it takes very long; it took me more than 12 hrs+). After flashing the sli, which is supposed to be flashed last, my phone boots to kernel panic mode. From this point, my phone can be seen as LGE androidnet port (COM41) (sorry I'm just typing this from memory)
2. From the kernel panic mode, I used the LG flash tool to flash a D855 TOT and a LG8974.dll. However, it still cannot detect my phone model. IMEI and PID still comes out as null. Back to #1, the reason I also flashed userdata and system partition because flash tool still cannot detect my phone. I was hoping to boot it up using the 1st method but it keeps on throwing it to kernel panic mode.
Any suggestions how to revive my LG G3?
hey, i have the same issue, did you find any sulotion?

Moto G5 Diagnostic Port setup for QPST

I need help getting my phone into the correct mode to be recognized by Windows as a Diagnostic PORT, so the phone registers in QPST.
The phone works for ADB and storage in charging mode and MTP mode, respectively.
However, the phone is not detected at all when i choose RNDIS mode, which I understand is the necessary setting to configure a diagnostic port for QPST.
- I have also tried booting in BP TOOLS from fastboot, same results.
Motorola Device Manager is installed, phone is XT1676 3GB/16GB running LineageOS 14.1 with superuser, TWRP.
did uh find any solution bruh same problem is goin on with me !!!???

PC No Longer Detects Phone After Rescuing with Stock OTA File

My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.

QPST Issues with SM-G9880. Phone you have chosen does not support file system ?

Hi there,
I've decided to try and unlock Band 20 LTE CA as well as some 5G bands on my S20 Ultra 5G (HK CSC). I've installed Qualcomm usb drivers, put the phone into RMNET + DM + MODEM + ADPL mode and rebooted the phone. Direct USB-C to USB-C connection to my laptop. Windows recognizes the device in the LP / COM category, no driver warning, all seems well. I punch the port into QPST port add, and lo and behold, when I try to open EFS file system explorer, it just says "phone you have chosen does not support EFS" and then spouts some more popups listing the incompatible filesystem numbers. Tried 2.7.496 and .474 Versions, 474 didn't even recognize the phone, and 496 seemed to wrongly recognize it... Does anyone else happen to be in the same boat as I am ? Cuz I'm mighty stuck here.
EDIT: 496 correctly recognized SM8250 - the part number of the Snapdragon 865. So, yeah, that worked... still, can't access EFS.
QFIL rooted phone (free from Qualcomm), you need to put the phone in diag mode (developer options, adb debugging first); on PC adb shell; su; setprop sys.usb.config diag,adb then you'll see a mystery port pop up in Device Manager, update and select from drivers on the device, go to Qualcomm, and select the 901D port. Then QFIL will let you connect to it. But you gotta have root. And what you can do now is pretty limited from what we've seen it appears they have locked down some of the band adding. You can at least backup the modem / IMEI to a QCN file and save off it your experiments don't work so your phone isn't messed up. It's under EFS explorer somewhere after you have connected, EMMC mode, made backup. Something like that (I'm talking from memory here).

Categories

Resources