Lg Optimus P769 Security Error - LGST Download phase not working - LG Optimus L9 P760, P765, P768, P769

So for about two weeks now my phone has been getting this LG Security Error (therefore rendering it useless). I was trying to install a newer version of CWM (I was using l9recovery.apk or whatever it was) and I forgot that my bootloader was locked. Since then my phone has been a paperweight. I put a lot of research into trying to fix it and everything has ended up in failure. I first tried the LG Mobile Support Tool. Everything worked until it got to the downloading phase (it just stops and ceases to work). Then I tried to recover it via Fastboot. This also failed because I couldn't get it to detect my device (I couldn't get the omap4430 drivers installed, either). So if anyone knows a way to fix the LGST downloading phase or a way to get Fastboot it'd be greatly appreciated. Thanks in advance. Otherwise, if this doesn't work, would you guys recommend a JTAG service from Ebay? This would be my last resort.

Check this thread.
http://forum.xda-developers.com/showthread.php?p=36351786
It works
Sent from my Android powered coffee coaster.

Related

[Q] LGNPST not recognizing E970 anymore

Hey guys, I seem to have soft-bricked my E970 (which was running stock ICS) in the process of trying to get the bootloader unlocked using Freegee's ZIP method.
I was able to get into Download Mode, so I got LGNPST installed and flashed a TeenyBin, but 85% through the process (after the reboot) I got an error from LGNPST about the device disconnecting along with a Windows "USB device not recognized" notice.
I was able to get reconnected and complete the flash (100%), but my device still didn't get past the LG logo. I figured the interruption might have screwed the flash up, so I tried it again, but I got the same error, only this time I wasn't able to complete the session, and now my device isn't being detected in LGNPST at all
Am I SOL? I can still get into Download Mode, and my device is still showing up in Windows. Any suggestions? What are my options if I can't get my device recognized in LGNPST anymore? I dug around on the forums but couldn't find a solution.
Quick update: I tried following this guide to unbrick my E970 without having to use LGNPST, but am unable to download the KDZ file for my phone since I don't have a way of getting the serial number. I got the IMEI from my carrier but no luck there either.
Anybody?
Bump
ct456568 said:
Bump
Click to expand...
Click to collapse
Finally figured it out with some help at the freenode IRC chat. I reinstalled LGNPST from scratch on a clean Windows 7 install and LGNPST picked up my phone like a charm. Must have been some kind of driver issue. I ended up flashing the Teenybin ALTbin and then the latest stable CM10, along with a hybrid 84/27/84 radio to fix some call issues.

Any help appreciated!

Hi everybody - any help with the following problem is appreciated, I've thrown everything I can find at it but I'm just over my head at this point!
My LG G watch worked great, up until one morning when it got stuck in a bootloop - if I had to guess, the battery must have run out at the exact wrong time, during an OTA update. Maybe. Anyway, stuck in a bootloop.
I managed to install TWRP bootloader, and apparently uninstalled everything but the TWRP bootloader, as it now has the 'no OS installed!' dialogue whenever I try to exit.
I had minimal success installing ADP drivers, but never managed to make a PC/watch connection past fastboot OEM unlock. At the moment (a few months after i had that working) my PC doesn't recognise the watch at all.
So I've bought an OTG cable, and the plan is to put a flashable ROM (hey, even the stock one if I can find it) on a USB stick, navigate to it on TWRP via install, and take it from there. Anyone know if that's what I should be trying / where I can find that particular ZIP file?
Also worth noting, I never toggled on ADP debugging when the original OS was working.
Here's the info from the fastboot screen- ANY help is appreciated!
Product Name = Dory
Variant = dory 4GB
HW Version - rev_11
Bootloader Version - Doryz11c
Serial Number - 03b1175b02a23642
MSN - 406KPMZ0096923
Signing - production
Secure boot - enabled
Lock state - unlocked
Have you tried the instructions of the thread about fixing adb after the update? May work for you. I don't think the watch supports OTG...
http://forum.xda-developers.com/showthread.php?t=3347122
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Should have asked months ago
MihaiSG said:
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Mate... worked a dream. Thanks so much!

Alcatel One Touch Pixi 7 9006w tmoble help

I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol

HELP!!!!! Unable to flash stock KDZ to LG G5 RS988!

I have been pulling my hair out trying to figure out how to get my phone to flash the stock KDZ.
The other day there was a stock zip that I could flash and that would allow me to keep TWRP installed if I flashed Magisk just afterwards to keep the new boot image but with TWRP. Long story short it did not work out in the end. My phone continuously too no end bootloops over and over again. I get the error code:
Boot verification Fail!
-cause : MISMATCH_SIG_Len
The only thing I am able to get the phone to do differently than that is if I plug it into a computer and hold down the up key which will get me into Download Mode. I have all the appropriate drivers installed but the device is only recognized as LGE AndroidNET USB Serial Port (COM3) I think I switched it to COM3 though.
I installed the LG Flash Tool 2014 and the appropriate KDZ for the device but to no avail I am unable to successfully flash the image back.
I had to flash stock KDZs with my old LG G3 and it worked flawlessly. Now this is reporting that there is no IMEI or something. I'm trying to pull the information off of the phone but it's not even doing that anymore.... so I'm not too sure what information to give you.
I just bought this phone not too long ago! I refuse to accept that it's fully bricked I don't believe in that unless that motherboard inside is snapped clean in half. I'm sure there are ways of fixing it.... I just don't exactly know how.
If anybody can help at all that would be greatly appreciated!
I was just getting back into having a rooted phone and miss it dearly already!
Thanks!
-RioPlay
P.S. Any feedback at all is appreciated! I HAVE to fix this!

From bricked to custom ROM in 2019 (GUIDE)

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!!!

Categories

Resources