Hello
Yesterday I was flashing my ROM but it failed. Now when I try to startup the phone (LG D802) it doesn't even give me the LG startup screen. I did some research and tried to start with an NVFlash. I'm kind of new at the smartphone world, they are telling me to take out the battery but is it suposed to be this hard to take it out? Screwing it all lose, disconnecting a lot of connectors?
So I started without taking the battery out, in the device manager I do not get an APX device but the QHSUSB_BULK, when I try to install the driver to this device it says the folder does not contain any driver...
That's how far I get, I tried to find some similar threads right here but anyone else seems to manage to get into some fastboot mode or download mode or something similar. I don't...
Any help is welcome...
Related
Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
FenriX` said:
Hi! I really head your help!! I looked a lot around and followed lots of guides on how to revive my phone, but i've some big issue with it and i really hope that someone here may help me...
The Hard Brick (it won't turn on, it won't charge, it seems like he's totally dead) occurred the other day, i was trying to open googlemaps and the SP was really slow, so i turned it off, and then i wasn't able to turn it on again, at first it was stucked at the screen with the logo (before the splash animation, the logo that you can't normally change) then i managed to turn it on after 2 or 3 times taking off the SD card, but i got a corrupted homescreen, i turned it off again and then, after 2 or 3 times, i got the Hard Brick!!
Probably in my last attempts i created a bounch of errors in the rom that bricked my phone.
Here's what i've done to revive it:
- SPFlashTool 1332.0.187
- official drivers, recovery, rom, etc, from the jiayu.es website.
- removed the battery, manually installed the drivers.
- with spft i loaded the scatter file of the official rom and started the format:
the phone is recognised as Mediatek USB VCOM (Android) (COM3)
i always got the error: S_COM_PORT_OPEN_FAIL (1013)/B] (with every option available)
I tryied to download only the preloader.bin and the recovery.img but i recive the same error.
- someone give me an advice: to remove every old driver for the phone and leave the SPFlashTool to recognise the phone forcing the installation of the drivers. And i really don't get how to do it, the windows update automatically detect the device, if i stop the windows update i simply get an unknown device, the SPFT don't have a chance to recognise it and force the installation of the drivers.
Does anyone of you have a solution, a similar problem, a way to revive my cellphone?
I really can't effort another one XD
Click to expand...
Click to collapse
There is a guide right here
I already tryied to revive my phone with this guide, but with no success...
I was thinking that maybe someone can show me the right driver (with all the package of driver that i find i always have no idea which one i've to install)
And maybe someone already tryied to revive a jiayu g4a and know the name of the right preloader, 'cause apparently what i need to do is to download into the SP the right preloader to revive it...
I have a bricked LG E455F, it is stuck in a boot loop with recovery mode inaccessible due to a "Security Error" message, leaving me with the option of flashing it.
At first I would like to say I'm new to this kind of procedure, if anyone knows any other fix, it would also be very appreciated. In a first moment I tried using the LG Mobile Support Tool, however, every time it gets to 5% it shows me this error(not allowed to post images yet, so here's the imgur image path "/ssZCcSl.png"), as in each try it would download everything again, taking a really long time, I started using the LG Flash Tool 2014, again, with no success, I tried changing the COM ports, removing battery, changing usb port, even using a different computer, searching for this problem I found several other people at the same situation, however, almost none solutions, and zero working solutions.
I would like to, if possible, try at maximum to keep the files I have in it and keep as stock as possible. So, what would be the best course of action in this case, how should I proceed?
Obs: I am using W10, and my second computer W8.1;
Obs²: The ROM I'm using with the LG Flash Tool is the one downloaded by the LG MST, I just copied it before it was automatically deleted.
Obs³: I can still access Download Mode.
Same problem here
Im facing the same problem here,
I had something similar happening to a d605, flashing would not succeed and I tried A LOT of different things, even dismantling it to short a resistor and make it boot in mtek mode to flash via SP flash tool, SP flash tool reported it could not find the EMMC of the device.
I then googled about it and found out a LGs phones are having EMMC problems once they get 2 years old. So I guess its just a matter of LG making ****ty phones that do not even last more than 2 years.
Im afraid this device is having the same problems...
when it reaches 5% remove the USB cable and connect again
I have an LG K7 on Metro. It's in some sort of boot loop. I have searched XDA and the net for a solution and keep coming up with solutions involving download mode. I'm unsure of what to do next. The phone has Error # 9 Authentication error as well as error 1009. When trying to go into Download mode it goes for about 10 seconds and then reverts to the LG welcome screen. When you try to turn it on it just stays on the LG welcome screen or cuts off. When plugging it up to my Windows 10 PC it shows LGE Android MTP Device in the Device Manager. I've tried to download the Drivers from the LG site and ran the installation on the computer with no change. I've tried to update the drivers from the Device Manager Screen with no change. It also gives you the noise when it connects to the PC. LG UP won't recognize the device and neither with the LG support tool. I have tried everything that I am capable of understanding at this point (which isn't much). I have read about trying to get it into EDL but can not find the correct test points... even if I did find the correct test points I'm not sure if that will even help me to fix the device. I need to breathe some life back into this phone. I hope I did not post this in the wrong place, or violate an XDA rule. I just really need some help... XDA has the most complete guides and accurate information I just can't find it about my particular situation. Anyone's assistance or thoughts (written to a non-techy person/non-developer newbie chic) would be helpful. This is week 3 of me scouring the net for answers. Thank you
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.
Hi,
I bricked my phone, a SHARP Aquos C10.
After unlocking the bootloader I was able to install several rom. The last one was LineageOS 18.
I bricked the phone when I tried to replace LineageOS Recovery with TWRP by dint of trying.
The phone is not completely blocked. It gets stuck for a long time on the "battery" logo which replaced the "Sharp" logo when the unlocked it. After several minutes, it vibrates and restarts.
I can restart it by long pressing the OFF button, I can't turn it off, I can't put it in recovery mode.
I can just put it in download mode but unfortunately it is no longer recognized by the PC.
So, bricked or not bricked.
Thank you for your help.
Nobody can help me ?
Hallo,
if you still can go to the download mode, maybe not all hope is lost. Your phone might not have
a hard brick, but only a soft brick. Everything should be fine as long the download mode isn't bricked too.
I had a similar problem once with a tablet after flashing it.
You need to install the USB-Drivers for your device on your PC and then reconnect it.
This might sound ridicolous if you already have installed them, but sometimes
a deinstallation of the USB-drivers and reinstallation of the drivers might help.
I found the following site for the drivers:
"https://gsmusbdriver.com/sharp-aquos-c10".
If you prefer an official source, you can use: "http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/ADBDriver.aspx"
However both sources seem to look reliable for me, even if I can't test it, without having a SHARP device.
If you are not sure, you might compare it with other tutorials and look for reviews.
Installing the drivers can't lead to harm to your device until you don't connect it.
Things can't really get worse if you install the drivers. The only thing that could happen is, that either the PC will say that it recognizes the device or that no device can be recognized, so it's worth a try. Please report me, if it worked for you and you are able to flash again. I hope this will help.
With kind regards
dontdropme
Hello,
Thank you very much for your help.
Yes, I installed the USB drivers. I unlocked the phone for you I installed another rom.
I reinstalled the drivers following your links. Unfortunately that does not change anything. The phone is not recognized. No sound comes out of the computer when I connect the USB cable.
I tried on 2 computers, 1 on Windows 10 and in Windows 10 / Xubuntu dualboot.
When the battery is empty and I try to turn it on, a red battery will light up and flash. As I charge it, the battery changes color to green.
I don't have download mode if the cable is not plugged into the computer or the charger.
:/
Hallo,
the download mode is supposed to be only able to get started if you connect the device to the computer or another device, this is not strange. You need to go to the download mode and try to flash the stock firmware for you device. Try it at first without a device recognition of your PC and find out, if you need to do a hard reset before, to regain factory settings. I have listed, in color, a short number of things you could do now. If this still doesn't work only the SHARP team or a specialized company might help.
What you could do, is to ask the SHARP support for a source for the USB drivers and how to do a hard reset to regain the factory settings. I don't know which flashing tool you use for you device.
Normally if your device is not recognized by plugging it in to the PC-USB-Port the flashing tool shouldn't recognize it either, but it might be just an error of Windows, and the flashing tool is not allways depentent to the USB-drivers, but relies only on the question if you can go to the download mode, so you could give it a try to flash even in this case. Start the flashing software and look what will happen.
You said, that you have successfully flashed until now, which means that the flashing tool supports you device. If you can't flash now anymore, you might also not make a backup, which would be important, because the only things you could try now, is to find the stock firmware and flashing it.
If you haven't installed any important data on your system after flashing LineageOS or if you already made backups of your applications in a cloud or another drive you need not to care. It is possible that you will need to do a hard reset before. You can find on hardreset.info, in the section "All devices", how to do it or ask the SHARP support. If you fear you have still important data on your phone a backup is normally recommended.
Because flashing a ROM not only wipes your data, but removes the guarantee, the result is: Restoring the phone to a usable device by any helping team of SHARP's customer care service in you city, even if you have any service buildings, might be expensive in this case. To go around high prices you would need too look around also for other data restoring companies or specialists, if nothing works.
But at first, if you are able to do it; I would recommend to do a hard reset of your device, which should restore it to factory setting, which should make the drivers work.
Even if they don't work, ask SHARP for actualized USB-drivers. Try flashing also with and without working USB drivers, and find SHARP's stock firmware for you device first, which is a "must do", if you want to have access to the original recovery mode again. Flash this stock firmware after you have done a hard reset. After flashing the stock firmware you should be able to go to the custom recovery mode again, if not, only a specialized company or a help team of SHARP's customer service might help.
Hello,
The adb and fastboot commands wait for the device to connect.
SHARP support is not responding.
Hello, did you try "https://getsupport.sharpusa.com/Contact-Us/Product-Support"?
Because of the actual situation with the Virus, they might need longer to answer, so you need to be patient. As I see you already tried to connect your device after the use of CMD.exe. Installing the drivers with CMD and checking the Windows Hardware Manager if the Installation worked correctly is one way to do a driver install. I am sorry if this didn't work for you. If it does not, only a specailized soft- and hardware team can help, which could get expansive, but maybe not as much as buying a new device, so I hope for you Sharp will answer and give a correct Installation guide and that it will fit to solve your problem. I wish you good luck and that you don't need any other company than Sharp to help. I know that nobody is amused if all help and waiting does not help, after bricking bis device, but unfortunately I can't do more for you. I wish you success and keep your device in a safe place just for the case.