Database Info

Looking for ROMs for LG VS890/FX3

Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.

I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.

UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.

Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).

UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.

Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.

UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.

It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .

Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.

UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
I did as you said, but I'm still on 4.1.2:crying:

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

[H915] Root Guide + Restore Any Bricked LG V20

Just in Time for The New Year I would like to show Everyone How to root there Canadian variant LG V20!
Current Known issues
- No Service From Carrier
- Seems VERY Laggy (Can be Fixed with using a Kernel)
Other Information
- Yes you can Restore to factory Settings with this Method (So Don't worry if you screw up)
- Sorry far I Only know This works on the H915 however the Restore should work with all LG Models
- This will give you a Bootloader to have access to fastboot Commands
- Working TWRP Recovery
So After Reading the No Service Part many are mostly not going to be interested... I uploaded this Thread anyway to see if anyone could find a fix to this issue. (When one is found I will update this with the fix)
So If you still want to Root your Canadian LG V20 Let's do it!
DOWNLOAD THE ZIP FILE HERE
https://mega.nz/#!ABZV0AZZ!8LBGgpjiGT1ij6scshWTQO4tGhUb9GMUcTHtKLLhfW0
- I DO NOT TAKE ANY RESPONSIBILITY FOR YOU BREAKING YOUR DEVICE
- I HAVE NOT CREATED ANY OF THESE FILES I ONLY PUT EVERYTHING INTO ZIP FOLDER FOR YOU TO DOWNLOAD AND MAKE THINGS CONVENIENT AND SIMPLE
- PLEASE THANK THE ACTUAL DEVELOPERS WHO CREATED THESE FILES (LISTED BELOW)
FILES USED/THANK THESE PEOPLE
@me2151 Dirty Santa Files (Boot2.img, Step 1.bat, Step 2.bat and RUNMEFIRST.bat) -
HTML:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
@jcadduono recowvery and dirtycow exploit (used with Dirty Santa)
HTML:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Stock Images for LG V20 H915 you can find those here
HTML:
http://lg-firmwares.com/lg-h915-firmwares/
(You will need to be flashed on H91510d for this to work however you could try 10e if you wanted)
@autoprime UPPERCUT for LGUP (This is what allows the LG V20 to be read and will allow you to downgrade to 10d if needed and will let you restore to stock using Download Mode at any time! This will only be used for you if you mess up with the root and need to flash back to stock or you need to upgrade or downgrade to the 10d firmware)
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
@Chainfire SuperSu v2.79 SR1
HTML:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
WHAT DO YOU NEED BEFORE YOU START
- A Copy of LGUP
- An LG V20 H915 Running the 10d Firmware (if you need help flashing this firmware read below before Step 1)
- The Zip File I Listed above to Download
- ADB and LG Drivers
- A Windows Computer
HOW TO UPGRADE/DOWNGRADE TO FIRMWARE VERSION 10d
Step 1 - Boot Your Device into Download Mode (Turn the phone off hold the Vol + Button and plug in your device to the Computer)
Step 2 - On your Computer find the Zip File (extract it) and Open Uppercut.exe (This should launch LGUP and Make sure your Phone is Connected to your Computer)
Step 3 - In LGUP Select the Upgrade button (even if you are downgrading it will still work) then find the Firmware .kdz file for 10d
Step 4 - Flash the KDZ back onto your device
ROOTING THE DEVICE!
Step 1 - Install a Terminal Emulator App to your Device
Step 2 - Verify your device is plugged in and that ADB sees the Device (adb devices)
Step 3 - On your Computer Open the RUNMEFIRST.bat (do not close this window)
Step 4 - After loading up RUNMEFIRST.bat run Step1.bat (if you see permission denied on the files Flatland and Flatland64 this is normal)
Step 5 - Once the shell prompt opens in the step 1.bat window type "run-as con" (without quotations then hit enter) then type "chmod 0777 /storage/emulated/0/*" (yet again not in quotations and then hit enter)
Step 6 - Once that has finished on your phone open the Terminal app you downloaded earlier and type in id (if untrusted_app is displayed continue if not redo the steps)
Step 7 - In the Terminal Emulator type applypatch /system/bin/atd /storage/emulated/0/dirtysanta then watch the RUNMEFIRST.bat to see when it tells u to open Step2.bat (when it tells u to open Step2.bat open it)
Step 8 - You should now Be into a Somewhat usable bootloader on your device... now we Stop using DirySanta and Start to do things manually by ourselves open up a Command Prompt and type "fastboot flash boot boot.img" this will flash the boot2.img used in the Dirty Santa Exploit
Step 9 - After that finishes type "fastboot flash recovery TWRP.img" This will put TWRP (For the H918 Variant) on your device
Step 10 - Boot into TWRP (Remove battery then put it back in hold the Vol - Button and the Power Button Once LG Powered by Android Logo Appears Release the Power Button then Hold it Again, A White screen should come up say yes to both screens then should boot into TWRP)
Step 11 - Now that you are this far I recommend you backup everything so that you can start from this point if you mess up any upcoming steps that way you do not have to reflash the stock image and start from step 1 again....
Step 12 - Select Wipe from the Main menu then go to Format Data then type yes and enter (This will remove the password lock currently enabled on the device)
Step 13 - On the Main Menu select Install browse to your SD Card where you put your SuperSU.zip File onto and flash that to the device
Step 14 - Once that is completed return to the main menu select the Wipe menu again go to Format Data then yes again
Step 15 - Go back to the Wipe Menu and go to Advanced and select Dalvik, Data and Cache then slide to wipe after this finishes reboot to the system
Step 16 - Once in the System complete the Android setup and enable USB Debugging again then type adb reboot recovery (if your device does not boot into Android this is when u go back into TWRP by doing the remove battery method and holding those buttons down as I stated before and you Restore your Backup you made in Step 11 and you try doing those Steps again)
Step 17 - Once Back into TWRP (you may make another backup here if you would like) select Install then Flash SuperSU to your device again... Go back to the Main Menu Select Wipe then Advanced and Select Dalvik and Cache then Slide to Wipe and reboot into the System
Step 18 - Once back into Android you should see SuperSU on your device and you may download a Root Checker app of the Play Store to Make sure your Device is Fully Rooted and Working!
Please inform any Issues in the Replies below and I will add them to the List for People to Know before they Attempt rooting... If anyone finds a Fix for the Modem file to get service working on the LG V20 H915 while rooted please reply and i will Add that to the guide BELOW!
I DID NOT MAKE ANY OF THESE FILES SO PLEASE THANK THE CREATORS (LISTED ABOVE) FOR THEIR HARD WORK AND EFFORTS!
I THINK I BRICKED MY DEVICE/ THE ROOT DID NOT WORK/ I WANT TO GO BACK TO STOCK
Step 1 - As Stated Above to this all we need to do is Enter Download Mode (Remove Battery reinsert battery hold Vol + and plug in the Device) and then run the UPPERCUT.exe File
Step 2 - Select Upgrade browse over to your kdz file and select it then flash it to your device! Your Device Should boot up into Android (I Have Bricked my LG V20 Many Times Removing TWRP and the Bootloader and having nothing but the LG Logo and the Download Mode and I could Still get into the Device after doing this so it should work for you! However any problems should be dealt with the developer on his forum listed here
HTML:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
)
Anyone willing to Try installing things like Kernels and ROMs I would assume you would be using H918 Supported Files For those as thats what TWRP is running in.....

Will be adding a Zip File will all the Files need in a Couple of Minutes....

There seems to be a hidden settings menu on our Devices in which we can play around with the Modem Settings among other things.... you need to open the Phone App and Type in *#546368#*915# and the menu should come up.... Maybe somebody can figure out how to get Service running.... All Credit for this goes to @KedarWolf in his post listed here https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098

Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet

markbencze said:
Nice little write up. Did you try this on the wind/freedom 915 or videotron 915? My guess would be that you tried it on the wind 915 and if so i bet it has something to do with their slightly differnet bands they use albeit for a change an unlocked wind device works fine on other networks. But i really have no clue if there's a connection on why there's no signal. This kind of thing is beyond my pay grade. I would be guessing someone like @autoprime would be someone to ask but chances are he has other things to worry about and likely doesn't have the device.
But keep plugging away. You may figure it out yet
Click to expand...
Click to collapse
Yes the Wind H915 still haven't got it figured out yet hopefully someone will soon then we will have an official working root for the Canadian Variant

I would have jumped on the Freedom Mobile (formerly Wind) deal ($30 for 6GB for the first 10 months) if the H915 had been root and has an unlocked bootloader. LG's track record of offering unlocked bootloader is looking very bleak for the H915.

@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.

Emilius said:
@TheDantee I am sure the service issue will be resolved soon but "Seems VERY Laggy" part is worrying me more. What is the reason for that? I like the possibility to go to the default LG rom like nothing happen.
Click to expand...
Click to collapse
Sorry i should mention that a Kernel fixed this issue for me!

TheDantee said:
Sorry i should mention that a Kernel fixed this issue for me!
Click to expand...
Click to collapse
Service issue or laggy part?

Emilius said:
Service issue or laggy part?
Click to expand...
Click to collapse
Laggy Part

Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,

SHABBA JOTS said:
Noob question, is the phone fully functional after step 10 (TWRP).
The reason I ask is because I really only need to get to TWRP as I want to enable google assistant.
At this point, the root is not a big concern for me.
Thanks,
Click to expand...
Click to collapse
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....

TheDantee said:
Shoulbe be but you will need to still do a format on the device or you will get locked out and it will ask for a passcode....
Click to expand...
Click to collapse
So SuperSU messed the service reception? Not bootloader?

Emilius said:
So SuperSU messed the service reception? Not bootloader?
Click to expand...
Click to collapse
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?

TheDantee said:
I don't think its SuperSU Causing the problem... In the bootloader (debug) that is provided in the DirtySanta root it states the device as an unlocked US996 LG V20 I feel that this is because it has no idea which provider its with since we are Canadian.. I have tried flashing many many modem files from many different firmwares I either get modem blue screens on boot (Goes away permanently if you remove sim card) or I get no Service in the System it self... so personally I think it is the Bootloader since its a debug bootloader because the Canadian Variant does not seem to have a bootloader.... May I ask what is your reasoning for SuperSU being the issue?
Click to expand...
Click to collapse
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?

Emilius said:
Based on your answer to SHABBA JOTS I get feeling that maybe is SuperSU creating that problem if until step 10 (TWRP) is all good. So soon we do step 8 (flashing boot image) service is gone. Is that right?
Click to expand...
Click to collapse
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol

TheDantee said:
Currently I have no access to my V20 so i can not try and tell you but if you are willing to reset and try the steps again up to Step 8 then lemme know the answer... however the system is very very very unstable many crashes tons of lag massive downgrade in battery without that boot.img... what if u flash twrp once in the bootloader but not the boot.img try that.... then get back to me Curious now lol
Click to expand...
Click to collapse
He he, I am an Nexus person. I am so afraid to mess up my V20. With Nexus it is so easy, in 2 steps you are done. I miss that part I mast say.

Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?

markbencze said:
Ok so i gave this a quick read and from what i gather you flash the bootloader before you flash twrp and super su. So here's a question that may or may not have been tried. Is there any reason you can't follow this method to root and then flash stock recovery and then flash stock bootloader?
Since it seems bootloader is the issue with having no data or signal. You would at least have root but just not twrp. Does that make sense?
Click to expand...
Click to collapse
It's look like H915 dues not have bootloader at all.

Emilius said:
It's look like H915 dues not have bootloader at all.
Click to expand...
Click to collapse
Well it has to have a bootloader. It's just locked right. Like if we pulled apart the stock kdz we should be able to find it and my theory is we could use flashfire to flash stock recovery and also flash thr bootloader since twrp can't to my knowledge flash bootloaders. We would be left with root but no recovery. I could be so far from being right but who knows. This could be the only way to have root and a working phone.

I bought a Pixel 2 directly from Google, is it possible Verizon locked my phone?

I bought the original Pixel from Verizon and that was a complete waste. Then the Pixel2 was released, and I bought it online (directly from Google). I've had it for a long while.
The first thing I did was oem unlock and flash twrp, Magisk, and Elemental X. I was running the stock rom and just let all of the updates slip past (updating the kernel of course) and had a few issues so I thought I'd factory reset and update the phone.
But I didn't take the sim card out...
When the phone rebooted it behaved *exactly* like the original Pixel if you had the sim card in. It specifically sets up according to what Verizon wants on the phone.
Now, when I go into the developer settings, the oem unlock is greyed out!!!
Does Verizon lock Pixel phones regardless of its origin?
I'm not completely stupid, this just doesn't make sense... Anyone else have this issue?
Honestly, I didn't think something like that was possible. Can anyone here confirm the hardware is the exact same? Is it possible Verizon signing keys can overwrite default/official Google keys?
Or will the phone behave as normal if I reset without the sim in?
Gonna try it and report back after work (gotta wait another 8 hours or so as of writing this).

Exactly how did you update it, and I mean every step you took?

The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.

allcaps33 said:
The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.
Click to expand...
Click to collapse
USB debugging is only for ADB, and has nothing to do with fastboot commands. When you attempted to run the flash-all script, were you in ADB or bootloader? In ADB it will fail, because it doesn't recognize fastboot commands. However, in the bootloader, if it's not recognizing fastboot commands, that's a whole different animal. OTAs, when it comes to VZW are dangerous, so it's always best to just sideload them via stock recovery. They should come straight from Google, but I'm afraid that something that you did in the entire process broke that.
In all honesty, all you really needed to do was unzip the latest factory image, run the flash-all script while you were still unlocked, and be done with it. The -w in the script would have taken care of the factory reset for you, as it's a full wipe.
Let us know if what you tried worked, and best of luck ?

I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...

An update to this mess:
Still working with known exploits to try and get back to where I was. Looks like I'm gonna have to pull from CVE or ExDB.
Any suggestions from the pros?

allcaps33 said:
I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...
Click to expand...
Click to collapse
I do apologize for underestimating your knowledge. That being said, an OTA can't re-lock the bootloader without permission, as that would completely wipe userdata. And, neither can the presence of a SIM card. I fear that, with everything that you did, as far as getting your phone as clean as possible, you may have put the device in limbo, so to speak, and the OTAs, combined with vzw's penchant for locking bootloaders, may have made it susceptible to becoming a Verizon device. Just a thought.

I totally agree with you.
I'm just completely confused how this happened...
As you said, with an unlocked bootloader, it *might* have been possible that through some kind of bug it may have taken something VZW specific... But... The OTA packages don't actually contain the entire ROM do they?
From what I noticed, they're almost all under 80 MB, while the actual ROM packages are (on average) 1.5 GB.
At what point could this crossover happen?
(The reason I bring up package sizes is that would be the most likely reason for an overwrite... I think...)
Can I probe you for more theories? Out of the box solutions never work, perhaps you might trigger ideas within the community.
Thank you very much @DuckRuckus for your help!
Still to this point attempting anything within fastboot seems to just not work...
I can get "fastboot devices" and "fastboot reboot bootloader" to work. But that's about it. No other commands issued get so as a response.

Getting root on the BNTV460 is a pain....

Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.

Articul8Madness said:
Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.
Click to expand...
Click to collapse
If it is close enough to 450, and you can get into fastboot, you can try and boot the linked boot.img
fastboot boot m19_ST16C7BNv205.img
Same modifications I had to use to get the first boot image I found to work with BNTV450.
avb, mtk type and signature removed.
Also patched with Magisk 19 (canary release)
For good measure.
https://drive.google.com/open?id=1LgtB2JKCKwLJ64mUlij5Cb_cJrBi8Av1
PS.
Tested above modified v2.0.5 boot.img on BNTV450 running v1.0.2, so it should work on BN v1.0.2 and up.
Good Luck.
Cheers.
PPS.
Just ordered one. (Should show up in 2-3 days.)

Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.

Articul8Madness said:
Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.
Click to expand...
Click to collapse
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304

turtleletortue said:
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304
Click to expand...
Click to collapse
I appreciate it, but I've since taken it back. Tell you what though, maybe I'll pick up a used one on ebay and try it