Database Info

[Q] How to enable DIAG mode on Defy? (For QPST)

I moved this from the general forum as I think it might be more related to android development (sort of)
Does anyone know how to enable "DIAG" or diagnostic mode on the defy?
(This is required to identify itself correctly to Qualcomm Phone Support Tools as well as other things)
It seems you just need to hold "T" during boot to do this on a Droid, and only enable USB debugging on a Droid X
On some phones like the Samsung Fascinate apparently only this is required:
Code:
Settings - Wireless Networks - Enable Dialup Networking
Also, either:
Code:
echo 1 > /dev/qct_diag_enable
or
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
are said to work for "many" CM7 phones
But I can't find anything about doing it on a defy. Anyone know how you can do this?

Well, I contacted Motorola, and they told me:
Motorola said:
diagnostic modes are only for the information of the technicians, not the end users. We will not be able to provide you any information about this.
Click to expand...
Click to collapse
I paid for this phone, I don't see why they can't tell me how to use the diagnostic mode. They could have just said that it will void your warranty if you use it...
Anyway the important part seems to be setting the modem to diagnostic passthrough, but I'm not sure how you actually do that. Setting it to data passthrough seems to be what USB tethering does, so I'm going to look into that now.
If anyone has any ideas on this or knows the command to enable the diagnostic mode, let me know!
EDIT: The phone portal usb setting aready opens a data port on 192.168.16.2:8080 and I need to open a diagnostics port on 192.168.16.2:11008 as well. Is this likely to be something simple like a command to open the port and the modem will already be listening on that port? I don't know much about networking in linux/android

Try.... it for usbd
usb_mode_ngp
usb_mode_modem_adb
usb_mode_msc_adb
usb_mode_charge_adb
usb_mode_rndis
usb_mode_mtp

Sorry Quarx, I don't understand what those are! Are they commands that I have to type somewhere?
The closest I can find is things like this:
Code:
/sys/devices/virtual/usb_composite/rndis/enable
but nothing seems to happen if I "echo 1 > enable" - it still stays as a 0

try to hold vol+ vol- and power button while boot.

For example.
# Enable ADB mode
write /dev/usb_device_mode msc_adb

@drakeM: That boots in safe mode, which stops non-essential services from starting, but I can't get diagnostic mode through it (or I don't know how to)
@Quarx: I couldn't get those commands to work - I don't have "write" on any of the ROMs I've tried, so I tried echo, which didn't work. I got an error of "could not create /dev/usb_device_mode: error 16"
I tried doing it like this:
Code:
echo mtp > /dev/tempfile
mv /dev/tempfile /dev/usb_device_mode
This ran without errors for all the commands, but I don't think it did anything. I don't know if that was because of the way I did it?
Apparently you can enable diagnostic mode from fastboot:
Code:
fastboot oem rtask c
Is it possible to reboot into fastboot, maybe with 2nd init?

mmec2 said:
I don't have "write" on any of the ROMs I've tried
Click to expand...
Click to collapse
write is for *.rc in rootfs, or other *.rc files that might be imported.

racca said:
write is for *.rc in rootfs, or other *.rc files that might be imported.
Click to expand...
Click to collapse
oh..... ok, so I need to put one of the commands in the "on boot" section of init.rc, restart then try again etc. etc.

Ok, am I doing something stupid? init.rc and init.mapphone_umts.rc get recreated every boot. How can I change them? They just keep changing back to the original version every time I reboot.

[Q] ZOPO ZP990 wont boot after changes to /system/build.prop

