This Thread dedicated to LG V10 VS990 variant only, I may add another threads for other variants soon.
If you tried to downgrade your VS990 to lower version or flashed with wrong firmware, Chances you stuck on Qualcomm Mode 9008.
in this guide I will show you how to Unbrick Your VS990 LG V10.
1- Install Qualcomm Drivers: Download from here
2- Install QPST: Download QPST 2.7.460 from here
3- Download Qfil Unbrick Files from here: VS9902AA with Fixed GPT modified Error.
4- Extract the Qfil zip file you downloaded.
5- After installing the drivers & QPST, Open Qfil from this location C:\Program Files (x86)\QUALCOMM\QPST\bin
- Plug your Phone via USB, If Everything works correctly the phone should appear as Qualcomm HS -USB QDLoader 9008 on top.
- From Select Build Type select Flat Build.
- Tap On Browse and select the file prog_emmc_firehose_8992_lite_lge1.mbn from the Qfil unbrick files Folder.
- Tap on Load XML Button and select rawprogram0.xml then patch0.xml.
- Click on Download, The unbrick process should begin,
6- If everything works correctly, You should see success in the log area, After that disconnect the phone, unplug & plug the battery, Hold Volume UP and connect the USB cable, Your phone should go into Download Mode.
7- Flash your phone with the latest version VS9902AA (recommended), You can download it from here.
Warning! Newbies Guide
Many users faced GPT Modified problem with bootloops after the unbrick process, if that's the case, You have to open your device and short the test point like its shown in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please follow this guide carefully.
1- You have to disassemble the phone: follow this guide
2- Using tweezers, Gently short the small resistor like shown in the image above to gnd (Ground), while you are doing that connect USB to PC, Wait few seconds you should see your device in Qualcomm mode, you can unshort now.
(Don't push too much on the resistor, you could brick it.)
3- Now, repeat the old process with new VS9902AA Unbrick-Qfil-Fix-GPT-Modified Qfil files.
4- If this method works, Please report quickly in the comments.
Note: If you have a problem with Qualcomm drivers, You should disable driver signature verification from your windows. Just google it & you will find how.
I'm sorry for my bad english.
Donate if I helped.
If you have any issues you can post it here, I will try to help.
Greet thank's This work perfec
cheetzcell said:
Greet thank's This work perfec
Click to expand...
Click to collapse
Did u unbricked your device?
cheetzcell said:
Greet thank's This work perfec
Click to expand...
Click to collapse
Is this metode works? Bcz i have bricked H900 with VS990 Mainboard inside
---------- Post added at 12:31 AM ---------- Previous post was at 12:21 AM ----------
cranknet said:
This Thread is dedicated to LG V10 VS990 variant only, I may add another threads for other variants soon.
If you tried to downgrade your VS990 to lower version or flashed with wrong firmware, Chances you are stuck on Qualcomm Mode 9008.
in this guide I will show you how to Unbrick Your VS990 LG V10.
1- Install Qualcomm Drivers: Download from here
2- Install QPST: Download QPST 2.7.460 from here
3- Download Qfil Unbrick Files from here: VS99029A - VS9902AA this is the latest version right now.
4- Extract the Qfil zip file you downloaded.
5- After installing the drivers & QPST, Open Qfil from this location C:\Program Files (x86)\QUALCOMM\QPST\bin
- Plug your Phone via USB, If Everything works correctly the phone should appear as Qualcomm HS -USB QDLoader 9008 on top.
- From Select Build Type select Flat Build.
- Tap On Browse and select the file prog_emmc_firehose_8992_lite_lge1.mbn from the Qfil unbrick files Folder.
- Tap on Load XML Button and select rawprogram0.xml then patch0.xml.
- Click on Download, The unbrick process should begin,
6- If everything works correctly, You should see success in the log area, After that disconnect the phone, unplug & plug the battery, Hold Volume UP and connect the USB cable, Your phone should go into Download Mode.
7- Flash your phone with the latest version VS9902AA (recommended), You can download it from here.
Note: If you have a problem with Qualcomm drivers, You should disable driver signature verification from your windows. Just google it & you will find how.
I'm sorry for my bad english.
Donate if I helped.
If you have any issues you can post it here, I will try to help.
Click to expand...
Click to collapse
How did u make qfil files, i will try to help you make qfil file from another kdz version. The lollipop one.
petriandra said:
Is this metode works? Bcz i have bricked H900 with VS990 Mainboard inside
---------- Post added at 12:31 AM ---------- Previous post was at 12:21 AM ----------
How did u make qfil files, i will try to help you make qfil file from another kdz version. The lollipop one.
Click to expand...
Click to collapse
Try with VS9902AA version, if it doesn't work, You may try with H90021w unbrick files in V10 At&T section.
It will work, but you will face problems like security settings stopped, no hotspot.... I recommend you to use it as a last resort.
cranknet said:
Try with VS9902AA version, if it doesn't work, You may try with H90021w unbrick files in V10 At&T section.
It will work, but you will face problems like security settings stopped, no hotspot.... I recommend you to use it as a last resort.
Click to expand...
Click to collapse
Hi cranknet,
The qfil completed successfully. I removed the battery and put it back again. Plugged the USB cable with vol up pressed, kept it pressed for another 10-15 seconds, then released it. Nothing! I repeated the unplugging and plugging process. Nothing. Before qfil I was in Qualcomm mode. Now there's nothing. It's still plugged in for the past 10 mins. I don't know if this is normal. Anyway LGUP is not recognizing anything either. Did I miss something?
Thanks.
Update: After about 15 mins the phone booted with the LG Life's Good logo. I guess the battery must have been empty and after it charged some, it booted. Anyway, now it's in an unending bootloop. I disconnected from PC and again connected with volume up, after some vibration it gives a "790 GPT modified: 3" message on top left and then goes in bootloop. LGUP still doesn't recognize the phone (neither does it show now in device manager). But at least I am glad now that my phone shows some signs of life. With a little help it should be back to complete normalcy. Waiting for guidance.
Thanks.
pricksharp said:
Hi cranknet,
The qfil completed successfully. I removed the battery and put it back again. Plugged the USB cable with vol up pressed, kept it pressed for another 10-15 seconds, then released it. Nothing! I repeated the unplugging and plugging process. Nothing. Before qfil I was in Qualcomm mode. Now there's nothing. It's still plugged in for the past 10 mins. I don't know if this is normal. Anyway LGUP is not recognizing anything either. Did I miss something?
Thanks.
Update: After about 15 mins the phone booted with the LG Life's Good logo. I guess the battery must have been empty and after it charged some, it booted. Anyway, now it's in an unending bootloop. I disconnected from PC and again connected with volume up, after some vibration it gives a "790 GPT modified: 3" message on top left and then goes in bootloop. LGUP still doesn't recognize the phone (neither does it show now in device manager). But at least I am glad now that my phone shows some signs of life. With a little help it should be back to complete normalcy. Waiting for guidance.
Thanks.
Click to expand...
Click to collapse
What Qfil u use?
petriandra said:
What Qfil u use?
Click to expand...
Click to collapse
The one provided here by cranknet in this thread. I uninstalled all previous versions and drivers including qualcomm, lg usb, etc. But I guess it was not an issue. Qfil completed successfully. Or didn't it?
Thanks.
V10 H901 w/ vs990 now in bootloop
Alright. I followed cranknet's every step in detail. I used only the files downloaded from the op. My qfil was successful on all counts. It all took not more than 5 mins. I saved the log and I can see there was not a single error. Yet. When I rebooted with volume up, it went in a bootloop instead of the download mode. I get a a "790 GPT modified: 3" before the lg logo appears and keeps on bootlooping then on. Any idea what it all means?
Thanks.
pricksharp said:
The one provided here by cranknet in this thread. I uninstalled all previous versions and drivers including qualcomm, lg usb, etc. But I guess it was not an issue. Qfil completed successfully. Or didn't it?
Thanks.
Click to expand...
Click to collapse
I will try tonight with qfil that i made from VS990_11B kdz, i'll let you guys know soon. Hope it will works
pricksharp said:
Hi cranknet,
The qfil completed successfully. I removed the battery and put it back again. Plugged the USB cable with vol up pressed, kept it pressed for another 10-15 seconds, then released it. Nothing! I repeated the unplugging and plugging process. Nothing. Before qfil I was in Qualcomm mode. Now there's nothing. It's still plugged in for the past 10 mins. I don't know if this is normal. Anyway LGUP is not recognizing anything either. Did I miss something?
Thanks.
Update: After about 15 mins the phone booted with the LG Life's Good logo. I guess the battery must have been empty and after it charged some, it booted. Anyway, now it's in an unending bootloop. I disconnected from PC and again connected with volume up, after some vibration it gives a "790 GPT modified: 3" message on top left and then goes in bootloop. LGUP still doesn't recognize the phone (neither does it show now in device manager). But at least I am glad now that my phone shows some signs of life. With a little help it should be back to complete normalcy. Waiting for guidance.
Thanks.
Click to expand...
Click to collapse
is there any battery logo or sign while u charging the phone, for 15 minits before the logo come out
petriandra said:
is there any battery logo or sign while u charging the phone, for 15 minits before the logo come out
Click to expand...
Click to collapse
No. If I plug it into the charger or to the laptop through USB, the bootloop begins even if I haven't pressed any keys. Then I must take the battery off to stop it.
Now if you mean, if I did get any sign when my phone was supposedly charging when I first booted my phone after qfil? Then no. There was nothing. The screen was blank and dead as a dodo. Or the way it was since the LGUP MM update a month ago. I waited 10 minutes then replied on this thread about it and 5 minutes later the lg logo came up and the bootloop started. I unplugged it from the laptop, removed the battery, put it back in, pressed the vol Up and plugged the USB into my laptop. "790 GPT modified: 3" and bootloop goes on and on again.
Thanks.
Twiddling my thumbs. I've been at it for the past 12 hours straight. The qfil was successfully completed in the first five minutes. Rest of the time I thought - any moment now till someone responds with the solution. Tired. Taking a nap. I have put the mail notification on and I'll be up the moment I receive a response from xda.
pricksharp said:
Twiddling my thumbs. I've been at it for the past 12 hours straight. The qfil was successfully completed in the first five minutes. Rest of the time I thought - any moment now till someone responds with the solution. Tired. Taking a nap. I have put the mail notification on and I'll be up the moment I receive a response from xda.
Click to expand...
Click to collapse
im also waiting please i have almost lost all hope because my pc cant recognize my phone anymore
pricksharp said:
Hi cranknet,
The qfil completed successfully. I removed the battery and put it back again. Plugged the USB cable with vol up pressed, kept it pressed for another 10-15 seconds, then released it. Nothing! I repeated the unplugging and plugging process. Nothing. Before qfil I was in Qualcomm mode. Now there's nothing. It's still plugged in for the past 10 mins. I don't know if this is normal. Anyway LGUP is not recognizing anything either. Did I miss something?
Thanks.
Update: After about 15 mins the phone booted with the LG Life's Good logo. I guess the battery must have been empty and after it charged some, it booted. Anyway, now it's in an unending bootloop. I disconnected from PC and again connected with volume up, after some vibration it gives a "790 GPT modified: 3" message on top left and then goes in bootloop. LGUP still doesn't recognize the phone (neither does it show now in device manager). But at least I am glad now that my phone shows some signs of life. With a little help it should be back to complete normalcy. Waiting for guidance.
Thanks.
Click to expand...
Click to collapse
after flash the right files from kdz phone should enter dl mode if wrong files flashed with qfil phone will not show any sign of life then you need to short test points to put it in qualcomm mode again
samy2015 said:
after flash the right files from kdz phone should enter dl mode if wrong files flashed with qfil phone will not show any sign of life then you need to short test points to put it in qualcomm mode again
Click to expand...
Click to collapse
Samy, as you know, my phone was hard bricked and was in Qualcomm mode for over a month. After this qfil flash I'm at least getting the LG logo. I thought this was a good development. A bootloop doesn't seem as hopeless as a cold hardbrick. Isn't this a good sign? Do I surely need to short test points? I will definitely if it's necessary.
Thanks.
samy2015 said:
after flash the right files from kdz phone should enter dl mode if wrong files flashed with qfil phone will not show any sign of life then you need to short test points to put it in qualcomm mode again
Click to expand...
Click to collapse
what is the right pin for test point for v10? any pictures?
---------- Post added at 02:54 AM ---------- Previous post was at 02:34 AM ----------
Try the qfil last night, ended with success status, but phone become dead. No bootloop, no logo, no qualcomm mode. Already tried the to short test point, nothing happend. Duh... epic fail
petriandra said:
what is the right pin for test point for v10? any pictures?
---------- Post added at 02:54 AM ---------- Previous post was at 02:34 AM ----------
Try the qfil last night, ended with success status, but phone become dead. No bootloop, no logo, no qualcomm mode. Already tried the to short test point, nothing happend. Duh... epic fail
Click to expand...
Click to collapse
Hello cranknet we are counting on you please help us let us know if there is no hope thank you... is there any way we can get our phones to qualcomm 9008 mode again
cranknet said:
This Thread is dedicated to LG V10 VS990 variant only, I may add another threads for other variants soon.
If you tried to downgrade your VS990 to lower version or flashed with wrong firmware, Chances you are stuck on Qualcomm Mode 9008.
in this guide I will show you how to Unbrick Your VS990 LG V10.
1- Install Qualcomm Drivers: Download from here
2- Install QPST: Download QPST 2.7.460 from here
3- Download Qfil Unbrick Files from here: VS99029A - VS9902AA this is the latest version right now.
4- Extract the Qfil zip file you downloaded.
5- After installing the drivers & QPST, Open Qfil from this location C:\Program Files (x86)\QUALCOMM\QPST\bin
- Plug your Phone via USB, If Everything works correctly the phone should appear as Qualcomm HS -USB QDLoader 9008 on top.
- From Select Build Type select Flat Build.
- Tap On Browse and select the file prog_emmc_firehose_8992_lite_lge1.mbn from the Qfil unbrick files Folder.
- Tap on Load XML Button and select rawprogram0.xml then patch0.xml.
- Click on Download, The unbrick process should begin,
6- If everything works correctly, You should see success in the log area, After that disconnect the phone, unplug & plug the battery, Hold Volume UP and connect the USB cable, Your phone should go into Download Mode.
7- Flash your phone with the latest version VS9902AA (recommended), You can download it from here.
Note: If you have a problem with Qualcomm drivers, You should disable driver signature verification from your windows. Just google it & you will find how.
I'm sorry for my bad english.
Donate if I helped.
If you have any issues you can post it here, I will try to help.
Click to expand...
Click to collapse
Question. Should I uninstall all drivers, including the universal Google device drivers BEFORE installing the Qualcomm drivers?
kofi26 said:
Hello cranknet we are counting on you please help us let us know if there is no hope thank you... is there any way we can get our phones to qualcomm 9008 mode again
Click to expand...
Click to collapse
Samy2015 from the successful V10 f600l unbrick thread suggests test pin shorting to get back to the Qualcomm 9008 mode again. I will definitely do it but I am waiting for cranknet for his view on might have gone wrong with this. Mine was hard bricked due to the update and now on bootloop after this qfil unbrick.
---------- Post added at 06:18 AM ---------- Previous post was at 06:02 AM ----------
petriandra said:
what is the right pin for test point for v10? any pictures?
---------- Post added at 02:54 AM ---------- Previous post was at 02:34 AM ----------
Try the qfil last night, ended with success status, but phone become dead. No bootloop, no logo, no qualcomm mode. Already tried the to short test point, nothing happend. Duh... epic fail
Click to expand...
Click to collapse
Following are the links in which the test pin shorting is vividly demonstrated. But just the shorting. I won't go further as the rest is for non-vs990 motherboards.
http://www.aryk.tech/2017/11/lg-v10-hardbricked-unbrick-solution.html
https://forum.xda-developers.com/showpost.php?p=73004040&postcount=2
Related
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
I have the same problem help!!!
LoToR122 said:
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
Click to expand...
Click to collapse
No responses to Emergency mode flashing by KDZ?
Try at least with HARD RESET... Hold Power Key + Volumen Down key + Home key
When LG logo appears, release all the keys! Good luck!
LoToR122 said:
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
Click to expand...
Click to collapse
Give me a pm when you have 1 hour I might have an idea to save you.
christi9503 said:
Give me a pm when you have 1 hour I might have an idea to save you.
Click to expand...
Click to collapse
Can you help me? pls
kikobuendia said:
I have the same problem help!!!
Click to expand...
Click to collapse
First, there is no such thing as hardbrick (not anymore, most modern phones cant be hardbriked )
Be sure, u have all the drives and whatnots installed in the copmuter !
from: http://forum.xda-developers.com/showthread.php?t=2730501
[Q] How to install a .kdz?
[A] (Tutorial thanks to @[W]ar[H]ead, confirmed working by TaZRAge)
#1) First to get into download mode:
1. Remove battery
2. Put usb to computer and phone (w/o battery)
3. Hold "Vol up" button
4. Put battery back
You will get into download mode (aka emergency mode).
#2) Unpack kdz flasher, and install msxml.msi.
#3) Run KDZ_FW_UPD.exe set "type" to 3GQCT and "phonemode" to DIAG.
#4) Choose the .kdz file to flash. Download link is under the "Downloads"
#5) Click "Launch software update" and wait. Phone must be connected in download mode(!). KDZ installer might get stuck but DO NOT disconnect it. (Unless it stays that way for a hour as a example)
NOTE: .kdz is a .kdz, you cannot extract it. If you get a .zip from the LG .kdz site you did something wrong.
Cisf said:
First, there is no such thing as hardbrick (not anymore, most modern phones cant be hardbriked )
Be sure, u have all the drives and whatnots installed in the copmuter !
from: http://forum.xda-developers.com/showthread.php?t=2730501
[Q] How to install a .kdz?
[A] (Tutorial thanks to @[W]ar[H]ead, confirmed working by TaZRAge)
#1) First to get into download mode:
1. Remove battery
2. Put usb to computer and phone (w/o battery)
3. Hold "Vol up" button
4. Put battery back
You will get into download mode (aka emergency mode).
#2) Unpack kdz flasher, and install msxml.msi.
#3) Run KDZ_FW_UPD.exe set "type" to 3GQCT and "phonemode" to DIAG.
#4) Choose the .kdz file to flash. Download link is under the "Downloads"
#5) Click "Launch software update" and wait. Phone must be connected in download mode(!). KDZ installer might get stuck but DO NOT disconnect it. (Unless it stays that way for a hour as a example)
NOTE: .kdz is a .kdz, you cannot extract it. If you get a .zip from the LG .kdz site you did something wrong.
Click to expand...
Click to collapse
You don't know what you are saying. You can HARDBRICK ANY modern device. By definition hardbrick means phone won't turn on won't respond and in some cases recognized as usb when connected to pc as usb bulk or qcom usb. etc. You damage the second bootloader and tell me what happens. You will see what you get.
christi9503 said:
You don't know what you are saying. You can HARDBRICK ANY modern device. By definition hardbrick means phone won't turn on won't respond and in some cases recognized as usb when connected to pc as usb bulk or qcom usb. etc. You damage the second bootloader and tell me what happens. You will see what you get.
Click to expand...
Click to collapse
first this is offtopic. Second, u are wrong ! Unless the phone is pshisicaly damaged (misfuctioning components or damaged), u cant hardbrick the phone with uploading different soft. on it (unless u change voltages and overclok, if that is possible on the device). Ofecourse they are exceptions, but all major modern manufactors, make hardbrick proof devices. Also, how exactly would u modify the emergency mode, and more important even if you could, why wold u do it !?
More on to the topic, none of the operations of rooting, bootloader installing, kdz install or CMx install , gets near the emergency mode. It remains intact.
Just retry all normal steps for installing kdz or recovery again, check the cables, all drivers on pc, and is best to have a charged phone battery.
EDIT: @kikobuendia
i found this post, same operations as mentioned in first reply, but more detailed:
http://forum.xda-developers.com/opt...optimus-l9-ii-lg-d605-unroot-unbrick-t2964693
Cisf said:
first this is offtopic. Second, u are wrong ! Unless the phone is pshisicaly damaged (misfuctioning components or damaged), u cant hardbrick the phone with uploading different soft. on it (unless u change voltages and overclok, if that is possible on the device). Ofecourse they are exceptions, but all major modern manufactors, make hardbrick proof devices. Also, how exactly would u modify the emergency mode, and more important even if you could, why wold u do it !?
More on to the topic, none of the operations of rooting, bootloader installing, kdz install or CMx install , gets near the emergency mode. It remains intact.
Just retry all normal steps for installing kdz or recovery again, check the cables, all drivers on pc, and is best to have a charged phone battery.
EDIT: @kikobuendia
i found this post, same operations as mentioned in first reply, but more detailed:
http://forum.xda-developers.com/opt...optimus-l9-ii-lg-d605-unroot-unbrick-t2964693
Click to expand...
Click to collapse
I am not gonna reply again but I am just saying you have no idea. Do not talk unless you are sure you can hardbrick any device with just root and just writing on second bootloader partition. Read about it if you don't know. Do not argue about it.
I can't get into download mode
kikobuendia said:
I can't get into download mode
Click to expand...
Click to collapse
Then that's a hard brick pretty much. Pull the battery out and connect the phone to PC. Tell me if it gets recognized.
EDIT: OFC wait like 6 seconds then put it back and after that connect to USB.
When i connect it pc makes a sound
kikobuendia said:
When i connect it pc makes a sound
Click to expand...
Click to collapse
I don't care if it makes a sound or not it's like it gets recognized? Look into device manager.
christi9503 said:
I don't care if it makes a sound or not it's like it gets recognized? Look into device manager.
Click to expand...
Click to collapse
Yes but flashtool doesnt recognize it
kikobuendia said:
Yes but flashtool doesnt recognize it
Click to expand...
Click to collapse
If you want to get this fixed just listen to me. It won't work like this tell me the answers to my questions and we might solve your problem. What is your device recognized as. Make me a screenshot of device manager if you can't explain.
neutrondev said:
Then that's a hard brick pretty much. Pull the battery out and connect the phone to PC. Tell me if it gets recognized.
EDIT: OFC wait like 6 seconds then put it back and after that connect to USB.
Click to expand...
Click to collapse
I have the same probalem, cant get to download mode, when i connect to pc it recognise it in hs usb qdloader 9008, any solutions to fix it. I flashed wrong .tot file.
did you managed to unbricked it?
I have the same probalem, cant get to download mode, when i connect to pc it recognise it in hs usb qdloader 9008, any solutions to fix it. I flashed wrong .tot file.
Click to expand...
Click to collapse
No, no luck yet. Seems to be impossible.
I connect to this post cuz my d605 is also facing a similiar issue, no system, no recovery, no adb, download mode worked only twice, for the rest, only emergency mode works, phone cannot even charge.
Phone is recognized from pc, I uninstalled modem drivers but stays in Emergency only few seconds then it shuts down (not sure if its the battery, since it doesn't charge as well). It shuts down actually at the moment that LG mobile support tool seems to recognize it.
It worked couple of times, phone was keeping staying in emergency mode for the beginning of the procedure but at the moment it need to put the kdz into the phone, the phone die.
The two times download mode worked, same, just shutting down immediately. This with LG support tool or LG flashtool2014.
KDZ_FW_UPD worked the first time after install and then doesn't run anymore, on two different Win10 machines.
I have no idea how to come out of this nightmare, just want to flash it :/
Ag0n1a said:
I connect to this post cuz my d605 is also facing a similiar issue, no system, no recovery, no adb, download mode worked only twice, for the rest, only emergency mode works, phone cannot even charge.
Phone is recognized from pc, I uninstalled modem drivers but stays in Emergency only few seconds then it shuts down (not sure if its the battery, since it doesn't charge as well). It shuts down actually at the moment that LG mobile support tool seems to recognize it.
It worked couple of times, phone was keeping staying in emergency mode for the beginning of the procedure but at the moment it need to put the kdz into the phone, the phone die.
The two times download mode worked, same, just shutting down immediately. This with LG support tool or LG flashtool2014.
KDZ_FW_UPD worked the first time after install and then doesn't run anymore, on two different Win10 machines.
I have no idea how to come out of this nightmare, just want to flash it :/
Click to expand...
Click to collapse
well, sorry for not replying earlier. My phone was on guarantee for about 2 months after I wrote the post. I just send it to LG Hellas via the e-shop I bought it from and in about 2-3 weeks, I had my D605 back like it was brand new. I searched a lot about my D605 hard bricked and I found that it is not fixable. My phone could not go into download mode though, as yours. Hope I helped you even a lil bit. Sorry for my bad English.
Hello,
I have a LG P715, and it is stuck on security error. When i try to switch it on, it displays lg logo for 10 seconds and then the screen flips and i see security error with lg logo.
I tried googling it, i found out i have to use lg mobile support tool. To use it, I need to put my phone in emergency mode, which i cannot do.. All tutorials say to plug in usb while pressing Vol - key, which when i do, leads me to a screen with a blue battery icon with a lightning bolt icon in it.
Any help will be appreciated.
Azim Javed said:
Hello,
I have a LG P715, and it is stuck on security error. When i try to switch it on, it displays lg logo for 10 seconds and then the screen flips and i see security error with lg logo.
I tried googling it, i found out i have to use lg mobile support tool. To use it, I need to put my phone in emergency mode, which i cannot do.. All tutorials say to plug in usb while pressing Vol - key, which when i do, leads me to a screen with a blue battery icon with a lightning bolt icon in it.
Any help will be appreciated.
Click to expand...
Click to collapse
Hello Azim! Are still having troubles with your LG P715? Well! I have done the following:
1 - Downloaded a CIS V10j rom to this model P715
2 - I copied/pasted the 3 adb drivers (Adb, AdbWinApi.dll and AdbWinUsbApi) that I found on Android Multi Tools V1.02b folder (found to download) to the folder C:windows/system32 (My o.s. is Windows 7 x86. if yours is windows 7 x64, you must copy/paste them to C:windows/sysWOW too).
3 - Opened the LG mobile support tool and I chose to install the drivers to the LG P716
4 - Renamed the fold C:LGP716 to LGp715
5 - I ran the "windows enabler" (KDZ FOLDER) as admin and then, I switched it on at the "TRAY" close to the clock. Maybe this has not made any diference. I just have done it. you'll find it searching for kdz update with windows enabler.
6 - Then, I plugged the phone to the pc (while LG mobile support tool was still open) through usb holding vol- and it worked. (LGE AndroidNet Usb Serial Port s been recognized)
7 - So, I closed the LG mobile support tool and I ran the KDZ as Administrador and in compatibility mode to Windows xp sp3 ( right click on kdz icon and check the boxes due to these options at the window COMPATIBILITY).Good luck ! Sorry for my bad English. hug
---------- Post added at 03:23 PM ---------- Previous post was at 02:33 PM ----------
Almost forgot that the mobile got stuck at LG start windows and I performed a reset and it worked
Flash this boot.img on boot partition first via TWRP 3, then flash any rom (stock rom recommended first).^
[If you don't have recovery then flash modded kdz by maxx_hr.]
OR
Check that it is boot.img and not boot.img.zip or boot.zip.
What rom are you going to use?
Tel me if this helps and click the thanks button.
But to FLASH, he will need to set it on Emergency or Download mode first. Maybe this will fix his trouble it the future, if he ll needs to make the procedure again. ^_^
thyahuh said:
But to FLASH, he will need to set it on Emergency or Download mode first. Maybe this will fix his trouble it the future, if he ll needs to make the procedure again. ^_^
Click to expand...
Click to collapse
Maybe he hard bricked his Phone in the past? If he can use adb, then he can restore the emergency partition so he can access emergency mode.
http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/general/unbrick-lg-l7-ii-single-dual-t3166282 see section 6.2 and then come to kdz flashing - http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/development/kk-kk-kdz-p710-root-t2950532 use kdz for p715 from 1st post itself, then reply here.
Hi. Earlier today, I tried to root my phone using a program called LG OneClick Root. I was going to post a link to the article where I read about it here, but I can't since I have less than 10 posts. I clicked the start button after installing and launching the program and it started trying to root my phone. After a while, I got a message saying that rooting failed. Ever since then, my phone has been unresponsive. It doesn't even vibrate when I press the power button. I'm blind, so I'm not sure what the screen is showing. Does anyone know of a way to fix this? Did the program I used somehow brick my phone? Please help as soon as you can.
Living4God1991 said:
Hi. Earlier today, I tried to root my phone using a program called LG OneClick Root. I was going to post a link to the article where I read about it here, but I can't since I have less than 10 posts. I clicked the start button after installing and launching the program and it started trying to root my phone. After a while, I got a message saying that rooting failed. Ever since then, my phone has been unresponsive. It doesn't even vibrate when I press the power button. I'm blind, so I'm not sure what the screen is showing. Does anyone know of a way to fix this? Did the program I used somehow brick my phone? Please help as soon as you can.
Click to expand...
Click to collapse
Uninstall the app and see if it is still unresponsive. If not, follow this tutorial here on how to root your device. I would not follow those articles that tell you to install an one click root tool. The thread I have linked involves installing a custom recovery since the bootloader can be unlocked.
On the unresponsive part, if you have uninstalled the app and it is still unresponsive, try factory resetting the phone. This method involves turning off the phone, holding down the Volume Down button, while holding down the vol down button press and hold the power button until one second after the phone has turned on. While holding down the vol down button, press the power button a couple more times until the factory reset screen comes up. Use Vol up and down to scroll and power button to select.
I am bad at explaining things, so sorry if you do not understand.
Hope this helps!
Xsavi said:
Uninstall the app and see if it is still unresponsive. If not, follow this tutorial here on how to root your device. I would not follow those articles that tell you to install an one click root tool. The thread I have linked involves installing a custom recovery since the bootloader can be unlocked.
Hope this helps!
Click to expand...
Click to collapse
Thanks. I'll try that link. I didn't install anything on my phone, just on the computer. The app I had did everything through ADB. I don't know how I would even uninstall things from my phone with it being unresponsive. I haven't heard a sound or vibration out of it since before I posted this thread.
Living4God1991 said:
Thanks. I'll try that link. I didn't install anything on my phone, just on the computer. The app I had did everything through ADB. I don't know how I would even uninstall things from my phone with it being unresponsive. I haven't heard a sound or vibration out of it since before I posted this thread.
Click to expand...
Click to collapse
I don't think doing what that link says will even work. ADV can't seem to detect my phone when I plug it in. My computer makes a sound like there was a device plugged in, but I can't do anything with it. I'm glad I have insurance on this phone. Hopefully getting a replacement won't be too hard.
Lg up and uppercut with the firmware/kdz of the aristo 2 may fix it. Never use one click roots unless its off XDA and even then be careful with links. Also that link xsavi posted should work just make sure to follow the steps.
I just wanted to let everyone know that my phone is working again. I didn't have to do anything to it. I had someone else look at it, and it turns out it was completely dead for some reason, even though it had been on the charger for hours and there's nothing wrong with the charger. For some reason, it wouldn't respond at all for me, even after those hours, but when someone else plugged it in and messed with it, it came right on.
Lg aristo 2
Can anybody help me with rooting an LG aristo 2 i dont have a pc all i have is a chromebook
LG Aristo 2 qualcomm 9008 unbrick
my aristo 2 super hard bricked ...only shows up QDL 9008 in device manager and won't boot..completely unresponsive. Is there any fix? I've tried extsd card method to no avail. Please help.
Living4God1991 said:
I just wanted to let everyone know that my phone is working again. I didn't have to do anything to it. I had someone else look at it, and it turns out it was completely dead for some reason, even though it had been on the charger for hours and there's nothing wrong with the charger. For some reason, it wouldn't respond at all for me, even after those hours, but when someone else plugged it in and messed with it, it came right on.
Click to expand...
Click to collapse
Do you still have the phone?
LG Aristo 2 qualcomm 9008 unbrick
NonStickAtom785 said:
Do you still have the phone?
Click to expand...
Click to collapse
don't know if you were talking to me but if so then yes I still have it but it's completely dead and only shows qsb 9008 in device manager.
Tesh3180 said:
don't know if you were talking to me but if so then yes I still have it but it's completely dead and only shows qsb 9008 in device manager.
Click to expand...
Click to collapse
In device manager? You mean on window?
I didn't realize you had a bricked device to. I am here to help. I have been updating the threads as much as possible.
Does it allow you to boot into recovery or download mode?
Recovery Mode: Power+Volume, Release Power after buzz and Press again quickly.
Download Mode: Plug in Device while holding Volume Up button.
NonStickAtom785 said:
In device manager? You mean on window?
I didn't realize you had a bricked device to. I am here to help. I have been updating the threads as much as possible.
Does it allow you to boot into recovery or download mode?
Recovery Mode: Power+Volume, Release Power after buzz and Press again quickly.
Download Mode: Plug in Device while holding Volume Up button.
Click to expand...
Click to collapse
yea I've tried both modes but think bootloader is corrupt ..wont go in recovery or download mode. And yes it shows qsb9008 in device manager in Windows and in linux it shows qualcomm device. Probably gonna need unbrick image but phone is still relatively new so unable to find anything on how to unbrick it while it's in qualcomm 9008 or QDL mode.
Tesh3180 said:
yea I've tried both modes but think bootloader is corrupt ..wont go in recovery or download mode. And yes it shows qsb9008 in device manager in Windows and in linux it shows qualcomm device. Probably gonna need unbrick image but phone is still relatively new so unable to find anything on how to unbrick it while it's in qualcomm 9008 or QDL mode.
Click to expand...
Click to collapse
It's not new bro. I've already developed a lot for it. If it shows up as that you can unbrick it using the .kdz
Sent from my LGE LM-X210(G) using XDA Labs
---------- Post added at 07:42 PM ---------- Previous post was at 07:25 PM ----------
Tesh3180 said:
yea I've tried both modes but think bootloader is corrupt ..wont go in recovery or download mode. And yes it shows qsb9008 in device manager in Windows and in linux it shows qualcomm device. Probably gonna need unbrick image but phone is still relatively new so unable to find anything on how to unbrick it while it's in qualcomm 9008 or QDL mode.
Click to expand...
Click to collapse
It could be fixed if you have the encryption used by the vendor.
Sent from my LGE LM-X210(G) using XDA Labs
NonStickAtom785 said:
It's not new bro. I've already developed a lot for it. If it shows up as that you can unbrick it using the .kdz
Sent from my LGE LM-X210(G) using XDA Labs
---------- Post added at 07:42 PM ---------- Previous post was at 07:25 PM ----------
It could be fixed if you have the encryption used by the vendor.
Sent from my LGE LM-X210(G) using XDA Labs
Click to expand...
Click to collapse
I've tried lg bridge, lg mobile support tool, lg up but they won't recognize the phone..i even tried emmc dongle and it flashes the partitions but never comes out of QDL mode. I also extracted partitions from the kdz and tried fastboot but it won't go in fastboot mode or recovery or download mode.. I also tried boarddiag tool but msm8917_32 programmer isn't available. So at this point it's just a paperweight..lol. I'm gonna retry lg flash tool but if I could maybe find some way out of qualcomm 9008 mode I could probably unbrick it. Every time I plug it up to pc it shows as QDL9008 and every now and then it'll show up as unrecognized in device manager. I'm a newb to this stuff but I know that I flashed wrong rom and after that it never powered on again.
---------- Post added 08-12-2018 at 12:09 AM ---------- Previous post was 07-12-2018 at 11:56 PM ----------
Tesh3180 said:
I've tried lg bridge, lg mobile support tool, lg up but they won't recognize the phone..i even tried emmc dongle and it flashes the partitions but never comes out of QDL mode. I also extracted partitions from the kdz and tried fastboot but it won't go in fastboot mode or recovery or download mode.. I also tried boarddiag tool but msm8917_32 programmer isn't available. So at this point it's just a paperweight..lol. I'm gonna retry lg flash tool but if I could maybe find some way out of qualcomm 9008 mode I could probably unbrick it. Every time I plug it up to pc it shows as QDL9008 and every now and then it'll show up as unrecognized in device manager. I'm a newb to this stuff but I know that I flashed wrong rom and after that it never powered on again.
Click to expand...
Click to collapse
Again..thank you for all the time and help you've offered. I know one day I'll eventually fix it. Probably have to send it in but hoping I can do it myself with QFIL. Any idea of test points on LG Aristo 2..?
Tesh3180 said:
I've tried lg bridge, lg mobile support tool, lg up but they won't recognize the phone..i even tried emmc dongle and it flashes the partitions but never comes out of QDL mode. I also extracted partitions from the kdz and tried fastboot but it won't go in fastboot mode or recovery or download mode.. I also tried boarddiag tool but msm8917_32 programmer isn't available. So at this point it's just a paperweight..lol. I'm gonna retry lg flash tool but if I could maybe find some way out of qualcomm 9008 mode I could probably unbrick it. Every time I plug it up to pc it shows as QDL9008 and every now and then it'll show up as unrecognized in device manager. I'm a newb to this stuff but I know that I flashed wrong rom and after that it never powered on again.
---------- Post added 08-12-2018 at 12:09 AM ---------- Previous post was 07-12-2018 at 11:56 PM ----------
Again..thank you for all the time and help you've offered. I know one day I'll eventually fix it. Probably have to send it in but hoping I can do it myself with QFIL. Any idea of test points on LG Aristo 2..?
Click to expand...
Click to collapse
Well QDL9008 stands for Qualcomm Download Mode 9008. I think. I'll try to get some research in and let u know what I find. Maybe the bootloader is the only thing that's bricked because the bootloader is Qualcomm based and what not.
Sent from my LGE LM-X210(G) using XDA Labs
NonStickAtom785 said:
Well QDL9008 stands for Qualcomm Download Mode 9008. I think. I'll try to get some research in and let u know what I find. Maybe the bootloader is the only thing that's bricked because the bootloader is Qualcomm based and what not.
Sent from my LGE LM-X210(G) using XDA Labs
Click to expand...
Click to collapse
you are absolutely right. Can anyone do an adb dump of their aristo2..? maybe I can flash that onto extsd card and boot from there..?
Tesh3180 said:
you are absolutely right. Can anyone do an adb dump of their aristo2..? maybe I can flash that onto extsd card and boot from there..?
Click to expand...
Click to collapse
I wish I could help you there but all I have is 1.8 GB Chromebook. Very crappy. I'll PM some people to see if I can get an ADB dump for you:fingers-crossed:.
Sent from my LGE LM-X210(G) using XDA Labs
Hello, I have also bricked my Aristo 2. I have been looking all over online about what to do. The QPST, QFIL shows up a lot. I've parsed my GPT file, all that good stuff. But I can't find a way to make a proper emmc firehose.mbn. I've tried many other methods to no avail. Bootable SD, Chimera, CS tool, etc. Do I am very interested as well. My device shows in the Windows device manager as Qualcomm HS-USB QDLoader 9008. But, it shows up. I even have a dump I made before this happened through LGUP Dev mode, but I can't get it back on there.
Help me. I kinda like that phone
Ah.Pook said:
Hello, I have also bricked my Aristo 2. I have been looking all over online about what to do. The QPST, QFIL shows up a lot. I've parsed my GPT file, all that good stuff. But I can't find a way to make a proper emmc firehose.mbn. I've tried many other methods to no avail. Bootable SD, Chimera, CS tool, etc. Do I am very interested as well. My device shows in the Windows device manager as Qualcomm HS-USB QDLoader 9008. But, it shows up. I even have a dump I made before this happened through LGUP Dev mode, but I can't get it back on there.
Help me. I kinda like that phone
Click to expand...
Click to collapse
You need an emmc dump? Like the emmc that TWRP generates from a backup? Let me know because I think I can help you with that.
NonStickAtom785 said:
You need an emmc dump? Like the emmc that TWRP generates from a backup? Let me know because I think I can help you with that.
Click to expand...
Click to collapse
Yes, I believe so, I sure will try it. I didn't get one off the dump from LGUP
Hi Friedns,
During the unbrick process of my LG G3 d851 T-Mobile, I mistakenly flash the sbl1 partition before flashing any other partitions (using the "BoardDiag_v2.99a_modified_by_willcracker" ), my phone turned on (showing battery with exclamation sign). Now, I'm unable to repair it, I'm too much worried and wasted a month or so while searching the solution. Please help me to get back to previous state sothat I can flash partitions in right sequence.
Thanks in advance.
musmanzulfiqar said:
Hi Friedns,
During the unbrick process of my LG G3 d851 T-Mobile, I mistakenly flash the sbl1 partition before flashing any other partitions (using the "BoardDiag_v2.99a_modified_by_willcracker" ), my phone turned on (showing battery with exclamation sign). Now, I'm unable to repair it, I'm too much worried and wasted a month or so while searching the solution. Please help me to get back to previous state sothat I can flash partitions in right sequence.
Thanks in advance.
Click to expand...
Click to collapse
Sorry to hear that, you would need to flash the entire firmware again.
I personally use the LGUP tool, you can download it here https://www.mylgphones.com/download-lg-up-software
Next, you would need to find the .kdz firmware of your phone. Try searching on google for it, it should be around 1gb file. Flashing that stock firmware should repair your phone.
Thanks for reply bro.
Unfortunately no software is detecting my device.
It's just appearing as "LGE androidnet usb serial port" in device management.
How could I unbrick in this situation.
musmanzulfiqar said:
Thanks for reply bro.
Unfortunately no software is detecting my device.
It's just appearing as "LGE androidnet usb serial port" in device management.
How could I unbrick in this situation.
Click to expand...
Click to collapse
Is your device in download mode? It has to be in download mode, then you can use LGUP to download the firmware.
Device is completely off, not turning on, no recovery mode and no download mode. Screen just turns on when connected to PC without battery and then shows sign of exclamation.
musmanzulfiqar said:
Device is completely off, not turning on, no recovery mode and no download mode. Screen just turns on when connected to PC without battery and then shows sign of exclamation.
Click to expand...
Click to collapse
Hi , maybe this can help you:
https://www.google.rs/amp/www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/amp/