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
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...
This post was closed and i was told to ask it here. I posted it in the wrong area and im sorry about that.
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Hey all,
Got a HomTom HT16 for cheap today and it was labeled as "Not Charging"
Gave the battery a quick charge on USB and nothing was on the screen.
Got my Multi Meter out and checked voltage of the battery which is fine.
I then connected the phone to my PC and nothing was installed (Drivers etc).
Ultimately I figured, it's a cheap phone - probably the Software.
Got SP Flash Tool V5.104 (Which is the latest I believe) and downloaded 2 x Stock Roms for the HomTom HT16 Pro, one labelled as a V1.17 and one a V1.20.
MTK Drivers are all installled (The MTK all in one pack from here I believe, I have flashed several phones on this PC with no issues)
Unzipped the ROM file, loaded the scatter into SP Flash Tools and connected the phone without battery and held Volume Up. (Yes the COM path was shown in SP)
The progress bar went red - showed DOWNLOAD DA 100%. Stayed on that for 32-38 seconds before coming up with "brom error s_ft_download_fail(4008)"
Stuff I have tried:
I tried earlier versions of Flashtool.
Tried using the other stock ROM.
Tried another Stock ROM from another site.
Tried a different computer.
The phone is detected in Windows if I hold Volume Up - it stays connected, holding Volume down is just, reconnect, disconnect so on so forth.
Tried different USB Cables and Ports.
Tried just the format option on it's own and same error.
Tried just the Preloader flash and same error.
And the phone is completely bricked. Like, no signs of life - EXCEPT an occasional tiny Vibrate. That's it.
(Tried Power + Volume Up/Down to no signs of life either)
I don't know guys, been googling for the last few hours and read a lot of XDA threads and other sites and it's usually just - It's SP Flash, USB Cable or ROM. But all seem to be fine as far as I am aware of.
If anyone could help me out in this situation I would be appreciative. Maybe someone who knows their way round SP Flash better than I do? Usually I take the battery out, load the scatter, click download and plug in phone plus Volume Up or Down - depending on the make.
And if any additional info is needed, I can provide.
Update:
Have tried going to a version 1.12 Firmware.
When I load it, it says PMT Changed for ROM, Format All + Download.
I do that and it comes up with Error 4010 Format Fail.
I tried some hex figures as well but it seems like it's completely dead.
Can't flash anything to it. Unless I take it someone who has an Infinity Box or something. No idea.
Can anyone suggest anything else?
Thanks
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
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!