Has anybody here had their phone repaired via Verizon's Asurion insurance? - Verizon LG G3

I'd paid $180 in Asurion phone insurance as part of my Verizon plan over the last 18 months I've had my G3, and I think it may be time to finally use it.
Some time within the past several days, it appears I must have pressed too hard on my screen at some point because now, when the screen is dark/black, there is a reasonably noticeable 'smudge' (for complete lack of a better word) inside my screen that is a lighter color than the rest of everything else. I can't really seem to think of the correct words right now to describe it, but it's basically what you'd imagine would happen when you press a screen too hard. The fortunate thing is, it's really only noticeable when the screen is dark, but it's still enough to drive me nuts.
I had a few questions about Asurion. ~3 years ago, I paid my $100 deposit and sent my old Galaxy S3 in because I broke the screen. They sent me back a brand new phone. It was sealed in the original stock box and it came with everything a new phone does (headphones, cable, charger, all the paperwork.) Plus the phone was very clearly not a refurb; it was flawless. I was under the impression I was meant to either have the screen repaired on my phone or get a refurb, but I absolutely got a brand new phone. Maybe I was lucky.
But I understand that my experience likely wasn't typical. So I want to know, from people who have sent their faulty/broken phones in to Asurion:
- Did they fix your problem and send your old phone back? Or,
- Did you get a refurb? Or,
- Did you get a new phone?
Normally, I wouldn't care, but my serious concern is that I might get a new or refurb phone that has an updated OS. This brings me to my next question(s).
- If I get a new/refurb phone back from Asurion that is running 47A or something else relatively new, will I still be able to unlock my bootloader, install TWRP, root, and just generally get everything back to the way I have it now, loaded with customization and modifications? Or do the newer G3 updates keep the phone locked down permanently, in which case I'll be SOL? What's the most recent software update to which I'll be able to make all of my modifications to?
Sorry for the wall of text, but I just want to make sure I get everything cleared up. I would really like to get this screen issue repaired ASAP, but if there's any chance at all that I'll be stuck on stock un-rooted forever when I get the phone back, I'm not going to take that chance. But if it's trivial to unlock the bootloader, install TWRP, and root the newer updates like 47A, I'll be sending my phone in ASAP.
Thanks.

I haven't used Asurion since about 2009 so can't say much.
I can say that it doesn't matter what stock ROM a replacement would come with, including up to the latest which is 47A, you won't be stuck. Just flash the 10B TOT using the .DLL that was extracted from the 35B KDZ, root with the Stump app, install TWRP with TWRP Manager from the Play Store and flash whatever you want.

This might be a little late for you but had to replace my verizon vs985 lg g3 back in December. I paid my $100 copay, and Asurion sent me refurb. Even when it looks like a retail phone it's usually a refurb unless the phone is brand new and they haven't gotten any bad ones back to fix up. Asurion doesn't have a repair department. This is the first smartphone I've gotten through asurion, back in the days of flip phones I got a bunch of replacements and often I had to get 2-3 before I got a refurb that actually worked. This g3 worked ok on the first try, although I do have one weird rebooting issue, that started a week after I got it, and recently got way worse may or may not be hardware related, theoretically they should send me another refurb if it is hardware under their warranty(without another copay), but I have a feeling getting them to honor it will be a battle.
It came with Lollipop at the time, i forget if it was 5.0.1. or 5.1.1.

madmax988 said:
This g3 worked ok on the first try, although I do have one weird rebooting issue, that started a week after I got it, and recently got way worse may or may not be hardware related, theoretically they should send me another refurb if it is hardware under their warranty(without another copay), but I have a feeling getting them to honor it will be a battle.
Click to expand...
Click to collapse
If I were you, before bothering try anything else I would restore to stock using the 10B TOT, because TOTs flash more partitions than KDZs and can fix weird issues that flashing KDZs and other ROMs can't.

roirraW "edor" ehT said:
If I were you, before bothering try anything else I would restore to stock using the 10B TOT, because TOTs flash more partitions than KDZs and can fix weird issues that flashing KDZs and other ROMs can't.
Click to expand...
Click to collapse
My refurbished phone is stock never rooted never flashed verizon vs985 currently on 5.1.1. It reboots only during phone calls. Do you think rooting it and doing all that stuff you suggested, would be of any use to me?

