Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
djordjesl said:
Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
Click to expand...
Click to collapse
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
EDIT: Pretty sure it's going to be a flag in a flat file. Combing over my init.rc file now, and i found a strange file called smpl_boot with a single 0 in it, not sure what it does
BStinsonWhadup said:
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
Click to expand...
Click to collapse
Can you enter Download Mode? (Holding volume down when G2 is turned off and plug the USB)
I also experienced this when restore using TWRP. But fortunately I can flash back to stock.
BStinsonWhadup said:
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
Click to expand...
Click to collapse
I think you dont understand me, when i did restore twrp shows that restore was completed, and when i do a reboot it shows
450 Fastboot mode started
500 udc_started()
Now i cant do nothing with phone, i try to power off and turn on it just go to
450 Fastboot mode started
500 udc_started()
djordjesl said:
I think you dont understand me, when i did restore twrp shows that restore was completed, and when i do a reboot it shows
450 Fastboot mode started
500 udc_started()
Now i cant do nothing with phone, i try to power off and turn on it just go to
450 Fastboot mode started
500 udc_started()
Click to expand...
Click to collapse
ahh i misread your post thinking you somehow had status messages on your screen during boot and that you got into TWRP each time. the question above this post asking about download mode may help you
BStinsonWhadup said:
ahh i misread your post thinking you somehow had status messages on your screen during boot and that you got into TWRP each time. the question above this post asking about download mode may help you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2451696
specifically:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
fixed it for me for anyone finding this post that CAN get to TWRP, the above linked post has other hints as well that may work for OP
I got this same thing when I tried to update TWRP using flashify, I can reboot to phone , running CleanRom 2.0 but not to recovery in order to flash other stuff.
ossito2012 said:
I got this same thing when I tried to update TWRP using flashify, I can reboot to phone , running CleanRom 2.0 but not to recovery in order to flash other stuff.
Click to expand...
Click to collapse
I somehow managed to do this as well. Did you get yours working again?
Edit: Fixed it up with this APP (Note that 3 other similar apps did NOT work): https://play.google.com/store/apps/d...l.freegee_free
Yozzo1 said:
Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
Click to expand...
Click to collapse
My situation is a little different than yours, but you may be able to do this method (which is what I am working on at the moment). As long as you can get into download mode.
http://forum.xda-developers.com/showthread.php?t=2432476
help !!
Hi, sorry for my english , I'm french
I wanted to flash a custom rom on my LG G2 D802 .
I wanted the Paranoid Android (PA +) with 4.3 JellyBean .
So I made the
Backup
Wipe data / factory reset
Wipe cache partition
Wipe dalvik Cache
After I
Choose zip ( custom ROM ) from sd card
Then I
Reboot System Now
And turn on my laptop, I get an error message saying
[640 ] started Fastboot Mode
[ 690] udc start ()
I realized I had to flash AOSP kernel before changing to a ROM paranoid . But my kernel is blocked and so I have to go back to the stock ROM
When I did this tutorial using lg tools , flashing stops at 49% with an error message .
I also saw that I could access the recovery mod by following this link http://forum.xda-developers.com/show....php?t=2565904(but I saw that I could not otherwise reboot my phone after it was bricking ) and therefore flash my stock Rom which I had made the backup . But I do not know if the ROM has been saved and if it remained in my files after the Wipes.
If it is not there, is that in buying a micro USB ====> HUSB adapter, I could install a stock ROM from a USB key ? Or is there a way I can put files from my computer to my laptop which has no port micro sd?
And is what I could with my kernel "blocked " ?
Thank you very much
Same problem here too. Can't get a recovery installed no matter what i do
Does anyone have a solution yet?? Same thing has happened to me.
If you can't go into download mode but get fastboot mode instead first repair download mode using http://forum.xda-developers.com/showthread.php?t=2477595 and than flash back to stock 4.2.2 using http://forum.xda-developers.com/showthread.php?t=2432476
My G2 can not go into download mode and recover mode, and my computer can not recognise it so I can not put anything to it.
fast boot
udc error.
CAN SOMEBODY
EXPLAIN IN SIMPLE WAY STEP BY STEP.
Thank you
Had this exact error too, fortunately flashing furnace kernel fixed it.
Tahir, I had to try several times until i succeed to boot to my recovery mode, try several times.
was having this issue. but i figured out my problem. the rom i was installing was a note3 rom. hahahaha. thats what happens when u have too many phones. and files in your computer. anyways.
i ddnt have to revert back to stock. i was able to reboot to twrp via hold power button and volume down buttons, when lg pops up, let go and press and hold both buttons again. when white screen with words comes up, press power then power then power. then ur back to twrp, at least mine did. and restored my recent back up.
nimrodsv said:
Had this exact error too, fortunately flashing furnace kernel fixed it.
Tahir, I had to try several times until i succeed to boot to my recovery mode, try several times.
Click to expand...
Click to collapse
How did you flash the kernel if you couldn't get into recovery?
I have download mode, but lg support tool only goes to 49% and I get error.
Would like to flash this kernel if you have another way
rodpgfx said:
How did you flash the kernel if you couldn't get into recovery?
I have download mode, but lg support tool only goes to 49% and I get error.
Would like to flash this kernel if you have another way
Click to expand...
Click to collapse
I could, after 5-6 times pressing Vol Down + Power method
nimrodsv said:
I could, after 5-6 times pressing Vol Down + Power method
Click to expand...
Click to collapse
I have similar issue after trying to install Xdabbed Camera on my LG G2 running with ClaudyG3 ROM.
I have flashed the Xdabbed Camera zip file sucessfully via TWRP 2.7.0.0 but when I reboot the phone after successful flashing the phone went into Fastboot Mode and UDC as mentioned above. Can my phone back again to recovery mode? I have backup ready, but only can restore if I can go into recovery TWRP...please help
epwt said:
I have similar issue after trying to install Xdabbed Camera on my LG G2 running with ClaudyG3 ROM.
I have flashed the Xdabbed Camera zip file sucessfully via TWRP 2.7.0.0 but when I reboot the phone after successful flashing the phone went into Fastboot Mode and UDC as mentioned above. Can my phone back again to recovery mode? I have backup ready, but only can restore if I can go into recovery TWRP...please help
Click to expand...
Click to collapse
Try booting to recovery after you charge your phone for at least one hour and while it's NOT CONNECTED to the computer
If that's doesn't help try using ADB
Related
[SOLVED] Okay so I got my i/o tab back up and working. See this post http://forum.xda-developers.com/showpost.php?p=14586131&postcount=2.
1. I downloaded those 2 things.
2. I booted into odin mode by powering off the device and holding the power and the left volume (volume down) until it brings me to a usb and a triangle sign with an android figure.
3. Press Right volume (volume up) to select the right icon on the screen.
4. Plugin the tab to your computer and load the odin3 v1.85 application.
5. Press PDA and find the PDA_SIGNED_P7105.tar.md5 file
6. Click start and let it reboot and it should be fixed! (well that's what fixed it for me)
So I tried installing the starburst rom on my i/o tab that I won (from phandroid!), anyways I was on an unlocked 3.1 rom that was rooted. So I installed rom manager from the market to get cwm on it. After that I backed up my current rom, and then I flashed the starburst rom.
After the rom finished flashing it rebooted and is now stuck in a bootloop of continually showing the samsung galaxy tab 10.1 splash screen.
I can't get back into cwm at all. I've tried getting it back with odin and with nvflash. Also fastboot isn't working for me (says waiting for devices both on my windows and linux machine). I've tried flashing both stock recovery and cwm via odin and via nvflash but nothing is working.
I'm not really sure where to go from here. I've spent the last 5 hours or so on xda and google. Any help would be appreciated.
The first attached files shows what happens when I select the USB image, the second shows what I get when I hold down the power and down volume, and the third is me flashing cwm through odin, but after flashing it, I still can't get into cwm.
I'm not an expert, but you may want to check the file you are trying to flash as it may be corrupt. Maybe try redownloading and flashing with odin. If that does not work you may need to reflash your firmware, I think there is instructions in the dev form on where to download. Also check if the IO edition is different model from the retail WIFI version.
Hopefully this is helpful,if not I'm sure someone else will chime in.
I checked the md5 of it and it matched. How would I reflash with odin? All I can see that I can flash with odin is the recovery. I don't know how to flash anything on my tab in it's current state. I can't get cwm back, and all I get is fastboot usb mode and odin. Fastboot isn't working and odin says it flashes the cwm recovery correctly and everything, but then it's not there.
Thanks for your input, any input is greatly appreciated. Was hoping to get my tab updated to a touchwiz rom, now I can't even use it.
I had same problem happen with mine out of the blue and it's stock I/O.
Maybe the thing i'm flashing in odin isn't for the I/O tab?
kbutlermd said:
I had same problem happen with mine out of the blue and it's stock I/O.
Click to expand...
Click to collapse
Did you fix it? I had this happen once before but I forget how I was able to get fastboot to work to issue a fastboot -w command.
Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?
mjm128 said:
Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?
Click to expand...
Click to collapse
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup
used2hvatreo said:
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup
Click to expand...
Click to collapse
I think maybe my partition table is effed up? I'm not sure.
I tried fastboot and flashing the backup that I had on my computer (fastboot flash system system.img ; fastboot flash data data.img ; etc), but it just hangs at the samsung galaxy tab splash logo.
I'm using the ota that comes in the files for dummies in the dev forum.
thank you SO MUCH ... I was stuck for hours until I found your thread
but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????
Sheeda Talli said:
but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????
Click to expand...
Click to collapse
you are not in download or recovery mode. turn your tab all the way off, and then use the key-combo to get into the menu where you choose recovery or download mode.
then odin will see it
Jtag will available soon for 10.1
which key combination ??????????
there is nothing shown on my tab
no light
no charging sign
blank black lcd while in """'NVIDIA USB Boot-recovery driver for Mobile devices"""""" mode
in device manager
so good to hear that mine is not bricked
So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>
mjm128 said:
So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>
Click to expand...
Click to collapse
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..
gunzo71 said:
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..
Click to expand...
Click to collapse
Simply doing fastboot -w has never worked for me. It would just bootloop. Only way i've been able to restore it is through the steps I listed in this thread.
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!
hi guys,
i flashed recovery using the manual method from this thread http://forum.xda-developers.com/showthread.php?t=2468858.
I wasn't able to use the last command
Code:
rm /sdcard/g2_security
I thought it didn't work , i also updated the my phone software.
When my phone restarted it went to cwm and now its stuck there.
Now when I try to boot I can either get in CWM or some Korean Recovery Menu with three option (i tried all nothing happend) or just stuck in boot loop!
I can't get in download mode by pressing vol up and plugging usb cable (tried all possible methods)
I will be glad if someone can help me out.
Thanks in advance
That's an unexpected situation to say the least.
So in short: installation of recovery worked, but you lost access to your ROM.
Correct?
Now, if you had a flashable ROM on your sd card you would be sorted, no?
I would say, get any compatible ROM, put them on a micro sd card and plug them into your phone. Flash through cwm...
Am I misunderstanding?
Otherwise there is always the fully back to stock option:
http://forum.xda-developers.com/showthread.php?t=2475045
Zentac said:
That's an unexpected situation to say the least.
So in short: installation of recovery worked, but you lost access to your ROM.
Correct?
Now, if you had a flashable ROM on your sd card you would be sorted, no?
I would say, get any compatible ROM, put them on a micro sd card and plug them into your phone. Flash through cwm...
Am I misunderstanding?
Otherwise there is always the fully back to stock option:
http://forum.xda-developers.com/showthread.php?t=2475045
Click to expand...
Click to collapse
I was able to fix my phone using this thread. I was able to get in recovery but not in download mode. After executing these commands I flashed stock firmware through LG flashing tools.
aatish said:
hi guys,
i flashed recovery using the manual method from this thread http://forum.xda-developers.com/showthread.php?t=2468858.
I wasn't able to use the last command
Code:
rm /sdcard/g2_security
I thought it didn't work , i also updated the my phone software.
When my phone restarted it went to cwm and now its stuck there.
Now when I try to boot I can either get in CWM or some Korean Recovery Menu with three option (i tried all nothing happend) or just stuck in boot loop!
I can't get in download mode by pressing vol up and plugging usb cable (tried all possible methods)
I will be glad if someone can help me out.
Thanks in advance
Click to expand...
Click to collapse
The same exact thing happed to me. did u fix it, if yes can you please tell me how??
I have the same issue. Nothing mentioned in other threads is useful just because I CAN'T ENTER DOWNLOAD MODE. Totally stuck Help! Devs! Anyone!
Try installing some custom rom from recovery...after installing custom rom you can enter into download mode and do whatever u want...return to stock using kdz files or anything else..
I recently got an lg g2 and rooted it, but it would never boot into recovery mode correctly. Well one night i was trying different chargers because it kept saying it was charging and would vibrate and say it was charging again, i woke up and the screen was lit but wasnt booting. I tried to restart it, no affect, tried to recover it, when it does this it goes into the blank screen again and does nothing, it also wont go into download mode. when plugging into the computer around 15 drives pop up and say they need formatting and it says that is is some qual disk drive and wont install any drivers. tried adb and the phone isnt recognized. am I SOL? What else can i try. One disk drive mounts and has a folder named image.
Short version
-wont boot
-no download mode
-recovery does nothing
-computer does not recognize as phone
-comes up with 15 disk drives that needs to be formatted
-one has a folder named image with stuff in it
-adb wont recognize phone
-tried the lg recovery tool and b/c no download mode it will not read the phone (tried to force install the drivers of the phone to see if it would work to no prevail)
Help :crying:
well today i got it to go into twrp recovery mode and can use adb with it again.
-will not boot
-can get into twrp now
-says when booting
fastboot mode started
udc_start()
reset
portcharge
-wont go into download mode but for a second
anything i can do to push a stock rom or to get it to go into download mode, ive been reading threads upon threads and just need some advice or anything now, ive tried almost everything and im exuasted.
etm34 said:
well today i got it to go into twrp recovery mode and can use adb with it again.
-will not boot
-can get into twrp now
-says when booting
fastboot mode started
udc_start()
reset
portcharge
-wont go into download mode but for a second
anything i can do to push a stock rom or to get it to go into download mode, ive been reading threads upon threads and just need some advice or anything now, ive tried almost everything and im exuasted.
Click to expand...
Click to collapse
Why not just go back to STOCK?
-for download mode, dont try to BOOT into download mode. Use the method of holding VOL UP while plugging in USB when the Flashtools are ready to go with the TOT and DLL files.
Follow this link:
http://forum.xda-developers.com/showthread.php?t=2633150
etm34 said:
well today i got it to go into twrp recovery mode and can use adb with it again.
-will not boot
-can get into twrp now
-says when booting
fastboot mode started
udc_start()
reset
portcharge
-wont go into download mode but for a second
anything i can do to push a stock rom or to get it to go into download mode, ive been reading threads upon threads and just need some advice or anything now, ive tried almost everything and im exuasted.
Click to expand...
Click to collapse
if you can get to fastboot mode this guide http://forum.xda-developers.com/showthread.php?t=2477595 has a way to recover download mode so you can get back to stock just make sure you download the files for your device
PhillyFlyer said:
Why not just go back to STOCK?
-for download mode, dont try to BOOT into download mode. Use the method of holding VOL UP while plugging in USB when the Flashtools are ready to go with the TOT and DLL files.
Follow this link:
http://forum.xda-developers.com/showthread.php?t=2633150
Click to expand...
Click to collapse
Like I said it goes into download mode but only for a second then it goes back to the fastboot screen.
XxZombiePikachu said:
if you can get to fastboot mode this guide http://forum.xda-developers.com/showthread.php?t=2477595 has a way to recover download mode so you can get back to stock just make sure you download the files for your device
Click to expand...
Click to collapse
Did this already, didn't repair it, said device does not have enough space during the last step. it allowed it to go into download mode for a second, but will not stay in it.
Solved my problem, will post a guide for others this weekend with the same issue.
etm34 said:
well today i got it to go into twrp recovery mode and can use adb with it again.
-will not boot
-can get into twrp now
-says when booting
fastboot mode started
udc_start()
reset
portcharge
-wont go into download mode but for a second
anything i can do to push a stock rom or to get it to go into download mode, ive been reading threads upon threads and just need some advice or anything now, ive tried almost everything and im exuasted.
Click to expand...
Click to collapse
Don't know if it's of any help but check out my post on fixing a hard bricked g2 had a similar problem an was able to get it fxed
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.