i have a ZTE Max Duo Tracfone which is stuck in a boot loop. What is different about my phone caught in a boot loop, from (other phones caught in a boot loop mentioned on this website is that other people have flashed ROMs which caused the loop, but I have not done that. My device is not rooted. I don't know how it happened but I rebooted because UNDER PHONE SETTINGS/APP I could not clear the cache from google play or anything. Under the reboot menu, I have since wiped the cache and know that the inevitable end is to re-set the phone which will wipe out my calendar, my data, etc.
My question is this, is there anyway I can transfer my data or files on my internal hard drive while it is stuck in the boot loop? I have installed Wondershare android and Mobiledit, but neither have been able to find my phone to transfer the files. Could it be that when a phone is stuck in a boot loop, windows 10 cannot read the phones internal hard drive until the booting is finished? Therefore, since the OS cannot advance past the loop, I can't open the phone to copy it?
I have installed the ZTE universal driver, but Windows (pc) doesn't recognize my phone when I plug it to the PC via cable. Under WINDOWS 10 DEVICES, it says nothing, but once I plug in my phone, Windows 10 device Manager does say Universal Serial Bus Devices/ADB interface, and under (OTHER DEVICES), a device called MTP appears with a yellow asterisk, but i see nothing about zte driver. I tried to update MTP with the ZTE Driver, but it said incorrect driver. Maybe I need the ZTE DUO driver which I haven't been able to find on google. I only have used the universal zte driver.
Not a noob, but not an expert either. Recently installed Android studio, but I don't see anything on the menu which allows me to run commands for the phone. am willing to try anything to save my data.
thanks you, james
Related
Hi, I'm very new into the smart phone world and in quite a predicament.
I tried to install CM11 from stock ROM via TWRP.(Installed via Autorec)
Reboot to recovery then wiped Dalvik Cache, Data, Cache then install "cm-11-20140509-NIGHTLY-vs980.zip" with successful result.
After reboot the LG logo appeared then black screen, and LG logo again in the boot loop.
Being the thoughtful and intelligent young man that I am, I didn't make a recovery before hand. It won't enter download mode, only recovery mode. My PC won't recognize it either, even when trying to sideload in TWRP. I've been googling and trying things for over 4 hours now. Hopefully someone here will be able to figure it out.
Much thanks, Z
Somthing I just now noticed, when I plug it into my PC it recognizes something being plugged in, tries to install drivers and fails. I was fairly confident I had all of the necessary drivers but I will re-download them.
-Updating the drivers did nothing, the PC still won't recognise my phone.
I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Just saying, whenever you root your phone you gotta make sure to have a stock firmware in case of emergencies... It's no one's fault.
hi all,
does anyone have a solution to installing a custom rom on blu studio xl (lte)? the stock rom is on Android 5.1 and its laggy as all hell.
thanks much in advance,
ak
Install mtk v com drivers.
Similar thing happened to me on a mtk phone, I have all software and drivers etc on my home pc, not here. Send me a message tomorrow to remind me and I'll Google drive them and give you a link, with instructions. It can be fixed! Don't panic! I assume you have stock firmware? If not, get that ready and downloaded ready. Also, a few different versions of SPflash tools, some don't work on some phones, even the same phones. And different USB leads also.
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.
So this is a budget phone , spent hours obsessing over rooting it, did the whole process several different times several different ways,
the funny thing is , i can't event brick this device . this runs OREO 8.1 which a chopped down version of the full OREO 8.0 , basically it's designed for budget "entry level phones" . So i'm wondering
why they would make it so unbrickable? is it possible that this device doesn't even have a bootloader? if not why is it so hard to get to it?
Can't access fastboot mode nor the bootloader
One year later and this is still an issue. Here is my situation:
I bought an OTG (on-the-go) cord that allows me to connect a USB stick to my phone in order to extend my storage capabilities, but my phone doesn't natively support OTG (it basically doesn't have the drivers for it). In order to add support for it I need to root my phone, which I am having serious trouble with.
After hours of researching, installing, uninstalling, and factory resetting I've narrowed everything down to not being able to access the bootloader to select the fastboot mode. Here are my phone details:
Device Name: LG K20 (boot screen says "LG k20 Plus" however)
Model: LM-X120WM
Android Version: 9
Build Number: PKQ1.180904.001
Software Version: X120WM11c
As far as configurations go, I have:
- Enabled Developer Support
- Enabled OEM Unlocking
- Enabled USB Debugging
- Made my computer a Trusted Device on the phone
- There are no special "adb" options or configurations within my phone (I saw one website mentioned something about "adb" some options, but I only saw this once, and my phone doesn't have it anyway).
So far I have tried:
1) Holding the Power + Volume Down button for 10 seconds, then releasing the Power button when I see the LG logo, then repress the Power button until I see the "Factory Reset" menu. All this does it give me options to Factory Reset unfortunately (which I've done).
2) Holding Power + Volume Down button for 10 seconds. This simply reboots the phone and does nothing else.
3) I've downloaded, installed (on both my phone and my computer when needed), and tried rooting using the following programs: Dr.Fone, KingoRoot, RootGenius, iRoot, SuperSU Pro, and Superuser. There were some others I tried as well, but I determined I couldn't get anywhere with them specifically because I could not access fastboot mode (one example is "Magisk Manager").
4) Using ADB tools within command prompt (the most commonly recommended method) I tried rebooting the device into fastboot mode using the command "adb fastboot bootloader". The phone simply reboots and that's it, it has not switched into fastboot mode. You can confirm if you are by using the command "fastboot devices", which my device never shows.
5) I have gone to the LG website in order to download the drivers for this phone, however, while I am able to locate my specific device on the LG website, it directs me to download the "LG Mobile Support Tool", rather than download the drivers specifically for this device. I downloaded and installed the LG Mobile Support Tool but when the tool loads it does not recognize my device and tells me I need to install the drivers, which it gives me an option to do. Naturally I start the process to install the drivers but when it gives me the list of phone models mine is not in there *and you cannot proceed without selecting a model*. So, I tried using the closest model to mine (the LMX510WM), but it still didn't work.
6) Because LG does not have a direct download of the drivers for this device specifically I have tried downloading a variety of different drivers for this device. None have resolved the issue, but at this time *I believe* I have the most recent version of the LG drivers available "LGMobileDriver_WHQL_Ver_4.5.0".
7) I've tried adding the USB drivers through any install tools that came with them, and I've tried installing them manually via "Device Manager -> Add Legacy Hardware" and choosing the driver files specifically. This has not resolved the issue.
8) Installed the "wpdmtp.inf" file found within "c:\windows\INF" as recommended for Windows 10 users on one forum or another. Did not resolve the issue.
9) Installed the full Android Studio suite hoping something I was missing would be available, I also tried using the "adb" tools they provided: no love.
10) I also tried powering off the phone, holding the Volume Down button while plugging in the USB cord. This is supposed to do *something*, the instructions says I should enter "download mode", but on my phone does nothing.
11) the XDA-Developers forum suggested installed LGBridge_Setup.exe if I was having problems with drivers, which I have. When I ran the program it wasn't able to connect to my phone.
At this time I've uninstalled almost all software and all extra drivers from my computer (I left only the "LGMobileDriver_WHQL_Ver_4.5.0" drivers), as well as having factory reset the phone.
Everything is ready for another attempt, I've just run out of ideas. Thoughts?
Hi, I have also been trying to root this phone for the last year, but failed.
Everything is exactly the same as your phone regarding Build#, model # etc except i have software version X120WM10c .
The phone always wants to update but then it fails every single time.
I am hoping to root the phone so i can debloat it, and remove the restrictions preventing me from using it the way I want.
Anyone have any advice/info please post here. I will do the same.
Anyone? No response in almost a year.
ckeays said:
Anyone? No response in almost a year.
Click to expand...
Click to collapse
first of all you guys, are talking about two diferent very disimilar phones.. mediatek v20,qualcomm on the k9.....
myself i have a x210wm k9 im trying to find compatable firmware for.
The phone is working fine without root. Seems very fast for $99 CAD phone!
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.