Database Develop

[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.

How to UNBRICK HTC desire 626 (When all else fails!!!)

This is made for the AT&T HTC desire 626, But It should work with other similar 'desire' phones,
just download the image for the model you own.
(Note: the buttons for 'download mode' and 'force reboot' should be similar for most models, look it up if needed)
So after spending around 8 hours trying to unbrick this phone, I finally found a working method!
This is a combo of about 6 guides, and some of my own work. so I'll credit who I can remember.
This guide is not meant to be noob friendly, it expects you to have at least some knowledge of android, and flashing.
Anyway, You'll need a few things.
1. Good Quality Micro USB cord
2. HTC sync manager (official link)
3. Stock Rom
(official links) find your model, and carrier.
-----
How to unbrick!
(NOTE, this will DELETE ALL DATA, including the built in storage for music/videos)
Step 1: Enter Download mode
unplug your phone, power off, and boot into Download mode, Hold: [Power]+[Volume Down]
{
"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"
}
Step 2: run the installer for HTC sync manager. (this will install the drivers we need)
Step 3: uninstall HTC sync manager. (only sync manager, we need to keep the drivers)
Step 4: Pause your anti-virus program, or allow the stock image flashing program.
Yes, I know how shady that sounds, double check the link, it's an official HTC program.
And yes, flashing firmware over USB is NOT something most programs often need to too. it makes sense it's treated as a virus.
If you're really worried, use a spare PC. [works on windows only]
Step 5: Connect to your phone via USB.
Make sure any other android devices are disconnected.
And if possible connect directly to the main USB ports, avoid using an (external) USB hub
Step 6: Start Flashing!
Run the Flashing program, the name starts with:
Code:
RUU_
It may take some time to startup, and you'll need to give it admin rights.
To proceed, you'll just need to keep clicking 'Next',
You'll have to agree to some terms, and eventually you'll see the "upgrade" button, click that to start the process.
It will now start flashing your phone, Your phone may reboot a few times,
and the progress bar will fill up to 100% more than once.
(it flashes each part individually, 'Boot image'. 'system', etc)
The whole process should not take very long, it should be done in well under an hour.
The main program will tell you when it's complete.
The phone will automatically reboot, and the phone will be returned to stock!
Notes:
-This will remove root, or any custom, recovery
-If you plan to sell the phone, please note, this dose not unregister the phone from your google account.
IF you want to sell the phone, re-setup the phone as normal. Then, sign in to your google account, and manually remove it
-This dose NOT re-lock your bootloader.
To re-lock, go back to download mode, and run:
Code:
fastboot oem lock
-I am writing this after only 4 hours of sleep, so expect some grammar errors.
And I don't remember all of the buttons prompts from the flashing prompt. but it's very straight forward.
----
Here are some issues I had when following other guides online, this may help some with similar issues.
---
1. phone stuck at HTC logo screen, can't force power down!
Answer: Hold [power] +[volume up] for 10 seconds, that will reboot the phone
2. I Can't get the software to run. (closes after a few seconds)
Answer: If you're running bit defender, it will block the program, unblock it, then turn off bit defender.
3. I can't get the program to run at all!
Answer: Try re-downloading. if you're on the AT&t 626, then the hash should be: MD5: f4d2bdab11290c367136067a96d3dfaf
4. Program fails to flash (stuck at 0%)
Answer: HTC sync manager seems to interfere with the flashing, uninstall ONLY sync manager!
5. Can't enter download mode
Answer: With your Phone OFF, Hold [Power] + [Volume down] it will take you to a weird screen. that is download mode
6. flashing stuck for more than 10 mins! (progress bar never moves.)
Answer: restart using the same method above for stuck at HTC logo screen, then boot to download mode.
-----
Sources:
https://www.reddit.com/r/htcone/comments/3o1l0r/htc_desire_626s_stock_rom/
http://www.htc.com/us/support/htc-desire-626-att/howto/658492.html
http://www.modifyandroid.com/stock-roms/htc/how-to-flash-stock-rom-for-htc-desire-626-att/
http://forum.xda-developers.com/desire-626/development/ruu-att-626-t3272165

Thank you. By simply uninstalling HTC sync manager on your PC allowed me to update and flash ruu thru adb. No more errors! ?

A Guide to Bringing The “Bricked” P10 Plus Back to Life With All Its Details

{
"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"
}
It all started with preparing the P10 Plus to install HarmonyOS. But by an error we have corrupted the device irreversibly. Similarly, if you have broken your P10 Plus while downgrading or updating software, we have good news for you, you can bring your P10 Plus back to life at no cost. Tested and approved!
Let's get started quickly.
First of all, you need to connect your device to your computer to detect the problem. If your device shows as USB_SER in device manager, the steps are even simpler for you. Because USB_SER mode is a mode that you can think of as an emergency recovery mode, created for the purpose of installing recovery software on your device. If your phone switches to this mode as soon as you plug the cable into this mode, it will be enough to follow a few steps. But if you don't get any response when you connect your phone to the computer, we're sorry, you need to turn on your device.
Before proceeding with all these steps, we would like you to know that you are responsible for any problems that may happen to you on the way to unlocking your device, that the Huawei Family is only the guide provider and will not take any responsibility. All these steps will cause your device to be considered within the scope of "unauthorized intervention" if it has a warranty, and we want you to know that you cannot claim any rights in any problem that may occur.
We will continue to explain the hard way, because many devices cannot enter emergency recovery mode on their own.
The list of needs for those who will perform the transaction the hard way is as follows:
- A conductive cable (paper clip, etc.) that will allow you to put your device in emergency recovery mode.
- Thin Phillips screwdriver
- Screen removal vacuum and pick to quickly remove the screen
- Archive with all the files that will bring your device back to life
We will continue to explain the steps, assuming you have removed the screen, you can learn this type of removal from the internet professionally.
When you remove your device until the motherboard is visible, disconnect the battery for your safety, then remove the intermediary cable that connects the lower board to the motherboard, you will see the emergency rescue (testpoint point). Connecting this point takes some patience and experience because you also have to reattach the lower board cable to the motherboard. We used T-7000, which is a screen adhesive, to provide this process. After gluing one end of the conductive cable to the point indicated in the photo with a T-7000 style easy-release adhesive as a tiny dot, attach the connecting cable to the motherboard. Connect your phone to your computer while touching the other end of the conductive cable to one of the metal plates on the motherboard. Then if you did everything right, your phone will appear as USB_SER on your computer. This is a sign that you are approaching the recovery stage.
When it shows as USB_SER, there is a small step you need to take, you need to disable the driver signature verification, otherwise the driver for the emergency mode will not be installed. There are variable steps you need to take to accomplish this, depending on the version of Windows you have.
Windows 7: Type cmd in search and right click to run as administrator, then execute bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS and bcdedit.exe -set TESTSIGNING ON commands. Then restart your computer.
Windows 8/8.1/10: Settings > Update & security > Recovery > Advanced reboot > Troubleshoot > Advanced > Change startup settings > Press 7 on the keyboard. Driver signature verification will be disabled.
11: Settings > Recovery > Advanced reboot > Troubleshoot > Advanced > Change startup settings > Press 7 on the keyboard. Driver signature verification will be disabled.
You can now continue with all these steps by installing the driver for your device. Find the device manager, select the device named USB_SER, right-click it, then click the update driver software button. Then click the browse drivers button on my computer, select the "usb_serx64" folder in the archive we shared with you, and click next. When prompted to install driver, click Install this driver software anyway button. The operation is successful and USB_SER will now appear as Huawei USB COM PORT.
Again, run the program called PotatoNV, which is in the archive. Select "Kirin 960" in the Bootloader section of the program. Then “Start!” Press the button. Disconnect your phone from the computer when the download line at the bottom is full. Then close the PotatoNV program, your device will be in fastboot mode:
We can interpret this mode as vegetative life, if you restart your device without taking any action, the device will enter the emergency recovery mode again. Since our goal is to recover the device, let's continue!
Reconnect your phone to the computer and run the command line named ”flash_1” in the unbrickfw folder in the archive. Recovery images will begin to install on your device. This whole process can take about 15 minutes. When the installation process is completed, your device will automatically reboot and you will get rid of all this torture. As soon as you see the Huawei logo, all the processes are complete.
That's it!
Main source

Question HELP msmdownloadtool - Unknown USB device (Device Descriptor Request Failed)

Good morning everyone. First of all I apologize if I'm posting this in the wrong place.
I have a Realme 8 Pro (RMX3081) I was trying to flash a rom through msmdownloadtool, everything was perfect, the program recognized my device correctly and a few seconds after starting the operation you can see that in the communication status it said "verify data" and then "WCSM communication failed (WCSM code: 4010 the project number is not matching.)
Then I disconnected my phone from the computer and it no longer turns on and when I reconnect it the device manager recognizes it as "Unknown USB device (Device Descriptor Request Failed)"
I also want to point out that something similar had happened to me before, however, although the phone did not turn on, when I connected it to the computer the device manager recognized it as "Qualcomm HS-USB QDLoader 9008", but now he recognizes it as Unknown USB device (Device Descriptor Request Failed). I don't know what I can do please help
I do not know if this has a solution, I will be very grateful for your answers.
Attached screenshot of the error.
{
"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"
}

I explain the solution. Apparently when I tried to flash the phone it went into EDL mode and disconnected from the computer, maybe that's why I'm not sure.
To exit EDL mode just press and hold Volume Up + Volume Down + Power (in that order) until the phone vibrates.

dieguin96 said:
Good morning everyone. First of all I apologize if I'm posting this in the wrong place.
I have a Realme 8 Pro (RMX3081) I was trying to flash a rom through msmdownloadtool, everything was perfect, the program recognized my device correctly and a few seconds after starting the operation you can see that in the communication status it said "verify data" and then "WCSM communication failed (WCSM code: 4010 the project number is not matching.)
Then I disconnected my phone from the computer and it no longer turns on and when I reconnect it the device manager recognizes it as "Unknown USB device (Device Descriptor Request Failed)"
I also want to point out that something similar had happened to me before, however, although the phone did not turn on, when I connected it to the computer the device manager recognized it as "Qualcomm HS-USB QDLoader 9008", but now he recognizes it as Unknown USB device (Device Descriptor Request Failed). I don't know what I can do please help
I do not know if this has a solution, I will be very grateful for your answers.
Attached screenshot of the error.
View attachment 5743421
Click to expand...
Click to collapse
How to access the msm tool. It asks for username and password?

Check and compare project numbers, they don't match.
Use the same ProjID from the PHONE end download the same PROJID *.ofp (Downloaded as PROJID 20714.
To get ProjID - Get the PCB number
dial : *#899#
press the PCB num
Try to use option Try to use default NV.

TechnoR1 said:
How to access the msm tool. It asks for username and password?
Click to expand...
Click to collapse
This video explains
I tried it and it works. You need at least 10 dollars and you can use the program a couple of times.

Question [FIXED] fastboot.exe/Mi Unlock Tool won't recognize my device

Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}

Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?

ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything

yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh

Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.

_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem