I installed 10k rooted on my P705 and was about to install a custom recovery, when the phone came on it was in emergency mode but the computer could no longer detect it, I have tried all the usb ports on about 4 computers and changed the cable trice, So I'm a little bit sure it's nothing to do with the pc. I have tried putting it on holding volume + and -. Any help will be really appreciated because I am stuck right now.
I have gone through the forum for like 6 hours, I couldn't find anything , I apologize before hand if this was treated elsewhere.
Did you try flashing your stock firmware with Software update [KDZ] 1.0.4.4 (KDZ-Flasher) while in emergency mode?
Remove the Drivers and plug the phone in our PC.. maybe reinstall the Drivers
yes I did try to flash it but the computer doesn't detect it in the first place. So I get a " no phone found"
kevios12 said:
Remove the Drivers and plug the phone in our PC.. maybe reinstall the Drivers
Click to expand...
Click to collapse
thank you but that didn't work either
Just to be clear, you're trying to flash your stock firmware with Software update [KDZ] (KDZ-Flasher), while in emergency mode (your phone in is that yellow emergency mode)?
If so, then maybe try the LG MOBILE SUPPORT TOOL.
I'm not familiar with it, but I read here that it's an alternative to Software update.
need4steer said:
Just to be clear, you're trying to flash your stock firmware with Software update [KDZ] (KDZ-Flasher), while in emergency mode (your phone in is that yellow emergency mode)?
If so, then maybe try the ...
I'm not familiar with it, but I read here that it's an alternative to Software update.
Click to expand...
Click to collapse
Thanks but Thats not exactly the problem, It DOES NOT READ to begin with. If the laptop could detect the phone, then I would be able to flash "anything". My problem is the laptop cannot detect the phone....
I'm confused - what do you mean by "DOES NOT READ"?
Your wrote that you are getting "no phone found" in Software update [KDZ].
So I asked if this is happening when you are in the emergency mode (your phone screen is kind of yellow and there is "emergency mode" in it).
I also wrote that if you were in emergency mode, then try LG MOBILE SUPPORT TOOL.
use another computer, maybe a problem with your OS (windows)
need4steer said:
I'm confused - what do you mean by "DOES NOT READ"?
Your wrote that you are getting "no phone found" in Software update [KDZ].
So I asked if this is happening when you are in the emergency mode (your phone screen is kind of yellow and there is "emergency mode" in it).
I also wrote that if you were in emergency mode, then try LG MOBILE SUPPORT TOOL[/URL].
Click to expand...
Click to collapse
Heres the problem, its not detecting, If you can tell me some way to make the laptop detect the phone in emergency mode, I will be extremely grateful, ps kdz equally says no phone found cuz.... the laptop cannot detect the phone and LG MOBILE SUPPORT TOOL equally cannot find the phone connected to the laptop. So..........................................
d-hammer said:
Heres the problem, its not detecting, If you can tell me some way to make the laptop detect the phone in emergency mode, I will be extremely grateful, ps kdz equally says no phone found cuz.... the laptop cannot detect the phone and LG MOBILE SUPPORT TOOL equally cannot find the phone connected to the laptop. So..........................................
Click to expand...
Click to collapse
Okay, I got it.
Did you install the latest drivers?
If not, you can do so by downloading and installing them from your support site or by downloading and installing LG PC SUITE.
After that please open device manager and see if there's anything there with an exclamation or a question mark. If there is, please don't continue and post back what it is.
Only when you see that everything is okay, disconnect your phone, turn it off, enter into emergency mode (by clicking volume up + volume down + power button), make sure that you're in emergency mode (the yellow screen), connect your phone, run Software update [KDZ] (KDZ-Flasher), make sure to set the right type (CDMA / 3GQCT), make sure to leave the PhoneMode in DIAG, browse your kdz stock firmware file, and then click on "Lunch software update".
I'll be looking forward for your comment.
Please don't give up!
luthfi_11 said:
use another computer, maybe a problem with your OS (windows)
Click to expand...
Click to collapse
thanks but I actually tried it on linux, it didn't detect it either.
d-hammer said:
thanks but I actually tried it on linux, it didn't detect it either.
Click to expand...
Click to collapse
i have no problem with windows 7 & windows 8, just try another computer bro
d-hammer said:
thanks but I actually tried it on linux, it didn't detect it either.
Click to expand...
Click to collapse
Try what I suggested above.
Yesterday i was upgrading my LG P705 to 4.1.2 usind KDZ V20B, but it failed & its now stuck in emergency mode. The main problem is my PC is not recognizing it. I uninstalled LG drivers & installed again, but then also, its not recognised my my PC. Please Help.
---------- Post added at 06:00 PM ---------- Previous post was at 05:54 PM ----------
d-hammer said:
Thanks but Thats not exactly the problem, It DOES NOT READ to begin with. If the laptop could detect the phone, then I would be able to flash "anything". My problem is the laptop cannot detect the phone....
Click to expand...
Click to collapse
u fixed your phone or not. plz help. I'm also stuck in same problem.
diwaker0 said:
Yesterday i was upgrading my LG P705 to 4.1.2 usind KDZ V20B, but it failed & its now stuck in emergency mode. The main problem is my PC is not recognizing it. I uninstalled LG drivers & installed again, but then also, its not recognised my my PC. Please Help.
---------- Post added at 06:00 PM ---------- Previous post was at 05:54 PM ----------
u fixed your phone or not. plz help. I'm also stuck in same problem.
Click to expand...
Click to collapse
Same problem here. I downloaded a program called Optimus Toolkit, as I have an Optimus LGl45c, and the program is for
Linux. Same problem- CAN'T SEE PHONE. Program must use ADB, which CAN'T SEE PHONE while it's in emergency mode, as
apparently the correct partition isn't mounted!! Windows KDZ updater sees phone (try the solution from another blog- run in
different compatibility mode: right click on program>properties>compatibility. this worked for me) but the KDZ Updater can't
find the LGMobileDL.dll... lol! wait til you try it!...) So, for he/she who suggested LG PC Suite, please listen. Suite CAN'T SEE
PHONE either, and refuses to run any further....
Anybody have any tricky ways to flash a boot? It would have to be a Linux hack method.....
I think he did not check usb debugging so cant find phone
Not sure if it will work but no harm trying at this stage:
take out batteries,
wait for 30s,
put it back,
hold power and volume down
when keys light up, touch menu button (not the home button)
feel vibrate?
LOL!
pwhitpod3 said:
Same problem here. I downloaded a program called Optimus Toolkit, as I have an Optimus LGl45c, and the program is for
Linux. Same problem- CAN'T SEE PHONE. Program must use ADB, which CAN'T SEE PHONE while it's in emergency mode, as
apparently the correct partition isn't mounted!! Windows KDZ updater sees phone (try the solution from another blog- run in
different compatibility mode: right click on program>properties>compatibility. this worked for me) but the KDZ Updater can't
find the LGMobileDL.dll... lol! wait til you try it!...) So, for he/she who suggested LG PC Suite, please listen. Suite CAN'T SEE
PHONE either, and refuses to run any further....
Anybody have any tricky ways to flash a boot? It would have to be a Linux hack method.....
Click to expand...
Click to collapse
K. A couple weeks later- for those of you with l45c:
You will get to the point where you find that LGNPST is the only thing that will flash. Having troubles registering the .dll? That cost me
over a week. Move the dll to your system/lg electronics/lgnpst folder and open the cmd window (terminal screen) as administrator.
Edit: Use the command> regsvr32 "name of dll".dll
You should google the regsvr command, as it is different for 64 bit machines, and there is a different system file to put the dll in..
Trouble is, we have no proper dll for the 45c. I tried the ms690 dll with an ms690 bin. Unfortunately, it flashed all the way through- and
now I have a perma-black screen... so don't try that.
I DO have an LGL45C-CT2 binary.... just no dll for the 45c, as usual. Not that it would matter- LGNPST cant see phone any more than
ADB could- there is no more 'emergency download'. I will check the battery, etc...
Morale of story- once again, there is evidence that the l45c is not supported. It is not an MS690, and probably not a P690... Use
LGNPST at your own risk, but quit pounding your head over other methods! Time wasted...
Until next time... keep hacking....
<del>
Can someone please post a link to download qhsusb dload drivers and tell how to install theme please.
Is your phone working? Because if you're plugging your phone to the computer and getting this error and your device is not working... it means your eMMC is fried.
Sent from my Nexus 10 using Tapatalk
My phone is dead 15 days ago!!! it is stuck on frozen lg logo splash screen, no recovery mode, only hard reset mode, when tempting download mode, it goes only to the first screen where it's writtend download mode with blue dots, another thing when on lg logo splash screen, my phone shows in device manager under modem and port com, i wanted theses drivers to try linux methode!!! any help would be much appreciated. thank you
Do you know how to use adb and fastboot?
<<Turc şi Mândru>>
yeah, the problem is, adb can't read my phone while it shows normally in device manager
devdassi said:
yeah, the problem is, adb can't read my phone while it shows normally in device manager
Click to expand...
Click to collapse
Did you solve your issue? I am in your same situation
Hi everyone,
I have a turkish phone with the model Avea in touch 3 large, which is a ZTE Q blade maxi.
I'm facing a problem when i get into the bootloader mode, the computer doesn't detect the phone at all.
Can't use the fastboot... whenever i run: <fastboot devices> i get absolutely nothing
when the phone is on i can run : adb devices , but not fastboot devices
i believe it has to do with the phone drivers...
i used padnet to install the phone driver = MT65xx
can anybody help ???
thanks a lot
Sir,
Please wait until mods will move this thread to the device specific forum (ZTE Blade) for more relevant answers.
Stand by
Good luck
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.
Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.