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?
So I was having so many issues with my rooted phone crashing on jasmineRom 7.0 I thought maybe an OTA update had made it through and started downloading. No matter what I was doing the screen would turn blue and then restart. Sometimes it would crash blue again during reboot, and sometimes it would crash and then show the green demigod crash screen. So I researched flashing the .tot files to go back to stock. KDZ I didn't care for because it still showed the phone as modified software, and I wanted full stock so I could use the extended warranty with Verizon if need be. I eventually got the .tot method to work and everything was hunky dory, and showing stock. I upgraded all the way to marshmallow and decided I love every bit of it, but I couldn't figure out how to get my contacts and stuff off titanium backup without root. So I figured, "well roots not the problem if an OTA tried to download it just means I missed a setting or something". So I rooted again. No issues, I reinstalled JasmineRom 9.1 this time. Eventually it started crashing again, although this time I followed absolutely every guide I could find on disabling OTA. So I thought, "Great it's Jasmine" and I really wanted Marshmallow anyway so I followed xdabbeb's guide for getting the 35b bootstack on my phone, worked great no issues, and then I installed xdabbeb's firmware, combined with Edor's debloating zips. Everything was working great! I had no issues, I backed up just my apps, and some data, and reinstalled others and everything was great and working fine, and the phone was still official, no OTA's getting through. That was almost a full week ago. Yesterday I woke up and the phone wouldn't turn on. I took the battery out and put it back in and the phone came on, but then crashed with the blue screen again. So I thought great I guess I'll put it back to stock and use the warranty. By this time though I was having trouble getting it to load past the LG screen. I finally got it into TWRP and was able to wipe everything (except SD card) and then I stuck it in download mode and went to install the .tot files. Weeeeelllll, long story short, it crashed during download mode install with the LG Flash Tool. So now the phone gets stuck in download mode everytime I pull the battery and power it on. And crashes again every time I go to install anything. KDZ doesn't work, the flash tool says it can't communicate with the phone, because it crashes. And LG Flash Tool for the .tot files seems to crash everything it loads the modem, or consistently crashes on LAF:bin_user_mode. So I have no idea. At the moment it just looks like my phone is all funky defective, and Verizon may take it back and give me a new one so I'm going to try that. HOWEVER! If anyone has any ideas on what the issue is or what else can be done, I still want to hear it. Feel free to post
Also I've tried updated drivers for the computer, I've tried rolling back drivers, I've tried different KDZ files, I've tried the LGUP8974.dll fix where you flash that in flash tools and then flash the vs985 dll, which is what I had to do to get it back to stock the first time. I've tried everything I could find online except anything to do with fast boot and shorting the pins. Which I haven't tried because I can still access download mode it just seems to be stuck in download mode. Those methods from what I understand are for hard bricking, and for people who's phones don't turn on at all. Although if Verizon won't help I may try one of the laf recovery methods.
Thanks!
[SOLVED] My LG v10 is in a bit of hiccup because of this. I have tried multitude of things with still no solution.
I have attempted to go into the mount of menu of TWRP and mount the system, after mounting I have tried everything from reinstalling a rom, wiping it, resizing, restarting to system, a few terminal commands, and they all lead to same exact scenario. The phone restarting, flashing the lg logo for half second than going to "this device software cant be checked for corruption" yellow triangle screen till TWRP comes up.
I have also tried 3 different versions of TWRP, installing kdz files, using an lg bridge/up update, and also some prayer. The only thing that has ever gotten me close to getting this baby back into shape was the lg bridge software update in download mode. Brought it to full startup from system but than ended on a white screen asking for a password 30/30 attempts to get into the phone, and I don't have encryption and even if i did it would be gone after the numerous factory resets and data wipes.
Are there anymore possibilities for me to try? The problem seems to be the system partition not mounting in most cases but I seem to have a reached a dead end.
Edit 1 w/Solution:
What ended up solving the problem (bad firmware, anti-rollback stopped me from going to a good one) was the following post by tungkick (THANKS TUNGKICK), once I got the microsd card ready and in the v10 I than put the phone in download mode (volume up + battery + usb to comp).
From there I used the lg bridge tool to detect the phone and than update back to stock. The key thing is i didn't chose the regular update option I chose the option on the bottom right (of my lg bridge application) that said update without error recovery I believe (sorry updating this away from home so I can't remember exactly). Once the update was done there was no screen with asking for a password, no bootloop, and so far no problems with the stock software.
Hopefully this is helpful one day to someone with a bricked v10 and almost gave up hope like me.
That happened to me when I tried rooting, I flashed the latest official kdz (select update) to get the official stock rom again
Sent from my LG-H901 using Tapatalk
luisoman2000 said:
That happened to me when I tried rooting, I flashed the latest official kdz (select update) to get the official stock rom again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Tried that and flashing tot files, feel like I cant do much unless I can install the /system partition on start up or get through the anti rollback settings.
As of now I can use twrp fine and get in download mode. But that seems to be it
Dunno what to say, do you have the latest version of lgup?
Sent from my LG-H901 using Tapatalk