Database Users

[Q] LG G2 F320L got bricked, almost give up here [PLEASE HELP]

Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance

ecko no yaro said:
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
Click to expand...
Click to collapse
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk

I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english

Mati0807 said:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Click to expand...
Click to collapse
did you try to go from lollipop to kitkat?

heavy_metal_man said:
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means

Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/

ecko no yaro said:
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Click to expand...
Click to collapse
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
---------- Post added at 06:20 PM ---------- Previous post was at 06:05 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Right, you need to follow this guide i think. Ensure your read it fully before you attempt anything. Now, the lollipop update apparently changed some partitions so I would flash the bumped twrp from the development section instead of the 2.6.3.2 version recommended. Then once you can boot into recovery flash the rom recommended in this post

heavy_metal_man said:
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
Click to expand...
Click to collapse
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode

ecko no yaro said:
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
Click to expand...
Click to collapse
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!

heavy_metal_man said:
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
Click to expand...
Click to collapse
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so

ecko no yaro said:
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
Click to expand...
Click to collapse
Hmmm. im stumped. I think its a bit of a catch 22 here. What i think has happened is that the rom flash that was done has changed some of the partition layout, but the methods of fixing that issue is either with DD commands from a custom recovery (which you dont have and cannot flash) or with DD commands using ubuntu when the device is auto-mounting all of your partitions. Its worth a look if you have an ubuntu disk around, if not download here, burn to disk or mount it to a bootable usb and see if ubuntu has any luck with it. Either that or try installing any drivers you can on the pc to get download mode working.
there is also this as a last resort but i've never had to do this so i cannot vouch for it :-/ Good luck pal.

Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
and install bumped recovery 2.8.5.1, then next with otg cabble flash these http://forum.xda-developers.com/showpost.php?p=59079665&postcount=536.
and now i install cloudyg2 and i feel great xD thank you!

Mati0807 said:
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
dear do you have above mentioned tool bcoz i can not download , this page do not open
Click to expand...
Click to collapse

new link http://www39.zippyshare.com/v/UphAeXOO/file.html
With all files for d802. i used these for my phone!
Only run these tool, and smile

Z00TD ZE551KL Zenfone 2 Laser *hard bricked*

I somehow managed to lock myself out of the phone, no boot, no fastboot recovery mode, no access through adb (device not recognized), no nothing. Anyways just looking for assistance in this. I know there must be a way, but I haven't seen anything clear enough to precisely *unbrick* my beloved ASUS Zenfone 2 Laser ZE551KL Z00TD. I've resorted to a Samsung Galaxy S5 that I rebuilt from an old broken ones spare parts. I'm more of a hardware repairer so flashing ROMS and all that is rather new to me. But I was having some success early on when trying to flash CM.13 onto it using ADB and TWRP, which is when the trouble started. I flashed the wrong recovery.img I think and somehow locked myself out completely. I'm not sure exactly what I did wrong, but after many failed attempts to flash CM.13 Marshmallow, I tried to revert back to the stock ROM and then realized that I didn't make a backup recovery.img. Doh! So now I'm completely stuck with a really nice looking paper weight. Please help! :angel:

okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...

crossmanx said:
okay man, if you connect your phone without battery using usb cable to your pc? and device manager shows any newly detected device for a few seconds? try this and reply me...
Click to expand...
Click to collapse
I did plug in the device, while the battery was still in it, and it came up as an unrecognized device when the balloon popped up at the bottom right of the PC screen. I unplugged it, took out the battery, and plugged back in, but nothing showed up this time. Although I didn't look in device manager though. But I will try that next. What's your thoughts on helping me solve this issue? I'd really like to learn how the actual company first loads their firmware onto the devices. Like what kinds of software and equipment they use. I'm sure it's on a major scale though and probably have machines doing most of the work, just like an automobile assembly line. LOL. But I really want to get this ASUS Zenphone unbricked. So any help would be awesome. Thanks very much!

thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.

Thanks Man!!! I really appreciate the help. I'll try all this and report back. Thanks Again!

Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!

