Database Users

[STOCK] VERIZON Nexus 6 [5.1][LMY47E] Firmware Image

For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.

So the difference in between whats out there and this is? I'm curious as the build is different.

coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.

Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app

Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.

Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.

Well no worries this all but confirms vzw is rootable and unlockable

Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx

Is there a rooted version??

Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition

Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.

Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?

How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat

mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).

Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!

mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?

elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:

mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA

Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone

Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?

Bootloader unlocked warning (on boot)

Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks

ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.

just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
It really doesn't matter. I just would like a cleaner boot cycle. Plus I know the MXPE is able to remove this warning.

There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.

fury683 said:
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
Click to expand...
Click to collapse
what do you mean? My warning is in orange.

collinjm01 said:
what do you mean? My warning is in orange.
Click to expand...
Click to collapse
http://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/

ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
.
After reading info on Android Security in this link you should know more about Verified Boot.
.
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
.
.
Techie info about SafetyNet anti-tamper detection here.
https://koz.io/inside-safetynet/
.
Interesting reading about what info Google is now able to pull from youe device.

It's an eyesore no doubt about it but I hardly reboot so it's somewhat bearable.

^^^ why did you bump a thread that died November 11 :lol:

Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.

sn0warmy said:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
Click to expand...
Click to collapse
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.

j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Click to expand...
Click to collapse
Thanks for this update! Will look forward to seeing you post back...while it's not life or death to me it is a rather silly and pointless message by the 100th time I've seen it lol so I would disable it in a heartbeat if I could

just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
No? How about Ya there should be maybe the cause they have a remove mod for the 5x over in the 5x XDA side.
Maybe the same process cause I wondered this question myself
Sent from my Nexus 6P using XDA Free mobile app

j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
Click to expand...
Click to collapse
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.

You need a custom bootloader to remove this. No kernel will take care of it for you. The warning message is within the bootloader.img. The 5x and the 6p are completely different phones. Regardless of the fact that they are both Nexus devices. What works for one will not necessarily work for the other.
Sent from my XT1080 using Tapatalk

Yeah, I've been quickly discovering that over the past 2 days. Very different phones indeed.

bouchigo said:
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
Click to expand...
Click to collapse
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app

androidddaaron said:
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I tried it earlier in the morning, and no go. I believe the /imgdata partition does not exist in the N6P, that's most likely why it was commented out from fstab.
Sent from my Nexus 6P using Tapatalk

SyCreed said:
hey guys i don't want to open a new topic cuz i think it's related here -
If i go back to fully stock, and re-lock the bootloader + factory reset after those operation, no one actually can know if the device was rooted or unlocked right?
Click to expand...
Click to collapse
Correct, if you do that it will be like out of the box.

Untouched 6.0.1 for boost/sprint/virginmobile

Its actually only 6.0 oops didn't look
If you are getting Error 7 Restore the stock system.img and it will flash
this is being uploaded i will have it up by the end of this day 1/4/2016
Update.zip file found here - Google Drive
when of course i get it fully uploaded
So if you have any questions or comments feel free to email me at [email protected] or text me at 5418870575 I do have school since I'm only 16 but will get to you asap
Me and 6th_Hokage think that the bootloaders completely locked because of the messages that the terminal gives system.img is unavailable because of this reason
Instructions
Step 1: Download the zip to your sdcard.
Step 2: Boot your phone into recovery mode by turning off your phone then holding the power and down volume button at the same time. Holdthese buttons until you see the recovery mode screen
Step 3: Navigate the menu by using the up and down volume buttons. Push the down volume button until you reach Update using sd card" It should be the last selection on the menu,
Step 4: Select this option by pressing the power button Once Step
5: Install the zip by selecting the update.zip.
Step 6: Let the install run(total time took about 15 minutes for me)
Step 7: Reboot the phone.
Your done.
I can't pull the system img I already posted what I was getting trying to pull it - bootloaders completely locked no way of bypassing it so far
Want to watch some tutorials on how to install the stock zv4 or zv5 come on by to my YouTube channel - Dominic Gresham

Ok ill say it... What the hell is this? Where did it come from?

Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.

jmacie said:
Since Boost has already started OTA, I imagine Dominic is capturing and preparing to upload it for us.
Click to expand...
Click to collapse
exactly i will also have a youtube video showing up soon enough

Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.

