Database Users

New Brazilian firmware

Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!

AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file

waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.

I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards

waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?

Do you have the phone in fastboot mode and connected to your PC while running the BAT file?

xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?

xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go

xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.

Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.

kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?

Anyone else?
[email protected]

xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.

this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...

Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.

Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:

Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?

rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.

LAF NUKER flashable zip

LAF NUKER wipes your Download mode and let you use Fastboot instead.:
Do this on your own responsibility, if you bricked your phone in some weird way then don't look at me.
But with this simple thing you can't brick your phone only if you flashed the wrong zip which wasn't from me.
This is more meant for developers/testers.
Click to expand...
Click to collapse
I was getting irritated that my Fastboot mode dissapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files, so I had to first attempt to get into the rom itself or recovery to wipe it again over and over. So I thought by myself why won't I make something easy and flashable?
This lightweight flashable zip from 2-4KB is tested by me multiple times so after you flashed it I HIGHLYsuggest that you need to test or you can enter download mode and see if it shows now fastboot. If so then everything succeeded like it should, it has an succes rate of 100% as nothing could actually go wrong with this.
This script/method should also work for the G3 and some other LG devices which have this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/laf
For the one's who care the shell script is located in the update-binary, updater-script is just dummy.
If you want to revert back, just flash the jb/kk/lp bootloader files.
Download:
https://docs.google.com/uc?authuser=0&id=0B1u3mnq0nstfZVN1eVQ3bEw5ODQ&export=download
Mirror:
https://www.androidfilehost.com/?fid=23991606952610950
Credits:
Jackpotclavin for the method to get into fastboot mode
Chainfire for the shell updater-script method
osm0sis for the guide about the shell updater-script

wulsic said:
LAF NUKER wipes your Download mode and let you use Fastboot instead.:
I was getting irritated that my Fastboot mode disapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files . . . .
Click to expand...
Click to collapse
My question is somewhat off-topic but I'm having a hard time understanding how bootloaders and ROMs work with the G3.
When I had a G2 I learned about the difference between Kitkat and Lollipop bootloaders the hard way when I tried to restore a Kitkat nandroid backup over stock lollipop and hard bricked the phone. My impression was that since the KK backup did not include a compatible bootloader I needed to flash one or restore to stock KK.
Now you are suggesting that ROMs for the G3 *include* bootloaders, which is news to me. Does this mean I can go back and forth between Kitkat and Lollipop ROMs without worrying about bootloaders? Or restore nandroid backups without the same concern? I don't want to have to downgrade to Kitkat every time I want to try a new ROM or restore a backup.
Thanks.

No most roms don't include bootloaders but some stock roms do, especially in the g2 community as I made this first for G2 but I also found out that it would also work on the G3. I guess g3 is the same as the G2 in terms of flashing. Lollipop stock roms need lollipop bootloader related files to properly boot but the bootloader is from kitkat with the g3 because else bump and flashing doesnt work. Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.

wulsic said:
. . . Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.
Click to expand...
Click to collapse
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.

channeledbymodem said:
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.
Click to expand...
Click to collapse
Well as far as I know the t mobile version has an unlocked bootloader so more freedom for flashers. I also hard bricked my G2 but before I hard bricked it there was a shortening method guide on how to hard unbrick your g2. Could also work on the g3 perhaps. Well that sucks that you needed to pay $45 lets just hope for you that it won't happen again.
If you want 100% clarification about the bootloader and different roms then you might want to ask it in the Q&A or a rom thread as I am a G2 user. But short story as far as I know. Lollipop bootloader related files for lollipop stock roms. And kitkat bootloader related files for custom aosp roms like euphoria cyanogenmod etc.

I don't know if the guy I paid (who fixed it the day he got it so it couldn't have been so hard for him) had to open it to short the pins but after watching a video showing it done I wasn't going to chance it. It was like repairing a watch. Plus I tried the sw method of viewing the borked partitions in Linux and then replacing them but I couldn't see them to replace so I paid for the repair. And I only had the damn phone for a month before I discovered the problem with T-Mobile and sent it back.
I must say the G2 was a *very* finicky device compared to the Optimus G Pro I had before. And that phone never worked properly with any AOSP ROM. I don't know why I'm so loyal to LG. Must be because the phones are cheaper and I really don't like Samsung any more.
Of course the Verizon Motorola Droid Ultra I bought for my wife used is even worse. It's completely locked down. You can't root Lollipop on it and you can't downgrade to Kitkat once you've taken the OTA update.
Until somebody can explain switching ROMs on the G3 to me like I'm five I think I'm just going to always go back to stock Kitkat, re-root and re-install TWRP. Seems the safest thing to do.

[Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files

Question: "How/When can I root Marshmallow?
Answer: "NO ROOT ON MARSHMALLOW"
Send me a PM with updates so I can incorporate them into the main post.
Tools & Drivers :
Make sure you have the right tools for the job!
LG Flash Tool
Windows specific:
Windows Drivers
LG Bridge for Windows ***NOT REQUIRED BUT HANDY***
Mac specific:
Mac Drivers
LG Bridge for Mac ***NOT REQUIRED BUT HANDY***
How To Root:
Start here and read both threads over twice if you are new to the process. There are the main guides used to achieve root
Original Root Method for the LG G4 - @thecubed Give them a Thanks!
DIY Root Injection Guide - @hackarchive Give them a Thanks!
Rooted System Images:
NEVER MISMATCH SOFTWARE VERSIONS AS IT COULD RESULT IN A BRICKED DEVICE. Match your phone's software version with the corresponding image
***An H81210x stock KDZ needs to be installed BEFORE flashing the H81210x rooted image. Also note that all carriers are cross compatible (Bell, Rogers, Telus, Wind), however Rogers devices should stick to Rogers images or you will lose VoLTE***
H81210E - @kleedrac Give them a Thanks!
H81210G
H81210N - @anterus Give them a Thanks!
H81210O - @Buddyjohn Give them a Thanks!
Rogers:
H81210H - @GibMcFragger Give them a Thanks!
H81210N - @nabbasi Give them a Thanks!
Stock KDZ's:
Used to remove root or for any other issues. Downgrade/Upgrade using these KDZ's. 10x for Lollipop and 20x for Marshmallow
Canadian DevTester Firmwares. Most KDZ's can be found here.
H81210N
Rogers:
H81210H - @Jok3r10 Give them a Thanks!
H81220E
Virtual Machine Linux Using VirtualBox:
How to inject root if you do not have a designated Linux machine. Pictures included in the step numbers!
Configuring VirtualBox:
1. Download, install and run VirtualBox
2. Create a new virtual machine. Abbreviated to VM from here on out.
3. Select your preferred distribution of Linux. I chose Ubuntu as I find it to be the most user friendly experience.
4. Designate preferred amount of RAM for the VM. Slide the arrow to adjust, but stay in the green to avoid complications.
5. Create a virtual disk for Linux to be installed onto.
6. Choose VirtualBox Disk Image to keep things simple.
7. Choose Fixed size for the storage on the physical disk.
8. Choose amount of storage and create. 8 gigabytes should be plenty as you can share folders, which we will do later on.
9. Download your preferred version of Linux, or Ubuntu in my case. I placed it into the VirtualBox folder for ease of access.
10. Run the Linux VM and chose the previously downloaded system image for the start up disk.
You should now be able to boot up a Linux VM to use to inject root into system images with! Just finish the installation process like you would a new computer.
Some tips:
If you followed the guide using Ubuntu, choose to fully install it, do not worry about the warning under erase disk and install Ubuntu, that only applies to the drive we just created and it wont erase anything.
Host key is the CTRL key on the right side of the keyboard, use that for hotkeys as the left one will have no effect.
HostCTRL + F is the full screen shortcut.
Sharing Folders:
1. In the VirtualBox window, click the device setting and choose Insert Guest Additions CD Image and run the program. Enter in your password you chose while setting up Ubuntu. It will install and once it is done you can restart the VM by clicking the gear in the top right corner.
2./2.5 Open the device settings again and go to the shared folder settings. Click the blue folder with the green plus and chose the file you wish to share and what you want to name it. I chose the entire C: drive to make everything easier. Select auto mount it and make it permanent.
3. Open up Files and create a destination for the shared folder simply by right clicking in Files and create new folder.
4. CTRL + ALT + T to open a new terminal and type in
Code:
sudo mount -t vboxsf FOLDERNAME /PATH/OF/FOLDER
Input your password after running the command, hit enter and the folders should be shared.
Installing Xposed Framework:
Utilize your device to the full potential. 110%
Guide to getting Xposed Framework fully functional - @tabp0le Give them a Thanks!

Reserved, thanks!

I'm downloading your 10G rooted image. I have 10E on my Bell G4. What would be the procedure to flash your image on my phone?

Sweet. Now we can finally get a proper thread going with all our resources on the first page. This will make the process so much quicker for the new comers

defender007 said:
I'm downloading your 10G rooted image. I have 10E on my Bell G4. What would be the procedure to flash your image on my phone?
Click to expand...
Click to collapse
Please do not flash the 10G rooted system image over you 10E G4! It states in the highlighted red text not to do so. I appologize if that was unclear. I am trying to compile all of the nessessary information into the first post and as you can imagine, it is a lot of work. I am actively working with my G4 but have only started doing so since the 10G update so I do not have any files other than the image I had rooted myself.
The DIY root injection guide found in my first post and in this quote is exactly how I injected root myself into my own system image. I've also wrote up a guide on how to install a linux virtual machine so you can do it yourself if you do not have linux machine.
Alternatively, if you can upload your 10E system image, I will gladly download it and inject root myself and have it uploaded into the main post.
spartan268 said:
Sweet. Now we can finally get a proper thread going with all our resources on the first page. This will make the process so much quicker for the new comers
Click to expand...
Click to collapse
That is the goal! If you have anything to contribute, please do as this will take a community effort.
Thanks guys!

Thanks for the response. So how can I flash a 10G file and root at the same time? Or should I just root what I have and hope Bell wakes up and releases the update?

defender007 said:
Thanks for the response. So how can I flash a 10G file and root at the same time? Or should I just root what I have and hope Bell wakes up and releases the update?
Click to expand...
Click to collapse
You do not flash a rooted image unless it matches the software version of your device. You need to find a rooted 10E image or inject root into your own ripped system image from your device. I currently do not have a 10E system image. If you supply me with your 10E system image, I can inject root into it for you if you cannot do it yourself. The steps to root your phone yourself are found here in this guide.
I am trying to find one right now.

Spudnubs said:
You do not flash a rooted image unless it matches the software version of your device. You need to find a rooted 10E image or inject root into your own ripped system image from your device. I currently do not have a 10E system image. If you supply me with your 10E system image, I can inject root into it for you if you cannot do it yourself. The steps to root your phone yourself are found here in this guide.
I am trying to find one right now.
Click to expand...
Click to collapse
Could he not flash the Telus 10G KDZ on his phone and then flash the 10G rooted system image you posted on his phone? I thought we found out that you could any carrier's KDZ on the Canadian LG G4s? (he would just have to manually input his APN afterwards)

eboy_gb said:
Could he not flash the Telus 10G KDZ on his phone and then flash the 10G rooted system image you posted on his phone? I thought we found out that you could any carrier's KDZ on the Canadian LG G4s? (he would just have to manually input his APN afterwards)
Click to expand...
Click to collapse
You can flash any Canadian H812 KDZ or system image on ANY Canadian H812, regardless of carrier.
It is recommended to flash the full KDZ first though if the version is different that what you are already running, to prevent issues.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
Rogers 10h rooted system image link, for your OP.
https://drive.google.com/open?id=0B-dYQXNfPs7UZUo4SjQxY1FiMUE

I already have the full KDZ file. So all i do is flash that then flash the rooted image, correct?

defender007 said:
I already have the full KDZ file. So all i do is flash that then flash the rooted image, correct?
Click to expand...
Click to collapse
Yes sir. Always triple check all of your files match the device also.

Love that this was decided on. The orphaned thread was a minefield for the new folks here.
In the OP, perhaps give an example of what kdz you are using and what rooted image is compatible...good for you for putting the warning in red, but I would emphasize again. Here is how I would make the post look:
------------
Rooted System Images:
NEVER MISMATCH SOFTWARE VERSIONS AS IT COULD RESULT IN A BRICKED DEVICE. Match your phone's software version with the corresponding image **ie. A Telus H81210H stock image needs to be fully installed BEFORE flashing the Telus H81210H rooted image. Also note that a Telus KDZ is compatible with a Bell, Rogers, etc. device. Just make sure that if you use a Telus KDZ, you flash the Telus rooted image**
H81210G
H81210H - Thank you @GibMcFragger
----------

chriskwarren said:
Love that this was decided on. The orphaned thread was a minefield for the new folks here.
In the OP, perhaps give an example of what kdz you are using and what rooted image is compatible...good for you for putting the warning in red, but I would emphasize again. Here is how I would make the post look:
------------
Rooted System Images:
NEVER MISMATCH SOFTWARE VERSIONS AS IT COULD RESULT IN A BRICKED DEVICE. Match your phone's software version with the corresponding image **ie. A Telus H81210H stock image needs to be fully installed BEFORE flashing the Telus H81210H rooted image. Also note that a Telus KDZ is compatible with a Bell, Rogers, etc. device. Just make sure that if you use a Telus KDZ, you flash the Telus rooted image**
H81210G
H81210H - Thank you @GibMcFragger
----------
Click to expand...
Click to collapse
Awesome, Chris! I will add this as I fully agree with everything you said and was wondering myself on how exactly to add this into the main post as it seems to be a problem issue with many users.

Spudnubs said:
Awesome, Chris! I will add this as I fully agree with everything you said and was wondering myself on how exactly to add this into the main post as it seems to be a problem issue with many users.
Click to expand...
Click to collapse
Awesome
Tyfoxx
Sent from my LG-H812 using XDA Premium HD app

Stupid question, how do I flash this phone?

Read the first post

I see that the 10G OTA is out for Wind, but Rogers already has the 10H.
Anyone know the difference? I am currently on 10F.
For the OTA description, it just says usability improvements through Google patch.

So there is a YouTube video of the Korean model G4 with twrp and a locked bootloader.. Hopefully this is the beginning of better things.
Sent from my LG-H812

Jason123420 said:
So there is a YouTube video of the Korean model G4 with twrp and a locked bootloader.. Hopefully this is the beginning of better things.
Sent from my LG-H812
Click to expand...
Click to collapse
What!? Post the link! But not in the Canadian thread, no one will see it here.

phineous said:
What!? Post the link! But not in the Canadian thread, no one will see it here.
Click to expand...
Click to collapse
Check the 'Korean Variant Rooted' thread by vn_mobile here in General. Posted on last page.

Can i flash this H910PR10j_00_1205 firmware to my AT&T H910?

Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?

ssgsunny said:
Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?
Click to expand...
Click to collapse
We need a link to actually see the file.

me2151 said:
We need a link to actually see the file.
Click to expand...
Click to collapse
https://lg-firmwares.com/lg-h910pr-firmwares/#more-4385

What is it for?

Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.

This is a nice way to brick.
Cross-flashing radios, and/or bootloaders = GG

me2151 said:
Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.
Click to expand...
Click to collapse
I tried it and now I am on a island by myself. I got service, made a phone call and got text. It run through about every service possible and then dropped them all!!! It was such a kick in the ballz. Come swim with me the water great!

h910pr
i can confirm i have flashed the h910pr rom to my att h910 and it worked fine for me. stuck on the claro software but its actually better than atts lol. maybe someone could work on this firmware version since we have a kdz of it.

@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?

Not sure.
runningnak3d said:
@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?
Click to expand...
Click to collapse
I was originally on the h910 att firmware, then used dirty santa to open the bootloader and root. I found a rom that i really like and ran fast as heck, but it wouldn't sync with my watch. I tried a factory reset with led me to a twrp boot loop and nothing i did would get me out of it. so i tried to reflash twrp and it led me to a bricked phone that wouldn't power on past the boot loader unlocked notification. After tons of research and a little tweaking to a few things i got lgup to recognize my phone and flash the h910pr kdz to my phone. if anyone needs i can make a zip of the tools i used and post it somewhere.
edit- uploading to mega right now. will post a link in a little bit to a zip with my lgup folder configured exactly as it needed. install lgup2016 and the lg drivers then copy the lgup from this zip over the lgup folder in your programfiles(x86). essentially all you really need here is the lgup_common.dll which is actually just the h918.dll with the name changed. i had read the fccid's on the h910,h910pr and the h918 were the same, which meant by a measurable standard they are the same hardware. so i took the assumption the dlls would be compatable. by pure blind luck with the folder layout as shown in the zip and the kdz included as well it took. i was a little worried because i had read someone tried this and could not get carrier service. i thought id at least make the phone usable in case a fix was found.my phone reports itself as an h910pr now but is connected to the att network with no issues, text, talk and web all work fine as well as att services.

I had checked a while back and saw that the h910 and h918 had the same FCC ID, which, as you stated, means they have to be the same hardware. I am using my h910 on T-Mobile, so now that I know (if it fails for some reason) that I can flash the h910pr KDZ, I am going to try the h918.
Sorry that you almost had a brick, but thanks so much for verifying that this works.

hi to everyone concerned, i have begun monitoring this thread;
https://forum.xda-developers.com/v20/help/lg-v20-h910-kdz-t3612524/page2#post72599368
please direct any inquiry's to my experience there. there is also a link and directions there to restore any bricked lgh910 to the h910pr version, as well as development on using the h915 and h918 firmware.

unlock boot loader US996

Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks

You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com

ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...

Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.

Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?

Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot

Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.

Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link

Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...

Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.

I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...

Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.

Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.

Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.