WormholeMatt said:
Well I realize it's been awhile, got pretty busy at work, I run a computer and smartphone repair shop.
But I've managed to get as far as getting the right drivers installed under COM PORTS, because it was showing up as RELINK HS-USB QDLoader 9008.
So after uninstalling those com ports drivers by uninstalling the device (you need to click the check box to uninstall drivers).
Then by holding down simultaneously the power + volume up + volume down buttons, while then connecting the usb cable back to the computer.
The device now showed up under other devices in device manager as QHSUSB_BULK. I searched and downloaded the Qualcomm HS-USB QDLoader 9008 drivers and installed them (The download was simply named Qualcomm_USB_Drivers.)
I installed the drivers to the QHSUSB_BULK device by clicking update driver software and then selecting them by browsing to where I saved them, in this case to my desktop. Note: I first had to download the .zip file, then extract that into my desktop folder I just called Firmware and Drivers. The name of the Driver pack I downloaded was called "Qualcomm_Drivers_QDLoader"
Now the device shows up as Qualcomm HS-USB QDLoader 9008 (COM10). I reconnected the device using the same method of holding down the volume up+volume down+power all at the same time with one hand and the other to plug in the micro USB cable that was linked to the PC. But I did this after which I took out the battery for about 20 seconds and placed it back in. This way I could check to see if the device was truly connected at that com port.
I have a plethora of software installed already to include, android debugging tools aka ADB+Fastboot+Tools unzipped using WINRAR to the desktop folder "adb", I also for some reason have AndroidSDKSlim.zip extracted to the desktop which just has the adb and fastboot tools in them. I also have QPST which has QFIL and a lot of other developer tools, and eMMC_DL_Tool_for_customer_ENG_V5.2.0R. I'm thinking I'll be needing these soon, so that's why when searching I just downloaded and installed all of these programs.
I'm at the point now where the phone is plugged in and the COM PORT appears to be open as far as I can tell.
Now I just have to figure out how to get the partitions, stock firmware, and all that back onto the phone so that I can unlock it, root it, load TWRP recovery, and then get it all back to life.
Any suggestions? Anyone? @crossmanx thanks for helping to get me started. Do you know where to go from here? I'm not even sure I have the right ASUS drivers installed, but I think that I do. This should be all I need correct?
Thank you. I'll continue to be as detailed as possible in my steps to recover my *hard bricked "ZE551KL Z00TD". Oh but on another note, I have heard that the stock rom or image recovery for the Asus Zenphone Selfie Z00T may work as well, but I'm afraid to try that. I just want to get this device back up and running with either the stock rom or and update MM rom like CM.13. Cheers!
Click to expand...
Click to collapse
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.

crossmanx said:
asus firmware for your device model is available on asus web site, download that and open that zip file, in that you will find boot.img, aboot or amass or droidboot.img, and also system.img files, and you have to push that into your device using qfil/qpst. i thibk you can do it also by emmc_dl is qualcomm drivers are installed properly and shows up as com_port, u just have to enter comport number and it wish push your files into device..
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
if you only push droidboot img then you will be able to get into the volume+ + power combo mode, so you can get access to fastboot, and after that you know all the procedures....
---------- Post added at 06:14 PM ---------- Previous post was at 06:04 PM ----------
well actually all the qualcomm based devices are unbrickable so sont worry your phone will be live again... you have to just experimenting it on...
well actually i dont have this phone...i am thinking about buying asus ze601kl? is this a good phone? how'z the performance and stability of cm13 snapshot version on your device? is dual sim and all the other things works without any bug? or it has any bug?
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
asus has such funky things in stock boot image as it verifies everytime on boot for valid image, if you have unlocked its bootloader before and try to update its firmware or install stock rom it creates problem. so cm13 is better choice.
Click to expand...
Click to collapse
Well, here I am ready to upload the ROM to the phone using QFIL. The phone is identified by the port. The only thing I'm having trouble with now is finding the "RAWPROGRAMMER" file to load from the firmware.
I'm not sure what else to do, I can't find the file anywhere.
Maybe this is when they say I need to get ahold of someone else exact same phone, root it, load twrp, and backup their original stock rom? I'm not sure. I just feel soo close to getting this done, but I keep missing files. I'm trying to load CM.13 but inside the folders for the firmware, there isn't any file in there. I've already found the patch file and the .mbn file that I need. Just missing the rawprogrammer file.
This is giving me a headache. LOL

