So I tried installing Cloudy G2 3.0 the recommended way, with the patches and stuff. I initially did a dirty flash from stock lollipop but the ui wouldn't load to I went for a full wipe. At some point during the install, something messed up and I was sent to fastboot. That's all I could get to, so I wrote over the .img files to restore the partitions and now I have access to the factory reset menu and the hardware key settings menu. The factory reset menu just freezes at "factory reset processing" if I try to use it. When I boot normally, I get to the LG logo where it freezes. No pulsing light or anything. Plugging it in at that point allows the computer to recognize it but no adb or fastboot options. LG Flashtool recognizes that the phone is there but won't flash any .tot file. If I try a D800 tot I get wrong model and if I try a korean tot I get a cross dl error. I really need help, I screwed up!
Edit: It was tricky, but I was somehow able to get into download mode. Still same as before though.
Edit 2: Seems the Korean .tot I had was for the F320K and I needed the F320S.. will download and see how it goes.
EDIT 3: Jesus f*cking christ! Finally! Got the correct KDZ and found the correct software. It's installing!
Now, should I keep letting the phone think it's Korean? Are there any perks or downsides?
EDIT 4: Boot loop. It loops for a while, optimizes apps, loads the welcome screen, crashes, and repeats. No access to download mode or fastboot except for one time.
Related
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!
I already snagged another phone so this isn't a dire emergency "HELP!", but I would like to learn all I can from this mistake, and maybe resurrect the phone.
My VZW G2 is badly bricked. It turns on, shows the LG logo, sits for 20 seconds, then reboots and repeats. I can't get into download mode, recovery, and definitely not normal boot. It doesn't say anything about security boot error or fast boot on the screen before rebooting. So far, I haven't been able to get to a point where the pc will recognize it... not showing up in device manager at all (no Unknown devices)
Here are the newb steps I took to get here:
tot flashed back to vs98010b
Rooted,
Backed up stock recovery
Flashed custom recovery (twrp2.6.3.2 > philzcwm6.19.3 > philzcwm6.19.7)
Took vs98011a ota update (yes, intentionally)
Now I'm in a recovery bootloop, no biggie - I wanted to see what the ota puts where.
Pulled what I wanted
- Now the newb mistakes -
Decided I wanted to do the ota, so I flashed the the stock recovery back... while in recovery
Rebooted - LG logo bootloop
I know flashing stock recovery was my big mistake, but I'd like to know why -
1. does something else need fixed to go back to stock recovery?
2. we can't dd the stock recovery while booted in recovery? (didn't even think about this when doing it since you can flash a recovery zip from recovery, but I guess thats different)
3. the stock recovery img must have been corrupted?
4. something else...
I'm counting this as an expensive lesson, so I would like to learn as much as I can from it.
Try this thread http://forum.xda-developers.com/showthread.php?t=2582142
shaungregg said:
Try this thread http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I did look at that thread but didn't read thru all 38 pages. I'll go ahead and start reading thru it to see if someone in my spot was helped. Key difference between my scenario and that thread is that I have nothing showing up in device manager - I'm not getting the qhsusb_bulk device in device manager which is crucial for that to work.
I'm hoping someone knows how to force it to some other mode besides download mode and recovery since those don't work.
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.
Hi,
First of all i committed a mistake of thinking that with TWRP aboot + stock Recovery i will be able to do OTA upgrade, which made my phone not booting, undetectable by computer and majorly not getting the LG Flash download mode by pressing any combination of keys., Stucks at LG logo.
Device: LG-G2(F320L)
KDZ stock: F320L21V_00.kdz
1. Flashed this kdz using LG Flash Tool 2014.
2. Flashed from F320L_AutoRec.apk, the images only aboot, and recovery.
3. From DorimanX project generated the boot.img with StockROM(F320L21V_00.kdz) version bootimage RAMDISK.
Everything was fine., till then.
After that, i got the OTA pop up., So, thought of installing OTA. As I had already faced the TWRP bootloop once and in some post i remember i read flashing OTA needs stock recovery image. Here is the place I commited the mistake. So, signed the stock recovery with aboot of TWRP using loki_flash. Accepted OTA. Thats it.
From then, no booting, no recovery, no adb, no fastboot, and unfortunately NO LG DOWNLOAD MODE also it goes.
When i try to go TWRP, it stucks up after the initial TWP message.
And pressing some key combination, the device goes to LG service mode, and showing the IMEI and some list of 3 options in korean which i dont understand. By pressing any of the option device reboots and stucks with LG logo.
Even my device is not shown up in the ubuntu, when i checked "dmesg".
Can anyone help to get the device into Either download mode or fixing the boot.
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
No solution yet?
The phone is still in the same state. Can anyone please suggest the solution to make the device working? Thanks in advance.
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.