Hello, I am new to xda-developers and have just joined up.
I have gone to great lengths to find an answer to my problem with Google and have searched this forum.
Not having any luck I have decided to call out for help.
My situation
- Country: Australia
- Model: ZOPO ZP990 Android phone.
- Android 4.2, Jelly Bean
- Phone is "rooted".
- No recovery backup was ever made.
- My 3G wasn't working. The best I could achieve was "2G EDGE" data connections.
- I have a good HSDPA connectivity with my old LG Android P500 phone in my area.
- As I bought the Zopo phone in China I don't have the option of "after sales service".
- I am an Android newbie and I know very little about Android systems in general.
I was very happy with this phone, except that I was having issues connecting to 3G.
I had used Mobileuncle to configure for the specific 900/2100MHz 3G service in Australia.
Setting the 3G bands with Mobileuncle for my region did not correct my problem with no 3G access.
I then followed the advice to make changes to /system/build.prop
As there were no similar entries in my default build.prop I added the following lines to the very end.
# Start Support for Australian 3G
ro.ril.hsxpa=2
ro.ril.hsdpa.category=5
ro.ril.enable.3g.prefix=1
ro.ril.hsupa.category=5
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.a53=1
# End Support for Australian 3G
I made a copy of the original /system/build.prop to /system/build.prop.bak as a backup.
I made the changes using Notepad++ (on PC) and an Android File Manager (provided root access) app.
I then rebooted and my phone hangs after it presents a ZOPO musical/visual start-up advert presentation.
My phone wont boot !!!
--------------------------------------------
<by pressing buttons on power-up I get the following>
Android system recovery <3e>
Enter: OK Key, Select : Vol UP/ Vol down
Reboot system now
apply update from ADB
apply update from sdcard
wipe data/ factory reset
wipe cache partition
--------------------------------------------
Using ADB(Android Debugging Bridge) Version 1.0.31
(I am using Mini-SDK and not the full Android SDK)
I have "Java Runtime Engine" but not "Java SDK" installed.
I connect the phone to my PC via USB and enter the "Android system recovery <3e>" environment.
I select the "apply update from ADB" on my phone.
I then enter the following commands into my PC.
C:\mini-sdk>adb version
Android Debug Bridge version 1.0.31
C:\mini-sdk>adb devices
List of devices attached
0123456789ABCDEF sideload
C:\mini-sdk>adb usb
error: closed
C:\mini-sdk>adb shell
error: closed
Besides the above commands I cannot get ADB to do anything useful.
I have "USB Debugging" turned off at the phone so I suspect this is why ADB doesn't work.
I know very little about ADB only what I have recently learnt with Google.
--------------------------------------------
I then downloaded the latest ZP990 ROM and Flash Tool V4.2
While I found the instructions straightforward I cannot establish communication between PC and phone via USB.
(I have the correct Android drivers installed on my PC and had full USB functionality before this problem started.)
Once again I suspect the fact that my "USB Debugging" is turned off prevents Flash Tool to work.
--------------------------------------------
I've noticed there is an "apply update from sdcard" in the "Android system recovery <3e>" environment.
I wonder if I can exploit this?
Is there a recovery ROM on the internet that I could download from the net to use on my sdcard?
If I could get any ROM to load, I could later use Flash Tool to do the final ROM upgrade.
Does anyone know if I could use the "apply update from sdcard" from "Android system recovery <3e>" to install a new ROM.
--------------------------------------------
Can someone please help me?
I work in the electronics/IT field, but I know very little about Android systems.
So all I need is guidance on moving forward.
If I sound like I know more about Android that is because I have done a lot of research on the internet to try and fix my phone.
--------------------------------------------

Are you able to do an ADB PULL of the backup you took, rename it on your PC to build.prop, do an ADB REMOUNT then ADB PUSH it back?

I fixed it myself !!!
No need to help me.
I found what I was looking for on the various Android websites around.
I needed to first instal the Mediatek USB VCOM drivers.
Install the latest copy of SP Flash Tool on my PC.
Down load the latest ZP990 ROM from the ZOPO website and unpack it.
Remove battery from phone for a short period. Put the battery back, but don't power up.
Start SP Flash Tool
Select the scatter-loading file from the ROM I unpacked.
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
Things went much easier than I expected.
Lost my data, but I got my phone back. :good:

[FIX] Unknown USB device (Device Descriptor Request Failed) Fastboot Windows 10

