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.
Related
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
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
Long story short, my older bro asked if I could fix his phone that crashed during the middle of a regular system update, and now what was suppose to be an easy recovery has brought me here to seek enlightenment, as I feel like I've just about exhausted all of the options I can at this point.
Some of the issues present
Hangs / Loops on Samsung Galaxy boot logo.
Sometimes when connecting USB displays water damage warning with consistent vibration in 2-3 second intervals until phone is restarted or powered bringing me back to issue #1 all over again.
Does not recall it being damaged by water in the past.
Phone not recognized by Windows - device manager displays (Error 43 : Unknown USB Device (Device Descriptor Request Failed) and the control panel device troubleshooter does not find any resolution to solve the issue.
Which leaves the device unable to be seen by ADB/Fastboot, unable to be seen by Odin to flash ROM, TWRP, Clockworkmod, also unable to disable FRP or encryption.
Some of the following things I've done / tried.
Installing several versions of the Samsung Android USB Drivers
Reinstall/Update/Uninstall all USB drivers
Automatically & manually updating driver in Device Manager
Running the troubleshooter via right clicking device in Control Panel
Erasing all traces of (broken) connected USB devices from the registry
Tried a different Windows PC
Tried three separate USB cables, all of which are OEM Samsung
Tried various USB 2.0, 3.0 and 3.1 ports
Placing the stock firmware renamed as "update.zip" in the root directory of SD Card then entering recovery mode and, mounting SD card, wiping cache / data, and selecting the option to Recover/Update from SD Card (phone restarts instantly and brings back to boot logo hang / loop).
Software I've used:
Samsung Android USB Driver (Lastest):
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Android SDK Platform-Tools for Windows:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
(2021-01-01) SM-A530W A530WVLSFCTL1 Android 9 Stock ROM: https://www.sammobile.com/samsung/g.../SM-A530W/BMC/download/A530WVLSFCTL1/1208986/
Samsung Odin 3.14.1: https://odindownload.com/download/Odin3_v3.14.1.zip
USB Oblivion: https://sourceforge.net/projects/usboblivion/
Some pictures that may important:
{
"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'm fairly confident that it is not an issue with the USB ports on the either PC, as my Samsung Galaxy A51 connects and is recognized just fine on both, which is leading me to believe it's either bricked to the point it unable to communicate properly by Plug n Play means, or the USB port on the phone could be damaged by means other than water.
Any help, suggestions, even some opinions please I beg of you before I end up in the nuthouse lol!
Try installing drivers from a separate source?
Hi!
This is my first post here, I hope I won't make many mistakes and troubles...
A friend of mine asked me to help him with his car Android based mirror.
The mirror is a "4G Adas Mirror" which is now stucked on the boot screen/logo.
Android version on the device is 8.1.
I've tried to reset through the hard reset button, without success.
I tried to connect the device on my PC to try to get access with adb, no success.
Adb cant see the device, the device list is empty.
When I check in the device manager on my PC I can see under "Portable Devices" installed,
with the name "MTP USB Device".
I also downloaded several drivers but can't install them, not for my device.
And now I'm out of ideas.
If somebody have any idea what could I still try to bring back the device into live, I would really appreciate.
Thank you.
Btw.:
My PC is running win10 x64 Pro
You're probably stuck with only the MTP interface (and not a composite device with MTP and ADB) but it might be worthwhile to double check.
Is the MTP interface active? Can you see any files in Windows File Explorer?
You can check with UsbView.exe to see if there is only one interface, the MTP.
The next step is to try various buttons on boot to see if you can get to recovery, fastboot or ROM bootloader.
Thanks for the fast replay, I cant access the device throug any file manager, as you mentioned, I checked with UsbView.exe already, just to be sure.
The MTP is active.
I've tried many many times the switch combination with the reset button, to try to get into any recovery or whatever cmd line mode, but without success.
The device hase only two buttons:
1. Power button
2. Reset button
{
"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"
}
Well, there's many ways to skin a cat.
If you open it up there could be a UART with a rooted hardware console.
There could be pushbuttons or test points to get into some other mode.
Good photos will tell us.
So, here we are....
the mirror crashed until I tried to open it.
However, if somebody is interested to hack and poke around this device, I'm familiar to open the device,
make schematics, pictures and try to hack into the device to try to make it alive again.
If somebody is willing to be a part to this pls. let me know and let's get started.
Open it up and take photos.
I'm trying and searching for a way how to open it but not fully crack the mirror, which is actually also a monitor...
I hope I will open the device soo and be back...
Hello everybody!
Yesterday, on 28 of December, I had a massage on my BV4900 pro that a systemupdate is now ready to be installed.
After download of 2,48 GB file the installation went on, the phone started in the next step. On the screen was this white circle and the installation-progress was shown under. After the update was completted, the phone didnt start. The screen ist black. I cannot do anything with it. I tried to flash the firmware or at least the preloader with sp-flash-tool, but cannot. The connection to sp-flash-tool is with 100% but then I see under device-manager is "Media Tek PreLoader USB VCOM (Android)". So the flash-tool does not flash. I tried with volume buttons to stop the battery-loading, but withou sussess. What can I try more to save the phone?
Some more informations: The red LED ist on, when the phone ist connected to pc or power-supply. The phone was rooted. The last android version: 12
And maybe this picture will help:
{
"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"
}
Just a Hint:
Do not flash preloader! preloader is responsible for preloader mode (which used by SP Flash Tool)
Do not use "Format all + Download" option. Formatting whole emmc will brick device.
regarding your issue. follow the recommendations of your screenshot.
aIecxs said:
regarding your issue. follow the recommendations of your screenshot.
Click to expand...
Click to collapse
Yes, I did it already. Nothing helps.
I spend the second day with this problem and do not come forward.
you already tried another cable and another PC? then probably usb jack is faulty. you shouldn't flash anything via usb then!
I am not the one who told you - you could try other flash tools. do not flash, just try to read back for now...
https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement
https://github.com/bkerler/mtkclient
Somebody else, who maybe has an idea?
I found this discription of the error:
The phone seems always be on. With power button I can only "restart" it. How can I shut it down?
Is there a tool I can use for switch the phone off?
Or maybe cmd-command for shutting down the device on com-port? I cannot find anything in internet. Only with adb. But I have no connection to adb, the phone is over adb not rearchable.
Maybe someone can show me the test point for this smartphone?