[HELP] Bricked IM-A860L (Pantech Vega No. 6) - QHSUSB_DLOAD - General Questions and Answers

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

Related

Acer Gallant Duo E350

Hi,
I've been having problems with this phone, everytime I turn on the data plan it keeps poping up messages that all the process have stopped working so whenever I rebooted this keeps happening.
I tried going into recovery mode (e3) and wiping (factory reset) everything but this doesn't work, everything remains the same,
So I was trying to follow the guide to root it and load cwm recovery (from this post http://forum.xda-developers.com/showthread.php?t=1899736) but it is not working.
I installed the drivers and I'm able to see my device in the windows explorer but when I start the runme.bat to root the phone it just throws a bunch of error messages.
{
"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"
}
So i tried to load the cwm recovery using the flastool and the process completed with no problem (the green circle appeared) but when I turn on the phone it loads the stock e3 recovery mode.
Is my phone broken ? what do you guys suggest I do ?
thanks in advance
i have this problem to :S somebody can help us??
Liquid Gallant won't reboot
I've got the same issue as mentioned in the post before; does the owner found a solution for his issue?
I tried to follow the tutorial on this forum and got the same issue when installing the *. bat file. File runs but won't detect the phone and closes.
Untill now the problem persists; frequent crash and shut down while using (wathever what, phone, internet, apps,..). I have not much experience with smartphones but it seems to me the internal boot is corrupt. Are any possible tpols or hints available or should the item be returned to ACer (when you know their helpdesk and utility service is crap!)
Same problem
Hello,
I had the same problem last year. I couldn't hard reset ( tried the 2 ways: via the settings or via the volum button when you start). It doesn't reset anything. The applications closes by themselves and I cannot do anything.
Last year, I sent the phone under the warranty and they repaired it and sent to me back.
Now I have exactly the same problem but my phone is not under warranty anymore.
Does anyone found a solution ?
Thanks.

[Q] Help Needed_ZTE v967s

Hi Guys,
I have a problem with my ZTE v967s, if you have any advice, I would really appreciate it!.
How did the problem appear:
1. My phone gave me an error that I have insufficient memory (apps had just few hundred MB, 1 GB was "Missing") so I assumed that it is probably a log file which was soaring and cutting my memory)Phone also had problem to start, I had to restart it few times will the android loaded properly (I assumed it was from the insufficient memory)
2. I have tried following:
a. Factory reset -> it didn’t work, It just restarted to phone.
b. Recovery mode - I wasn’t able to get in to it by holding "Vol+" + "Power" (I should have CWM installed, I did it when I had the phone new together with Max Flavor ROM.
c. I tried following tutorial http://kumaravel-s.blogspot.com/2013/09/storage-space-running-out.html (basically deleted data/log_other_mode)
After the deletion of data/log_other_mode, my phone doesn’t load at all. I either freeze on ZTE logo or it gives me error "encryption unsuccessful reset android" (button reset doesn’t react), lately, it just gives me the ZTE logo
What I tried to solve the problem:
Downloaded SPFlashTool backup ROM from Carliv (http://forum.xda-developers.com/showthread.php?t=2393986 ) and I tried to flash it in to my ZTE using SP Flash Tool. First 2 steps (red, purple) went ok, the third one (yellow) freezes on 0% and eventually it gives me error "BROM ERROR : S_DA_SDMMC_WRITE_FAILED (3149)"
Screen:
{
"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"
}
Same error when I flash whole ROM or just Recovery.
Drivers should be ok, I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2206421
Have somebody had this problem? Do you have some advice what might help?
Thank you!
munky02
Try spflash tool on different pc with windows xp
Dovahpig said:
Try spflash tool on different pc with windows xp
Click to expand...
Click to collapse
I have tried it, the problem persists. Do you have any other ideas?

Nexus 5 Hard Brick

Hey yall,
So just a hour or two ago (as of this thread), I hard-bricked my Nexus 5 and can't get it to power on again. I tried disconnecting the battery and plugging it in again and didn't do the trick. I looked through guides on how to fix it but can't find any guide to fix it. I used Boarddiag but that doesn't recognize the phone (my pc can connect it, but says it's not recognized, prob driver issue) and other software but nothing works. Also when it's plugged in it makes a high pitch sound coming from the top of the phone.
This is really my gf's phone (not actually mine) and tried to put lineageos 18 on it (which i successfully did) and tried using a guide to resize the system partition to install gapps but that bricked the phone.
If anyone could help, that would be great. I want to give the phone back for her to use.
{
"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"
}
ok so i just figured out a guide to patch the boot partition but is still not booting up. Guide said there was a "fastboot mod" what does that mean? (also i was using a windows 7 vm since windows 10 wasnt detecting it properly)
I know it's been a few days but i figured out how to do it!
You have to: (these are the instructions)
-download the 16GB or 32GB patch file (which ever one is for your phone)
-extract the zip/rar/7z file (if you find one)
-Figure out which COM your phone is and it is in the COM Ports in device manager labeled "Qualcomm HS-USB QDLoader 9008" (or if you're using a vm for this method like vmware it can pop up and show which device you're connecting into the vm)
-On the com port, change it to the specified number and change the device to Nexus5
-highlight AP check, SDRAM test (and change that to level 1) and Restore Device
-press start and then your phone should boot up after everything is done! (you have to find your rom though, since it is not in the patch file)
My Nexus 5 was running at once and suddenly turned off while it was about 80% charged
What do you think is the problem? My phone may also be Hard Brick?
deleted
chem20 said:
My Nexus 5 was running at once and suddenly turned off while it was about 80% charged
What do you think is the problem? My phone may also be Hard Brick?
Click to expand...
Click to collapse
No that's an battery issue

S7 - TWRP logo stuck, bootlooping into it & PC not recognise device - The End?

Dear Community!
I have an SM-G930F in a very hard situation I dont know what else I can do.
{
"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 installed a Pixelexperience ROM to my S7, worked pretty well, no issues (Rebooted many times, without any issue*)
*One time the battery drained and it turned off so I plugged it into a charger and it went to the TWRP loading screen.
I can hardly go into the Odin (Download) mode, but the problem is:
Windows gives me an error saying "A request for the USB device descriptor failed (Code: 43)"
The error was there since the Pixelexperience OS was installed (Even when the phone was on!)
I tried everything what possible to try to reinstall the stock firm, or just boot into the pixelexperience, but I think this is the end for the phone.
What I tried:
Cable:
- Tried 5 different cables, tested each other with other devices, everyone is working, but not with my Samsung
PC:
- Tried with 4 different PC running Windows 10/11
- Tried with USB 3.0-2.0
- Tried with, and without Samsung drivers installed
Phone:
- Ofc, tried to force reboot with volume down+ power button (Same thing, booting into TWRP)
- Let it drain overnight. Last thing I tried to do, but sadly no change.. If I turn on a charger, it boots into TWRP, not even to the "offline" charging screen.
If anyone can help me to cure this stupid problem, I would be very thankful.
Or maybe this is the end?
The partition has probably been corrupted. Don't ask me why, there can be many reasons. If you can turn on the phone in download mode then try uploading the stock ROM with Odin.
ze7zez said:
The partition has probably been corrupted. Don't ask me why, there can be many reasons. If you can turn on the phone in download mode then try uploading the stock ROM with Odin.
Click to expand...
Click to collapse
This is the sad part, because with 4 different pc with 5 different cables not recognise my phone as an USB device (Code:43) You can read it in the post. :\

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

Categories

Resources