First of all, I have a HTC Droid DNA. I was searching for about a year. Finally I got a solution for my problem and I know some of you are still out there with no solution.
The Fail Code is: Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
So I found a German solution where you have to go to regedit.
Step 1: You need to install the HTC drivers (Google, Samsung etc...) in the normal mode your PC will find your phone, but when you turn into Fastboot you get that error "Unknown USB device (Device Descriptor Request Failed) "
Step 2: Make sure you see that error in your Device Manager under USB - Controller
Step 3: Open "regedit"
Step 4: Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
Step 5: Create a new Key called
0BB40FF00100
Step 6: In that Key you create a Binary Value
Name: SkipBOSDescriptorQuery
Value: 01 00 00 00 (ignore the "0000" at the beginning)
Step 7: Reconnect the Phone and enjoy your FIX
I hope I helped you. I can just tell you that it worked for me. I m not sure if it works on all HTC devices.

tried it with a S7 right now, didnt work. thanks for your post tho!

Had the solution for windows 8.1, from a blog on microsoft MSDN. (Sorry can't link to it. Since I'm new @ xda)
But as it turned out the Datatype for SkipBOSDescriptorQuery has changed from windows 8.1 to 10. Instead of a DWORD Value in Windows 8.1 it should be a Binary Value in Windows 10 .
So thanks :good: Now I can connect via fastboot to my HTC Incredible S.
Ps. Google this:
why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43
And blogpost will show as top result

Thank you very much the regedit method worked for sure..
I spent 5 hours on my computer and laptop different usb cables different ports installing uninstalling drivers and ADB nothing
Thanks BoBo Rich:good:

Thnx!!

Didn't work for HTC Explorer (Pico)

Worked with the HTC Aria on Win10 x64!
Thanks a ton.
edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100

Has anyone else gotten this to work?
My Pixel XL isn't recognized at all when plugged in while in system, but it shows up as unrecognized when plugged in while in fastboot. But despite installing the drivers, Windows still refuses to recognize the phone. I tried the various solutions in this thread, but none of them worked. Perhaps it's because my Pixel's fastboot hardware ID is different, but I can't seem to find out what it is.

work perfectly for htc one xl (evita). Thanks !!

Thanks
After 48 Hours of searching!! thanks man! HTC ONE S (Ville)

Thanks! I have this problem with my Shield TV Pro, will try this after work.
Here's some PowerShell code for doing the registry editing, if anyone is interested.
Code:
#Requires -RunAsAdministrator
[string] $Path = 'HKLM:\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100'
[string] $Name = 'SkipBOSDescriptorQuery'
if ($false) {
# Create the path if not exist
if (-not(Test-Path -Path $Path)){New-Item -Path $Path -ItemType 'Directory'}
# Set "SkipBOSDescriptorQuery" to $true
Set-ItemProperty -Path $Path -Name $Name -Value 1 -Type 'DWord'
# Set "SkipBOSDescriptorQuery" to $false
Set-ItemProperty -Path $Path -Name $Name -Value 0 -Type 'DWord'
# Remove item
Remove-ItemProperty -Path $Path -Name $Name
# Remove path and item(s)
Remove-Item -Path $Path -Recurse -Force
}
Edit: This did not work for my Shield TV 2015 Pro unfortunately..

The error changes to "Port Reset failed". Error code remains the same 43. In my case I am trying to connect an LG G3 D858HK. I have tried many different cabels but no solution.

Unknown usb device error Motorola

Doesn't work on lg v20... Haven't been able to fix this issue for a while now..

Thanks for the info mate !
The registry key worked just great in my Windows 10 x64 computer at home and at my work laptop.
I have a Huawei P9 mobile Device.
Had this issue and nothing i tried seemed to work.
Your key did.
Thanks again !!!:good::good:

