Database Info

polaris diag mode

anyone can tell me hwo to enter diag mode?
I wanna use qxdm to monitor the radio protocol .thank u very much!

You need the QC diag drivers installed just do a search under mtty just rtask b then you will be prompted to install drivers it installs three devices ,one of them is the ZTE Diagnostics Interface 6000 CDMA , you connect qxdm or qpst via a com port.

I also want to know, but still can not understand what's meknb said,
Can explain more detail how to do.
ex: where to get drivers, what's mtty? Thanks

I had know how to use mtty, and also install the diag driver.
but while i reboot the phone, the diag interface also can not appear.
It only can appear while in bootloader mode(3 color display mode)
So how to let the diag also can appear while in normal mode, and use QXDM to take a log, since i want to catch some call log or data throughtput log.
Thanks.

Don't think you can do that it's either diag mode,normal or download mode.If you put the phone in diag mode in qpst you can use the efs file explorer to download the call and data log i think.

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

IMEI Flash Tool for Spreadtrum Phones

For All the Users they can flash their IMEI from the IMEI Writing Tool
Works For
MTK devices , Spreadtrum , More Device Still In Testing...
Steps.
1. Open The Tool
2. Connect Ur Cell Phone In Debugging Mode to PC
3. Install Drivers
4. Run Moborobo
5. Let it find your device
6. Now Select COM From Tool And click "READ IMEI"
7. If you found IMEI Fail or Connect Device In 30 Second Stop It And Change COM
8. When you find proper COM Just Put Your IMEI No Written On the Back of Your Phone And Click on "WRITE IMEI"
9. Wait for few seconds And its Done..
10.Reboot Device And Your IMEI Will be flashed
Note:- Before opening the Software Just Quit all the Android Emulator
And Unplug all the USB devices so that Finding COM will be easy...
Hit Like If I helped You

Master, thank you very much. This method worked on the phone g 207 jugate.

Welcome
masci said:
Master, thank you very much. This method worked on the phone g 207 jugate.
Click to expand...
Click to collapse
Most Welcome Dude

no response from phone..???
how i fix that?

what drivers has to be installed for example for a blu d140s spd 6820/8810 ?
I have 2 unknown devices on device manager.
ADB mode is active on the phone and adb drivers are installed/working, but there is no com port for the phone and for sure the unknown devices are the serial ports

not work for s4k avand spd
still not work for me i have do all the thing above but still not work its show imei null is there any tool without box flasher

help, i can't instal this driver on my windows 10 64 bit, how to do this? Sorry For My Bad English!

Ngpmnk said:
Most Welcome Dude
Click to expand...
Click to collapse
sir, when you say:
"2. Connect Ur Cell Phone In Debugging Mode to PC"
"3. Install Drivers"
you mean drivers of smartphone or other driver? because I have the drivers of my cellphone (Samsung Galaxy Young 2) (SM-G130M) installed on my PC (Windows 10 PRO x64) but i cant use the program "IMEI Writing Tool". The screen show me "Normal mode, the port has beed detected!" but when I click in read or try to change IMEI using "write" i get the following message Verifying for 20-30 seconds then, "NO RESPONDE!". I want to fix my IMEI because I can not make or receive calls the cellphone show me "not registered on the network". Can someone help me please please ? Sorry my bad english im no american. PEACE!

Link sir ?

Yet another Pocophone F1 bootloader unlock guide

