Database Develop

[Q] Rooting and the ADB Interface shows but...

Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3

martyslc said:
Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3
Click to expand...
Click to collapse
I'm thinking it should say "Droid Bionic" but not sure how to get it to show?? Maybe it wont in xp?
Any idea's??
-Marty

XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.

cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !

cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !

Huawei Ascend W1 ROM flashing

Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!
papalakaka

I found a way to solve this issue, but I have no idea why it worked.
I installed Windows 7 32-bit on my PC, installed the drivers, restarted and it was instantly recognized as Qualcomm (whatever) 9006.
So I started QPST Software Download app and I was able to download it. It seems that I had to use a 32bit operating system and not Windows 8, at least it looks like that. The Download button wasn't clickable and the device status has shown error on Windows 8 64bit and Windows 7 64bit. It was writable in 32bit. Hope this helps someone out.

Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick

papalakaka said:
Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
Thanks in advance!
papalakaka
Click to expand...
Click to collapse
You need to run as administrator

Huawei W1 does nothing as expected during flashing..
My W1-U00 started having problems with loading apps..whenever I tried to load my photos or weather channel app or whatever it looked like it tried to load the app but it redirected me on home screen. After a few days I had a problem with the space on device and some updates it needed so I tried to uninstall some of the apps but when I did so and restarted the phone the apps where back again. Since that point it's impossible to uninstall any app,impossible to reset the phone from the settings>about>reset phone and impossible to hard reset the device, I tried all the possible ways to do a hard reset but nothing, it just restarts like nothing happened and I get no sprockets logo. So after a few months I decided to reflash my device. Everything went smooth but after I clicked on the download button of the eMMC Software Download app instead make my device recognized by my pc as Qualcomm HS-USB Diagnostics 9006 the device restarts as normal and nothing happens. It's impossible to make it work, I tried all the methods available online but nothing...Any ideas??

jwiena said:
Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick
Click to expand...
Click to collapse
Thanks bro! I was crazy...

[Q] Can't get MTP to work

Hi,
I have been trying to connect my Nexus 6 to my work pc but I just can't get the MTP file copying mode to work properly. I have used the latest Google USB driver and actually it's not so bad. With USB Debugging turned ON, I see "Android Deivce > Android ADB Interface" properly installed in device manager. I even see my phone's serial no. when I type "adb devices" in command prompt. BUT the bloody MTP mode just refuses to work. It keeps showing up in Device Manager as "Other devices" > MTP, with a question mark next to it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I switch USB debug off, there's no Android ADB Interface, and the unknown MTP entry in "other devices" transforms to "Nexus 6", again with a question mark next to it.
I have tried to manually install the proper driver but for starters, if I just select the folder where the .inf files are located Windows don't seem to anything inside it and when I force it to use that file ("Show All Devices > Have Disk") it only shows ADB and Bootloader drivers:
So what am I suppose to choose there in order for MTP to work as it should?

Have you tried other pc or laptop??

Yes, the phone shows up correctly in all modes on my home pc.

Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ

DebianDog said:
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I did that to no success but in the end, I just tried a different USB2.0 port and it worked, all drivers installed correctly. Now the weird thing is I can read from the internal memory of the phone, I can delete stuff from it, but when I try to copy something to it it says: "Error copying. The device has either stopped responding or has been disconnected" so I can't yet copy to it. This is driving me crazy right now...

I have this issue this morning. Right click and Update Drivers > Browse For Drivers > Let me pick > Portable Devices > Standard MTP Device > MTP Device.

Need Method for Google Pixel 4 Android R QPST & QXDM Log Method

Hi ,
I Need to Know the Complete Method How to Connect Google Pixel 4XL Android R With QPST & How to Take QXDM Log for Google
Thanks ,
Nabil Anwar

Hi, I am trying to install QXDM5 ( QXDM5.5.1.280.7.Windows-x86) on win10. First i have installed QPST.2.7.485.7.exe and it is successful and then tried to QXDM5 but while installing seen the error saying that "QUTS.Core was not installed. Reason: CatalogError". Here i have attached error logs. It would great help if some one help me on this issue.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey!
I am working with the EDL mode, I am trying to use it as a way to unlock Pixel boot loader form it's carrier. Though I am still testing...
Let me see if I can help you guys:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.

Fast boot issue - Reported as '????????????' then switches to splash screen

Hey guys,
First time trying to flash a rom (using Windows 11). At first the Razer phone 2 showed up in my device manager as 'Android' with a yellow warning sign. I managed sort that by installing the latest android_winusb.inf drivers, and it shows up in the device manager As oculus Device>Andriod Composite ADB interface (not sure why it's under the Oculus tab, I didn't use the Oculus driver).
I've tried all three drivers (ADB Interface, Bootloader interface and Composite ADB interface) and the results are the same. When I send the 'fastboot devices' command, it will report
''???????????? fastboot'' and then it switches to the razer logo with 'Powered by Android' and 'Press any key to shutdown' text and is no longer in fastboot mode.
I assume the question marks are supposed to be a serial number.
Anyone have any ideas of what I might be doing wrong?
FYI, I've also tried 2 usb 2 ports, a usb 3, and two different Type A to C cables.

This happened to me. You need to run Powershell/Terminal in the path of the folder containing the Platform Tools. See example photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Also, make sure to follow this exactly. https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf

Thank you so much for your help, I will give this a try.

There is some sort of issue with Windows 11 and arter97-r12 and -r13. I was going to do a fresh install of SMR3 because of a few software issues and Google Play app updates. When booted into Recovery and making backups and moving files, I ended the session and rebooted "System" from TWRP boot menu. Upon execution, TWRP warned me there was no OS installed.. WORST NIGHTMARES. I've finally gotten it recovered, but what a MESS. Download platform-tools v33.0.1 from google and follow the directions from Razer to properly install ADB Fastboot drivers. See links below:
Platform-Tools: https://developer.android.com/studio/releases/platform-tools
Razer Driver installation: PDF attached
UPDATE: I found the issue was NOT necessarily my version of platform tools, It was my USB port. I am using a Surface Pro7 and tried multiple different cable and both the USB-C and -A ports to no avail. Would not communicate in fastboot mode, BUT, I then used a 4-port USB 3.0 hub, connected the phone, and all ADB/fastboot commands and communication functioned normally. once I figured this out, I was able to reinstall the proper drivers on Windows.

Same problem, u PC AMD?