V20 Method prior to attempt....
@texas### whos still having trouble with a V20 stuck in the firmware screen ( like me) and I have a theory so I'm posting this prior to attempting it but someone please let me know if I have this wrong.
I read this post on the first page of the thread by someone whos name I've forgotten now (sorry) but they wrote....
--------------- edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100 -----------------------
and based on this --- my V20 hardware ID reads "USB\VID_0000&PID_0002\5&2BF451F8&0&2" or rather the instance path does and using this I should be able to correct the value of the binary string to fit this corresponding ID for the VVVVPPPPRRRR correct? so value will be "0000000252BF451f02" ????
Im making the key and binary value now and I'll repost results later
I'm so invested in this phone both in time and sheer ignorance of what else I can do to get this damn thing out of the firmware screen.
* I've tried loading the "LG drivers from both LG composite device and VZW versions" to no avail.
*On a side note, tapping the power button brings up a "download mode" sub screen where is searches for wifi connections and after finding mine I went ahead and tried to connect 1- normally 2- removing my wifi password 3- using the WPS button to connect, all of which ended in "connection failed" so can someone explain the actual purpose of this option if there is no way to connect? or am I finding the wrong signal so to speak>?
Thanks
I'll gladly post all of my results or screen shots, (all failed so far) using ADB, uppercut, LGUP, odin, placing TOT files on the SD card, plus a few absolutely embarrassing methods but had to try something.
Please tell me someone knows a way out of this

Otherwise start a *.bat file containing
Code:
REG ADD HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\0BB40FF00100 /v SkipBOSDescriptorQuery /t REG_BINARY /d 01000000 /f
or use this in the Run window that you can call by pressing the Windows button and R, Win+R.

DEAD
Hi
Hope there's still anyone here that could help. I got the same error {The Fail Code is: Unknown USB device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43)} that appears on windows when watch is connected and i press the red button. I tried to get the identifier via device manager and microsoft message analyzer but it is not detected. What else can i do?
Thanks!

didnt work for the V40. anyone got any ideas?

SuperMike393 said:
didnt work for the V40. anyone got any ideas?
Click to expand...
Click to collapse
Have you tried going to device manager > universal bus controllers, right click USB Root Hub and unintall. Restart the PPC/Laptop and reconnect the device. It works on both Xiaomi and other brands as well.

XT1225 QPST QCN backup needed for Band Unlock analyse for CDMA

As you know,CDMA 850Mhz(BC0) shared the trace of UMTS850,so it could be possible for the XT1225 to fullfill the CDMA parameters in NV memory to get CDMA signal using the same modem fimware with XT1254,
I will give you short brief guide of get this backup,
1.enter fastboot by pressing vol (-) plus power button,choose BP Tools,then reboot into system
2.connect to the computuer then you will find a mdm_daig device in device manager in the unkwnon subset,manualy install driver for this device,then you will get a diag com port(Driver and screensshorts can be found in link below)
3.install QPST provided and add com port in QPST configuration,then using software download to get the qcn format backup!
link for the QPST software https://drive.google.com/file/d/0B3bizPCWTBjcaHZfYWJ4MVBXWk0/view?pref=2&pli=1

Detail backup guide provided by Azlun,http://forum.xda-developers.com/nexus-6/general/how-to-enable-nexus6-xt1103-4g-lte-t3042373
It will be appreciated for you guys provided such QCN file for analyse!

I tried your guide to help you, but no new devices appear when I start my phone with the BP Tools option. Is it because I am using CyanogenMod?

Shooting Star Max said:
I tried your guide to help you, but no new devices appear when I start my phone with the BP Tools option. Is it because I am using CyanogenMod?
Click to expand...
Click to collapse
Did you see some devices under unknown device tree?It goes like diag_mdm diag rmnet,maybe under CM it need such commands apply to make the diag port open.
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 2d09 > /sys/class/android_usb/android0/idProduct
echo 22b8 > /sys/class/android_usb/android0/idVendor
echo 1 > /sys/class/android_usb/android0/enable
start adbd
#under cm12
setprop persist.sys.usb.config diag,diag_mdm,serial_sdio,serial_smd,rmnet_smd_sdio,mass_storage,adb
#under cm13
setprop persist.sys.usb.conf diag,diag_mdm,serial_sdio,serial_smd,rmnet_smd_sdio,mass_storage,adb
Click to expand...
Click to collapse
the red vendor id different from CM versions,you need to find them in the properties of diag_mdm in device manager,but you can just have try if this works.
Anyway,thank you for you attention,bro~