madmax988 said:
My refurbished phone is stock never rooted never flashed verizon vs985 currently on 5.1.1. It reboots only during phone calls. Do you think rooting it and doing all that stuff you suggested, would be of any use to me?
Click to expand...
Click to collapse
I understand that. You don't have to root it - rooting isn't involved in what I'm suggesting; it's using official LG ROM files and the Windows software necessary to flash them. I'd flash the 10B TOT using the .DLL that's extracted from the 35B KDZ. Then I'd test the situation you describe while still on 10B and see if it reboots. If it doesn't, I'd flash the 47A KDZ and test it again.
Edit: unless you don't have the original USB cable. Always use the original USB cable that comes with a device when new to flash a phone from a PC.
Click to expand...
Click to collapse
There's no way of knowing if whoever actually refurbed the phone did what they should in order to return the software to a pristine condition. They obviously didn't QC their effort very well. It's possible they didn't even do anything to the phone. There's also no way of knowing if the person who owned the phone before it was refurbished ever rooted it. Even if they had (for example) flashed the 35B KDZ before they refurbished it (it's common to return to stock unrooted before turning a phone in under warranty), flashing KDZs doesn't solve as much as flashing TOTs does.
A couple of months ago I was having consistent weird issues that wouldn't go away no matter what ROM I flashed while rooted, or what KDZ I flashed. It wasn't until I flashed the 10B TOT that the issue went away - from there I was able to do again whatever I wanted (flashing ROMs, KDZs) without the issue returning.
Or you can exchange for another refurb and take a chance that you might get yet another different or worse half-effort fixed phone.

Related

Never Rooted Can't Boot Up

My dad's Optimus T supposedly can't boot up after he took out the battery and the device has been never rooted or anything(stock). I can't take a look at the phone to see whats wrong, but I'm preparing for the worst and want to know how to flash stock rom with kdz to maybe get it back up and running. I found the KDZ file and I am wondering what else I would need besides that? I've never done this before and looking for advice. Also, my parents never bought warranty so do you think TMO will replace it because it was never rooted and it also has the dust problem. So would they replace it since it is defective product, but then again it's been a few months since we bought it.
Thanks.
Feeshie said:
My dad's Optimus T supposedly can't boot up after he took out the battery and the device has been never rooted or anything(stock). I can't take a look at the phone to see whats wrong, but I'm preparing for the worst and want to know how to flash stock rom with kdz to maybe get it back up and running. I found the KDZ file and I am wondering what else I would need besides that? I've never done this before and looking for advice. Also, my parents never bought warranty so do you think TMO will replace it because it was never rooted and it also has the dust problem. So would they replace it since it is defective product, but then again it's been a few months since we bought it.
Thanks.
Click to expand...
Click to collapse
well to be frankily honest with you, get yourself a job and start buying your own phones so that you can get warranties and insurance on your phone's also yes check with TMO about replacing the phone, no sense in using a utility like KDZ if you know nothing about it, I cant help you with KDZ, ive never had to use it and never will, but Im pretty sure there are tons of threads that can point you in the right direction
Jrhodes85 said:
well to be frankily honest with you, get yourself a job and start buying your own phones so that you can get warranties and insurance on your phone's also yes check with TMO about replacing the phone, no sense in using a utility like KDZ if you know nothing about it, I cant help you with KDZ, ive never had to use it and never will, but Im pretty sure there are tons of threads that can point you in the right direction
Click to expand...
Click to collapse
It wasn't my decision to buy warranty or not and this isn't my phone. I'm using KDZ as a last resort so I'm not 100% set on it. Going to see what TMO can do first, but I don't have any hopes that they will do anything.
Feeshie said:
It wasn't my decision to buy warranty or not and this isn't my phone. I'm using KDZ as a last resort so I'm not 100% set on it. Going to see what TMO can do first, but I don't have any hopes that they will do anything.
Click to expand...
Click to collapse
well good luck to you on that, if you need any help, let me know and Ill try to get some info for you on w/e you need, keep me updated as to how KDZ works for you, I have no need for it but Im to damn lazy to actually do the research for a tool I wont use, the only problem I had was one phone I "accidently" semi-bricked, but was under warranty so I got it replaced and now my second phone is rooted, customed recovery and CM7 rom on it
If you haven't had a chance to take a look at the phone yet, then maybe you can start with that and trying something simple like taking out the battery, putting it back in, connecting the charger, and trying to turn on the phone? Then you can see what's going on. Maybe you'll want to try holding Power + Vol. down + Home to go into recovery from a turned off state. Keep in mind that stock recovery immediately begins its restore which (I think - custom recoveries spoil us) wipes user content.
Jrhodes85 said:
well good luck to you on that, if you need any help, let me know and Ill try to get some info for you on w/e you need, keep me updated as to how KDZ works for you, I have no need for it but Im to damn lazy to actually do the research for a tool I wont use, the only problem I had was one phone I "accidently" semi-bricked, but was under warranty so I got it replaced and now my second phone is rooted, customed recovery and CM7 rom on it
Click to expand...
Click to collapse
Well, it's strange how it happened because this phone is completely stock and my dad or I never did anything to change anything to it. I really don't think it would get bricked just by removing the battery out.. I'll just have to wait until he gets back with the phone.
UPDATE: All phones have a 1 year warranty if something wrong with the phone so TMO took the phone in and sending a new one on the way.
Wait, so did you get a chance to look at it, or did someone else take it to TMO?
maip said:
Wait, so did you get a chance to look at it, or did someone else take it to TMO?
Click to expand...
Click to collapse
I tried to turn it on and it stays stuck at LG logo with the 4 buttons blinking. My dad took it to T-Mobile and gave him a replacement
Sent from my LG-P500 using XDA App

