My Redmi K20 Pro lost IMEI, MAC Address and Baseband, every "unknown".
I fastboot TWRP and ROOT, activate USB Debug, push in Laptop, enable diagnostic mode by cmd commands, in Device Manager show Port Qualcomm HS-USB Android DIAG 901D (COM4). Open QPST ver 2.7.480, It show My Phone is SM8150. I try to restore QCN with QCN i download on internet (i dont backup it before). It error "Received an invalid command from the phone."
I try QFIL choose Port and Restore but when it run to "Checking if phone is connected...", it repeat "Checking for phone connection: 4" again again and to much again... Finally it notification "Phone is not connected to: 4" and "Restore Fail"
I dont know reason. Anybody can help me, I was stuck for 3 days. Thank you
I think you messed it up badly, take it to a service center and see if you can get it fixed.
Press F to pay respects.
Ps, don't mess with things you don't know how to fix
bacdi said:
My Redmi K20 Pro lost IMEI, MAC Address and Baseband, every "unknown".
I fastboot TWRP and ROOT, activate USB Debug, push in Laptop, enable diagnostic mode by cmd commands, in Device Manager show Port Qualcomm HS-USB Android DIAG 901D (COM4). Open QPST ver 2.7.480, It show My Phone is SM8150. I try to restore QCN with QCN i download on internet (i dont backup it before). It error "Received an invalid command from the phone."
I try QFIL choose Port and Restore but when it run to "Checking if phone is connected...", it repeat "Checking for phone connection: 4" again again and to much again... Finally it notification "Phone is not connected to: 4" and "Restore Fail"
I dont know reason. Anybody can help me, I was stuck for 3 days. Thank you
Click to expand...
Click to collapse
did you manage to fix that?
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Related
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Embeddednut said:
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Click to expand...
Click to collapse
fixed your issue?
Embeddednut said:
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Click to expand...
Click to collapse
Is your issue solved? If yes, Can you provide the steps to the solution?
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
I works be thankful of anyone can help me getting into the diagnostic mode
Thanks in advance
Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!
use the side usb port (the top black one, not the bottom orange one) and try the command again through FB
Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?
When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?
You need install fastboot drivers on your pc, so device manager will see your phone
Hi I am using LG v40 Version on Hovac 3.8 Custom Rom (Android 10) , rooted with Magisk. I Am trying to Put phone to Diag mode to get it recognized by Qfil to repair its imei. I have tried Services code method , Adb command method as well as terminal command method but my cell is not being recognized as Diag 901d port. Any leads?
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
FLAmbuRNE1 said:
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
Click to expand...
Click to collapse
only verizon roms doesnt have imei write protection (idk about A10 but for Pie its working)
if you imei on v40 already null you can try this guide
but use v40 verizon rom
on verizon rom for diag mode enable try this hidden menu code ##7764726405 and hit the call button type service code 000000
All guides seem to point towards the device being called HB-USB Diag 901D in the device manager.
I feel like this is a critical step towards being able to write protected NV items.
Trying to connect to the phone using QXDM tools does not work since the phone isn't recognized as being in Diag mode.
I've tried soooo many ways at this point but don't want to give up just yet.
Let me know if anyone has any luck in getting V40 to correctly connect in Diag mode - or prove to me that diag mode is achieved with the hidden menu (I don't see it working for me - guide me in case I'm misunderstanding something).
FLAmbuRNE1 - I stand corrected - via experimentation.
I was not seeing any ports change in Device Manager or any other application after issuing the
Code:
setprop sys.usb.config diag,adb
command as a super user or after enabling the diag port from the hidden menu.
QFIL's QCN Backup+Restore functionality kinda indicated that these commands do indeed make a difference. When QFIL Restoring QCN on my phone I noticed that QFIL was unable to reset the phone after sending data to the phone - unless I had done both of the above steps. As soon as I did, it would be able to restart my phone and verify that restore was completed.
I have some additional experiments on the way to try and figure out the exact memory locations in
Code:
modemst1, modemst2 & fsg
to modify and flash in order to restore my original IMEI. Fingers crossed...
I'll circle back here with what I find, or don't find. If I don't follow up, anyone interested, message me.
setprop sys.usb.config diag,adb
not work
C:\adb>adb shell
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
flashlmdd:/ $ su
flashlmdd:/ # setprop sys.usb.config diag,adb
flashlmdd:/ #
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Sathelp said:
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Click to expand...
Click to collapse
I'm able to detect device in "ADB Devices" when phone is booted into android OS, even the MiFlashTool also detects the device when phone in booted into OS.
But after i type ADB reboot bootloader, phone restarts into FASTBOOT, i can see RED "FASTBOOT" logo in phone screen but it doesn't get detected.
How come phone gets detected in ADB when Phone is booted into OS MIUI13 but not in FASTBOOT.
I'm on windows 11 .
I changed the cable also with a new Xiaomi cable purchased recently, still the same result.
You can never see a result to detect mi 11 ultra through ADB devices. Rest assured your device is already detected and ready to use. Even though can not see device address.
I had the same case. Make sure all the necessary drivers are installed.
At first mine was also not detected in fastboot. When I first ran MI Flash Tool, it automatically installed some drivers. And I also manually installed USB driver of MI 11 Ultra.
After that MI Flash detected my phone in fastboot.
A small suggestion from me: Use "Xiaomi ADB Fastboot Tools" for flashing. MI Flash was giving me, timeout error and my device got into fastboot loop. After flashing with "Xiaomi ADB Fastboot Tools" all went well.
hello, I also had this problem and to solve it I used the driver of Mi unlock which is at the level of the parameters and launch it in fastboot then connect it to the pc and the drivers must be installed
I had a similar problem with my Mi 10. Found via ADB but wouldn't show in fastboot. Tge way I solved it was to boot into TWRP recovery (assuming you have it) and then go to their reboot menu and choose fastboot from there. It will then put you into their version of fastboot and your computer should recognise the phone in fastboot mode.
I hope this helps
jaggub4u said:
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Click to expand...
Click to collapse
Adb and Fastboot is not the same thing!
If you're phone is detected in ADB, it means you have install the Adb Driver ( which more than probably is Google Driver or Xiaomi driver for ADB ).
In order for you phone to be in Fastboot do the following:
- Reboot to Fastboot and connect your phone to PC with original Xiaomi cable from the box
- Go to Device Manager > Other Devices > Android Device ( you will see a yellow sign, which means you don't have the Fastboot Driver )
- Download XiaomiMi11 Ultra Bootloader Driver.zip, unzip it
- Click on the Android Device with yellow sign > Update driver > Browse my computer for drivers > Select the Xiaomi Bootloader Folder
It will install the driver.
From here you're good to go!