Hi everyone,
Sorry for my ignorance but I haven't frequented these forums in years and as an old person I find the new search feature confusing, so if this information is definitively covered elsewhere I'd love to see it. I want to make it clear that I am NOT trying to unbrick my old hardbricked Verizon LG G3 VS985. I am simply trying to get the data off of it, if that's possible. Every guide I've seen talks about unbricking it, using QFIL to flash it, and using a "firehose file".
I can successfully short the pin to get the board into EDL mode and Windows recognizes it as a "Qualcomm HS-USB QDLoader 9008" on COM 3. QFIL seems to be able to communicate with it but I'm completely lost as to how to get data from the board. I just want to see if any old photos, videos, contacts, whatever might still be there and I don't have the first clue of how to get this to work. Do I even need a firehose file to do this? Should I just chuck the whole thing in the recycled electronics pile? I feel like I'm one or two clicks shy of cracking this nut. Thanks in advance.
A tad late, but maybe try following this titorial:
Related
think i hard bricked my optimus f6 after an attempt of installing unlocked bootloader. no emergency download mode, no boot of any kind. managed to get "qhsusb_dload drivers installed. do not know what to do???? any help please....
No one with any ideas about this situation ?
i'm stuck there too,i think there is a way with qpst tool but we need necessary .xml,.hex,.mbn files
That's a tough one. It's one of those situations that happens often enough, however, since not many people know how to fix something like this, most people don't even bother and just send it in to LG or write it off as a loss. The EASIEST way would be to find a shop with a RIFF box that can perform a JTAG service on that. But finding a shop that has the tool and knows how to use it (especially for your model) might be tricky depending on where you are. If you are wanting to try it yourself, you might try this thread as a reference point to maybe at least get you pointed in the right direction:
http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Obviously it is not for your phone, and the OP specifically says he does not know how to perform this on other phones, but it is the most detailed thread about it I could find. It should at least give the ideas to what kinds of files you need to find to get started. Good luck!
I know pretty much nobody will answer this question but I'll still ask it anyway. I have a Samsung galaxy centura with cwm installed. After formatting the SD partiton and swap it has a unlit screen. When connection to a computer is comes up as Qualcomm hs USB or something like that. After a bit of research I found out a guide on XDA that explains that we can use a program called boarddiag to unbrick these devices. I followed the steps but I can't figure out the correct chip in the program. Basically what I want is someone to point me in the right direction in using the boarddiag program and unbricking my phone. I also need the correct .tot file contains the phone partitions such as aboot, boot,modem etc. Help would be extremely appreciated because I'm at a dead end over here. Even if you are not familiar with the centura any type of advice would do no matter how small.[emoji4]
Devmountsu77 said:
I know pretty much nobody will answer this question but I'll still ask it anyway. I have a Samsung galaxy centura with cwm installed. After formatting the SD partiton and swap it has a unlit screen. When connection to a computer is comes up as Qualcomm hs USB or something like that. After a bit of research I found out a guide on XDA that explains that we can use a program called boarddiag to unbrick these devices. I followed the steps but I can't figure out the correct chip in the program. Basically what I want is someone to point me in the right direction in using the boarddiag program and unbricking my phone. I also need the correct .tot file contains the phone partitions such as aboot, boot,modem etc. Help would be extremely appreciated because I'm at a dead end over here. Even if you are not familiar with the centura any type of advice would do no matter how small.[emoji4]
Click to expand...
Click to collapse
Good luck! You might try getting ahold of daddy366...he might be able to put you in contact with someone from team Centura...if there is a fix for black screen of death they would know.
Sent from my XT1609 using Tapatalk
Alright, i have searched for months at this point. I have tried several potential fixes on this site and others. I have an LG Gpad 7.0 for sprint otherwise known as the LG LK430. After weeks of searching, i have obtained bother the TOT and KDZ files for this device. I'm not able to use the board-diag software due to not having the proper AP Chipset files, at least from what I'm able to understand. I have no bootloader or recovery as well as no system, but the device is able to be seen from the Qualcomm chipset. I can't use the LG software to fix it because the software isn't able to find the device, and won't let me select a port. I tried partitioning an sd card like one gentleman said in a post the DD the img files to each partition. I'm so lost and I don't want to give up on this. There has to be a way. Any advice would help. If anyone knows of a way to at least flash the bootloader back to it then that will get me the rest.... Ugh. Sadly I'm in a "please bro" state here.
EDIT: Fixed with unbricking service. No other way AFAIK. The error is caused by flashing to US998 20d from V300L 21k. Another user ran into the same error flashing from V300 21 to H930 20. So I guess the takeaway is to be careful when downgrading.
So I think I messed up and now my phone is stuck in UEFI crash (text screen with "LGE crash handler: UEFI crash"). It keeps bootlooping and I can't even turn it off.
QPST says it's in download mode when I plug it in.
Any chance I might be able to fix this?
Picture of the error screen attached
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
sandking707 said:
I think you need QFIL to find the emmc prog file, I also experienced the same problem.
Click to expand...
Click to collapse
I've been messing with QPST but of course there isn't much I can do as-is.
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
sandking707 said:
I can use QPST by Port Qualcomm HS USB QDLoader 9008, but I do not have a .mbn file if you have a share file thanks
Click to expand...
Click to collapse
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Read some other threads, there was a mention of a built in fastboot in the PBL but that seems to be untrue.
Maybe this isn't the PBL considering screen is working and there's LG branding.
I've also heard of a recent exploit for SD chipsets, something about the PBL's signature verification. If this works for the firehose, then maybe someone can modify an existing firehose to adapt for the V30, this way a leak won't be necessary. Though if anyone will bother is another matter.
seloka180 said:
it's a hard brick there is no solution for now (lg g5 .g6.v20.v30 ....) jus twait
im in the same situation on my v300s.:crying:
Click to expand...
Click to collapse
edit:
my device solved with jtag in repair shop.
Sent from my LGM-V300S using XDA Labs
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
test point lg v30
Duo8 said:
So I still haven't managed to fix this, but did some reading. The phone isn't even in 9008 mode so remote repair probably isn't possible. It shows up as a LG AndroidNet device or something. It might be in 9006 mode except with LG's USB ID (1004:6340) and without an interface to the internal storage.
I tried using a tool to communicate in sahara mode but it's outdated so it can only connect to the device and not much else, the commands are mostly invalid. Interestingly when I tried to switch to download mode it requests a 1KB "AMSS" image.
Anyway I'll need a way to enter 9008 mode if I'm to get it repaired. If anyone know of a way I'd appreciate it if you share.
Click to expand...
Click to collapse
there are two golden points near the ribbion of battery but not the big ones under the ribbion wehen you connect both the phone will go 9008 mode
i am stuck in the very same situation as OP please if anyone has any way or idea on fixing this issues let us know and so others can benefit from it as well
thanks
Sahara mode LG v30, please help!
Hello there,
my lg v30 us998 was 10% battery. I was browsing the web and suddenly it freezed up. I cound´t do nothing until it shut down itself after a few minutes. I plugged in to the charger and the same message showed: UEFI crashed. Sahara mode... Any help please?
Not sure if it is actually possible for me. Still no solution. I was waiting for a more complete reply ...
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
afireblood said:
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Click to expand...
Click to collapse
Update: Now in search of the Moto G7 specific blankflash.zip
If anyone knows where I can find that I would really appreciate it!!
I am not familiar with the g7. (I own a G5+). I believe the G7 code name is "river". You can look at https://mirrors.lolinet.com/firmware/moto/river/ and they show a blank flash - but let me say something - a blank flash must be exact for your phone. Its basically the main disk partition with other partitions inside. My phone has 64GB/4GB, and 32GB/3GB-2GB models - so you see a problem. But if all the G7s are the same, then this blank flash should be OK.
Also you can download the phones original firmware at https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/ , if its a US model. If its not, back up 1 directory and you can find it by either carrier or country. You can fastboot the firmware - which I would do before a blankflash,
Hope that helps.