Related
I've searched around a few threads but not having much luck on this. I've started on a different computer totally from scratch several times and it just doesn't recognise that the phone has been plugged in. It's really quite irritating as the ODIN CF root method is literally 5 clicks and should take about 10 seconds to do.
I plug the phone into my PC while it's on and it detects it as the USB device and I can go into the folders and copy music on etc etc.
I switch it to download mode, plug it in and it does sod all. No windows beep to say it's plugged in a USB device. If I open ODIN then plug it in it's not doing the COM added.
I've tried installing then uninstalling kies then rebooting, installing just the USB driver, uninstalling, rebooting, reinstalling, rebooting. Just NOTHING seems to make my PCs detect that I've plugged the damn phone in when it's in download mode. It should be such an easy process but I'm left banging my head against the wall mid way through because it just refuses to acknowledge the device. I unplug, switch it on, plug back in and there it is, device connected. I've tried different computers, different USB ports. It doesn't show up in device manager even.
So my question: any idea as to why it will detect when the phone is on normally, but will not even think it's plugged in when switch on in download mode? And of course, how to fix it would be useful!
OK I fixed it.
I uninstalled the USB driver and restarted.
Downloaded/installed a new USB driver (specifically SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.23.0-retail).
Went to download mode and it picked it up straight away! ODIN worked in 10s as expected.
Found the instructions here, for reference. http://www.modaco.com/topic/361286-...-phones-15230-for-win-87vistaxp-adb-fastboot/
I have a (supposed) MT6589 iPhone i5s clone which I managed to brick. I tried to use the instructions here to use the SP Flash Tool to unbrick it, but the first problem I have is with getting my Windows 7 (32 bit) computer to recognize the phone. I installed the MediaTek MT65xx Preloader VCOM driver and it connects for a second. I can see the device connected as a COM device, but it only stays connected for a second and then disconnects. (This is independent of whether I am running the SP Flash Tool or not.)
Is this a symptom of a bad driver? The other problem with trying to follow the instructions is that it says to remove the battery, but this copy is a 1:1 of the iPhone so it is not intended to be opened up. I tried to discharge the battery completely, but when I plug the device in, there seems to be no response (ie, Windows doesn't do anything). At some point, there seems to be some charge in the battery because of constantly plugging in the USB cable, and at that point, is when the device is recognized but is quickly disconnected.
Anyone happen to know what I am doing wrong?
So in general, I am first interested in:
Why is the device connecting properly (I assume) being recognized as MediaTek Preloader VCOM, then disconnecting in about a second?
Is it related to not being able to disconnect the battery?
In theory, wouldn't a dead battery be the same as disconnecting the battery?
When battery is dead, nothing happens when I connect the phone to my PC. This seems odd since I am supposed to be able to connect to the PC without any battery... What is the difference?
Per instructions, I've been pressing the + volume button when connecting, but I seem to get similar results no matter if I press + or not.
Should I be loading any other drivers besides the MediaTek Preloader drivers?
Thanks.
PS. I've decided to open up the phone using a video found on YouTube, and found that the battery is soldered, so I am not so motivated in trying to disconnect the battery if possible.
Update: OK, the problem I likely had with the phone is that since the phone was in a type of "boot loop", I couldn't actually tell it was on or not... And plugging in the cable only worked if the phone is off. Once I made sure the phone was dead due to battery dying and made sure I did not turn the phone on, I could connect, let the battery charge long enough for the phone to respond to the PC, and then it was recognized by SP Flash Tool. However, seems I may have tried flashing something incompatible as the phone is not responding. I'll likely need to write another post once I can find the symptoms of what is going on.
Try hardware preloader MOD which means test point on the phone board; by soldering one to GND and another point on the board (connecting points are clear on the board), this will stop connecting and disconnecting phenomenon
Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
alchzor said:
Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section so that the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
Hi, sorry to hear that happened to you. I suggest you to post this on Xiaomi reddit page, so more people can help you. Here is the link:
https://www.reddit.com/r/Xiaomi/
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.
okay so, i just got this phone. did all updates, enabled bootloader unlocking and made my mi account, downloaded the mi unlock tool and everything.
heres where the problem comes in.
everytime i try the button combination to get into fastboot, it works. but then when i connect my phone to my computer, the fastboot splash screen turns black with little text at the top saying "press any button to shutdown" or something like that. it just wont stay on the fastboot screen, its like its exiting fastboot mode on its own.
why does it do this, and what can i do to fix it?
note: i have downloaded all drivers and software to get this to work, and nothing seems to be coming to light.
please help me, i am very confused.
update: actually, it seems to be fine before i open the mi unlock tool. it seems that when mi unlock tool is not open, it stays in fastboot mode, but as soon as i open mi unlock tool, it just kicks me out of fastboot mode, and goes to a black screen with something at the top saying the exact same thing i mentioned earlier.
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Deexterity said:
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Click to expand...
Click to collapse
i already have enabled usb debugging. but for some reason, it won't just stay in fastboot mode.
was thinking about calling xiaomi and seeing what they have to say. because i cant find anything on this matter, so its probably just something im doing wrong. though it may be my version of windows. i have Windows 8.1. so maybe thats the deal?
this is stressful lol
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Deexterity said:
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Click to expand...
Click to collapse
i know, i did that too. but the problem still persists... ill try some other time.
thanks for helping though
First off this is much better place to ask questions. When phone is running and you connect to pc can you access storage?
If not check drivers, try different usb cable, and try different usb ports.
If yes then can you access the phone via adb?
If not it is a pc issue probably drivers.
If so leave phone booted and connected then open unlock software. Once software is up and running go to terminal/command prompt and type "adb reboot bootloader" without quotes.
I don't think it is windows version but with Microsoft anything is possible. I still use windows 7 for all this stuff.
Had the same problem on my Desktop with Ryzen, i tried it on my laptop with Intel Celeron and it worked from the first try without any drivers installed. If you have AMD that might be the cause
Hello.
My personal experience says:
1 Install Drivers on the PC/Laptop.
2 Activate DEVELOPER OPTIONS
3 Accept O E M Unlock
4 Allow usb debugging
5 Shut down Wi-Fi and use only DATA in order to connect - verify the device to the Mi account you have. When connected, press "understood" or ""accept"" (however it pops up).
6 Connect the phone to the PC/Laptop
7 After being connected, shut down the phone and put it in FASTBOOT. Make sure your PC ""reads"" your phone. Do it through command line/power shell, and make sure it shows up as alphanumeric in command line (i hope you know what to type - e.g fastboot devices)
8 Download and use the mi unlock tool (preferable Versions 2.....). Connect through this tool to your Mi account
9 Ask for permission to unlock // unlock your phone if days-hrs have passed. Ignore any pop-up message/warning and go on.
VERY IMPORTANT NOTES:
A. The phone must be recognized from the PC as ADB INTERFACE (in device manager) both in normal and Fastboot modes. Any other case is waste of time.......
B. Use a good cable and have the mobile charged!
C. In case you have another (older) device connected to your account, disconnect-delete it or else you will end up stuck with a ""cannot unlock message""
D. The process will not work if your PC runs some Win 10 versions as well as if built with RHYZEN PROCESSOR. Prefer PCs running win 7 or 8.
E. You must have DATA connection available or else you will not be able to connect-verify the phone to/through your Mi account !!! it is a new (dual function) fail - safe procedure from xiaomi!!!
F. Make sure you have the correct drivers installed to avoid a brick - bootloop etc
Hope it helps!
Gathered from my own experience!
To summarize: The xiaomi imposes too much rodeo and much time spent of the user to just "try" to unlock a simple bootloader, better to change of apparatus and to be happy with the practicality. lol