Related
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接:https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚:g5cg
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
Abandoned War Place said:
FIX REFUBRISH/DOWNGRADE ETC STUCK AT 16% DOWNLOAD MODE UNABLE TO GET BACK TO STOCK
error 0x2000 invalid command response Has Been FixeD WITH THE LASTEST DLL FILE
FILE INCLUDE (DLL+PATCH_DLL+SETUP LGUP+DRIVER) package
Please Read The *READ ME FILE FOR THE RIGHT INSTALLATION WITHOUT GETTING ANY PROBLEM :
Link Easy To Download No Ads Bulllsh*t.................. :
https://drive.google.com/file/d/0B_yWw6RLoA-gdTMtZFczMUhQOHM/view?usp=sharing
Click to expand...
Click to collapse
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBzib...230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
Click to expand...
Click to collapse
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
jam1445 said:
3. One the Write Completes. Eject Card and insert in your LG G4 H811. Press Volume Up Button while connecting the USB Cable.
4. There you go, it will open the download mode.
Click to expand...
Click to collapse
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Good job. If your using this and you're gonna buy a SDCard on purpose, be aware that this fix might not work on your device. Ehehe
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
inso420 said:
@Jirrick im getting the same error on LGUP where do i find a newer version of the dll?
Click to expand...
Click to collapse
are these what you looking for.?
https://forum.xda-developers.com/showpost.php?p=73586554&postcount=921
VS986 Stuck on Download Mode
Jirrick said:
Today something went wrong while flashing weekly LOS build and my LG G4 (H815 with v20P firmware) went into very fast bootloop: https://www.youtube.com/watch?v=9gm0dh6bLp4
In this state i wasn't able to enter recovery, nor fastboot, nor download mode. Only IMEI screen (Vol Up + Vol Down I believe) was accessible which was no use.
Here are the steps which got me out of troubles:
A) Verify that you have LGUP installed and have proper 8994.dll version for your device.
Different versions of FW use different libraries which results in errors during flashing.
Steps:
1) Install LGUP with this guide https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
2) Get the right DLL. You can try this one:
...or extract it directly from KDZ file with extractor https://forum.xda-developers.com/showthread.php?t=2600575.
You need to extract it from FW version that your phone is already running, not from the one you are about to flash! (when flashing from v20d to v20p you need v20d version, but when reflashing v20p FW you need the v20p DLL)
3) Navigate to LGUP install folder (default "C:\Program Files (x86)\LG Electronics\LGUP")
4) Overwrite the old DLL located in "model\8994" folder version with new one in
I don't know the exact compatibility, or how many different DLL versions are out there. Hopefully it doesn't brick the device even more when wrong version is used, it just doesn't work.
B) Write h815 image to sdcard as mentioned here:
It worked for me with just 8GB one. Be aware that the image written to SD have like 20 partitions so windows might go crazy.
C) Follow these steps:
D) At this moment my G4 finally entered Download mode
I was able to reflash KDZ using the usual procedure (select UPGRADE, find a KDZ file, restart LGUP, select REFURBRISH and START). Initially I got 0x2000 error at approximately 16% (boot displayed as status) that was caused by old version of 8994.dll library.
E) Back to stock
Now you should have stock H815 again so lets flash LOS back as usual
Kudos to OPs: @bullghost , @shakeyabooti , @leptdre , @jam1445 and other posters on G4 section of XDA!
Hope this helps someone!
Click to expand...
Click to collapse
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
I just did all your steps for my VS986 , and I got 2 G4 Verizon's back up and working , Thank you so much.
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
inteLzzz said:
I'm using a 16gb microsd, but however I try to image it (exfat, fat32 filesystems, different win32imager versions) also have tried different cables, but it still doesn't show any sign of life. I bricked it exactly the same way as OP did. Does anyone have anything else I could try to fix this? Also does the battery charge when its on 9008 mode?
Click to expand...
Click to collapse
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Jirrick said:
Can you get at least to the IMEI Display mode (Vol UP and then quickly Vol DOWN, keep both pressed until it shows up)?
Click to expand...
Click to collapse
No could it be caused by low battery? I remember it being like 30% when I bricked it, and does it charge under 9008 mode?
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Jirrick said:
Sorry to hear that. I'm afraid this is beyond my knowledge if it wont even enter the IMEI screen. I suppose you can leave it bootlooping in charger over night and then try in the morning?
Click to expand...
Click to collapse
It does not bootloop, straight up dead. Just shows 9008 forever on the pc, I left it for like 2 hours like that yesterday. I'll leave it overnight today and if not I'll hack up a direct 5v 1a charger to charge the battery directly. If both don't work i'll probably flash LS991 files in QFIL and use it as a tablet afterwards.. damn i got this phone not even 2 weeks ago perfect condition and all. Will not buy any more damn LG devices.
Oh, I thought your phone was rapidly bootlooping like mine did. Sounds like the person who sold it to you was aware that the phone is on last legs (probably even baked the phone so it runs for few days more) and screwed you over. My next phone wont be LG either.
WARNING
DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO.
If you do, I am not sure what shape your phone will be in.
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock). If you don't, you will probably brick your phone.
If you use this on any model V30 besides the H932, you will be stuck in a bootloop, and you will not be able to fix it since you will have wiped out download mode!
This is safe if no mistakes are made (typos, missing a step, etc). However, if you do mess up, the risk is high that you lose download mode at best, or brick your phone at worst.
If you deviate from this procedure, and think: "I can just skip a step, or I can do this on my own Linux install". Don't complain if you brick your phone.
PREREQUISITES:
You MUST to be on 10d: link
You must have H933 10h laf installed. You will need the KDZ: link
We are going to flash this using the patched LG UP: link MOD EDIT: original link dead. Try THIS ONE instead
It MUST be installed in: Crogram Files (x86)LG ElectronicsLGUP
You can't just unzip it anywhere and run it, it will not find the model file.
You need TWRP: link
You need an SD card that is formatted for FAT16 with TWRP copied onto it EXACTLY as it is named when you download it.
You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL.
After installing TWRP, grab @weakNPCdotCom's latest TWRP flashable ROM threads: Oreo 20s or Pie 30d
MOD EDIT: If your phone is (or has been) on Pie, you need to use a later LGUP version to roll back to Nougat 10d, then SWITCH to the original LGUP version linked below for the remaining steps. See this post for details.
PROCEDURE PART 1: Getting a working LAF onto your phone
By far this is the most dangerous part of this procedure.
Make sure you are on or downgraded to 10d
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions -- ignore it, and click OK.
As a safety feature, LG UP will start flashing those modified partitions after laf completes flashing.
After the flash is initiated, pay close attention to the "step" and as soon as it changes from laf to another partition, PULL THE USB CABLE!
If you let it completely flash the H933 KDZ, your phone WILL reboot, and you WILL have a brick that can't be fixed.
You NEED to pay attention. The additional partitions that are flashed are very small. The second that step changes from laf to
the next partition, PULL THE USB CABLE!
Click OK and it will start flashing.
Once laf is flashed, and you have pulled the USB cable, you can click exit, and then re-open LG UP.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
MOD EDIT: Refer to THIS POST to make sure that LGLAF is able to read the SD card
Code:
git pull
git checkout h932-dd-write
./step1.sh
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination (with phone off, hold vol down + power. When the LG logo appears, immediately release and then hold power until you get the the factory reset screen. Choose yes twice and you will be in TWRP) to IMMEDIATELY boot into recovery. If you don't, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
CREDITS:
Lekensteyn -- His base work on the G2 / G3 gave me a GREAT headstart!
@steadfasterX - He added some real nice features, great guy to bounce ideas off, and just testing crazy ideas because he wasn't afraid to brick his phone Also, for FWUL
tuxuser - Helping with my lacking in Python
@smitel - His original reverse engineering of LG UP. Great inspiration!
-- Brian
XDA:DevDB Information
[H932] lafsploit 1.5, Tool/Utility for the LG V30
Contributors
runningnak3d
Version Information
Status: Testing
Created 2018-09-14
Last Updated 2020-07-21
PROCEDURE PART 1: Getting a working LAF onto your phone
Make sure you are on version 10d. Again, check in Software Info / Software Version if you are unsure.
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions (cache, OP, userdata) -- ignore it, and click OK.
Click OK and it will start flashing.
Once the flash completes, your phone will reboot into the OS. Just power off, and go back into download mode.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP and rooting
Make sure the SD card is in your phone.
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
Code:
git pull
git checkout h932-dd-write
./lglaf.py
These next commands you will type into the LGLAF shell. It will look like this:
Code:
LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)
Type a shell command to execute or "exit" to leave.
#
You will type these commands at the # prompt that you see above. When you enter the commands, you will NOT get any indication that the command completed. However, if you get this:
Code:
Hello, I am LAF. Nice to meet you.
then you typed the command incorrectly, and you need to try again. There are TWO spaces between !EXEC and toybox.
Also, the phone will NOT indicate that flashing is taking place since we are using dd and NOT the normal WRTE opcode. When you enter !CTRL POFF, the phone will go to 100%.
Lastly CAPS matter. These lines need to be typed exactly (better to use copy / paste). If you mess up, it is no big deal, just try again.
Code:
!EXEC toybox dd if=/storage/external_SD/twrp.img of=/dev/block/sde bs=4096 seek=10246\0
!CTRL POFF
You can now pull the USB cable, and your phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination to immediately boot to TWRP:
Power off your phone
Hold vol down + power.
When the LG logo appears, immediately release power (and ONLY power) and then immediately hold power again until you get the the factory reset screen.
You never let go of vol down until the factory reset screen appears. Once it appears, you can release both buttons.
Choose yes twice by using the vol down key and power to select, and you will be in TWRP.
You should only tap the power key to select yes. Don't press and hold, and don't spam the power key.
It takes TWRP a little bit to boot -- be patient.
If you don't do this, and you let the phone boot into the OS, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
By THIS part, I mean if you mess up the key combo, and the phone boots to the OS, you only have to do PART 2 -- not this entire process.
ROOTING:
OK, so now you are in TWRP, we need to flash a few things or TWRP will be wiped out, and your phone will be encrypted again.
First swipe to allow modifications
Choose wipe / format data / type yes
Choose reboot / recovery -- this will reload TWRP. Do not choose reboot / system. Make sure that when it reboots you are able to mount data without it prompting for a pin / passcode.
If it does, then you need to format data again and reboot to recovery because you chose WIPE and not FORMAT.
Pick install, and browse to your SD card where you have Magisk, dm-noverity-opt-encrypt, and rctd remover
You can install each one individually, or you can add them all together in the queue -- it is your choice. Also, Magisk needs to be flashed first -- the order of the other two zips doesn't matter.
Now that they are flashed, reboot to recovery yet again just for good measure. If everything looks good, reboot to system and you should have a rooted phone.
OPTIONAL:
If you would like a second copy of TWRP on your laf partition (I *highly* recommend this), follow these instructions:
Download the version of TWRP that you want to install onto laf.
Rename it to twrp.img
Boot your phone to TWRP, and connect it to your PC
Open a command prompt where you downloaded TWRP and type:
adb push twrp.img /sdcard/
adb shell dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/laf
With the phone off, hold vol up and plug in the USB cable and you should be greeted by your second copy of TWRP.
CLEANING UP:
If you do NOT want TWRP on laf, then we at least need to get the H932 laf back onto your phone.
Download this zip onto your phone: h932_laf.zip
Boot to TWRP
Choose install, and browse to where you downloaded the zip
When it finishes flashing, you will have the H932 laf back.
I can't say this enough, you should really consider keeping two copies of TWRP around. You will never be in a situation where you go: "Man, I wish I had download mode, but all I have is TWRP".
However, there are plenty of times that you may wish that you had a second copy of TWRP. Imagine flashing a ROM that wipes out recovery. Oppps. Imagine flashing a new version of TWRP and
it doesn't boot -- again -- opps.
-- Brian
I've added link to WTF instructions pointing T-mobile H932 users to here. ALL other V30/30+/V30S can use that easier method, but T-mobile H932 HAS to use this method.
OK -- those are the final instructions for now. Root away!
I have upgraded to Oreo, and then downgraded to 10d and tested this 4 times so I know it works fine. However, getting H933 laf onto your phone is dangerous. PLEASE pay attention and pull the USB cable. You can be too quick -- pulling it while it is still flashing laf. If you do, then you just need to flash 10d and start again. However, if you wait and your phone reboots, the H933 has a different RSA key and your phone is toast.
I don't have a TMO G7 to test with, but this should work for them as well. Just need to find the correct laf to flash for them.
-- Brian
I remember when the OP released this method for the T-Mobile G6 (I used to have one). Many bricked their phones in the process. Others were successful and happy. Too risky for me.
I can't post a screenshot right now, but here ya go -- proof that this works:
Code:
joan:/ $ su
joan:/ #
joan:/ # cd sys
sys/ system/
joan:/ # cd system/
joan:/system # cat build.prop | grep H932
ro.product.model=LG-H932
ro.lge.swversion=H93210d
ro.lge.factoryversion=LGH932AT-00-V10d-TMO-US-JAN-11-2018-ARB00+0
joan:/system #
-- Brian
First thing: Nice job, Brian! Thank you, and those who helped bring this to light by being guinea pigs.
Second: Brian, there appears to be a break in the link for FWUL. I was still able to copy the link text, then take the break out after pasting it into the address bar to get to the page, but wanted to let you know that the break is there.
runningnak3d said:
OK --
I don't have a TMO G7 to test with, but this should work for them as well. Just need to find the correct laf to flash for them.
-- Brian
Click to expand...
Click to collapse
Man I hope that's true but the g7 has a locked bootloader HTC style unlock now. LG haven't unlocked the Tmo version last I checked unless I missed something
Also, so it's okay to OTA to Oreo now? I'm on nougat and much rather be on Oreo
NOOO Don't ever take an OTA. You will need to flash an Oreo zip to get back. I am guessing there isn't one since there would be no need.
I don't have time to make one today unfortunately.
EDIT: and what?! you mean TMO finally has a locked bootloader on the G7 just like all other carriers? They didn't just strip fastboot flash, they removed oem unlock as well?
-- Brian
inuyasha1999 said:
First thing: Nice job, Brian! Thank you, and those who helped bring this to light by being guinea pigs.
Second: Brian, there appears to be a break in the link for FWUL. I was still able to copy the link text, then take the break out after pasting it into the address bar to get to the page, but wanted to let you know that the break is there.
Click to expand...
Click to collapse
Fixed. Please let me know if you catch anything else.
-- Brian
runningnak3d said:
NOOO Don't ever take an OTA. You will need to flash an Oreo zip to get back. I am guessing there isn't one since there would be no need.
I don't have time to make one today unfortunately.
EDIT: and what?! you mean TMO finally has a locked bootloader on the G7 just like all other carriers? They didn't just strip fastboot flash, they removed oem unlock as well?
-- Brian
Click to expand...
Click to collapse
I should have added im sick in bed today and haven't rooted yet so itd be a 100pct stock OTA. Is it still not recommend to OTA to Oreo beforehand?
And yup, it appears LG has done the HTC style unlock and the Tmo version isn't unlockable yet and probably won't be Imo. I think it was LG but could be Tmo since it seems the more custs they get, the more like at&t they become
Josh McGrath said:
I should have added im sick in bed today and haven't rooted yet so itd be a 100pct stock OTA. Is it still not recommend to OTA to Oreo beforehand?
And yup, it appears LG has done the HTC style unlock and the Tmo version isn't unlockable yet and probably won't be Imo. I think it was LG but could be Tmo since it seems the more custs they get, the more like at&t they become
Click to expand...
Click to collapse
If you did, you will be wasting your time since you have to downgrade to 10d.
I will try to get a 20a flashable zip up as soon as I can.
-- Brian
runningnak3d said:
If you did, you will be wasting your time since you have to downgrade to 10d.
I will try to get a 20a flashable zip up as soon as I can.
-- Brian
Click to expand...
Click to collapse
Wow. Being so sick has made me not think straight . I can't believe I didn't think about that since you have to flash back to 10d.
No pressure on the flashable. It isn't that big of deal for me or us but thanks for thinking about us with the extra work.
Hey Brian. I dont know if you saw my pm but im glad it works
@me2151 No, sorry, my PM box is so backed up. I am going to have to spend some time this weekend going through it.
This isn't quite the same as lafsploit for the H918, but the concept came from research for that project.
Next tasks:
* Get Oreo and root working on the V20
* Get all other G6s root in addition to the H872
* Consider buying a V30 so I can help here as well
-- Brian
runningnak3d said:
@me2151 No, sorry, my PM box is so backed up. I am going to have to spend some time this weekend going through it.
This isn't quite the same as lafsploit for the H918, but the concept came from research for that project.
Next tasks:
* Get Oreo and root working on the V20
* Get all other G6s root in addition to the H872
* Consider buying a V30 so I can help here as well
-- Brian
Click to expand...
Click to collapse
Ah lol. My pm had jsut suggested taking a look into the h932 since its similar to the h918 in regards to bootloader. yea you should join us. I have my P rom working now. ill probably hold off on releasing it to the public though til i do more features. However. Only non stock rom to have enforcing on Joan
@runningnak3d
You stated, "You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL."
When I went to the page it has 2 options/2 types of FWUL... which should we download:
"Main Download Server:
persistent mode ( read FAQ #4 ): Latest version (click)
forgetful mode ( read FAQ #4 ): Latest version (click)"
I'm guessing Persistent mode version....?
Thanks
runningnak3d said:
WARNING
DO NOT LET YOUR PHONE REBOOT, OR POWER OFF UNTIL I TELL YOU THAT IS WHAT YOU NEED TO DO.
If you do, I am not sure what shape your phone will be in.
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock). If you don't, you will probably brick your phone.
If you use this on any model V30 besides the H932, you will be stuck in a bootloop, and you will not be able to fix it since you will have wiped out download mode!
This is safe if no mistakes are made (typos, missing a step, etc). However, if you do mess up, the risk is high that you lose download mode at best, or brick your phone at worst.
If you deviate from this procedure, and think: "I can just skip a step, or I can do this on my own Linux install". Don't complain if you brick your phone.
PREREQUISITES:
You MUST to be on 10d: link
You must have H933 10h laf installed. You will need the KDZ: link
We are going to flash this using the patched LG UP: link
It MUST be installed in: Crogram Files (x86)LG ElectronicsLGUP
You can't just unzip it anywhere and run it, it will not find the model file.
You need TWRP: link
You need Magisk: link
You need an SD card that is formatted for FAT16 with TWRP copied onto it and named twrp.img. Also copy the Magisk zip onto the card.
You need to grab FWUL (version 2.7 or later) and burn it to a USB stick: link
Even if you have Linux, and you think you can install the dependencies, don't. I know this works from FWUL.
PROCEDURE PART 1: Getting a working LAF onto your phone
By far this is the most dangerous part of this procedure.
Make sure you are on or downgraded to 10d
Boot to download mode
In LG UP, choose partition DL.
Pick the H933 10h KDZ
Click start
You will be given a list of partitions to flash, ONLY check laf
Click start
You will get a warning about additional modified partitions -- ignore it, and click OK.
As a safety feature, LG UP will start flashing those modified partitions after laf completes flashing.
After the flash is initiated, pay close attention to the "step" and as soon as it changes from laf to another partition, PULL THE USB CABLE!
If you let it completely flash the H933 KDZ, your phone WILL reboot, and you WILL have a brick that can't be fixed.
You NEED to pay attention. The additional partitions that are flashed are very small. The second that step changes from laf to
the next partition, PULL THE USB CABLE!
Click OK and it will start flashing.
Once laf is flashed, and you have pulled the USB cable, you can click exit, and then re-open LG UP.
Choose partition DL again, and this time pick the H932 10d KDZ.
Select all partitions except laf. If you forget to uncheck laf, you will have to do this all over again.
When it completes, it will reboot your phone.
Go back into download mode. This time you will be running the H933 laf, and we can continue with PART 2
PROCEDURE PART 2: Installing TWRP
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to
touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
Code:
git pull
git checkout h932-dd-write
./lgaf.py
!EXEC toybox dd if=/storage/external_SD/twrp.img of=/dev/block/sde bs=4096 seek=10246\0
!CTRL POFF
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP installed. At this point you can flash a ROM, or Magisk or whatever you like.
You must use the key combination (with phone off, hold vol down + power. When the LG logo appears, immediately release and then hold power until you get the the factory reset screen. Choose yes twice and you will be in TWRP) to IMMEDIATELY boot into recovery. If you don't, then recovery-from-boot.p will wipe out TWRP, and you will have to do THIS part again.
You will have to format data, and make sure you flash Magisk before rebooting into the OS!
CREDITS:
Lekensteyn -- His base work on the G2 / G3 gave me a GREAT headstart!
@steadfasterX - He added some real nice features, great guy to bounce ideas off, and just testing crazy ideas because he wasn't afraid to brick his phone Also, for FWUL
tuxuser - Helping with my lacking in Python
@smitel - His original reverse engineering of LG UP. Great inspiration!
-- Brian
XDA:DevDB Information
[H932] lafsploit 1.5, Tool/Utility for the LG V30
Contributors
runningnak3d
Version Information
Status: Testing
Created 2018-09-14
Last Updated 2018-09-14
Click to expand...
Click to collapse
Feedback
I had a moment to go through the instructions as a "typical user", and am providing feedback to make this as painless as possible, crystal-clear, & hopefully prevent any bricks!: (Please correct any inaccuracies!!)
runningnak3d said:
This should go without saying, but you MUST have your bootloader unlocked (check OEM UNLOCK in developer options AND fastboot oem unlock)...
Click to expand...
Click to collapse
EVERYTHING should be said!!! Especially things that will brick our phones People like me that ARE extremely computer literate and have been 'custom rom-ing' for almost a decade still won't know all of these nuances. I've been just catching up on all of these advancements with the V30 and your latest discovery, read hundreds of posts, but I still won't pretend to know everything! And apparently a mistake like this could've made my phone gar-bosh. So don't underestimate peeps like me So: in Android phone settings->Developer Options: There are 2 checkbox(es) we need to select? "OEM Unlock" and "Fastboot OEM unlock"? (Im not sure about the latter mostly)
runningnak3d said:
...You MUST to be on 10d...
Click to expand...
Click to collapse
Link or steps if you're NOT? Ways to check? (I like many users will either get a random phone off ebay, or have one already, and won't know our baseline or how to determine this. & is this a deal breaker if it's not 10d?)
runningnak3d said:
...You must have H933 10h laf installed...
Click to expand...
Click to collapse
Link or steps if you're NOT? Does that link also contain the software or is there another link we need? (Again, if there's another link, version-mismatch might cause unpredictable results for some users)
Fat32: I've used SwissKnife https://swissknife.en.uptodown.com/windows to do easy FAT (same as FAT16) formatting. I say this because I already saw issues around this.
I'm looking to buy a V30 only since you figured this out Much thanks! I'll say that again, you're awesome & I'm jealous! It sounds like now ALL variants can get the bootloader unlocked and a custom recovery installed: H932 via this thread/method & all other variants via WTF exploit (Again, please keep me honest!). (I just want to double-check my info so I (& others) buy a phone that will be able to get a custom ROM & plan to get the H932 and will report back if/when I get band 71 working for those interested.
I know some of you that have been in this since the beginning are thinking, come on man, read the posts! Like I said, I have been for over a week. There are thousands of posts, and even if I/we read EVERYTHING, we still wouldn't be able to decipher the bad info from the good! ...so thanks for your patience I'll post more once I actually try this. And thanks again Brian!! Really awesome...
---------- Post added at 03:07 PM ---------- Previous post was at 03:01 PM ----------
runningnak3d said:
* Consider buying a V30 so I can help here as well
Click to expand...
Click to collapse
Umm... For all of us that use this and get it working, I think we should do donations until Brian can get a free V30, eh?!? (Can't yall read between the lines ) Besides, think of all the additional support you'll get if he actually has a phone to test with!! haha
@igotroot
Did you get it working yet? If not I can run you through the hardest part of it. Also, choose the persistent FWUL. Basically persistent mode means it saves your data when you leave. It's just easier that way
Disclaimer: This WILL void your warranty. I am not liable for breaking/bricking your phone, you losing your data, or any nuclear war/other catastrophe. This process WILL totally wipe all data on your phone. Make sure you have a backup! You will also forever see "bad key" displayed in the top left of your screen for a few seconds after a reboot after unlocking the bootloader. There is currently no way around this that I'm aware of (let me know if you have a way)
This guide was assembled from mingkee's G7 guide here: https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
You will need:
1. Your Moto G7 Power (Any hardware version, any carrier, but running Android 9 Pie)
2. A stock boot.img for your hardware version, here are the two that I have. You can just extract the boot.img from a stock ROM for a hardware version not listed, although I'm not sure it actually matters which one you use. Experiment at your own risk.
XT1955-5 US: https://mega.nz/#!L0sHzSKY!323GrDQ8BTsPmKvrSoU7DV-2kJuVris0cWN8Xt3u_6o
XT1955-2 LATAM: https://mega.nz/#!uk912I4B!12_EgPML2l5sIXDeDGVqiVDB2RwA6iF6-H-mivNecOo
(Full stock ROM's for both versions will be linked in the next post. )
3. A USB cable to connect your G7 to a computer
4. Motorola USB drivers: https://support.motorola.com/uk/en/...moto-g-family/moto-g7-power/documents/MS98028
4. Your bootloader unlock code from Motorola, more on that below
5. Android SDK
Step 1: Unlocking the bootloader
First we'll need to unlock the bootloader, to do this, you'll need your unlock code from Motorola:
https://support.motorola.com/us/en/bootloader
Note that this will require you to register your device with Motorola, and this WILL void your warranty.
Then, download and install the Motorola USB drivers (link above), you may need to reboot your computer after installation.
Next you'll need to download and extract/install the Android SDK
https://developer.android.com/studio/index.html#downloads
Note that you'll only need the "command line tools" for this guide, unless you really want the whole SDK (huge).
Extract the command line tools to anywhere really, C:\Android is fine for Windows. If you downloaded/installed the whole sdk, the tools you need will be in C:\Users\[your username]\AppData\Local\Android\Sdk\platform-tools
Once you have that, open up a powershell window in your tools folder by holding Shift and right-clicking in the folder.
Now, reboot your G7 to fastboot mode by powering off, then holding power+volume down until you're in the bootloader. Now, connect your G7 to your computer with your USB cable.
In powershell, verify your device is recognized by typing "./fastboot devices". Your G7 should show up by its serial number.
Now, type "./fastboot oem unlock [your motorola unlock code]". THIS WILL WIPE ALL DATA ON YOUR PHONE. After that, use the volume up and down buttons and then the power key to restart the bootloader. You should now see "flashing_unlocked" at the bottom of the bootloader screen. Now use the volume/power buttons to select "start" to boot the phone. You will see "bad key" displayed in the top left corner of the screen. This is normal. The phone should boot and bring you to the Android set up wizard. Go ahead and set up the phone as you normally would.
Note that at this time, if you go to "Update" in system settings, it may warn you that "system integrity is compromised" and that you will no longer receive OTA updates. This is also normal, we'll fix that in a bit.
Step 2: Rooting
Now that we have an unlocked bootloader, we can flash things to the phone through fastboot (at the time of this writing, TWRP or other custom recoveries are not available for the G7 Power. Once it is, you can use that to flash the Magisk .zip file instead of using powershell).
Copy the correct *_boot.img for your hardware version to a folder on your phone. I used the downloads folder. (not too sure if the version makes a difference; I was able to flash the entire US XT1955-5 firmware/rom to my Latin America XT1955-2 without a problem, but experiment at your own risk)
Download and install the Magisk Manager APK through Chrome or browser of your choice on your G7
https://github.com/topjohnwu/Magisk/releases
It will ask you if you want to allow [your browser] to install things from unknown sources. Say yes.
Then, open Magisk Manager and tap "Install". Then tap "patch boot image file". Select the *_boot.img you copied earlier and let it run. It will tell you when its done.
Once it completes, copy the patched *_boot.img back to your computer and place it in the same folder as your Android SDK tools (where fastboot.exe and adb.exe live)
Now power off the phone then boot to fastboot, again by holding power + volume down until the bootloader appears.
Now in powershell, type "./fastboot flash boot [the name of your patched boot.img].img" and hit enter. Alternatively, type "./fastboot flash boot" then hit space, then drag your patched *_boot.img into powershell and hit enter.
(Note, if you get an error saying "Invalid partition name boot__a" like I did, add a "_a" to "boot" ie "./fastboot flash boot_a [the name of your patched boot.img]" instead. )
Powershell should tell you "Image signed with key bad key". This is normal.
Now use the volume up/down buttons and power button to start the phone.
Once booted, load up Magisk Manager again. You should see all green checkmarks. Congrats, your G7 is now rooted! One last thing:
Tap where Magisk says "tap to start SafetyNet check". This tests to see if its able to fool Google's checks and let you install OTA updates or use Android Pay. If you did everything properly, this should all check out fine. Confirm by going into Updates in System Settings and verifying that you are up-to-date and it doesnt say anything about "device integrity compromised".
Thanks to everyone who's work I shamelessly paraphrased. I wanted to make a concise guide specifically for the G7 power as I didn't find much online regarding it. (And the stock US rom was ridiculously hard to find and acquire). I'll link stock US and Latin America G7 Power firmwares/roms in the post below in case anyone wants to go back to stock, once the upload finishes. Note: there is no known way at the time of this writing that you can ever get rid of "bad key" being displayed at boot once you unlock the bootloader (again, if anyone knows how, let me know! Thanks!)
gedster314 linked me to a site in another thread where stock ROMS for a lot of devices can be found, including the XT1955 (codename: Ocean).
https://mirrors.lolinet.com/firmware/moto/ocean/official/
"RETUS" on that page would signify "Retail, US"
until some good custom roms will pop out i don't have needs to unlick/root...
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Baby steps my friend.
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Got everything to work! Flashed Tethering Enabler too. Thank you!
nucher said:
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
Click to expand...
Click to collapse
There's one more reason to root: CF Lumen
I want all devices have same exactly same white tone.
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
turboyo said:
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
Click to expand...
Click to collapse
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
diversenerd said:
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
Click to expand...
Click to collapse
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
turboyo said:
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
Click to expand...
Click to collapse
I was wrong in my first thread, my -2 does NOT have NFC. Heres the newly minted LTE Band unlocking guide: https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-enable-lte-t3925246
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Darkstarsx said:
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Click to expand...
Click to collapse
What kind of issues? I haven't noticed any ill effects of rooting with this method.
my touchscreen is not working at all after the rooting step. how do i fix this?
jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Try rolling back to stock with my other guide. Then try again.
Thanks for the guide, phone is now rooted. Is it safe to do a factory reset to be able to start the phone set up again to automatically download apps, settings, etc from Google? If not, is there another, better way to do that?
diversenerd said:
Try rolling back to stock with my other guide. Then try again.
Click to expand...
Click to collapse
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Chickenaa said:
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
Click to expand...
Click to collapse
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Poto222 said:
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Click to expand...
Click to collapse
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Chickenaa said:
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Click to expand...
Click to collapse
Someone on the Telegram group has a working TWRP build, he said he'll be posting it soon.
I gave up on unlocking the bootloader of my V50 sprint version because I thought it was impossible. Not until I stumbled upon this guide in the LG G8 forum.
I think it is good to have the information in the LG V50 thread also. The thread is owned by Seasee606.
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
good idea !
I ve put this thread in the LG V50 wiki : https://android.fandom.com/wiki/V50_ThinQ ! - everybody is welcome to contribute
I ve just received my korean V50 and I ll try to bootloaderunlock-root it as soon as I ll have the time ...
pierro78 said:
good idea !
I ve put this thread in the LG V50 wiki : https://android.fandom.com/wiki/V50_ThinQ ! - everybody is welcome to contribute
I ve just received my korean V50 and I ll try to bootloaderunlock-root it as soon as I ll have the time ...
Click to expand...
Click to collapse
I don't think it's been confirmed to work on the G8 let alone a single V50
ldeveraux said:
I don't think it's been confirmed to work on the G8 let alone a single V50
Click to expand...
Click to collapse
did you see there are at least 2 custom roms for the V50 ?? then how do you think people bl unlock their V50 ??
pierro78 said:
did you see there are at least 2 custom roms for the V50 ?? then how do you think people bl unlock their V50 ??
Click to expand...
Click to collapse
Did you look at the original G8 thread? People bricking left and right, zero help from the developer who posted the method. I think one guy who says he got it working on a Sprint V50. Have fun bricking your phone!
people on the V50 telegram (founded by the LineageOS dev) seem to be helpful ...
pierro78 said:
people on the V50 telegram (founded by the LineageOS dev) seem to be helpful ...
Click to expand...
Click to collapse
I'm on xda so I don't have to resort to telegram. we've been over this.
I ve just done it on my V500N
took me about 2 hours so not so easy but not impossible
maybe I was lucky ?
couple of difficulties :
* first I could not get into EDL mode but I took the LG USB cable from the box and this worked
* the first time I exited the QFIL partition manager the phone rebooted to EDL mode but was not recognized as "qualcomm device" (there was an unknown usb device in the device manager) ... I just manually rebooted into EDL mode and the phone was recognized as "qualcomm device" this time and I could continue the method without issue ...
(deleted) (see below)
pierro78 said:
nice (and strange !) surprise :
* after bootloader unlock I was supposed to enter "fastboot flash abl_a abl_a.bin" and "fastboot flash abl_b abl_b.bin" but the phone rebooted without issue (telling me first I was bl-unlocked)
Click to expand...
Click to collapse
Oh I had to "fastboot flash abl_a abl_a.bin" and "fastboot flash abl_b abl_b.bin" otherwise my software version would be LM-G850N20z (instead of V500N20z)
I successully unlocked my V50 sprint version. It was fairly easy to do it.
1) To be safe, use the original LG cable. was not successful unlocking the bootloader the first time when I used a generic cable. Even though I was able to enter EDL mode.
2) Make sure to verify that the correct abl_a.bin and abl_b.bin versions are downloaded. The size should be about 1MB.
3) One part in the guide that was not clear was which abl engineering image to flash on a and b partitions. Well, it is the downloaded abl_a.bin that should be flashed in the abl_a and abl_b partitions.
I can see this is very recent which gives me hope, I just bought a v50 (v450vm) on a whim and am wanting to flash twrp and install an aftermarket rom on it. Is there a working version of twrp for this model and has anyone had any success in flashing it? I'm really wanting to the try the new unofficial dotOS version that was recently posted. Thanks in advance for any help/info provided.
I finally got around to rooting my Sprint V50 (LM-V450PM), and I agree that the overall process wasn't difficult. It's just that the guide has little to no explanation for specific models, causing a lot of confusion among users in that thread. It also doesn't help that the guide's OP pretty much posted it, edited it once, and never returned to XDA. And the TWRP installation guide posted by someone else is poorly laid out and has been rightfully criticized by others.
So, here are some pointers from my experience:
- Getting into EDL mode is a bit tricky in getting the timing right, so it may take a few tries to get used to it.
- As has already been mentioned, it's a good idea to use the LG OEM cable to connect the phone to the computer. Some people have been getting a "Sahara fail error" in QFIL that might be due to different cables
- You are backing up the abl and boot partition files for both A and B slots because you don't know yet which slot is active on the phone until you enter fastboot mode, which gets enabled after flashing the modified abl engineering file to replace both abl_a and abl_b partitions.
- For getting root, the newer Magisk versions no longer have a separate Manager APK and ZIP files; they are combined into one APK file now. So, instead of the Manager, you just install the single APK file from the Magisk website. From there, you should be able to patch your boot image file just like it says in the guide.
For TWRP:
- As lallolu mentioned in another post, there are two different versions: One for USA models and one for non-U.S. variants. I'm assuming that the U.S. one is for the Sprint and Verizon V50 while the non-U.S. is for all other types.
- You flash the TWRP ZIP package inside Magisk manually as a module. Note that this will remove root as it tells you on the progress screen when done flashing.
- Since for some reason, the touch screen is not active when entering recovery from a reboot, you need to turn off the phone and then enter recovery via the button combination. Some V50 models appear to have the button combination disabled, and there is a separate guide on here for getting it back, but on the Sprint model, it's still enabled: With the phone off, hold volume-up + power, and when the logo shows up, briefly release the power button while still holding volume-up and then hold power again alongside holding volume-up until the factory reset screen shows up. Answer YES twice, and you will eventually enter TWRP.
- TWRP will greet you with a password, but you just hit cancel to continue and get to the main menu. From there, you'll need to go to Wipe and Format Data (where it will ask you to type "yes") to remove encryption.
- Now you want to get root back by flashing Magisk. All you need to do is rename the Magisk APK file extension to ZIP and flash that in TWRP. Right after that, you should also flash a file called Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip which is also needed to remove encryption.
- Reboot into the system, go through the initial setup, and everything should be set.
For the Verizon model, I'm assuming that the "Enable OEM unlock" switch in the Developer Settings doesn't exist, and so the Verizon FRP image used for the Verizon G8 should also be used. The button combination to enter recovery may also be different. But everything else should be identical to the process for the Sprint model.
C D said:
I finally got around to rooting my Sprint V50 (LM-V450PM), and I agree that the overall process wasn't difficult. It's just that the guide has little to no explanation for specific models, causing a lot of confusion among users in that thread. It also doesn't help that the guide's OP pretty much posted it, edited it once, and never returned to XDA. And the TWRP installation guide posted by someone else is poorly laid out and has been rightfully criticized by others.
So, here are some pointers from my experience:
- Getting into EDL mode is a bit tricky in getting the timing right, so it may take a few tries to get used to it.
- As has already been mentioned, it's a good idea to use the LG OEM cable to connect the phone to the computer. Some people have been getting a "Sahara fail error" in QFIL that might be due to different cables
- You are backing up the abl and boot partition files for both A and B slots because you don't know yet which slot is active on the phone until you enter fastboot mode, which gets enabled after flashing the modified abl engineering file to replace both abl_a and abl_b partitions.
- For getting root, the newer Magisk versions no longer have a separate Manager APK and ZIP files; they are combined into one APK file now. So, instead of the Manager, you just install the single APK file from the Magisk website. From there, you should be able to patch your boot image file just like it says in the guide.
For TWRP:
- As lallolu mentioned in another post, there are two different versions: One for USA models and one for non-U.S. variants. I'm assuming that the U.S. one is for the Sprint and Verizon V50 while the non-U.S. is for all other types.
- You flash the TWRP ZIP package inside Magisk manually. Note that this will remove root as it tells you on the progress screen when done flashing.
- Since for some reason, the touch screen is not active when entering recovery from a reboot, you need to turn off the phone and then enter recovery via the button combination. Some V50 models appear to have the button combination disabled, and there is a separate guide on here for getting it back, but on the Sprint model, it's still enabled: With the phone off, hold volume-up + power, and when the logo shows up, briefly release the power button while still holding volume-up and then hold power again alongside holding volume-up until the factory reset screen shows up. Answer YES twice, and you will eventually enter TWRP.
- TWRP will greet you with a password, but you just hit cancel to continue and get to the main menu. From there, you'll need to go to Wipe and Format Data (where it will ask you to type "yes") to remove encryption.
- Now you want to get root back by flashing Magisk. All you need to do is rename the Magisk APK file extension to ZIP and flash that in TWRP. Right after that, you should also flash a file called Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip which is also needed to remove encryption.
- Reboot into the system, go through the initial setup, and everything should be set.
For the Verizon model, I'm assuming that the "Enable OEM unlock" switch in the Developer Settings doesn't exist, and so the Verizon FRP image used for the Verizon G8 should also be used. Everything else should be identical to the process for the Sprint model.
Click to expand...
Click to collapse
I tried tge volume up+power but twrp don't show up
Khmer_Boy said:
I tried tge volume up+power but twrp don't show up
Click to expand...
Click to collapse
Did you briefly release the power button and then hold it down again? It may take a few tries to get it right if you are not used to doing this. The white factory reset screen will show up if you did it correctly.
I got into the white factory reset screen by doing the volume down+power. What do i do? Select erase or just exit?
Khmer_Boy said:
I got into the white factory reset screen by doing the volume down+power. What do i do? Select erase or just exit?
Click to expand...
Click to collapse
As I mentioned above, you have to answer YES twice. If TWRP is installed, it will go there, and nothing will be erased. If it isn't installed, then the phone will do a factory reset.
C D said:
As I mentioned above, you have to answer YES twice. If TWRP is installed, it will go there, and nothing will be erased. If it isn't installed, then the phone will do a factory reset.
Click to expand...
Click to collapse
Ok. I got into TWRP, but it doesn’t recognize The internal storage. Is there a work around to it?
Khmer_Boy said:
Ok. I got into TWRP, but it doesn’t recognize The internal storage. Is there a work around to it?
Click to expand...
Click to collapse
Did you format data like I mentioned above?
C D said:
Did you format data like I mentioned above?
Click to expand...
Click to collapse
I’m going to give it another try