Actually the only file I need is the .xml file that it asks for in QFIL. Which I guess is supposed to be in the stock rom somewhere. But in order to get that, I'm guessing I'll have to use my wifes phone (she has the exact same model as I do). I'll just have to make sure to not delete anything or mess up her phone. lol
And I'm also thinking that I will have to install stock ROM first before flashing the CM.13. So I'll have to get that stock ROM from her phone, since I deleted mine on accident.

that xml file is basically a partition structure file for your phone emmc. i think it might be there in your firmware.zip
you just have to find rawprogrammer file, i think it is there where you find unbrick guide for all qualcomm devices.....you just try that file it might work for your phone too..and after adding rawprogrammer you can add firmware parts from firmware.zip file or you also can clone your wife's phone emmc, using emmc dump to raw extension.
---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------
you dont need to install stock rom first, only you need to send droidboot,recovery or maybe boot partitions, if you have deleted modem and other partitions, then those will also. if you get fastboot then you can flash twrp and can flash cm13.
---------- Post added at 03:09 PM ---------- Previous post was at 03:00 PM ----------
there will be different named xml file in firmware.zip for you phone's firmware you just try try yourself available xml files in firmware. if it will be wrong xml then it will auto terminate no need to worry.

What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.

flash stock firmware using this tool: maybe it works
https://androiddatahost.com/326a2

crossmanx said:
What happened man! there is no response from you, since very long time!! I think you have solved the problem and been very happy with the phone live again.
Click to expand...
Click to collapse
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol

