Database Users

[Q] Flash stock with security error

Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.

did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:

kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
No problem if you brick a sammy phone. its easy to flash stock rom. How did you brick your g2?
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
Totally at a loss at this point.
Click to expand...
Click to collapse
Why did flashing a rom leads you to that error? Sorry but not familiar with your roms but is this rom really for your LG G2 model?

lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
Hey I'm in the exact same position as you... did you manage to figure out a way to get into recovery?

kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.

kureta said:
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.
Click to expand...
Click to collapse
I am on the same boat, same problem, and don't know what else to do...hope someone could help us out.

Yep me to same issue. Pretty much tried 6 different methods and still stuck

Solution
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile

Any luck anyone? I can't get the suggestion in the last post to work because my phone just goes from the LG Logo to Security Error. I can't get to download mode. Or recovery. Or get ABD to see it.

Odd
quatrix1 said:
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile
Click to expand...
Click to collapse
i have to choose upgrade recovery and it gets past analyzing then doesnt show a bar for downloading software...

HELP!!!!!!!!!!!!!!!!!!!!!
Can someone help me I successful in installing twrp though autorec apk and the same for rooting my g2. I flashed cm with nightlies and noticed that twrp had a update. I downloaded the zip and try flashing it like flash a recovery in flashify but that din't work and readed that zip flashing though twrp didn't work but renumber this video and though it would update my recovery to 2.7.1 but it was successful in doing so but when I got to recovery it was 2.7.0. That not the problem form there I tried to boot into my system. Then it turn off though that I passed power off instead but when turn my g2 back on I found that I had a security error show up then turn back off. So can someone help show me a tutorial on unbick or a way to remove error. Also I have the d800 and i have some idea without going though unbicking a hard factory rest or flasing twrp form there site in fastboot. Finally that lg mobile support tool say that im up to date. I think doing the autorec twrp recovery locked as my phones recovery like trying to flash a rom with a locked bootloader.

Ok guys i trying to help cause it happen to me too,sorry for my english too slow but i try,when you try go twrp with volume up+power buttom it still show security errow,that ok your device not hardbrick yet,when you try volume down+power buttom it show hard reset it does mean it clear all rom,picture in internal but it go to twrp again,and them just flash another rom in your device and it done,have great day piece

I had the same problem on my G2 was using twrp to flash cyanogenmod not sure what i did and phone rebooted to show security error message. I entered recovery mode (power and volume down release when logo pops up and press power and volume down again hold for a second then tap both buttons a few times) pulled up the option to factory reset so i did and it booted me into twrp and allowed me to flash cyanogenmod correctly this time and the phone started back up with no problems. hope this can help someone else as well.

Anybody know the solution?
I also have the security error boot loop after flashing KK baseband files... I tried to enter recovery mode by holding vol down & power button but it wont work...
it does work when i enter download mode (vol up + power button), but i don't want to have to download the stock LG ROM..
anybody know how to by pass the security error boot loop to allow me to reflash?

kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
if you still bricked. try this
get your tools from here: http://forum.xda-developers.com/showthread.php?t=2432476
keep reading or follow above thread. both will work.
best of luck.
After all the drivers installed correctly
make sure your phone is connected to the
com41 port change it if it already not ( Under device manager > Go to Ports (COM & LPT). You should see LGE AndroidNet etc... Right click it and go to Properties > Port Settings > Advanced > Change COM Port Number to COM41 > OK > OK > Close Device Manager )
run flash tool
1. choose type CDMA
2. chose PhoneMode: DIAG
leave rest as it is.
3. choose your kdz file.
then go to download mode
1. power off
2. press and hold vol + key and plug usb cable
3. done )
We have go 2 flashing modes.
1. Normal Flash is for flash with keeping data
2. CSE flash is totally new start preffered.
hope this helps.

thanks but it was a long time ago and I further messed up things, ended up sending it for warranty. they have replaced the device.

me too messed up my cell 1st i was on cloudy g2 v2.1 installed cm11 nightlies but the camera was not so good so then installed cloudy g2 v2.1 n since then i was having problem regarding sound during call and also some hard noise like siren starts randomly, i searched alot but didnt got any solution. wiped all many times (including internal storage ). but no luck then i thought i might be baseband error so i just downloaded auto recovery n flashed it n then stuck into security error but thank GOD i had custom rom in my sd card that time i flashed it back but still em having the sound error.

lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
k2thejx5 said:
Yep me to same issue. Pretty much tried 6 different methods and still stuck
Click to expand...
Click to collapse
Hey guys, I was in the same boat for a little but was able to fix it by downloading the 801C firmware and flashing it. The firmware file should be a KDZ extension and you should also download LG Flash Tool 2014. Turn the phone on by holding the Power button and Volum up while it is plugged into your computer(It has to be plugged into a computer with LG phone drivers or it won't work).
Follow this tutorial and you will be set.
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Start at step 17 on Method 1 and you should be golden.
Hope this helps guys!

Brick and Restart Loop no Download

Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks

Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??

Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app

Same Problem here! Exact Same

Also having this issue, stuck in the secure boot loop, can't get to download mode.

Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!

Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.

I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.

Stuck at boot logo, computer has access to file system

I'm in a very peculiar position here, where my LG G2 is stuck as the LG boot logo, but when plugged into my computer I have access to the internal storage. Here's how I got to this situation:
I previously owned a G2 on CM11 that had hardware issues. Before swapping it out due to those issues, I had made a backup using the package listed here, which created a few .img files, including boot.img.
On my new phone, I rooted, installed TWRP, made a backup of stock
Flashed Mahdi Rom
After flashing Mahdi Rom, my phone would immediately boot into fastboot, showing "fastboot started (new line) udc_start"
I did with the procedure listed here to be able to access download mode, and this was successful.
I then followed the procedure here to return to stock, but I got an error in LG FlashTools saying that I had the wrong model number. After a bit of digging around, it seems that this error may have been caused by the Mahdi Rom flash renaming my phone to "G2" instead of "d800".
After troubleshooting this for hours, I took a stab at flashing the boot.img file mentioned earlier through fastboot. Flashing this boot.img is what triggered the predicament I'm in now - I can access the phone's internal storage on my computer via USB, but it's stuck at the LG logo.
At this time, my phone will not ADB, fastboot, or enter recovery; I can only access download mode. When trying to enter recovery, it loads for about 1 second and then I'm kicked out and it goes back to the LG load screen.
Thank you in advance for any and all help

Try here http://forum.xda-developers.com/showthread.php?t=2687768

THANK YOU
MK45A said:
Try here http://forum.xda-developers.com/showthread.php?t=2687768
Click to expand...
Click to collapse
Holy **** it worked! Thank you for linking this, my D800 baby has been resurrected.

[Q] Ruined Fastboot mode, but regular boot works?

Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?

As I understand; If you're trying to boot it to recovery mode, it goes to fastboot mode, right?
If I understood right; you need just flash recovery to your device.
G2 has a different boot process from other devices. If bootloader failed to boot the thing you want to boot, it goes to fastboot mode. That's why it goes fastboot mode when you try to boot it to recovery.

Ah yeah, i just couldn't figure out how to get it out of Fastmode. I was a little confused about the difference between fastmode and recovery.
I seemed to have fixed the problem by AutoRec, for whatever that is worth. Now it boots into TWRP's recovery mode. Shouldn't be hard to get cyanogenmod now.

TheAmericannomad said:
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
Click to expand...
Click to collapse
if you want go back to stock and you can't enter in download mode you can try follow this but USE THE CORRECT FILES FOR YOUR DEVICE!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2477595
to extract laf.img from kdz.
http://forum.xda-developers.com/showthread.php?t=2600575
Give a thank to the OP of the threat.

[Q] Recovery Boot loop, can't go into recovery or my ROM: standby maybe have answer

Greetings.
I am sure there is an answer on XDA but an hour of Googling has got me stumped. Please point me to the right answer.
Starting point
Rooted N900T, stock rom, stock recovery.
What I did
Installed ROM Manager
Told ROM Manager to install the latest CWM for my phone. Completed with no errors.
Tried to boot into recovery with the standard "hold power, vol down, and home" but I could never get into recovery. It would look like it would start to boot into recovery then it would reset and boot into the regular ROM.
Then I told ROM Manager to reboot me into recovery.
Then it went badly... I am stuck in a boot loop that continuously shows going into recovery, then samsung logo, then repeat.
I have pulled the battery, tried to go into download mode, tried connecting USB, tried Odin.
What I want is a working phone. I would like to back up the stock rom and go to CM12 nightlies but for now I will just take a working phone.
Please help,
David
think I found the answer at http://forum.xda-developers.com/showthread.php?t=2666432
At least I got out of the loop, not fixed but progress.
That worked, the only other piece of info you might need if someone else has this problem is that there is no PDA button on the latest version Odin, it is called AP