Good morning. I've been lurking here for sometime but never posted before, but I'm hoping someone can help me with what appears to be a bricked captivate.
This morning I woke up to an unpleasant surprise. When I picked up my Captivate, running CM7 stable, I got a flood of messages about apps that were hanging. I ended up force quitting several of them and then decided to reboot the device. After rebooting my phone was stuck on the CM7 splash screen. I ran some updates from the Market last night, but can't think of any changes that those updates or I would have made to cause the system to become unstable.
I managed to use the three button method to get into recovery and tried clearing the cache and data and fixing permissions, but still was unable to boot the device (remained stuck on the CM7 splash screen.)
I then tried to do a recovery to a previous ROM that I had backed up (Cognition 4.x - I don't remember the exact versions but it was one of the last releases in the 4 series.) During the recover process the phone threw an error while trying to write the boot instructions. CM7 is a gingerbread ROM and Cognition 4.x was eclair, so I'm wonder if this effort to restore could be the reason that things have gotten worse.
Now I'm stuck on the ATT splash screen and am no longer able to get into recover via the 3 button method.
Not being able to get into recovery makes me fear that the phone may be bricked, but I'm hoping that someone on this forum may have an idea.
I appreciate any help that anyone has to offer.
Correction
One quick correction. The Cognition ROM I mentioned above is based on Froyo, not Eclair.
Thanks again for any help.
me too.... please help
---------- Post added at 11:40 AM ---------- Previous post was at 11:03 AM ----------
http://forum.xda-developers.com/showthread.php?t=731989
shows how to put it in download mode. with the big triangle.
take the battery out, unplug it, put the battery in, hold down vol - and put in the USB. it takes a few tries, but i got it.
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
will put clockworkmod back on your phone.
choose your rom.
i'm going to try the cyanogenmod nightly again, but at least you get recovery mode back, your phone isn't bricked yet.
i finally managed to get into download mode last night. even though i wasn't able to use the three button method to get into recover, i was able to hold the volume button, plug in the usb and get the phone into download mode. then i used odin3 to go back to stock. from there i rooted, re-flashed cm7 and then gone from there.
hope that helps.
so i rooted successfully and installed cwm and that went all well too, but when i flashed a cm rom without wiping the caches and installing g-apps (kinda stupid i know) now im stuck with the security error screen. ive spent ALL DAY LONG trying to fix this stupid phone. i installed B2C lg app and it gets to 35 percent of the update process before i get a error at 35 percent that says "/image/dot.gif invalid path". and its such a pain in the ass because i have to reinstall the drivers every time i wanna retry the update because it says the phone is already up to date. i guess i will try the fast boot method more but i cant move past the omapp detection even after i pointed windows towards the fastboot omap driver it just keep connecting and disconnecting over and over.
after working with it further i think i actually messed my phone up more, i did connect fastboot with my phone after getting the timing down. i flashed jb xloader uboot and got the same security error then i tried to flash with the kdz updater and i couldn't tell if i didn't wait long enough for the kdz to unpack or the updater froze. now im stuck in a boot loop if i put the battery in
now my phone wont go into software update mode, i tried flashing clockwork with fastboot and now im back to a security error instead of a boot loop.
i have no idea why it wont go into software update mode someone please help, im getting to the point where the l9 is gunna meet a hammer...
after approximately a 10 hour day working on this **** on my one day off this week i destroyed that stupid phone, thanks for your guys phone i hated that stupid l9 from day one android isnt supposed to be all locked up like that. tmobile was the worst carrier i ever had virgins 3g had more bandwidth then tmobiles "4g" hsdpa prolly gunna get a siii from virgin now...
that was the most frusterating day of my life... now after a whole day of nothing working for me i can't get this F#$%#$ captcha!!!!!! aahahaha
Use the offline flash method. Quit pissing in the wind and then wonder why you're getting wet. You are using pieces of several different methods and that won't work. Install x and u boot and then use the offline flash.
LG-P769v20h. 'this the season to give thanks so hit the button already!
Relax....breathe....go to your cave to see your power animal...lol. Just use fastboot to flash the ICS u and x. Then you should be able to flash the 20h kdz using offline flash.
Sent from my LG-P769 using XDA Premium 4 mobile app
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
You may need to hold the volume up and plug in the USB cable to enter upgrade mode.
Sent from my LG-P769 using XDA Premium 4 mobile app
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
acefr said:
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
Click to expand...
Click to collapse
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
---------- Post added at 07:10 PM ---------- Previous post was at 06:47 PM ----------
so, i looked at the other thread and still dont see any issues. until you answer my questions, i cant speculate as to the cause.
only suggestion i could make,
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens.
bweN diorD said:
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
Click to expand...
Click to collapse
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
Click to expand...
Click to collapse
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
bweN diorD said:
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
Click to expand...
Click to collapse
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
Click to expand...
Click to collapse
install both of these drivers then try the tot flash tool again.
https://www.mediafire.com/?q1blsp6151rcmf9
https://www.mediafire.com/?x22q33votbv086d
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
btw, did you try this i suggested earlier?
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens
Click to expand...
Click to collapse
bweN diorD said:
install both of these drivers then try the tot flash tool again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
Click to expand...
Click to collapse
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
acefr said:
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
Click to expand...
Click to collapse
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Actually
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
---------- Post added at 11:56 PM ---------- Previous post was at 11:47 PM ----------
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
***Edit**** I just tried the suggestion of removing everything and vol down and power. shorter vibration than usual but still nothing.
soateufel said:
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
Click to expand...
Click to collapse
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
okay. so im gonna try the tot method. I installed both drivers and plugged in my phone and the phone driver just installed so ill let you know what happens.
bweN diorD said:
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
Click to expand...
Click to collapse
ya no dice... trying to kdz right now with the most recent drivers.
bweN diorD said:
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Click to expand...
Click to collapse
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
acefr said:
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
Click to expand...
Click to collapse
Tbh, I don't know what else to tell you to try, sorry.
I Have the same problem except
When I turn on the phone normally I get the lg logo then the notification light blinks I can seem to get the drivers working like recovery mode and download but the download mode is not working right it says dowload mode then goes to a black screen I get it showing it in device manager in Windows 8.1 but its not lg driver it starts with a Q can't think of it right now it under ports I can't seem to flash anything when it boots I get the Security boot error and then after the lg logo nothing happens except the notification lights up and blinks I was upgrading from 10B to 12B then my phone rebooted and can't boot into the system any help please I need this phone working
Same issue here!! Just vibrates, black screen, no boot
asdecker said:
Same issue here!! Just vibrates, black screen, no boot
Click to expand...
Click to collapse
Did you get into the brick by enabling band 3 and 7? Or what did you do prior to bricking it? Maybe we can figure out what is causing this together.
mine happened when i used lucky patcher to odex my system apps to make more space
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
asdecker said:
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
Click to expand...
Click to collapse
When you and soateufel tried the TOT flash, which step did you encounter issue? Did you get the same Model Information Check Failed warning like in my picture at post #13?
I rooted my phone today. That went well. The purpose to root my phone was to install the ported LG G4 camera app on my LG G3.
I tried to post a link to the steps I was following, but I am too new to post them. If someone wants me to PM them the links, I can do that, if allowed.
My phone will now not boot. It goes from the LG logo to the Android dude laying down with a red triangle coming out of his chest.
I have booted into recovery. I have tried all of the options, safe mode, USB debug mode, factory data reset, wipe cache, and power down. Nothing seems to work. When the phone attempts to boot up while plugged into a windows computer the device manager recognizes the phone.
I am lost. Can anyone help me or am I going back to Verizon and hoping they dont turn me away?
-Jeff
wesleypipesyo said:
I rooted my phone today. That went well. The purpose to root my phone was to install the ported LG G4 camera app on my LG G3.
I tried to post a link to the steps I was following, but I am too new to post them. If someone wants me to PM them the links, I can do that, if allowed.
My phone will now not boot. It goes from the LG logo to the Android dude laying down with a red triangle coming out of his chest.
I have booted into recovery. I have tried all of the options, safe mode, USB debug mode, factory data reset, wipe cache, and power down. Nothing seems to work. When the phone attempts to boot up while plugged into a windows computer the device manager recognizes the phone.
I am lost. Can anyone help me or am I going back to Verizon and hoping they dont turn me away?
-Jeff
Click to expand...
Click to collapse
did you try going into download mode and returning to stock?
there are tutorials in the general forum if you need it.
There is a video on YouTube by a guy named Max Lee called "how to unbrick or Unroot lg g3". Great video and great instructions (saved my ass). BTW I can't figure out how to attach link.. Sorry
Sent from my VS985 4G using XDA Free mobile app
So what started at 8pm ended at 3am. I used the video mentioned. I had to do it 3 times. Each time the end result was different. Including a blue screen with the number 2 and then the blue screen with the number 3. Thank you guys.