kcarden said:
Ok ill say it... What the hell is this? Where did it come from?
Click to expand...
Click to collapse
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one

DominicGresham said:
boost mobile a week ago said that marshmallow 6.0 was coming out for the phone im half way uploaded it should be up vary soon maybe like another 20 minutes but i did run into some issues when capturing the system.img
here i have attached a image of the error that i get and its a weird one
Click to expand...
Click to collapse
thanks 6th_Hokage again for the commands

br0adband said:
Well it should be 6.0.1 because that's what ZV7 is so so so... get some kind of confirmation on it 'cause I'm pretty sure there's no 6.0.0 for our CDMA devices.
Click to expand...
Click to collapse
ya it is 6.0 thats the android version

Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.

Is this for the sprint lg stylo too thx

i instaled update.zip i put in sd card recovery and install beware they stuck in update system image long time but they instaled fine

Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!

br0adband said:
Well that ain't right, geez, guess they'll have to push another update at some point to get that .1 happening. Bleh, I'm selling my Stylo this morning anyway so I guess I'm pretty much done with them till I can find a good deal on a T-Mobile model, the 1GB of RAM just ain't workable for me.
Click to expand...
Click to collapse
You must be new to the whole Android thing

add​
jmacie said:
Thanks Dominic! and also [email protected] for preparing me to be patient for the update to install. Looking forward for the root solution Dominic, Thanks again!
Click to expand...
Click to collapse
thanks and work great is less lagging and more fast response

the one thing we now have to work on is root for 6.0 and pulling the system.img i can look into the international G3 forums to see how they did it
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
mike9976 said:
Is this for the sprint lg stylo too thx
Click to expand...
Click to collapse
should work an technically you should've gotten it first ._.

Where is the option to adopt sd card??
I did the update through recovery and the only thing i can't seemed to find is how to make sd card adoptable on my lg stylo??

Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...

Anyone with root able to uninstall root and install update yet?
Either with simple unroot or factory reset