Hi,
first of all... YES this is another bootloader unlock guide for the Pocophone F1.
But wait...
I just started to play around with this phone and run into some flaws by following all the other guides here. So i decided to give this process an update.
So maybe this is the real dummy guide
In fact i'll really try to concentrate on all the details and what is really recommended for the unlock process only (no method b or something).
Prerequisites:
Windows 10 Drivers
Check first if all drivers are already present on you Windows 10 PC (or could be installed by the OS):
- Connect via ADB and check for driver install
- Power down and enter fastboot mode (Volume down + power) and check for driver install
Then power up your phone again.
Create the Mi Account on your phone
Create a Mi Account on your phone with a SIM card and data connection established.
Create the account with your phone number otherwise unlock will fail later on, during the 3 initial checks of the Mi Unlock tool (e.g. no phone number is bound to the account).
There's no need to sync anything else from your phone with the new account, so to keep data at home, disable anything related.
You may check the login to the new MI account on your PC afterwards. Then verify the account with the SMS code, which is send to your phone.
Prepare to unlock now:
Next steps on your phone
1. Go to Settings > About phone
2. Find the MIUI Version and touch this area 7 times
3. Go to Additional Settings > Developers Options
4. Press and check USB Debugging and OEM Unlocking
5. Go to Settings > Developers Options > Mi Unlock Status > Add Account & Device (information about Device-ID, IMEI and IMSI is gathered and bound to your Mi account)
At this point you should sign out from the MI account on your phone.
Steps on your PC
6. Go to MIUI Unlock website
7. Download Mi Unlock tool https://en.miui.com/unlock/download_en.html
8. Unzip it anywhere on your PC and start miflash_unlock.exe
9. Login to your account, this time from within the MI Unlock tool, the tool then checks if all information is valid
10. You will be prompted to connect your phone in fastboot mode
Final steps with your phone and PC
11. Shut down your phone manually, and hold Volume down + Power button to enter Fastboot mode.
12. Connect your phone to PC using USB cable and click "Unlock".
ATTENTION: All user data will be erased (factory reset).
Afterwards you may hit the button in the Mi Unlock tool to restart your phone.
The bootscreen on your phone will now already show the unlock symbol and it may take a little while for the device to restart.
In fact the phone may even seem to hang at some point. Be very patient or try to long-press power button to force a restart.
That's all about it!
For all the next steps please follow the multiple guides here at XDA-developers. They're not hard to find :highfive:
Administrators: If you really think this guide is redundant... do your work. Anyway i hope it will help even more to not get into trouble during the process.
Cheers,
scholbert

Fastboot driver issue
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.

rasput1n380 said:
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.
Click to expand...
Click to collapse
Trying on an AMD pc/laptop?

taranbeer8 said:
Trying on an AMD pc/laptop?
Click to expand...
Click to collapse
No I am on Intel machine.

rasput1n380 said:
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.
Click to expand...
Click to collapse
Reinstall fastboot drivers or Try different pc or notebook , same thing happened to me still don't know why this happened

taranbeer8 said:
Trying on an AMD pc/laptop?
Click to expand...
Click to collapse
Does this not work on AMD? I'm using a ryzen 7 desktop PC.

moozey said:
Does this not work on AMD? I'm using a ryzen 7 desktop PC.
Click to expand...
Click to collapse
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs

guhvanoh said:
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs
Click to expand...
Click to collapse
Borrowed an Intel laptop and had no issues with unlocking my Poco on there. Thanks for your help, that script might come in handy for a friend.

Can you provide the link or some context for that?
guhvanoh said:
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs
Click to expand...
Click to collapse
Can you provide the link or some context for that? Like maybe the channel link or content

abrahamjroy said:
Can you provide the link or some context for that? Like maybe the channel link or content
Click to expand...
Click to collapse
Hope this doesn't get deleted. The admins frown at this... @ PixelExperiencePOCO
Note the misspelling of pixel, you need fastboot_fix .
HTH
Sent from my SM-T720 using XDA Labs

Question Can't find my phone as Diag mode on device manager

I tried everything but no success yet to find my s22 U as diag mode on the win device manager
Tried via Adb
Tried via *#0808#
Tried via Terminal emulator
Rooter via Magisk
Any help?
Thanks

Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!

perfectswanson said:
Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!
Click to expand...
Click to collapse
Yea i went through the Dm+Modem+Adb option by *#0808# but does not show on device manager as Diag.
i have the samsung drivers from their site

Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:

perfectswanson said:
Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:
Click to expand...
Click to collapse
Nothing changed.

It doesn't change the device in device manager when you change the USB mode. It always says the same thing, only time the device changes in device manager, is when it's in fastboot mode, Download Mode, or EDL mode. You can change the usb settings back and forth and it will not change the device in windows. I think we're talking about different things. Try Holding Vol+ While plugging in the phone to the computer, while the phone is off, AND without touching the side-key or power button. But I think that is just High Verbosity logging. Just out of curiosity, what are you trying to accomplish?

All guides i saw show the phone as Diag on the win device manager...
I lost my imei. You have replied my other post asking about the phone is Sm-s908e.
I'm trying to backup Qcn so i can rewrite imei
Following this guide https://www.hovatek.com/forum/thread-26051.html
But not success to put the phone on Diag mode to be recognized on Qfil
Now I'm trying to flash original rom to see any change
Thanks for the help

I have managed to put the phone on diag mode using Adb.
There was a diferent code on Adb
I was using: "
Code:
setprop sys.usb.config diag,adb
"
And the code that managed to put the s22U into diag is: "
Code:
setprop sys.usb.config rndis,diag,adb
"
(Thx to this This thread)
Now that i have access to my Qcn file it looks corrupted (Or encrypted) comparing to a generic Qcn that i found here on the forum
looking what i can accomplish