Database Info

[HELP] Bricked IM-A860L (Pantech Vega No. 6) - QHSUSB_DLOAD

Dear XDA-Developers,
Phone: Pantech Sky Vega No. 6 IM-A860L
Android: 4.4.2 (Stock Rom)
Internal Storage: 32GB
SDcard: N/A (didn't use any)​
What happened?
For years I have been using Sky Pantech Vega No. 6 (IM-A860L) without complaints and then it started crashing (an application Crash Error followed by a restart).
Recently the Crashes became very frequent (once in a week) followed by some Android Recovery process that restarts the phone after doing some "File Check". Yesterday, it started crashing in same manner after each restart (i.e. Phone starts, in next 10 to 20 minutes same Application crash error > Android Recovery process / File Check System > Restart).
Desperately, I tried to re-install the stock ROM "IM-A860L_S1234209.BINX" from ( online official self upgrade page ). That page doesn't work anymore so I search this very forum and found "(Offline)Sky Flash Tool 2014 B2". With that I was able to install above mentioned BINX file without any problems.
Phone booted and everything seemed "Okay". But after 15 minutes it crashed again (it was still plugged into my computer / Windows 7 x64). But this time the Android File Check process didn't appear. In fact nothing appeared at all. But on my computer, I saw my phone getting recognized as "QHSUSB_DLOAD". At this point, I tried starting / powering up the device but no luck. It was blank. No activity what-so-ever.
What did I do next?
Searched the net like crazy. Found that people using other phones (Qualcom based) also had this kind of problem with their devices. I saw some guides showing how to revive the phone by:
1 - Installing QHSUSB_DLOAD Drivers (installed 64bit version of the drivers).
2 - Installing QPST and Flashing two files (8960_msimage.mbn & MPRG8960.hex) with help of emmcswdownload.exe software.​
After installing the above drivers, in device manager, my device is being shown as: Qualcomm HS-USB QDLoader 9008
At this point, using the emmcswdownload.exe software, I'm supposed to flash above mentioned files (as shown below) and then either my phone will revive or it will start showing a mass storage device in the Device Manager.
{
"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"
}
However, after : after 20~25 minutes, nothing happens except my phone starts heating up and the heat gets so intense that I have no other option but to unplug my device.
Please help revive my phone. Thank you

USB connection works only sometimes on SAMSUNG S4 ValueEdition (lineage-18.1-20210717-nightly-jfvelte-signed.zip)

Hi,
I have installed the last LineageOS 18.1 (Android 11) on a SAMSUNG S4 Value Edition.
I got almost everything working, but the USB connection.
Settings-System-Advanced-Developer Options-Default USB Configuration = File Transfer
Now, if I go in System-Connected Devices and the USB cable is plugged in it should appear OTHER DEVICES - USB connection but it doesn't !!! It actually does appear but only very very rarely and randomly !!!
Please offer feedback, many thanks !
Regards

You set USB-mode to File Transfer ( AKA MTP ): File transfer will change your phone to USB mass storage, allowing you move files between the phone and the other device (such as your computer). To access phone in this USB-mode requires another driver.

Many thanks for the quick reply.
But that was the idea! I want to be able to access the S4 jfvelte internal memory (pictures, docs, etc) from a PC.
My expectation was that when I connect the phone to the PC (Win10) via USB cable I can access the phone from WinExplorer but this is NOT so... only very rarely the phone is shown in Explorer.
Contrariwise when I connect another (real) S4 with the official Android 5 I can always access the phone from the PC.

jwoegerbauer said:
To access phone in this USB-mode requires another driver.
Click to expand...
Click to collapse
Does it mean that one should update the jfvelte USB driver first ?
If YES how can I do this ?
Where can I find the right USB driver ?

On windows PC install the MTPdrive 4.1 app - a trial version - what is attached:
MTPdrive is intended to map devices to a drive letter. It works with all devices that operate in MTP (Media Transfer Protocol) mode.
Screenshot:
{
"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"
}

jwoegerbauer said:
On windows PC install the MTPdrive 4.1 app
Click to expand...
Click to collapse
Done. However I cannot notice any change.
The phone is still not visible in Explorer.
If I start the MTPdrive.exe there is no device detected:

I have just installed the last UBS drivers from SAMSUNG (Samsung-USB-Driver-v1_7_43_0.zip) on the Win10 PC.
The Samsung S4 phone (jfvelte - Lineage 18.1) behaves in the same way, namely the phone is most of the time not accessible from the PC via the USB cable. This looks to be a LineageOS 18.1 jfvelte bug. Any idea if there is a way to talk with the LineageOS developers, eventually to report such an issue ?

Hi,
The topic is solved: it was because the phone screen was locked ! as soon as one connects the USB cable to the phone AFTER unlocking the phone screen it works as expected, meaning one can access the files/pictures etc which are being stored on the phone !!!
Many thanks for all !!!

Question ROG phone 5s not recognized in fastboot mode, but ADB works... Windows driver issue?

Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"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"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,

Success is disgusted by some people, and will not share any files for free in the future.

It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.

What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...

For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed

[Discussion] [Question] Android hardware/software structure.

Update:
My phone was not recognized by the computer since the usb flex was broken, the data lines did not work, but the charging lines did.
Watch this video for a solution:
Hello!.
Can someone who understands the subject explain to me how the startup architecture of an android device works at the hardware/software level.
I recently completely lost control of my android device, after some problems flashing a corrupt rom. I don't understand if I deleted any important files or what happened, but my device is not detected by any computer, leaving me unable to use adb or any USB flash tool. I also don't know if this problem has to do with the usb card, since this, if it sends power, the device charges, and is detected by the computer as a generic usb.​
{
"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"
}
Hard brick / Device not found. Sony M4 Aqua E2303.
I installed a faulty ROM which caused my phone to not be detected by my computer (it shows up as an unknown device). I want to flash the original rom, but there is no way, because when I do it with the flashtool and it asks me to connect the...
forum.xda-developers.com
Gretings!

RenzoMag said:
Hello!.
Can someone who understands the subject explain to me how the startup architecture of an android device works at the hardware/software level.
I recently completely lost control of my android device, after some problems flashing a corrupt rom. I don't understand if I deleted any important files or what happened, but my device is not detected by any computer, leaving me unable to use adb or any USB flash tool. I also don't know if this problem has to do with the usb card, since this, if it sends power, the device charges, and is detected by the computer as a generic usb.​
Hard brick / Device not found. Sony M4 Aqua E2303.
I installed a faulty ROM which caused my phone to not be detected by my computer (it shows up as an unknown device). I want to flash the original rom, but there is no way, because when I do it with the flashtool and it asks me to connect the...
forum.xda-developers.com
Gretings!
Click to expand...
Click to collapse
The "device descriptor request:failed) issue is more than likely not a problem with your device, it is more commonly a problem with your PC or your device drivers that are installed on your PC.
If you do a Google search for:
"Unknown USB device(device descriptor request: failed)"
It should find links to guides and videos with troubleshooting steps to solve this issue. Try the methods they describe, sometimes you have to repeat the solution several times before the issue is corrected.

Question Pixel 7 Pro stuck on "usb serial device" with no screen

Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"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"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?

Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...

it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.