I got a Motorola Test Command only if ADB is disabled. I will try soon. Thanks!

Samsung Luna StraightTalk S120VL FRP Bypass

Samsung Luna StraightTalk S120VL FRP Bypass
In Model Number usually..
BL = Tracfone
VL = Straight Talk
(Both the same company but there are differences in ways used to do FRP removal depending on certain devices so I always list accordingly)
Tested on U2 firmware APJ2 so not sure if this works on U1. If the U2 firmware is wanted I will host and post it here.. It can be found by searching google too.)
Security Patch: (October 1, 2016) and.. should work fine on any other.
I had a stack of these phones gave to me for FRP Removal and these days I usually use Uni Android Tools, OctoPlus, or Z3X boxes for SamSung work. I tried while knowing this would most likely not be possible with this handset model. Success = 0. Tried a multitude of other operations and still nothing. Upgraded Firmware to the latest U2 because i had it, couldn't find a (free) combo in the time i looked and thought maybe it would allow something different.. I might be right. This is the first one in the stack I have done this on. So I will edit / post about U1 (Binary 1) models once this one is finished off. I know the methods work below just getting this write up done first. Anywho..
Whats needed? (each will depend on method taken below)
1) Bluetooth EarPiece
2) Old sim card (Verizon best for this way)
3) ADB Installed (Install this anyway as it's handy to have!) - Here is a link to a super quick and easy installer that will do it and while making ADB systemwide. Thanks to XDA user @Snoop05
Link for basic info - https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Link to Thread for dicussion - https://forum.xda-developers.com/showthread.php?t=2588979
DIRECT DOWNLOAD LINK - https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
4) ADB FRP Removal Application
Lots of ways past this initial point.. Here are 3 i know of that will work for this $20 old pocket buddy.
1) Preperation - First start off by hard resetting your Samsung Luna S120VL
Next find a sim card. I used an older used Verizon sim card. No longer in service. Put it in.
Boot phone. Goto Emergency Dialer. Dial 112 and instead of taking you to 911 (good yeh?) you'll get a voice greeting by Verizon. While this happens pair your bluetooth. (best if you have it in pair mode before dialing)
2) Removal - Three ways to do this. 2 more possibilities to do at the bottom of this post.
a. Connect to WiFi with Bluetooth. -> [Will do this when i get time]
b. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+ Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup. Stay on the very first page of the setup wizard.
-
Now open CMD prompt type
Code:
adb devices
and make sure your device shows something like this -
List of devices attached
8e60d4bf device
Yeah? Ok now copy the following code and paste it into the CMD window and press enter.
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Follow through the Setup Wizard which will quickly drop you onto your home screen and now you are done!
If the above command does not work in your case you can try the following command below. This will take you to login screen and then you can enter you Google account.
Code:
adb shell am start -n com.google.android.gsf.login/
If both previous commands do not work then try this.
Code:
adb shell am start -n com.google.android.gsf.login.LoginActivity
c. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+. Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup.
-
Now use one of the many apps out there to remove FRP now that ADB is enabled. I will ask the moderators about posting but not sure it is allowed. Also the one that is easiest to use and that I recommend will trigger a false positive on Anti Virus. IF ok to post I will update this thread with a download.
----
Other Methods?
Accessibility Mode Method - When i get time (if it's possible.. as a quick check on U2 APJ2 didn't allow much)
ADB enabled boot IMG - Found one and these can be made as well but the one i have found (free) is from the Factory Engineering Firmware I believe. I just don't have much more time to fool with these luna phones. You'd just need to flash this then no need for bluetooth.. Again when i get a minute and remember I will put it up here.
Enjoy!
-noidodroid

Thanks