LG G3 random reboots 11cand then Back to 10b

ok I bought two brand new LG G3's on Verizon both rooted and stock roms.
Wife's run perfect...
Mine has random reboots. I first tried doing a full wipe reset and still did the same thing.
Then I unfroze everything and let it update to 11c to see if an update would help. Nope only got worse almost was unusable because it restarted alot.
So then I flashed it back to 10b and re-rooted and set it back up. All was good for a few days and then back to random reboots.
I hate to do it but I think I may have to call verizon and get it replaced.
Before I do this... Is there anything else I am missing to try???
I know they are just gonna give me a refurbished phone. I thought about just buying another new one...
More info...
I do have the wireless charging sticker on both LG G3's. I thought I read somewhere that it can cause issues???
So today I took the back cover off with the charging sticker and will run the phone for the day and see how it goes.
I do have a case over the phone still.
Nothing???
It seemed to get better but just rebooted on me today once. I was in the middle of texting when it did it.
The phone just shuts down and then restarts all on it's own.
I have never had a phone do this to me before.
I guess you can try and verify if it's the Rom or not by flashing another one. Since you're rooted and on 10b you can easily install twrp recovery with the flashify app and try flashing a different Rom. (Make a backup and clean flash) Try a stock based Rom if you want the phone to be how it is out of the box. Jasmine, Skydragon, and Beanstown are all stock based roms. You'll definitely get better battery life and performance over stock but still have all the stock features.
But if you've already flashed back to stock 10b and it's still randomly rebooting then you may just have a bad phone...and that sucks. Be sure to flash back to stock if you have to turn it in.
startswithPendswithOOH said:
I guess you can try and verify if it's the Rom or not by flashing another one. Since you're rooted and on 10b you can easily install twrp recovery with the flashify app and try flashing a different Rom. (Make a backup and clean flash) Try a stock based Rom if you want the phone to be how it is out of the box. Jasmine, Skydragon, and Beanstown are all stock based roms. You'll definitely get better battery life and performance over stock but still have all the stock features.
But if you've already flashed back to stock 10b and it's still randomly rebooting then you may just have a bad phone...and that sucks. Be sure to flash back to stock if you have to turn it in.
Click to expand...
Click to collapse
Yea I did think about doing that and probably still will.
Right now I am looking at just buying another LG G3 and keep this one for testing. If I can't ever get it to stop rebooting on it's own. I may mess with verizon for a replacement. I will keep what they send me if and only if it looks mint. I know they send you trash refurbished phones.
I bought these two LG G3 out of contract brand new (350 each). I don't goto verizon and buy phones and have not been in a contract in the last 15 years with them.
kendive said:
Yea I did think about doing that and probably still will.
Right now I am looking at just buying another LG G3 and keep this one for testing. If I can't ever get it to stop rebooting on it's own. I may mess with verizon for a replacement. I will keep what they send me if and only if it looks mint. I know they send you trash refurbished phones.
I bought these two LG G3 out of contract brand new (350 each). I don't goto verizon and buy phones and have not been in a contract in the last 15 years with them.
Click to expand...
Click to collapse
Did you try wiping the dalvik and cache?
Also you may have a defective phone. If it keeps rebooting even after a fresh install of 10B you might have a defective phone/battery.
tech_head said:
Did you try wiping the dalvik and cache?
Also you may have a defective phone. If it keeps rebooting even after a fresh install of 10B you might have a defective phone/battery.
Click to expand...
Click to collapse
Yes I tried wiping that and everything else...
I am pretty sure it's a defective phone. I ended up buying another one and then I will flash this bad phone back to stock and get a replacement from the big V...