Same problem ZE601Kl
WormholeMatt said:
Nope, I still haven't unbricked it just yet. I had to put it on hold for a bit while I got much work done. But I will try again soon. I miss my phone. :'( lol
Click to expand...
Click to collapse
Hi Guys ,
Same problem happened for me with my Asus Zenfone 2 laser Ze601Kl.
I have tried QFIL , QPST all the qualcomm related softwares to make it work , but everytime i am getting same error " SAHARA FAIL "
I have tried with COLOR OS for One Plus One and which was having one chinese flasher and sadly that also showing the same error ,
AS far as i know i have installed the qualcomm drivers successfully and it is showing in device manager also . I have tried with Windows 7 X64 , Windows XP SP 2 . Still no luck
My phone has been dead since 1 month Somebody please help me

ZB500KL in Qualcomm HS-USB QDLoader 9008 no fastboot
Please help
I in Russia
Asus ZenFone Go ZB500KL in Qualcomm Snapdragon 410 MSM8916 detected pc only Qualcomm HS-USB QDLoader 9008. Please help

Try this https://forum.xda-developers.com/zenfone-3/help/hard-brick-asus-zenfone-3-ze520kl-t3483874/page3
Follow last post, technically you only need adb connectivity to flash all at once with one click. Hope this will help you.
Of course, now you need the rom for your device.
Sent from my ZenFone 3 using XDA Labs

crossmanx said:
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
Click to expand...
Click to collapse
Good to see anyone talking about LINUX here! I have my ZE550KL briked and the only thing I've been able to do till now are booting in fastboot and Android Recovery modes.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
Click to expand...
Click to collapse
Wow, this helped me a lot! My Linux system was not able to recognize the device but reinserting the battery and trying volumeUP+PowerButton did the trick! Now running 'fastbood devices' lists it and of course that made it visible through Virtualbox too [Windows 7 guest OS].
Now, considering that I would really like to resuscitate my phone by using LINUX, what else should I do in order to succeed?
Thanks a lot and best regards.

crossmanx said:
thanks man! I think you have to download QUALCOMM drivers! from internet. and install it into your pc. after installing drivers there will be a connection into your device manager when you connect your phone with pc. it maybe QUALCOMM 9006/9008, or QDLOADER or Qualcomm mmc storage. is this shows up into your pc, you are done,, you can push firmware parts into your device using qpst or qfil softwares. I will send you the link for guide.
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
if your phone is hard bricked then you might see broken partitions into LINUX! if you use any Linux distro then you will find many partitions when you connect your phone to your pc into Linux. we can adjust or backup or restore partitions using Linux simply, if we have image files of firmware.
---------- Post added at 10:54 AM ---------- Previous post was at 10:49 AM ----------
try to search"unbrick all qualcomm snapdragon devices" into google and you will find out how to unbrick using qfil/qpst. you have to download stock firmware for your phone.
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
try to press volume down button + power button combo and see what happens? after that try to remove and reinsert battery. again try volume up + power button. in last volume up + volume down + power button after removing and reinserting battery.
give results.
Click to expand...
Click to collapse
can you help me
same mode, manage to flash and download finish success.
Finish Download
Start Download
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download

sorry dude, i have no more info about asus devices. so can't help. remember only buy phones which have flashtools available like lenovo, mi, oppo, zuk etc.

XT1766 Hard Bricked....!!

Hi,
After Flash With Wrong Firmware My Phone(XT1766) Is Just Detected As Qualcomm 9008 Device And Not Powering ON.. Can Some One Kindly Provide Me Blank Flash File Or Any Other Solution For This Model..??

i did the same thing
i need help too because i did the same thing....trying to repair apn i just killed my moto e4 xt1766 and there is no fastboot .....please any solution???

If it detects phone Qcom 9008 you can still fix phone by using special emmc write tool ( hard to find ) but there are some on interwebs ....search on Google * try this one ALTHOUGH I HAVEN'T TESTED IT*
I fix QCOM Lg device like that
If your phone is dead dead dead you must Google video on test point ...with test point( shorting your board ) ...phone will detect on usb as Qcom 9008 then you need special Qcom tool like above
*Don't remember name of emmc tool I used on LG*.

Even If We Are Able To Connect It Via Any Qualcomm Tool We Don't Have Appropriate Files Available To Revive It..
So I Think For Now There Is No solution For It( Until Any Developer, Programmer Comes Up With One)..
So I Really Hope Some One Is Working On It As Many Peoples Have Bricked This Model While Flashing It..

prince_arsalan said:
Even If We Are Able To Connect It Via Any Qualcomm Tool We Don't Have Appropriate Files Available To Revive It..
So I Think For Now There Is No solution For It( Until Any Developer, Programmer Comes Up With One)..
So I Really Hope Some One Is Working On It As Many Peoples Have Bricked This Model While Flashing It..
Click to expand...
Click to collapse
Just download this OFFICIAL TOOL FROM QUALCOMM called QPST and see if it can get your device as far as fastboot at which point you can flash files from custom recovery to custom rom
The article is about IMEI but it can do more
https://www.androidbrick.com/ultima...agon-xiaomi-mi5-imei-and-baseband-repair-fix/
---------- Post added at 07:29 AM ---------- Previous post was at 07:19 AM ----------
This QualcommProductSupporTool is official tool ...
1. Ask one guy on stock to dump
2. Use this tool and guide to put dump on phone
https://www.androidbrick.com/unbric...-have-the-right-kind-of-rom-qhsusb_dload_edl/
OR TRY TO PULL STOCK WITH THIS QUALCOMM. TOOL
https://androidmtk.com/download-qualcomm-sw-downloader
*DON'T be lazy your phone won't unbrick solo and nobody can make one button unbrick untool .

KevMetal said:
Just download this OFFICIAL TOOL FROM QUALCOMM called QPST and see if it can get your device as far as fastboot at which point you can flash files from custom recovery to custom rom
The article is about IMEI but it can do more
https://www.androidbrick.com/ultima...agon-xiaomi-mi5-imei-and-baseband-repair-fix/
---------- Post added at 07:29 AM ---------- Previous post was at 07:19 AM ----------
This QualcommProductSupporTool is official tool ...
1. Ask one guy on stock to dump
2. Use this tool and guide to put dump on phone
https://www.androidbrick.com/unbric...-have-the-right-kind-of-rom-qhsusb_dload_edl/
OR TRY TO PULL STOCK WITH THIS QUALCOMM. TOOL
https://androidmtk.com/download-qualcomm-sw-downloader
*DON'T be lazy your phone won't unbrick solo and nobody can make one button unbrick untool .
Click to expand...
Click to collapse
Nothing is working no appropriate file to flash?? Where we claim for that?

any body have blank flash file ?

Need blankflash
i think if someone just find the blankflash for this model it can be flashed whit UAT ....in qualcomm module because this tool recognize the QLOADER 900 port but i dont have any file who works to flash this model .......

Hi
Moto e4 plus XT1776 Qualcomm hard brick please need blankflash file

aminsagar1 said:
Moto e4 plus XT1776 Qualcomm hard brick please need blankflash file
Click to expand...
Click to collapse
Wrong forum. Go to the plus section. But I don't think anyone has that file.

Try the answer in my thread. It worked for me. Just boot to Fastboot and use RSD Lite (I used v6.2.4) and flash the Zip file linked in that thread. I had to manually unzip the file because RSD couldn't handle the long filenames on its own, but if you unzip it and select flashfile.xml inside the folder, it should work.
https://forum.xda-developers.com/moto-e4/help/soft-bricked-boost-moto-e4-stock-t3803233

chuman72486 said:
Try the answer in my thread. It worked for me. Just boot to Fastboot and use RSD Lite (I used v6.2.4) and flash the Zip file linked in that thread. I had to manually unzip the file because RSD couldn't handle the long filenames on its own, but if you unzip it and select flashfile.xml inside the folder, it should work.
https://forum.xda-developers.com/moto-e4/help/soft-bricked-boost-moto-e4-stock-t3803233
Click to expand...
Click to collapse
So the one I linked worked?

we have blank flash for XT1767 but not for XT1766 ....
maybe someone from inside the motorola would leak it in the future

hi
aamszia said:
we have blank flash for XT1767 but not for XT1766 ....
maybe someone from inside the motorola would leak it in the future
Click to expand...
Click to collapse
can u please shere the blank flash file for xt1767

prince_arsalan said:
Hi,
After Flash With Wrong Firmware My Phone(XT1766) Is Just Detected As Qualcomm 9008 Device And Not Powering ON.. Can Some One Kindly Provide Me Blank Flash File Or Any Other Solution For This Model..??
Click to expand...
Click to collapse
Yes we have solution for moto E4 XT1766 Sprint Sperry
https://www.youtube.com/watch?v=dDldcWPEALI

Hi
Can you share that software pls?

xt1766 & xt1767 dead boot repair with usb solution without touch emmc
click here to download files&instructions
https://mega.nz/#!QvQzGIKD!HhY-xK1eLqYx2u5JRz6VCPMoCJvJNG3cEBQOPf7e1QI
password
xpertgsm

irfang0349 said:
click here to download files&instructions
https://mega.nz/#!QvQzGIKD!HhY-xK1eLqYx2u5JRz6VCPMoCJvJNG3cEBQOPf7e1QI
password
https://mega.nz/#!MuIDnILb!eJmmo7IWMLi7DLcsALGKvIVSaKCr9_KjFCnaENeHIYY
Click to expand...
Click to collapse
Waste Of One KB of My Internet ......
He wants money lol .......

Might have some potential here for xt1766 anyways.

XT1766 hardbrick stuck in 9008 mode would normally require a blankflash. However, as is common in most Motorola models there is a boot from SD option that is automatically defaulted to in the case that the bootloader has been deleted or damaged. To use this boot from SD option you simply extract the bootloader to a blank sd card and insert it into the phone then reboot
Here is a bootloader provided to me (Untested)
mediafire.com/file/t2su47wbd3dizue/XT1766-BOOTLOADER.img/file

Qualcomm HS-USB QDLoader 9008

No really new here just cant access my account ....annywaayy
so s5 originally had become softbricked with no root or anything just one day the phone was stuck on the bootloader with FAILED modem.
Tried a few things via Odin and failed
CURRENTLY STATUS
Phone shows NOTHING and wont go into bootloader or recovery so i cant even check anything. it shows up as "Qualcomm HS-USB QDLoader 9008' when connected. Im aware of these options
QFIL - MDN file needed are all dead links
SD CARD IMG option- Cant find a working link to fix that either.
ANYONE CAN HELP ME OUT HERE!
PS: YES I SEARCHED HERE AND ALL OVER THE INTERNET AND ALL LINKS ARE DEAD or Cant find anything.

Mister_RTK said:
it shows up as "Qualcomm HS-USB QDLoader 9008' when connected
Click to expand...
Click to collapse
Is it SM-G900V?
Is it the single SM-G900V you have?
Which SW version of debrick image do you need?
YES I SEARCHED HERE AND ALL OVER THE INTERNET AND ALL LINKS ARE DEAD or Cant find anything.
Click to expand...
Click to collapse
Maybe. but the links in this post are still working.

bbsc said:
Is it SM-G900V?
Is it the single SM-G900V you have?
Which SW version of debrick image do you need?
Maybe. but the links in this post are still working.
Click to expand...
Click to collapse
since the device wont power on how could i find this out ?
Also Ive downloaded the links and tried putting each on a SD cards root folder but nothing comes up so i guess QFIL is my only option.

Mister_RTK said:
Ive downloaded the links and tried putting each on a SD cards root folder but nothing comes up
Click to expand...
Click to collapse
Those files are disk images.
You should write them as raw data directly to your microsd card.
Use win32diskimager under windows or dd under linux.

How to put phone into EDL Mode? Nokia X6 China (TA-1099)

I have Nokia X6 (TA-1099) from China but when I downgraded the OS it's gotten hard brick. Someone can help me to put it into EDL mode to I can recover it.

ManhDev said:
I have Nokia X6 (TA-1099) from China but when I downgraded the OS it's gotten hard brick. Someone can help me to put it into EDL mode to I can recover it.
Click to expand...
Click to collapse
hello, did you try an EDL-cable before opening the device?
seems it worked with the Nokia 5 and 6 http://forum.gsmhosting.com/vbb/f296/nokia-5-nokia-6-connect-edl-cable-little-ones-2246357/

meltbanana said:
hello, did you try an EDL-cable before opening the device?
seems it worked with the Nokia 5 and 6
Click to expand...
Click to collapse
Yes. I did but the phone can't boot into 9008. There didn't anything happened

ManhDev said:
Yes. I did but the phone can't boot into 9008. There didn't anything happened
Click to expand...
Click to collapse
I am in the same situation, I flashed manually different partition and got it wrong.
It booted with black screen all the way but QHSusb was working, EDL, emergency.
I soft-repaired, and then thougt it was unbrickable, but I was wrong.
I flash for fun modem.bin and it booted up. But later I flash a big-rom-update-zip in TWRP and then changed the boot-slut from B to A and restarted from recoverymode but DEAD, complete dead, nothing appears on the screen or devicemangar.
then it didn't boot at all.
I have a home-made cable and tried different button-combinations and cable-connected-combination during boot but nothing work.
Either I have destroyed QHSUSB-modem, ( I don't know if it is software related on UFS-storage or if the Qualcom-emergency-MODEM have a different chip that boots up.
Maybe I have incompatible critical-partitions from different rom?!
The last resort is to brake/carefully open the screen-glas on short the electricity from some chips and force the QHS-usb-mode, emergency mode. I have the Firehose.elf file that will help, and the partitions and patch0 file. But need to force boot inte Qualcomm-EDL , But how?
My chip-family-SOC is MSM9889 ta-1012, NB1-softwares-firmwares

I need the Firehose.elf file that will help, and the partitions and patch0 file，can you seed it to me？

short ur motherboard to enter EDL mode... i can provide EDL point if u want... after short the board HS... 9008 drive will show..update the drive to Qloader 9008.. than u can flash ur device with OST tool emergency mode.. choose firmware before july 2018.
Sent from my TA-1054 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
ur homemade cable wont work
Sent from my TA-1054 using Tapatalk
View attachment 5013803