Blu8 said:
Hey guys two quick questions, first the download seems to not be working, maybe uploading it someplace else would alleviate that. Secondly, doesn't booting into recovery force you to do a factory reset? If anyone that already flashed can clear that up I'd be grateful...
Click to expand...
Click to collapse
Blu8, I just re-dwnld's it went a 8,5 MB/s, that's my max ( downl'd to my PC, then transferred to my SD) and it was fine. So I don't know. Some guys on the facebook stylo page just now were having problems straight dwnloading to their phone, so I don't really know.
Kolma- I used the Un-root and un-brick-xda- http://forum.xda-developers.com/android/development/official-boost-lg-g-stylo-unbrick-guide-t3215198
then I used Dominic's update.zip in his OP on the first page and it all went fine. It took a bit of time to check, extract and install, so be patient, but it went fine for me. Good Luck!

This is Edwin bro lol thanks again
Sent from my LGMS631 using Tapatalk

[WARNING] Flag for unlocked bootloader

This I just an alert for anyone who is thinking about unlocking their bootloader. I wish I was warned about this before doing mine which ended up being ok but could potentially cause issues for people. Once you decide to unlock the bootloader you will permanently have a thrown flag at boot up which states your bootloader is unlocked. If you decide to relock your bootloader you will have a flag thrown that says your device may be corrupt... This is important because of your try to return your device at the store the employees will know it has been tampered with... Just so you know.
tApPeD fROM mY nExUs 6

Really when I relock and make mine stock again it doesn't do that. If you don't mind me asking what variant do you have?

I'm betting they'll find a way to mask that flag once things really get cracking around here. The proverbial floodgates have been opened!

jameslapc2 said:
Really when I relock and make mine stock again it doesn't do that. If you don't mind me asking what variant do you have?
Click to expand...
Click to collapse
H918 T-MOBILE
tApPeD fROM mY nExUs 6

andrewjt19 said:
H918 T-MOBILE
tApPeD fROM mY nExUs 6
Click to expand...
Click to collapse
This is not true, I factory reset mine and relocked the bootloader for an exchange when my loudspeaker died, after that it booted just like new. On T-Mobile h918
Common sense isn't all that common

ZDeuce2 said:
This is not true, I factory reset mine and relocked the bootloader for an exchange when my loudspeaker died, after that it booted just like new. On T-Mobile h918
Common sense isn't all that common
Click to expand...
Click to collapse
Well maybe you can offer some insight on how to do that instead of just criticizing. Pardon me if I'm reading that wrong but that's what your reply sounds like. This is the guide I used to go back to stock. Afterwards I tried to flash the stock recovery which failed or so I believe and then relocked the bootloader in fastboot mode. I still had a flag... How did your do it, if you will please.

andrewjt19 said:
Well maybe you can offer some insight on how to do that instead of just criticizing. Pardon me if I'm reading that wrong but that's what your reply sounds like. This is the guide I used to go back to stock. Afterwards I tried to flash the stock recovery which failed or so I believe and then relocked the bootloader in fastboot mode. I still had a flag... How did your do it, if you will please.
Click to expand...
Click to collapse
It's not a criticism, I removed root, in adb I did oem bootloader lock. It reset data, which in turn turned off developer options, resetting the oem unlock switch. Rebooted, and no security warning. I didn't bother flashing stock firmware, just unrooted, and relocked the bootloader in adb, That is all
Common sense isn't all that common
---------- Post added at 11:42 PM ---------- Previous post was at 11:35 PM ----------
Sorry you took my post as being critical, that wasn't my intention, I was just simply stating that I was able to remove the secure boot message, although T-Mobile didn't even check, I told them I had so ready backed everything to my SD card and reset. They just pulled the battery, sim, and SD card, stuck them in my new one, made sure my Google account loaded, and I walked out the door.
Common sense isn't all that common

ZDeuce2 said:
It's not a criticism, I removed root, in adb I did oem bootloader lock. It reset data, which in turn turned off developer options, resetting the oem unlock switch. Rebooted, and no security warning. I didn't bother flashing stock firmware, just unrooted, and relocked the bootloader in adb, That is all
Common sense isn't all that common
---------- Post added at 11:42 PM ---------- Previous post was at 11:35 PM ----------
Sorry you took my post as being critical, that wasn't my intention, I was just simply stating that I was able to remove the secure boot message, although T-Mobile didn't even check, I told them I had so ready backed everything to my SD card and reset. They just pulled the battery, sim, and SD card, stuck them in my new one, made sure my Google account loaded, and I walked out the door.
Common sense isn't all that common
Click to expand...
Click to collapse
Good to know. Although I tried those steps it still didn't take away the flag. But I suppose I did something wrong... Thanks for your input.
tApPeD fROM mY nExUs 6

funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.

dimm0k said:
funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.
Click to expand...
Click to collapse
I traded in my v10 still rooted, no question asked... And returned my first v20 for a blown speaker, it was rooted when I took it in, I did restored to to unrooted and looked the bootloader for the return, mainly to see if it fixed the speaker. But in all the years I've had T-Mobile, that is the first time I've returned a phone stock... No one has ever said anything about it.
Common sense isn't all that common

Yeah with sprint currently and I've returned rooted HTC 10, rooted note 4, rooted htc m8, and no questions ever.
Beastmode on my LG V20

dimm0k said:
funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.
Click to expand...
Click to collapse
Wow, thats funny. Im glad you had that luck. Idk that id be so lucky, but that made for good story.

I found a couple posts which were terse but sent me on the right path it seems. For others here is what I did:
1. Removed all of my accounts in the Settings.
2. Made sure USB debugging enabled.
3. Booted into download mode (hold volume down whilst inserting USB cable.
4. Fired up uppercut (being sure to disable A/V program first). Sees the device on a com port.
5. Loaded the 10p kdz, checked upgrade, and let her rip.
6. Device rebooted showing my apps and stuff. But no root any longer.
7. Factory reset the device.
8. Went through just enough of the setup to enable developer mode and USB debugging.
9. Note that OEM unlock is still on.
10. Did the following variation on what is shown in the first post of this thread <https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258>:
* adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
* adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
* fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
* fastboot getvar unlocked ----->THIS CONFIRMS THE BOOTLOADER HAS BEEN LOCKED
* fastboot oem lock---->THIS COMMAND WOULD LOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
* fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN RE-LOCKED
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
11. Device now boots without warnings and into stock Android welcome screen.
BTW - when doing anything like this with a device I always recommend that (a) use USB 2 port, not later, and (b) be sure to use a USB port that is on the computer's motherboard.

Stuck on twerp read only ...with lock

Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?

back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...

pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk

First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!