Related
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Nit3H8wk said:
I cannot boot into download mode and cannot boot into twrp. The phone will not boot no matter how long i hold the power button and there is no lights. When connected to the pc it shows up as Qcom Dload. Can someone please create a debrick.img. All you need to do is flash this in twrp and send me the debrick file which should end up on your sdcard.
h ttps://www.androidfilehost.com/?fid=23578570567721355
Click to expand...
Click to collapse
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
ThePagel said:
This has been tried before and it didnt work for the guy. Have you tried flashing a tot? It has the begining of the emmc so same outcome but you can skip all the sd card work. Good luck if the tot fails and no one steps up ill get you that debrick file just to see if your luck is better.
Click to expand...
Click to collapse
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Nit3H8wk said:
That was a no go i tried the older dll that bypass model checks but still fails. Guess there is a linux method that worked on the older g2 and someone with a g3 reported success so i already extracted the TOT files i need to dd over from linux.
h ttp://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah that's probably your best option I have a partitions dump from the tot if yours are not working for some reason. Instead of installing twrp If I was you I would boot into download mode after and flash the tot. I did do a debrick dump with the script that I can get to you tomorrow some time and if that doesn't work tell me and I can give you a link that has 250-500mb range for the dumps from when I was helping the other guy. They weren't made with a script but with terminal emulator but they should be the same thing just bigger because the smaller dumps weren't working for him. Any way here are the partitions just in case https://www.androidfilehost.com/?fid=23622183712472493
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
Oh and before I go to bed another thing you can try if you can send the images over but they don't seem to work. Hunt down the fastboot laf.img send that over then do the rest of the partitions via fastboot instead. Good luck!
Dead phone
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Nit3H8wk said:
Dead in the water. Only qpst seems to see it besides device manager (Qualcomm HS-USB QDLoader 9008). The linux method was for people who get the lg logo. I don't get anything but a black screen. Problem is i don't know enough about the qpst software to guide you on making the files. All i can say is try to make a backup using qpst and provide links. Don't know what else to do.
Click to expand...
Click to collapse
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
ThePagel said:
In order to get you the files someone needs to reboot from the hidden menu into somthing I cant remember. Its not mini os and the d851 lacks the option in hidden menu atleast I didnt see it. The d855 hidden menu has the option and I was going to try it but he ended up sending it in before I got around to flashing the d855 rom. If you want to fix it yourself and can do without a cell phone for a few days I can try but might not be able to get you the files until sunday if it works.
Click to expand...
Click to collapse
Yeah i will have to wait then can't afford the $175 deductible right now. Thanks for the help. I don't mind waiting just hope i can find a less costly solution know what i mean?
QPST
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Nit3H8wk said:
So it looks like i will need a hex file and mbn partition files vs the bin files that come from the tot file. From what i read in the forums lg offers a 1 year warrenty. So i guess as a last resort i could send it in for service but i would rather try to resolve it myself.
Click to expand...
Click to collapse
Yeah I got ready to do it last night but got side tracked hopefully tonight
qpst
ThePagel said:
Yeah I got ready to do it last night but got side tracked hopefully tonight
Click to expand...
Click to collapse
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
Ill be able to tell you tomorrow afternoon if I can do it.
Nit3H8wk said:
I get paid on monday so going to ship it out to LG then. But if you are able to get the hex and mbn and secure boot files let me know i would still like to tinker a bit before that time as i know it will take a few weeks to get the phone back otherwise.
Click to expand...
Click to collapse
I cant seem to get into diag mode or field test mode so I cannot create the files for you :crying: BUT before you completely give up on fixing it take a look at this http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
cesarandres_8911 said:
Qualcomm MSM8975AC
Hello
I tell them my story, mistakenly doing a ported rom stock LG G3 Marshmallow, I flashed my phone with the stock rom from Marshmallow (model D855) and after that I have bricked the phone. No download mode, no emergency mode, only is recognize for the computer as AndroiNet usb port serial.
Could please you help me to unbrick my lg g3 Phone model d851,t-mobile variant. When I plug in my Phone to computer, this is recognized as lgandroinet port serial but I have made a testpoint (open the mobile) to change the phone mode to Qualcomm HS-USB QDLoader 9008”. I have used tools like boardiag but I get the followin message: “No response from the device. Check PMIC first and if still boot problem, replace AP.” To look at this thread: http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ... but report that it is not compatible for ATT and Tmobile variations. I currently have two virtual machines: Window xp 32 bit and Ubuntu 15.04. My client OS is 8.1 Window 64 bit.
I will be very grateful if you can help me to find a solution or can show me which is the correct way. I've been several weeks looking for a solution but I have not been able to fix my cellphone. I hope that my computer still recognizes it.
Click to expand...
Click to collapse
I just did the same thing tonight, I'll let you know if I fix it.
mxpxboi said:
I just did the same thing tonight, I'll let you know if I fix it.
Click to expand...
Click to collapse
Hello,
What is your phone and variant model? Do you have D851 model?
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
mxpxboi said:
Yeah D851, Black Screen and only connects as "LGE androidnet usb serial port"
Tried flashing TOT file and I get the error "Model Information Check FAIL!"
Click to expand...
Click to collapse
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
cesarandres_8911 said:
Hello,
I will try help you, first of all you must to change the Qualqomm mode in your phone, namely change usb LGE Androinet by QDloader 9008. For this you must remove the battery from the phone, open the phone and use copper cable or tweezers and you must to touch two points on the mainboard in order to force Qualcomm mode on your phone. I have attached photos to guide you in this process. You must touch two points (without battery) and connect the usb cable to the computer. You'll hear a sound that indicates that qualcomm is active otherwise could see a battery warning on the screen. If this happens, you must disconnect the usb cable and repeat the process.
The second thing you're going to do is install the drivers appropriate for Qualcomm mode. Please follow this thread: http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
This is the download link for the drivers referred to the post: http://forum.xda-developers.com/attachment.php?attachmentid=3261089&stc=1&d=1428980071
Now your computer will recognize the cellular in the indicated mode (Relink HS-USB QDloader 9008).
The next step is to use the Boarddiag tool in this post but in the root folder, place the file sbl1.mbn which is located in the folder that you extract the file TOT.
I am currently uploading a package that includes bordiag tool, sbl1.mbn file, and TOT file extracted. When the upload is complete, I could tell you what is the download link, this contain the version of Boardiag that will work in our model. Currently my phone lg g3 D851 (chip MSM8975AC) was revived.
Click to expand...
Click to collapse
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
cesarandres_8911 said:
Good morning, please try downloading this package;
https://mega.nz/#!5lRGUZqZ!HZXaf4SP_PtuPEkg0ycdWXZP977_lBdVVqkI1P8DVtU
I'm not sure if it will work for your model, please performs the tests at your risk. Let me clarify that this is the same boarddiag version , only I try added the files needed.
Within the. 7z, there is a file called "TOT Extract", please extract it and open application BoardDiag. In the section "Target Dir" choose the path where you extracted the file.
Please inform me as it was with the tests.
Click to expand...
Click to collapse
Thank you SOOO much for your help so far.
I installed Qualcomm Drivers and touched the points and it connected.
But it says that the Drivers are blocked due to not being digitally signed.
And it's showing up in Device Manager as "Qualcomm HS-USB QDLoader 9008" with an exclamation point.
I am posting screen shots.'
You didn't have this issue?
What steps do I do in the BoardDiag exactly? Just add the directory with the file and hit start?
@mxpxboi it seems you're using windows 8/above, you have to disable driver signature, here is how to do it https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Sent from my LG-D801 using Tapatalk
I was trying to go back to stock os from cm11 on the Amazon fire phone. Downloaded a stock rom and tried to install using safestrap.
After I pressed reboot the phone turned off but didn't turn back on. It's not responding to anything , not even goes into recovery , but when I connect it to computer by cable , six partitions show up , five of which it says are in need of format , and one contains a folder named image , which has a lot of files.
I'm new to this , got cm by following a simple guide , help pls
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. Ialready disconected the battery- did not work out
Does any of you have any idea?
Thanks
How come no one answered to this issue since 2016
Good day everyone,
I wonder why this issue was not replied to since 2016 on a professional forum. Is it because its not fixable?
I just bought an Amazon Fire Phone 64GB, the AT&T version. I already knew the phone was a complete disaster, but I still bought due to my low budget. Its the SnapDragon 800 series processor which I considered for such a small budget phone. Anyways, I rooted it via KingRoot, installed Safestrap-Kodiak-4.0.1-B01. I then downloaded the Unlocked version of the Fire phone Fireware "update-kindle-35.4.6.6_user_466000820" (since I wanted to avoid AT&T bloatware. I reside outside the States so cant use AT&T, so no use keeping it running all the time and sacrifice my battery) and flashed that. It flashed alright but got stuck after the welcome screen after selecting English (United Sates or UK). I then thought of of reverting it back to its original state Fire OS Ver 3.5, so downloaded "update-fire-phone-121_1.0.1_user_101012120" and now it has no life what so ever. Now it in the same state as mentioned by 2 others on this thread. It shows total 6 partitions with only 1 partition with an "Image" named Dir and a few files around 53MB or so residing in it.
I have snapshots of the Image folder files and the "QHSUSB_Bulk" status shown in Device manager, but I cant seem to find an option here to attach my jpg's here. Gosh! It doesnt get dumber than this.
Requesting help from someone who can help me out with anything at all, links, text, vdo's.
I've already downloaded the following files, but dont have a clue what to do with any one of them
QPST.2.7.460
Qualcomm_Flash_Image_Loader_v1.0.0.3
SRKtool_2.1_droidth
Qualcomm HS-USB QDLoader 9008 Driver Qualcomm HS-USB QDLoader 9008 Driver2.1.0.4
Qualcomm HS-USB QDLoader 9008 Driver Ver8.5
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Now deleted the 29 partitions of the phone.
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
No life in the phone except for QDLoader 9008 (COM4)
Android# said:
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Click to expand...
Click to collapse
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
SohailAzeem said:
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
Click to expand...
Click to collapse
*****Sorry, just realized that you can't get into stock recovery anymore please disregard the following as obviously that would only help if you could enter recovery*****
I am sure you already tried but what i meant to say was if you tried power + volume up button, you end up in stock recovery and that's where you gotta go, and select "apply update from ADB" from the recovery menu.
But even before all this, first make a new folder on your desktop, then download the ADB drivers for windows from here: https://developer.android.com/studio/releases/platform-tools.html
Extract the ADB drivers into the new folder you just made. Now, go to https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550 and download the 4.6.6.1 bin file for Amazon Fire Phone, either version will work with AT&T phone, and also put the bin file in the new folder you made earlier. Rename the bin file to just 'fire' or something short and easy. Now on an empty space in that folder press Shift + Right Click together, and select 'open command prompt or windows powershell from here' depending on your computer OS.
Now make sure your phone is powered off, then press power + volume up together to get into stock recovery, and you will see option "apply update from ADB", select that and when phone is ready, connect it to the computer via usb cable. In the command prompt window on the computer, type 'adb devices' and press enter. It should show the amazon phone in adb devices list. Next, type 'adb sideload fire.bin'. If you named the bin file something else make sure you replace 'fire' with that. It will take about 5-10 minutes and once done it should be able to boot normally. You can use kingroot 4.1 and then replace the kinguser with SuperSU using the supersume app. You can download supersume app by searching online or from google appstore, either one works. Hope this helps.
SohailAzeem said:
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
Click to expand...
Click to collapse
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
bigrammy said:
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
Click to expand...
Click to collapse
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
SohailAzeem said:
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
Click to expand...
Click to collapse
If your able just return the phone as said then they will likely send you a replacement or refund. :good:
Nearly all phones are brickable if you try hard enough but this fire phone is very very easy to brick :laugh:
(In My Opinion only) If you want a cheap almost unbrickable phone then go with the cheap china brands using the MediaTek CPU's. Stay away from the flag ship brands like sony htc lg samsung which use MediaTek CPU's as these manufacturers locked their devices down by removing the MediaTek flashing method and installing their own.
SPFlashTool is the PC software and the Swiss Army knife used for MediaTek so ensure you research :good:
Team MAD (MediaTek Android Developers) Have quite a few devices they support so choose any of those depending on your budget and it will ensure you get some decent updates and running the Latest Android Version. :good:
Do your research by reading the associated threads before you choose.
https://github.com/MediatekAndroidDevelopers
i think you don't read carefully what the Problem is.
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. The Phone is not working not getting ON. The phone is in Dead Condition but if you Connect with PC it shows its Memory Partations. if any phone not getting ON than how can enter to ADB Mode...???
Hoping someone could help me.
I modified a tot file for my G4 and upon flashing it, it made the device unrecognizable. Instead of showing LG G4 , it displays as LGE Android MTP Device. My phone suffers from ILAPO so I can't boot to my phone and edit its build.prop or something.
Here's what I'm thinking:
Could it be possible to create a "Customer Driver" for my LG G4? A driver that could perhaps make my device recognizable again.
Here's my fault.
The name of the tot file is: LGH815AT-00-V10h-GLOBAL-COM-AUG-25-2015+0
There are just some MINOR changes that I made on that TOT file but has caused a MAJOR disaster (for me at least). Let me take a quick screenshot.
After this, I flashed the edited TOT file to my G4. It accepted it without any issue., well except now it can't be read by my computer, I guess because of the changes I made.
I would really appreciate it if someone could share at least their thoughts on this problem. The solution I could come up with is to make a "Custom Driver" for my phone to be recognized as a G4 Device. Is there a way to do that though?
Thank you in advance! I'm not ready yet to give up on you, my G4.
PS. I guess I can't post screenshots yet. Sorry!
Does your phone actually boot to the download mode? Or is it dead.
If it has no life at all other then the driver showing up when you plug it into the computer without a battery there is not currently a solution for that. If you can get to the Download Mode screen there is still hope for you.
premiso said:
Does your phone actually boot to the download mode? Or is it dead.
If it has no life at all other then the driver showing up when you plug it into the computer without a battery there is not currently a solution for that. If you can get to the Download Mode screen there is still hope for you.
Click to expand...
Click to collapse
Thank you for the response.
I CAN get into download mode. There is no probllem with the phone. The problem is with the drivers (i think). I edited the tot file (LGH815AT-00-V10h-GLOBAL-COM-AUG-25-2015+0) using Hex Editor. Changed the name of the model from H815 to H815T. Before my laptop recognizes the phone as G4 right now it's only an Android MTP device. Please help! I wish I could post a screenshot of the changes i made to the file but I need create 10 posts/replies before it lets me.
https://drive.google.com/file/d/1mg8BDBCaoCS_LXE0TBSd5TdKV81YUsCM/view?usp=sharing[/IMG]
Hi guys,
i need some help unbricking my d722.
what went wrong?
I tried to flash twrp with flashify and i ended up in demigodmode.
from there i connected the phone to my computer and like 10 portable drives showed up asking to be formatted. I formatted all except one drive because it was protected from.
After i formatted the drives my phone was dead with only a black screen left.
Since i can't find any .tot firmware files for this model i tried to use the .tot firmware for a g3 in BoardDiag.
but when i want to use the extracted .tot firmware files on my phone it says this:
no response from device, check pmic first and if still boot problem replace ap
i think i have managed to install qualcomm driver and the phone is recognized as a qualcomm when plugged in.
But i did not shortwire the motherboard because i can't find the GND
can anyone please help me fix my phone thank you so much!
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Wachecheiro said:
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Click to expand...
Click to collapse
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
sdembiske said:
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
Click to expand...
Click to collapse
I'll take a look at it, thanks
Seems like a similar problem as I had, that's not gonna work though. The only way to fix it is to use a firehose which you can use a one from a Cyanogen MSM8939 device.