Or.. I've installed the usb driver package from LG. And I can go to the power off-> charger mode, and get contact with the "modem device", or whatever it is they're using, for a short while. But that won't help me get the bootloader unlock routine to work, it just gets stuck in "download mode!!!!", presumably because it needs to do some weird online routine as well, that I didn't know about, or it needs to download something via gprs, or ... and so on. And in phone mode, the serial number/device doesn't show up. (I tried removing the memory card, on the off chance that having the "mass driver" device turning up would mess something up, but no luck.
Anyway. So is there a trick here, to get adb to detect the devices, or to make the "modem device" mode have precedence, or something of that sort? I'm a bit reluctant to try disabling some of the devices, even if that would work, in case there's something else I don't know about being run half-way as well.. will the mode change on reboot, and I'll get stuck with a brick..?
Have anyone else had the same thing? I can run the pc-suite and the lg support tool just fine. But it seems that what happens is I'm able to have the adb tool detect the serial number for a very short time, and then it disappears and I can't connect to it again. Therefore, no bootloader unlock tool init..
I had the same problems back a while ago.
It got solved on the 262-000 Bootloader unlock thread.
I think you need the newest adb and fastboot drivers
and disable the modem in system settings of your pc,
but search for the mentioned thread and look it up there
Hope you get it working
Related
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
GhostRai said:
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
Click to expand...
Click to collapse
Some people have reported that they have to try repeatedly before it will start in APX-mode. So try again and again before giving up, make sure battery is out and that you firmly press both volume-buttons while plugging it in.
If it absolutely, positively cannot enter APX-mode, then your last hope is Smartflash-mode. Does it start in Smartflash mode if you hold volume-down while plugging it in?
Oh, and make sure you're connected directly to a port on the motherboard.
EDIT: You can try deleting the APX-device from the PC too, to get it rediscovered and reinstalled. Unzip the attached archive and run the batch file in it. (It sets a parameter which allows the device-manager to display hidden and "ghost"-devices before starting it.) Select "Show Hidden Devices" from the View Menu, find the APX-device(s) ("NVIDIA USB Boot-recovery driver for Mobile devices") and delete it/them. Then try to reconnect in APX-mode again. (Have the driver ready.)
Hello all..
I'm sorry if this is the wrong section, but I can't connect my problem to anything similar..
I've been removing system apps on my phone and, unfortunately I selected Lg Home in a group, and without noticing I deleted it.
I did restart it after it.. and the problems started.
I was able to select the custom Home by LG somehow, but I'm enable to go into settings (getting "Unfortunately, Settings has stopped.")
After that, I noticed that I cannot do really anything on the phone.. my PC no longer recognize my device, usb debugging is disabled.
In addition, I cannot get into fastboot (boot loop, when I'm holding the keys),
I cannot go into recovery too.
I could only get to the LG hard reset page, did reset the phone.. with no success at getting anything back.
I have terminal emulator and SuperSU on my phone (it's rooted).
Is there anything I can do with the terminal? Like send LG drivers to my PC, or restarting in fastboot/recovery?
I even tried to flash the original ROM with LG Flesh Tool.
With that program I cannot get phone information, and when I try to flash I get a message saying that Upgrade stopped due to an error.
It asked me to restart and bla bla.. still same
I did try it from download mode, but my phone did not got recognized on the PC again, so nothing there too.
Whenever I connect the device to the PC, windows is searching for drivers for MTP Usb Driver (and fails everytime). Note: I did have those installed before I messed up the phone.
I have ADB and I'm working with cordova, so I tried to install another andorid on my pc, and it got recognized right away (every driver was installed without doing anything, and I can shell it).
Any advice?
Thanks.
Sorry for spamming..
But, nothing really??
formerly rooted H811. I unrooted with supersu and attempted to relock the bootloader. But It didn't take. It appears to be in some in between galaxy.
I get into fastboot, but "fastboot devices" comes up empty.
Would like to lock to update to 20X. No PC, only Mac.
LG Bridge sees USB, but not phone.
Help appreciated.
You do realize locking the bootloader will perform factory reset and wipe your data. Are you trying fastboot through MAC, not sure how it is different from PC so if that is causing the issue can't help much.
Is usb debugging enabled, and you have given permission in the pop-up that pops up on phone screen when you connect it to MAC/Computer the very first time? It is possible you missed that permission pop-up the first time and now permission is denied permanently. You may wanna uninstall and reinstall LG driver/device, connect phone again, and look for that permission pop-up on phone screen and allow it. Try connecting usb cable in different usb port too, that might make the pop-up appear again. Also, remember if bootloader is altered or you got custom recovery, phone will possibly soft brick and you will need to use LG Bridge or LG UP with phone in download mode to reflash kdz. Hope this helps.
Edit: For the permission pop-up to show, the phone needs to be turned on, be in mtp mode, and usb debugging to be enabled. Then once you have given permission, you use adb command to reboot into bootloader or i think with phone off, hold the volume down button while you connect to usb cable and not let go of the volume down button till phone is in fastboot menu.
Hi
After googleing a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops.
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connections to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode is on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to my PC
but as soon as fastboot kicks in I loose connection.
Meanwhile I'm out of ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seems this is the reason) the screen started to unlock/lock erratically. There never was enough time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looooots of patience) I can access my phone. Debugging and bootloader are turned on now. The only way to stop this screenlock/unlock behavior is to turn on flight mode ...
If the phone is connected to a PC I can hear the "unplug sound" as soon as fastboot starts and XiaoMi Tool V2 looses connection.
BTW: Even with many attempts I never managed to establish a connection to Mi PC suite.
And the USB-connection-preferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip
Philipp_P said:
Hi
After googling a lot and trying at least 1001 ADB and Fastboot-tutorials I still am stuck. I only want to flash my A2 with stock ROM, but as soon as fastboot kicks in the connection stops
My phone is unstable (how? see below) but not bricked! I can ...
... access recovery mode and fastboot anytime
... establish data and PTP connectios to my PC (Win 10)
... use it normally (apps, WLAN ...) as long as flight mode ist on!!!!! :cyclops:
... connect the phone with XiaoMi Tool V2 to me PC
but as soon as fasstboot kicks in I loose connection.
Meanwhile I'm out of Ideas how to establish fastboot-connection.
Here's the reason I want to flash - in case it matters: After an Andorid update (or at least it seams this is the reason) the screen startet to unlock/lock erratically. There never was enoug time to enter the code, so I made a factory reset. The problem still prevails, but without screenlock (and looots of patience) I can access my phone. Debugging and bootloader are turned on. The only way to stop this behaviour ist to turn on Flight Mode ...
If the phone ist connected to a PC I can hear the "unplug sound" as soon as fastbot starts and XiaoMi looses connection.
BTW: Even with many atempts I never managed to estabilsh a connection to Mi PC suite.
And the USB-Connection-Pfreferences very often turn to "no data connection". To fix this I usually have to plug out/in or even change USBport or even the computer (-> Win -Laptop)t! Whith no result.
What should I try to flash mi Mi A2?
Thanks and greetings
Phillip
Click to expand...
Click to collapse
Sounds strange . Does RIL work ? Like gsm and sim card ...anyway you need to buy a screwdriver from Amazon or Wish or Whereever and open your phone ..
Search for tutorial videos on youtube on " test point " . You will short the phone forcing it into edl ( deep flash ) mode . In edl you don't use fastboot but rather qualcomm 9008 drivers .
You can flash stock rom with QPST ( Qualcomm flash tool ) or just the regular Miflash from Xiaomi .
In any case ..UNINSTALL ALL I SAY ALL the stuff you have installed on your pc right now including adb .Reboot .Install Qualcomm 9008 drivers .Then download the LATEST VERY NEWEST version of Miflash that comes with drivers ..follow the instructions to install drivers and Mifash itself .
Then follow video tut to enter edl state with test point
VERY IMPORTANT HAVE MIFLASH PREPARED to flash very soon as in 1 or 2 minutes after you enter edl because there is a timeout after which you will get errors and would have to do the test point again ...
Good luck ..if the phone is stolen or contains stolen parts or you used some bypass to enter it to bypass lock screen once it connects to internet or gsm the troubles will most probably return ..if it was or is just some glitch this will solve it .
Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?
Philipp_P said:
Thanks for your help!
I’m not familiar to what RIL is all about. I just googled it, and I guess it works. I can receive SMS when flight mode is turned off and I get a 4G-connection. I can’t do phone calls, but that’s due to the screenlock-problem as soon as flight mode is turned off. I can’t even enter a phone number then … :silly:
I never heard of edl before but found videos. I’ll give it a try. Thanks for all your tips, especially about the edl-timeout. :good:
One last question before I start regarding the uninstalling of EVERYTHING … How can I be sure, I got rid of EVERYTHING? Windows program uninstall showed be "Mi PC Suite", "Universal ADB driver" and "Windows driver package Android USB device class …" I uninstalled all of it.
But I also used Minimal ADB/fastboot and XiaoMi Tool V2 (and probably other stuff I don’t remember anymore) as portable versions. I can delete those fodlers, but is that really enough regarding the drivers that were installed?
Click to expand...
Click to collapse
sure for the portables just delete the folders
Giving up
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.
Philipp_P said:
Screwdrivers arrived, disassembling the phone was surprisingly easy. Actually hitting the tinytiny EDL-contacts was surprisingly difficult on the other hand. :silly: But I managed. But also with EDL my computer pretends my mobile doesn’t exist when plugged in. I guess there must be a hardware-problem somewhere. A this point I give up and buy another one. Thanks for your support, KevMetal.
Click to expand...
Click to collapse
Sorry didn't work friend. Are you sure ? Did you remember to install Qualcomm 9008 drivers from Qualcomm ? Remembering to disable driver verification on windows 10 ...try just more time ...who knows ..
I used a computer with windows 7, because I found on the internet that there are less problems than with Win 10 …
Hello everybody,
To explain things a bit better than just this title. I have a Mi 5 that was working smoothly for quite a long time. Had a modified MIUI ROM flashed on it with many specific apps such as xposed, Magisk and also TWRP. However, my GPS has turned completely dead for some months. Couldn't use it anymore. After some researches, I found out it could be software related. So I decided to flash a new ROM (AOSP Extended) to see if that could fix the GPS issue.
First I backed up the whole system via adb on my laptop and then wiped the whole system. It turns out after trying to flash the AOSP ROM, I came across a message saying I should have MIUI 8.1.30 or older. Or something like that... Can't remember exactly. Just read that I was supposed to update my ROM to a newer stock ROM to be able to flash AOSP in a second time. I did a lot of different operations and I can't remember them all but it turns out one moment, adb started to flash a ROM because the adb command line was saying it. But it failed. Aftert that moment, my phone definitely got bricked. I have no clue what exactly happened, it's kind of confused...
Currently, the phone is always displaying dark screen with mi logo and "unlocked" mention below. Power and volume up will just reboot it to the same state (meaning twrp is not longer installed or accessible). In this dark screen mode, plug the phone to a computer will do nothing, it's not even detected in devices manager. On the other side, power and volume down will boot the phone into fastboot mode, the computer beeps when I plug the USB cable and I can briefly see the Android device with a yellow warning in the dev manager. But after something like 20 seconds, fastboot mode goes off and phone restarts on black MIUI screen.
I've tried to install Google drivers, Qualcomm drivers and did numerous actions but the phone isn't detected anymore. Also, tried to type command "adb devices" in the short time when the phone is detected by computer in fastboot but it shows an empty list. I'm pretty desperate, seems I've tried anything and I've no ideas now... Just saw there is possibly a hardware fix which requires to dismount the back of the phone. Not sure what it does but I'll try it out if no other solution shows up...
Any idea is welcome ! Thanks
Well, looks like my thread wasn't so popular Finally found a workaround after nearly 8 hours searching for a fix. Thought that might help anybody else having the same struggle as mine. What I can tell is that it's not related to the computer used since I've made the same operations on 3 different computers, same problem for each of them. In fact, there were two problems :
First the bootloader not remaining more than 30 seconds. To stop this, I had to open the devices manager and as soon as the Android device would appear after turning it into Fastboot, I would right click on the visible device (appearing with an exclamation mark) and update manually the driver following the process that is described in many topics (locate the Google Android devices USB drivers that I downloaded right before). The time is quite short so you have to be pretty fast, otherwise, the MI 5 would disappear, forcing you to do the fastboot mode operation again. I have to say that doing it without the device being recognized is not working. So if you install with the legacy driver option, it's not going to be associated directly to the device. At least, not in my case.
Once I had done this, the Fastboot mode would remain on. I found my way pretty fast until that moment but the problem was adb wouldn't detect my device. Typing "adb devices" command would return no result, no matter what I did. Strangely, installing an old version of MiFlash (last ones gave me error) would help the computer to detect the device. I don't know why, possibly because the drivers are better ? Anyway, MiFlash helped me to access the phone and Flash a new ROM. Usually, I was just using adb and it would do the job but this time not.
Hope it can help !