Related
Long story short, a kdz flash may have been interrupted. Now I am unable to boot my stylo at all. I can however see it under device manager, where it is labeled "Qualcomm HS-USB QDLoader 9008". Is there anything I can do to fix this?
I bricked mine and used LG Bridge to get to Lollipop and then I took the OTA to Marshmallow
Also, LG UP method can be used as well.
tube517 said:
I bricked mine and used LG Bridge to get to Lollipop and then I took the OTA to Marshmallow
Also, LG UP method can be used as well.
Click to expand...
Click to collapse
I kinda am stuck in this position too. Does LG bridge pick it up in this mode? Did you have that problem? I've been trying and it seems the only thing I can find is QPST using QFIL but then I can't seem to transfer the data and get an error about Sahara not being able to transfer the data over.
MrObvious said:
I kinda am stuck in this position too. Does LG bridge pick it up in this mode? Did you have that problem? I've been trying and it seems the only thing I can find is QPST using QFIL but then I can't seem to transfer the data and get an error about Sahara not being able to transfer the data over.
Click to expand...
Click to collapse
I have the MetroPCS version and totally screwed up messing around with something. I had no recovery. I had to use one of the methods to get it back up and running.
If you have the Tmobile or Metro version, you should be fine.
Did you have the same QDLoader 9008 issue?
LG Bridge doesn't appear to be working for me as it's not even detected.
Try LG Flash tool. That can get you back to Lollipop.
http://androidcreations.weebly.com/lg-g-stylo-update.html
Or LG UP method should work.
http://www.mylgphones.com/t-mobile-lg-g-stylo-h631-how-to-unrick-restore-back-to-stock.html (This is for the Tmobile version)
I can't actually access download mode, meaning neither of those options can detect my phone.
Wonkit said:
I can't actually access download mode, meaning neither of those options can detect my phone.
Click to expand...
Click to collapse
LG UP has an option that does not require download mode
I can't get LG UP to detect my device at all.
MrObvious said:
I can't get LG UP to detect my device at all.
Click to expand...
Click to collapse
Use a different USB cable. That's what happened to me. I had to try every single USB cable in my house, even from other phones.
AFAIK, in order to fix a hard bricked (Qualcomm HS-USB QDLoader 9008) lg stylo we need make something like this (http://forum.xda-developers.com/lg-...nbrick-g-stylo-ls770-qualcomm-hs-usb-t3368269) but for the H631/MS631 variant.
Can some of you look at THIS method used on LG V10 TMO variant for unbricking Qualcomm 9008?
I posted a thread HERE with the instructions from the user that created the backup and method to unbrick.
Hi, have the same qualcomm 9008 issue aftet kdz, so is there any solution?
So the brick is so bricked you can't even get to download mode.
Lg h631 hardbricked
Please any solution yet on this thread? I have had the same issue for a year now.
LGMS631 (MetroPCS LG G Stylo) Root/Unbrick/Recovery
So, I think I've managed to salvage my bricked Stylo, I somehow also managed to root my Fiance's LG G Stylo that's on the 6.0 update...
Since I can't find any ways to fix this problem on the internet I'll post what I did here so hopefully I can get some other people out of deep water with their phone.
Here is the thread I made I don't think it will work for a hardbrick, but it might be worth a shot..
LGMS631 MetroPCS LG G Stylo Backup (Unbrick/Root) Android 6.0
That won't work because your phone still works. You can boot past the 9008 mode.
So basically the phone is useless and can't be brought back to life at this point
I'm in the same position, flashed a lollipop kdz on a marshmallow and it effectively trashed the emmc. Without an insider leaking signed programmer and flasher mbns, flashing via sahara is not possible. For the moment, you need one of those expensive 20pin JTAG boxes and documentation for the ISP points(I can't find this info, it's paywalled). Under the shield facing the back of the phone is a header that may be for JTAG, but I haven't bothered probing as I don't think it's practical for unbricking.
Hi my name is Miguel and im new to xda and i have a serious problem so i bought my phone and i was using it a mp3 and stuff since i live over seas i tried to region unlock it and in the process bam phone restarted and nothing but a black screen i plug in my phone to my charger nothing happens i plug it in to my pc something happens but not on the phone but on the pc it started downloading drivers i can tell you what the bubble said because i came to europe for vacation and im staying here for a while but a friend of mine said your phone lost his boot-up and it wont do anything unless you buy a medusabox and get all the files im buying the medusabox or whatever but where can i get the files from he told me you need 4 files with ones are they any ideas?
What were you doing to region unlock it?
If you hold down the bixby, power, and volume down buttons, can you get into download mode?
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
ragarcia87 said:
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
Click to expand...
Click to collapse
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
huawei asker/fixer said:
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
Click to expand...
Click to collapse
Brittanyporter said:
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
Click to expand...
Click to collapse
This is very old but no all bricks dont leave in edl the devices also have groind points. All of us that tested the edl repair use qfil or the recovery script which i use on mine. You need a bit more than just the bootloader for repair. A whole barrage of sperate partitions as well as the programmer xml
https://drive.google.com/file/d/1CFRc7RljFHX1oN4WdDLUR3b3BmaGnNAc/view?usp=drivesdk
So this is a weird issue. My G Stylus has a Snapdragon 675 even though it's advertised as having a 678. I verified it with CPUZ and Motorolas own help app that comes back with the model SM6150 on the CPU.
Can someone else confirm this?
Working on trying to blankflash my hard bricked unit and noticed some stuff that threw me off while trying to get phone in edl mode via edl points on motherboard. The main thing that stood out is the motherboard is labeled as 2113-1 which i believe is the Moto One 5g. Anyway, I found the edl points and was able to blankflash unit although I am still hard-bricked looking for solutions.
Currently trying to convert firmware files in order to flash them with QPST software. Any suggestions would be greatly appreciated.
*Bricked unit after trying to "Fastboot set_active b" after flashing firmware.
LunaTuna said:
Working on trying to blankflash my hard bricked unit and noticed some stuff that threw me off while trying to get phone in edl mode via edl points on motherboard. The main thing that stood out is the motherboard is labeled as 2113-1 which i believe is the Moto One 5g. Anyway, I found the edl points and was able to blankflash unit although I am still hard-bricked looking for solutions.
Currently trying to convert firmware files in order to flash them with QPST software. Any suggestions would be greatly appreciated.
*Bricked unit after trying to "Fastboot set_active b" after flashing firmware.
Click to expand...
Click to collapse
Are you able to share where the EDL points are loctated on this device?
ezril,
Here are the EDL test point locations to mount as Qualcomm 9008. If you find out how to successfully blankflash this unit please inform me. When I run a blankflash script it appears to be successful but never turns back on, only blinking led.
i've included the firehose programmer and also a script from my successful/unsecessful blankflash.
Chase Whittemore said:
So this is a weird issue. My G Stylus has a Snapdragon 675 even though it's advertised as having a 678. I verified it with CPUZ and Motorolas own help app that comes back with the model SM6150 on the CPU.
Can someone else confirm this?
Click to expand...
Click to collapse
Same for me model minsk_a
...SD678 is SM6150AC. Suffixes are just overclocks.
Greetings everyone. I didn’t find a thread for this specific phone model. So I am putting it up here. Few days back I decided to unlock the bootloader of my LG W41 (LM-K610IM) and upgrade to a custom ROM. So, I used fastboot mode to unlock the bootloader and up until now everything went like a dream. Problems started when I couldn't get a TWRP recovery for my specific model. I downloaded a generic one and first tried to push it to my recovery partition. That's when I learned my phone doesn't have a recovery partition. I don't know what came to me then I used fastboot flash command to flash the TWRP image to my boot partition. It was successful but my phone won't start after that. It was a softbrick. Only the LG logo started bootlooping. But the worse was still not over. In an attempt to restore my device I searched everywhere for the stock ROM as the official website is down, but couldn't find any. At last, I zeroed in on a similar device by the same manufacturer LG K52. It had the ditto hardware like LG W41. Even the model number was similar. So, I downloaded the KDZ file. Extracted the dz from the kdz and the boot.img from the dz using LG KDZ extractor . Made a scatter file using a Hovatek instruction and using WWR MTK tool and formatted my device using SP flash tool and flashed everything. Till now my device was detected by the Windows 11 PC as a LGE device. Anyways the SP tool successfully flashed everything but after that my won't turn on any more. It's total dead. It won't power on, pc won't recognize it. I have tried connecting using USB and all possible hardware key combinations. It is dead bricked I think. All because of my stupidity. Now my question is, does it have any hope left or should I throw it away and buy a new device? I am keeping my fingers crossed and hope to find a superhero
Edit 1: SP Flash tool doesn't see my device any more. I have all the specific drivers installed. From LG and from Mediatek.
Try LG Bridge or check lg-firmwares.com
or
buy/borrow second device and 1:1 clone with mtkclient
Thanks for the quick response, but I have already tried LG Bridge, LGUP . After soft brick LGUP was seeing device as "unknown at COM Port 9". After hard brick it doesn't see it any more. Actually my PC won't see the device anymore
The firmware is not available at LG-firmwares.com but I have requested for it there. Keeping fingers
you should be able to repair preloader from bootrom mode (BROM)
How to enter bootrom mode. I am sorry if it is a noob question
Soumyadip999 said:
How to enter bootrom mode. I am sorry if it is a noob question
Click to expand...
Click to collapse
XRed_CubeX said:
To put your device in BRom mode you may need a different key combination or a test point, find out on the internet how to put the device in BRom mode or ask various devs of that device
Click to expand...
Click to collapse
find KCOL0 test point and short to GND
https://forum.hovatek.com/thread-11802.html
Okay let me ask and I will follow up. Thank you for the amazing guidance. Let's see if the poor device could be saved
you should poll lsusb in linux while trying to connect usb with both vol keys pressed. disconnect battery from pcb if possible to ensure phone is off.
Hello . I have OnePlus 7 pro I update it to android 12 and the next day something went wrong and my phone started an error Qualcomm crash dump something... Now it is stuck in EDL . Display none , power key And volume key works but keep booting in EDL even without connecting the USB cable . I flash the firmware with msm tool firmware flashed %100 but it didn't boot still in EDL .can someone guide me how to fix it
Can someone help!
jahanzaiblohani said:
Can someone help!
Click to expand...
Click to collapse
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
darksx said:
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
Click to expand...
Click to collapse
Drivers are correct and I was flashing it with USB 3.0 port .
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
KyRol said:
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
Click to expand...
Click to collapse
I have the old stock ROM which I flashed it in EDL but phone didn't boot when it is completed phone reboot too but not in normal mode in EDL again
Most often people have bad experience with qualcomm drivers. So make sure that you have some released after 2020 year, as oneplus 7 pro was released in 2020 year. Another issue is related to usb 3.x, better avoid that and try USB 2.0 instead, most of people have best results with older interface of that kind. EDL is kind of old solution, so better to stay away with USB 3.x and use USB 2.0.
Have you got any idea your flash is successful in edl tool? Have you got clean results or warnings/errors?
To be honest with you, I have to use EDL too, because I did wrong upgrade. I used custom ROM instead of stock ROM. Now I have not access to fastboot nor adb via USB either.
try different EDL ROMs, I found 2 threads. one is here, second there. As almost nobody anserws our questions, I will let you know what I did if I do it successfully.
Well, I discovered that I'm in pretty bad situation. In my case not only adb and fastboot does not works. It appears that EDL does not work either. Why? because I connected another oneplus phone over USB to PC and EDL mode was detected spot on. In case my o+7pro, well still same error as previously with adb/fastboot over USB. Something messed with USB on my phone at software side.
So I have to get motherboard get cheap. I do not thik that I can desolder flash or eMMC and revert that so easy.
Sorry Man, can not help you any
further. Turns out my issue is signifigantly other than yours.