G3 Automatically Boots into DL mode. Can't use LG Flash Tool, IMEI all 0's

I was having sms issues on cm13, and it was suggested that I flash the TOT again.
Not sure what happened the first time I tried to flash the TOT, but I was following directions as always and just assumed it would work flawlessly as it has done in the past. It failed somewhere along the line but I wasn't paying too much attention .
Now the phone automatically boots into DL mode (after LG screen, unusual), and anytime I try to flash a TOT now the flash tool goes from "Waiting for Connection" to showing a PID and showing my IMEI as null (all 0's). After some googling around I realize that this is not good in the slightest. The flash tool will timeout after ~20s and try again, but just keeps timing out endlessy after 20s.
This looks to me like a brick but I don't have enough experience or knowledge to say for sure. If anyone has suggestions I would greatly appreciate it.
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
roirraW "edor" ehT said:
Try the 10B KDZ just for the hell of it. I'm sorry to hear you're having so much trouble. Don't do anything rash, we'll see what we can do.
I hope you have a TWRP backup of the EFS (IMEI) in a safe place or once you get the phone working you'll have to use QPST or some such to manually type in your IMEI.
Click to expand...
Click to collapse
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
inexplicability said:
I tried flashing that kdz already, as well as the 47a. Both get up to that 4% like I had problems with before. Now the phone doesn't seem to want to boot into dl mode : ^) I can get into the system recovery but any of the options just take me to the LG boot screen.
And nope, no backups. I got this phone 4 days ago as a refurb to last me until the (supposedly) htc nexus phones in the fall. Never really got anywhere so didn't think to back anything up, especially not the imei. Never had a device be this finicky in my years rooting android devices.
Thanks for all your help man, but I may just have to chalk this one up as sunken costs and go back to my m7
Click to expand...
Click to collapse
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
thebigindian said:
Go with what roirraW "edor" ehT tells you first and foremost. What I'm posting is another option at last resort. If you dont have a backup of your imei, you will need an IMEI editor and use the IMEI that is printed inside your phone or on the box it came with.
I had the same problem. It's nerve racking but can be easily fixed. I'll look for the program I used and post it once I find it. Just so it's said, changing your IMEI is highly illegal. Make sure you restore your original that came with the device and not someone elses.
Click to expand...
Click to collapse
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
roirraW "edor" ehT said:
I know it may seem useless, but take the battery out and leave it out for an hour or more, then try to put it into Download mode again. When you try to put it in Download mode now, what happens exactly? Are you checking in Windows' Device Manager to see if the phone shows up in the Modem and Port sections? Does it ever show up?
Was it a warranty (LG or Verizon) refurb and do you have the option to try to exchange it for another?
Sure - I just wish I could do more.
What @thebigindian said reminded me - you may have to restore the IMEI before you can flash the TOT (assuming you can get into Download mode or at least QHSUSB_BULK 9008 mode). I have no idea how to go about that, though, as I've never had to - I just know there are threads in these sections on how to do it.
Click to expand...
Click to collapse
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
inexplicability said:
I've looked into restoring the imei, and have found that some users had success using a method for the lg g2, but most of these methods require some sort of booting. I am unable to boot to anything but the lg screen. I'll try why Rode says about leaving the battery out and see what happens from there.
I'll get back to you in a bit after the battery has been out for awhile.
I picked this up off of amazon as a refurb device. The first 2 devices I received were defective out of the box (first one had bent pins in usb port, second would bootloop and i didnt know as much about dl/recovery as i do now, it was probably fixable looking back) so that should have kept me away lol. I know I could probably get away with sending it back saying the device is defective or something, but it really is my fault (I believe) and wouldn't exactly feel good about doing that. Then again I don't exactly feel good about having a $120 brick lol.
Click to expand...
Click to collapse
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
roirraW "edor" ehT said:
I was afraid of that (can't put the IMEI back in without booting). I understand what you're saying but I honestly wouldn't be surprised if there was something wrong with the device anyway and that is the cause of why it bricked so easily. I don't trust refurbs.
I had a good experience selling on Swappa once but I haven't bought any through there so no idea if the experience would be better. I wouldn't buy any refurbed one. There's a black one on there that says Mint condition for $150. It's funny, some of them say 16 GB - as far as I'm aware there's no 16 GB version of the VS985.
Click to expand...
Click to collapse
Yeah now I don't trust refurbs either haha. It was worth a shot though. But yeah I noticed that about the 16gb device too when I was looking for a device to purchase.
I only picked up the g3 because a friend of mine asked about rooting his g3, wondering if he could get some more life out of it as his was becoming sluggish with all the bloat and whatnot. Figured I need a new phone now anyway and I would be able to get a g3, figure it out, then help him. That worked out great, didn't it?
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
inexplicability said:
UPDATE:
@roirraW "edor" ehT just thought I'd give you an update. I plugged in the device to power and it stayed at the charging screen with the loading icon for awhile, then I came back and it was in download mode!! Plugged into my pc and let windows install the drivers (took like 20 min, unusually long time) and was able to flash the 10b tot. IMEI is still 0, but at least there are ways to change that. Thanks again for your advice!
UPDATE 2:
Restored IMEI using this method: http://forum.xda-developers.com/showthread.php?t=2701861
Confirmed that mobile data / sms / mms are in working order... Going to try flashing cm13 again if that doesn't work I'll go back to stock and debloat as recommended
Click to expand...
Click to collapse
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
roirraW "edor" ehT said:
Wow. I'm always surprised when things actually turn around so well.
Do that IMEI (EFS) backup in TWRP although it must not have been too tough after all. You're welcome! It's helped me on various phones including this one from time to time.
Click to expand...
Click to collapse
I'll do an imei and nandroid backup once i get everything up and running. Tried using dirty unicorn, but google play services was failing. Tried cm13 but ran into sms issues again. Reluctantly installed stock 47a w/ debloat and it seems to be working ok.
Going to go off of your recommendations and use the xposed modules mentioned in the 47a thread until a more stable aosp based rom is available.
You may have actually helped me with my thread/issue, unwittingly.
Your symptoms are similar to what happened when I flashed anything lower than 46A bootloader wise... it would get a black screen (this is different than yours but keep reading), register as a device in download mode without any keypresses, and then refuse to flash the same way with all 0's IMEI.
It never occured to me to pull the battery for an hour. Maybe I should try that?
EDIT: ...And nope, that did not work either. I guess I just have to wait until marshmellow bootloader is exploited somehow...

VS985K purchased new from Verizon, ships with 47A firmware,new variant?

I have a new LG G3 from Verizon I bought to replace my aging Motorola Droid RAZR M. It seems this one is a model "vs985K" which I have never seen mentioned before. It shipped with 47A Marshmellow, and conventional tot flash methods (using 35B dll and such) do not work. States "no ks version."
So I dd'd in the relevant partitions from the 35B bootstack, and TWRP as needed. It bricked the phone. Black screen. Nothing.
Fortunately, I am not a noob at this. I shorted the testpoints to get into qualcomm 9008 mode, and to my absolute horror, even BoardDiag 3.99 would not talk to the board. It seems this may be a new part number. Swapping some files from a another tool got it to finally flash, and I'm still trying to recreate what I did, but however I did it now I know I have a tool that can debrick it via qualcomm 9008 mode and so I'm ready to try again.
After some messing, it seems the exploitable aboot is what makes it brick. Unless I am missing something. Anyhow that's not the point of this post. The point of this post is to discuss this potential new variant, and how the heck to get this on 10B. Any ideas? It really seems tough if I can't use the exploitable aboot.
PS: I would post how to debrick a vs985K, but because it uses tools and software that is of questionable copyright status, I can't. PM me if you are desperate and maybe I can help you, though.
The K is probably just referring to the color. Is it black?
Some people get bricked doing what you did, others it works fine including me when I tested that method several times. I have a thread in the General section about that method. The title includes "KS Error".
When some people do something that causes the black screen, they're still able to go through the motions of putting it in Download mode and you can see its in that mode in Device Manager, and then able to flash either the 10B TOT (with downgraded partitions, there's a chance you wouldn't get the KS Error any more) or the 10B KDZ, since the downgraded partitions would now let you flash any KDZ you want.
As far as I know, everyone who tried that method - those who didn't brick and those who did, were able to downgrade to 10B via TOT or KDZ after. Read the thread for more details.
Yeah, I was following your post. It led to a black screen. I know I got all the partitions but I had to short the test pins and use qualcomm 9008 mode to get back.
I'll try again and report back. Don't see what I could've possibly missed though. I'm trying to get back to 10B in the end.
Back at the black screen. LG FlashTool for TOT method seems to not want to flash it even though I can "kinda" get it into download mode (it just doesn't show anything on screen, but registers in device manager)
See attachment.
KDZ Methods similarly fail with "upgrade stopped due to an error"
Currently sitting at qualcomm 9008 mode with boarddiag, so if you have any ideas of what to flash, I can do basically anything, lol.
It seems flashing aboot is the culprit. I can flash just about any other part of the bootstack without issue. Is it possible 47A is blowing a qfuse or something to prevent aboot downgrades?
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
roirraW "edor" ehT said:
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.
I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?
Do you have the right special drivers to use with BoardDiag?
As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
Click to expand...
Click to collapse
Thanks. I didn't know about the extra letter, and mine is indeed black.
You've given me some leads to chase, if nothing else.
I'm not afraid to mess as I can debrick just about anything. First up on my list of things to try is a different USB port (I was using a USB 3.0 port).
Weird, after experimenting a lot, I find that the KDZ tool (from a fresh 47A install) let's me downgrade to 35B, but it ALSO gives me a black screen with similar behavior.
No idea what that means, but for whatever reason, it seems this device will not accept pre-marshmellow boot loaders.
http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.
R-T-B said:
http://forum.xda-developers.com/showpost.php?p=66096623&postcount=965
This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.
The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.
It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone.
Click to expand...
Click to collapse
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
b00ster23 said:
@R-T-B For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
Click to expand...
Click to collapse
Yeah, examination of my PCB shows it is version "2" as well, suggesting maybe this isn't the first revision. Maybe they are getting smarter.
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Don't get me wrong, I am not complaining I still have a phone afterall and I know this is all at my own risk. This may be speculation but I'd like to think it is educated speculation that a new hardware revision exists.
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
I'm going to try to use boarddiag to flash the entirety of the TOT. Any reason why this would be a bad idea? Seems as good as any at this point to see if it truly can't run 10B.
This may take a very long time, but heck, why not try?
Did not work. I think we can safely say whatever variant I have, a pre marshmellow bootloader will never load.
R-T-B said:
Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
Click to expand...
Click to collapse
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------
SofaSpud said:
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
My device shows a mfr date of 10/26/15. Settings/about identifies as Rev 1.0, don't see any model reference numbers with "ks" suffix.
Sent from my LG-D801 using Tapatalk
I wouldn't advise disassembly to check for the markings unless you've already voided your warranty for some reason, but thank you for thinking of me and looking around your phone.
My advice to you would be to start by poking around the forums and looking up how to do a 10B TOT revert. You'll need the TOT file, and a .dll to go with it most likely. This is the safest way (if it works) to revert to firmware where you can get (and keep) root.
R-T-B said:
I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.
Click to expand...
Click to collapse
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
roirraW "edor" ehT said:
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
Click to expand...
Click to collapse
Yes, I recovered, but it was complicated.
First off, I had to use a modified version of BoardDiag (I can upload this if anyone needs it, but I'm unsure as to it's legal status) with the qualcomm drivers and testpoint shorted. Second, I had to reflash the 47A files via that method, anything lower than 46A will brick it again.
All in all, it's pretty messy to recover from what I did, but I was confident enough that I've probably done it 4 times now... unfortunately all without success reaching anything below 46A. Even a 35B flash bricks it.
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
SofaSpud said:
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
Click to expand...
Click to collapse
Interesting. What's the "K" mean then?
R-T-B said:
Interesting. What's the "K" mean then?
Click to expand...
Click to collapse
Good question! After reading your posts I looked around a bit for info re the 'k' but didn't find much.
I have yet to root (or even carrier activate) mine. I just received the Totalwireless similar today, but am thinking that perhaps I shouldn't activate until after rooting and disabling OTA, in hopes of avoiding further lock down against rollback. Device is rollback level 2, FW 47A.
Sent from my LG-D801 using Tapatalk

Bought A Mint Cond. VS98510B

I was really lucky to be able to snag a G3 like that. It's for my wife who presently has a basic phone on VzW. I rooted the phone and unlocked the bootloader, installed TWRP and did a nandroid backup after I set up all the apps, contacts, etc. that she'll need. Today the SIM arrived from Vz and it wouldn't activate. I had to call the number provided and they were able to get it activated. But, unfortunately, it immediately started to download a software upgrade which I couldn't stop. It's sitting there waiting for me to select install now or
later. My question is, what can I do to make sure I retain root and all the setup I've done on it? Can I erase the download and, if so, where can I find its storage location?
I guess that if you are root you can always remove the Update Center, is the VS985 a good one, I have a D851 but I see there are some VS985 on ebay, just curious if the Verizon ROM is not full of bloatware.
I managed to get out of the TWRP bootloop I eventually wound up in due to stupid stuff I tried to prevent the OTA. I also managed to retain root and the Kitkat OS. I plan to eliminate the Vz and LG bloat by installing Skydragom ROM that I loved on my old G3. I'll do that in a week or so. I currently use an LG US996 Unlocked and rooted but I still love the G3. Mint ones are hard to find and ones with stock 4.4.2 version OS even more difficult - but worth the premium price. Good luck!
PhoneBill said:
I managed to get out of the TWRP bootloop I eventually wound up in due to stupid stuff I tried to prevent the OTA. I also managed to retain root and the Kitkat OS. I plan to eliminate the Vz and LG bloat by installing Skydragom ROM that I loved on my old G3. I'll do that in a week or so. I currently use an LG US996 Unlocked and rooted but I still love the G3. Mint ones are hard to find and ones with stock 4.4.2 version OS even more difficult - but worth the premium price. Good luck!
Click to expand...
Click to collapse
I actually had one that I kept on 4.4.2 but I used it for the first time in a long time, put my SIM card in and it downloaded the software. I just kept ignoring the installation notification. Couple days later My seven-year-old installed it! Now my phone is bricked. Is there no going back to 4.4.2 I guess?
I had a mint G3 up until the other week when I broke the digitizer (not the LCD, just the touchscreen) on a roller coaster (lap bar). I jumped to the LG V30 and am, at this point, kind of happy that I broke my screen. The camera + screen time on the v30 are just mind bogglingly better than the G3 was. Amazing what skipping ahead like 7 generations of phones does for the libido! (G4, G5, G6, G7, V10, V20, V30)

Categories

Resources