yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G5 Guides, News, & Discussion] sxotty:
Well they were in the root, so I guess I should have left them there. It said it could not find them so I compared it to the prior versions and saw they were in a new folder. I am using windows 7 in a virtual machine and there is no antivirus even installed on it. I can type the commands manually in adb and get to

logcat -s recowvery

command but it does not do anything.

This script should work on 20A not just the 10 versions right? What specific files is it looking for when it says it cannot find the exploit files. I redownloaded it again and then tried again. Still says exploit files are missing. I installed 7zip on the VM and then it unzipped properly though at least.

The image below is not loading imgur must be having trouble, but basically it shows the files in the root and the command prompt window saying files are missing in the exploit directory.

[IMG="missing"]https://imgur.com/5PrUrYE[/IMG]
[T-Mobile LG G5 Guides, News, & Discussion] sxotty:
some progress

Well I found out the reason it was having difficulty was that I ran the cmd file as administrator. Why would that cause problems? I have not idea.

Anyway now it says that the device does not look like a tmobile g5 should I continue? I say yes.

Then it says that the thing is locked, but it is unlocked (in fact I actually used fastboot to lock it, then unlock it again just to be sure). This was in the VM.

I tried in regular computer as well and it got much farther. But still had a problem.

"Wating for selinux pwn... (timeout after 3 minutes)

---selinux is ours! Rebooting ---

error: closed

---flashing no-verity-opt-encrypt---"

Not sure if that error was the problem, but it ended up booting into the regular bootloader that says

"No Command"
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
If you're free then PM me, I'll send you link to a test version. I have disabled all checks and everything. All it will do is root and flash TWRP. Also remember to copy recovery.img in root on internal storage.

Edit:

Added Ricksy Recowvery (More liter, streamlined version with just exploit and no-verity-encrypt). Check in 2nd post and make sure to read carefully before proceeding. And don't blame me if you brick.
[T-Mobile LG G5 Guides, News, & Discussion] sxotty:
Success

So I have to admit I did not use the script you put together, but upon starting the script it complained that the adb version did not match. I think this might be because I locked and unlocked the bootloader I am not sure. Somehow previously I had version 40 of adb even after downgrade on device. Anyway I checked the versions included with the script and found one that was 36. This was what I needed. I tried to uninstall adb from add remove programs, but version 40 persisted on the system level (perhaps if I had type .\adb it would have used the local file insted of system file). It was in c:\windows. I deleted that manually.

Then I typed in the normal series of commands mentioned but in powershell you have to add .\ before adb on each line. Lo and behold it worked finally. Hallelujah. So I am writing this to let others know that there is hope. I am not sure if all the steps were necessary, but in short, what I did was

Downgrade to 20A using uppercut

Lock bootloader in fastboot

Unlock bootloader in fastboot

Find adb version 36 which matched h83020A

Type in the normal series of commands according toh918-recowvery-unlock-v20-root-shell-t3490594

Then I used

stock-h830-30c-zips-imgs-kdz-2018-08-01-t3845206

To return to oreo but retain unlock and root.
[T-Mobile LG G5 Guides, News, & Discussion] OCO3HATb:
unrecognized device type

After successfully bringing my H830 back to life and flashing V20A, I am trying to root it.

For some reason the process hit a stumble block. Is it safe to proceed?

(see below)

Please select from the following options:

1) Run exploit and flash /sdcard/recovery.img (Leave selinux enforcing)

2) Run exploit and flash /sdcard/recovery.img (Set selinux permissive)

3) Install superuser ZIP from G:\EasyRecowvery-1.3b3\zips (Requires TWRP)

4) Restore stock boot and recovery from /sdcard/stock_*.img

5) Extras and Advanced Tools

0) Quit this script

(0-5) 2

Running in permissive exploit mode

Press any key to continue . . .

- - - Making sure we're good to go - - -

Checking permissions in the EasyRecowvery directory...Checking that the exploit files exist...SUCCESS!

Locating adb.exe... SUCCESS!

Looking for ADB device... h1_tmo_us

This device doesn't look like a T-mobile V20. Proceed anyway? (DANGEROUS!)

(Y/N) n
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
It's probably because you're using Original EASY RECOWVERY. Its fine to enter y and proceed only if you read FAQ properly. Remember to turn of integrity verification off from advanced menu if you're using original recowvery. If you use Modified or Ricksy recowvery it will not show these errors (hopefully)
[T-Mobile LG G5 Guides, News, & Discussion] OCO3HATb:
I advanced a notch but the process failed at the late stage(see below). The phone seems to be fine except I can't enter into the recovery mode any way but issuing the command adb reboot recovery which gives me this

I wonder if it hurts to run the same script repeatedly until it actually makes some "tangible" changes on the phone.

What about exploits? Can they simply rerun regardless of their previous run?

I am not sure what Error 1 is, but the script's complaining about absence of recovery.img is baseless

h1:/ $ ls -l /sdcard/*.img

-rwxrwx--x 1 root sdcard_rw 23490560 2019-02-23 19:27 /sdcard/recovery.img

h1:/ $

From another hand /sdcard/stock_recovery.img and /sdcard/stock_boot.img, reportedly created successfully, obviously do not exist.

Here's the execution log.

Please select from the following options:

1) Run exploit and flash /sdcard/recovery.img (Leave selinux enforcing)

2) Run exploit and flash /sdcard/recovery.img (Set selinux permissive)

3) Install superuser ZIP from C:\EasyRecowvery-1.3b3\zips (Requires TWRP)

4) Restore stock boot and recovery from /sdcard/stock_*.img

5) Extras and Advanced Tools

0) Quit this script

(0-5) 2

Running in permissive exploit mode

Press any key to continue . . .

- - - Making sure we're good to go - - -

Checking permissions in the EasyRecowvery directory...Checking that the exploit files exist...SUCCESS!

Locating adb.exe... SUCCESS!

Looking for ADB device... h1_tmo_us

This device doesn't look like a T-mobile V20. Proceed anyway? (DANGEROUS!)

(Y/N) y

Checking unlock status... SUCCESS!

Using device with serial LGH8301ea5fe45

- - - Pushing exploit to /data/local/tmp/recowvery - - -

Copying files... SUCCESS!

- - - Launching Recowvery on device - - -

Exploiting /system/bin/applypatch... SUCCESS!

Exploiting /system/bin/app_process64... SUCCESS!

Waiting for selinux pwn... (timeout after 3 minutes)

- - - selinux is ours! Rebooting - - -

Exploiting /system/bin/run-as... SUCCESS!

- - - Rebooting to persist selinux permissive mode - - -

Error 1: Operation not permitted

Creating backup of recovery at /sdcard/stock_recovery.img... SUCCESS!

Creating backup of boot at /sdcard/stock_boot.img... SUCCESS!

Flashing recovery.img for fun and for profit... FAILED!

Could not locate /sdcard/recovery.img. Please upload one and run the script again in "flash only" mode.

SOMETHING WENT WRONG! EXITING.

- - - Flashing no-verity-opt-encrypt - - -

Using C:\EasyRecowvery-1.3b3\zips\no-verity-opt-encrypt.zip

Press any key to continue . . .

Rebooting to recovery to flash no-verity-opt-encrypt.

If necessary, please exit the decryption screen when TWRP finishes booting, then continue.

Press any key to continue . . .

Terminate batch job (Y/N)? y
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
It looks like recovery.img is missing from root of internal storage. Did you download twrp recovery, named it as "recovery.img". And copied it to internal storage of phone?
[T-Mobile LG G5 Guides, News, & Discussion] OCO3HATb:
Of course. Did you see this above?

h1:/ $ ls -l /sdcard/*.img

-rwxrwx--x 1 root sdcard_rw 23490560 2019-02-23 19:27 /sdcard/recovery.img

h1:/ $

That's the point I was trying to make. The directory clearly contains recovery.img but does not contain 2 backups that the script reported creating successfully.
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Which toolkit are you using?
[T-Mobile LG G5 Guides, News, & Discussion] OCO3HATb:
I'm using Easy Recovery. Nothing else. When the script issued a warning

Could not locate /sdcard/recovery.img. Please upload one and run the script again in "flash only" mode.

I wanted to immediately verify the claim by issuing command ls -l /sdcard/*.img

which contradicted the script.

I do not quite understand why adb.exe is renamed into adb-recowvery.exe in adb directory. Wouldn't it be better using the default adb specified in PATH?

Anyway can you suggest something to repair this "No command" issue? My bootloader is unlocked now and the phone issues a warning screen every time it's rebooted. What if I lock it again? Doesn't Android restore the recovery to its default state? Or it is better to proceed with "flash only" mode?

I worry a little bit that the script did not back up the stock boot and recovery images(contrary to the log messages it produced). Not sure how big of a deal it may be.
[T-Mobile LG G5 Guides, News, & Discussion] OCO3HATb:
I finally rooted my phone. The tool somehow wiped out my recovery partition without leaving a copy. Without the copy the script would not proceed. So I had to use the second menu option 1 of "Easy" recowvery to gain SU privileges to issue shell "dd" command so that the TWRP image is placed into the empty partition.

The big problem with the tool is that it was designed for the dummies. But not those dummies that read books like Linux for dummies. It takes dummy of a special kind that without understanding what is done in the process reads the warning that the phone may be bricked and decides that it's a good idea to proceed. :)

The script attempts to prevent disastrous outcomes but fails by tripping over itself. IMO it would be much better to conduct the process in stages i.e. make the necessary copies and come to full stop, allowing the user to make sure that everything's ready for the next step. Without it I spent countless hours analyzing the nature of my problem and Windows and Linux scripts of Easy recowvery that should do the job in 15' tops.

PS: after TWRP was in place the options of the second (advanced) menu would not work either and they were wiping TWRP out of recovery partition so I just booted into the TWRP and installed the noverify and root from there.
[T-Mobile LG G5 Guides, News, & Discussion] fallenturtle:
Edit: Nevermind, figured it out.
[T-Mobile LG G5 Guides, News, & Discussion] raullgg5:
After you wrote "You can take your phone back to v20a by using the following guide." you only wrote "Anyways". Is there a link missing here? Or do I use the "Back to life thread" guide if I want to downgrade my phone from 20o to 20a? Thanks in advance and thanks for your guide!
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Yeah. There was some extra instructions in here which wasn't needed anymore. It's complete process as far as I can remember. And If anything goes wrong, there is our back to life thread.
[T-Mobile LG G5 Guides, News, & Discussion] Android#:
Thanks, it worked for LG G5 after moving the '1' folder to root directory of the PC. Since anti-virus was off during this, I am a bit confused as why is my PC asking to reboot saying that "Your PC needs to be restarted to finish setting up this device: LGE Mobile ADB Interface.". I thought this was not suppose to make any changes to the PC itself? Thanks.
[T-Mobile LG G5 Guides, News, & Discussion] gioni1:
I'm stuck unsuccessful encryption, after doing everything correctly.i can access twrp

Solved

https://xdaforums.com/lg-g5/how-to/solution-encryption-unsuccessful-format-t3931259
[T-Mobile LG G5 Guides, News, & Discussion] Redschista:
Hello @LL,

I am new to flashing phones. Back in the days I did something which worked, I don't remember what it was... ;-)

No I was sure I can install lineage on my H830, and offered for a couple of friends to help them too. To me they are noobs, to you I am a noob.

OK - I am working on my own phone H830 first atm and I am running in one trouble after another. I looked up at the lineage installation pages for the different phones - no problem... I thought... every step I run into a problem and have to google for hours.

No I followed this guide here, and again.... OK what happened:

- MTP is not working for me - I have to use another mode so that ADB (etc) recognize the phone

- no matter which of the both tools of this thread here I use, it doesn't work. Ricks recovery seemed to work at first, but I always end up at the "no command" android picture...

I don't know what else I can do....

USB Debugging is active, bootloader is unlocked succesfully, "recovery.img" is at the right place...

Can someone help please? (I would prefer ubuntu, but because these tools here only run on win, I tried win again)
[T-Mobile LG G5 Guides, News, & Discussion] Madfrog22:
Quote : "2: Connect phone with pc in MTP mode and copy recovery.img to phone’s internal storage (Make sure to select MTP as always to avoid problem during procedure). Extract recowvery software. (If it causes permission problems extract it to USB device and perform process from there)"

which one is recovery.img? am i skipping something?
[T-Mobile LG G5 Guides, News, & Discussion] Madfrog22:
may i ask which one is recovery.img?

edit : i just realized, i need to rename my twrp img
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Did you format data once to remove encryption? If so then that's something related to fulmics, try installing anyother rom or fulmics without magisk.
[T-Mobile LG G5 Guides, News, & Discussion] zee360:
My bad,I thought wiping data and formatting data were same so i just wiped and that caused error,thanks for help.
[T-Mobile LG G5 Guides, News, & Discussion] bigfloppydb:
I'm having some trouble with this and was looking for some advice.

I started with a 20f install and reverted to 20a using the .kdz files with LGUP+uppercut. It runs fine and I enabled USB debugging and whitelisted my PC. My bootloader has been unlocked since just after I purchased the phone some months ago and has been a working phone since.

I followed your your instructions to the letter (very clear, thank you!) and even went so far as to run the fastboot oem unlock commands just to confirm I was unlocked. It confirmed I am unlocked so I ran the EasyRecovery.cmd from the Recowvery_G5_Modified folder. I will note that I tried this multiple times with the " 1 " folder on the root of my C: drive, then at the root of a USB drive, and ultimately on the root of my laptop. ADB and fastboot work fine on both devices and I can perform all of the steps of your instructions without issue until I hit my error.

On any attempt to run, it says that it doesn't look like an LG G5 and asks if I want to run anyways. When I hit "Y" it says that the device is locked and I can't get past that point. I went so far as to lock then unlock the device again using fastboot and going back to factory but that didn't resolve the issue.

I did some Google-Fu and did not come up with anyone else that is having my issue so I figured I'd reach out. Also, I'm no expert, but I've been flashing with adb and fastboot for years so I don't think it's user error, but it isn't out of the question...

Thank you in advance and for all of your work! Please let me know if you need any logs or output.

Cheers
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Is your antivirus turned off (In Windows 10 there is a built in antivirus too).

Try Using process on another pc, use different data cable and USB port. Make sure that in developer option "Enable OEM unlock" is toggled to on.
[T-Mobile LG G5 Guides, News, & Discussion] bigfloppydb:
I'll try the antivirus trick. I did try this on two different computers and the bootloader is fully unlocked and has been for months. I even locked and unlocked it again to be sure.

"Enable OEM unlock" is greyed out in the ON state as my bootloader is unlocked already.

The odd thing is that it sees the device just fine when I type adb devices and it shows as unlocked when I put it in fastboot mode and try to oem unlock it again.
[T-Mobile LG G5 Guides, News, & Discussion] bigfloppydb:
I was able to get it working. I had to use the device unlock app from T-Mobile to temporarily unlock my device (Permanent wouldn't work) then I could run the script. Thank you for your input and this awesome script!
[T-Mobile LG G5 Guides, News, & Discussion] qmarshall:
Permissions denied.

Everytime I run the file and press 2, it tries to copy the files and says permission denied. The phone is showing up in adb but it says could not obtain enough permissions to run exploit
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Did you read FAQ?

Extract toolkit in USB device and try process from there.
[T-Mobile LG G5 Guides, News, & Discussion] qmarshall:
Yes i tried running from a usb device as well and i still get the same problem.
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Is your antivirus disabled? Try running script with admin rights.
[T-Mobile LG G5 Guides, News, & Discussion] qmarshall:
My antivirus is disabled and ive trued running the program as admin, but when i do. The program says im missing exploit files, even though I'm obviously not because when I run it normally its fine. And just to make sure ive even redownloaded and extracted the files again multiple times
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Try process on different pc, windows, port and data cable.

Also you are on V20 Nougat firmware, right?
[T-Mobile LG G5 Guides, News, & Discussion] ceralor:
The issue I found has to do with the bundled vs system-installed ADB file. After installing Minimal ADB/Fastboot, launch it and run `adb kill-server`. Then, go to the directory minimalfastboot installed to and copy adb.exe, fastboot.exe and the two DLLS to the extracted directory for the easyrecowvery script. Then, relaunch the script, hit 5 for options, then I think 8 to toggle to 'external' and try again. May have to run 'adb kill-server' in the "minimal" CMD window again to get it to see the phone. Fiddle with it a little. :)
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
When rooted but encryption enabled does he safety net get tripped?
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Encryption has nothing to do with safety net but root has.

If you are rooted with magisk, then, there won't be any trouble with safety net (Make sure to read everything about it, including magisk hide stuffs).

But if you root with formal way, supersu, then safety net will fail, meaning no AndroiPay, Pokemon Go etc....
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
Thanks for the reply. This is more clearly explained than I have seen before.
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
I've tried this method a few times and nothing seems to stick. My phone just reboots in the middle of the process and if I and reboot to recovery it says "no command". I've read through the read me a few times and am following the instructions step by step.
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Did you copied recovery.img to interal storage of phone?
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
I tried it both in /sdcard/ and /emulated/0/ what ever (I don't remember the path right now)
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Which toolkit you downloaded recowvery G5 modified or Autorecowvery
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
Both with the same result
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
You need to disable integrity check in Autorecowvery by entering 5 then enter 7. It will represent integrity as disabled. In Recowvery G5 modifies you don't need to turn it off. So make sure you are following it.
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
I tried that as well

I'm not new to rooting and work in IT so this is odd to me that I cant figure it out

I've been on stock 20a and have held off on updating just so I could root at some point if I wanted.
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
I finally got it to work but forgot to flash the no verity zip so I'll try again this evening.
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Did you find the issue behind the problem for toolkit not working previously.
[T-Mobile LG G5 Guides, News, & Discussion] dksoni411:
Did you find the issue behind the problem for toolkit not working previously?
[T-Mobile LG G5 Guides, News, & Discussion] eremeya:
No. Maybe part of my problem was I saw it do a reboot to OS and thought it was not rebooting properly and would interrupt the process.
[T-Mobile LG G5 Guides, News, & Discussion] nicodelius666:
hi, is there a way to adapt this guide to an unlocked IOT_H850_Marketing?

If yes can you do this for my phone? I'm frustrated by impossibility to unlock it.....Tnx!
[T-Mobile LG G5 Guides, News, & Discussion] misquia:
I got to the part where I could format data in TWRP to remove encryption. After I had formatted, I rebooted, completely forgetting to mount my phone, put in SuperSU, and flash it and now I'm on the "Encryption unsuccessful" screen. Is there a way to go into TWRP through some button combination or do I have to just press the "Reset" button on the screen and start the process over again? Also, I've tried "adb reboot recovery", but it couldn't find the device when I was on the screen.

This should really be part of the guide I think.

EDIT: Pressing the "Reset" button put me in TWRP, I then proceeded to putting in no-verity-opt-encrypt zip (just to be safe) and then I flashed SuperSU afterwards, but it keeps rebooting me into TWRP when I try to reboot to system.

EDIT2: I just tried flashing no-verity-opt-encrypt, the 'H830_20F_DeOdexed' ROM, and then SuperSU, in that order, and it's still rebooting me into TWRP. I guess I'll just have to use UPPERCUT to get me back to stock.
[T-Mobile LG G5 Guides, News, & Discussion] musicims:
I'm having a hard time getting this to stick. Unlocked the bootloader for my 830, got everyhting I needed. Tried the Modified and the 1.3b3 keep getting "This device doesnt look like _____ Proceed anyway? Y/N" worked around by killing the adb server. Fine. all goes well until it needs to boot into TWRP. wont boot into it, restarts twice, boots back into OS. No twrp, flashing of no-verity-opt-encrypt. Flashed twrp sucessfully and my fastboot getvar shows unlocked bootloader

Really would like to know what eremeya did to get it to stick
[T-Mobile LG G5 Guides, News, & Discussion] musicims:
So heres what went down for anyone struggling with this.

I dont know which made it work but I was getting hung up at "This device doesnt look like _____ Proceed anyway? Y/N" worked around by killing the adb server. Fine. all goes well until it needs to boot into TWRP. wont boot into it, restarts twice, boots back into OS. No twrp, flashing of no-verity-opt-encrypt." Device was never booting into TWRP after flash.

Two things changed and I dont know which actually made the difference

Moved to another PC, did NOT install mini ADB since the boot-loader was already unlocked from previous tries/PC, ran from USB with 1.3b3 in ADMIN mode with no error like I was getting before. I think there is a conflict with ADB mini installed and the ADB in this exploit.

ALSO, and I think this is what did it, Used TWRP 3.0.2-1 instead of 3.0.2-0. This guide only states to use 3.0.2.

This immediately booted into TWRP, but it would not flash the rest of the zips. I had the zips on an external SD just in case so no biggie. Just alot of workaround. Thx for the tools, just alot of trial and error, really do appreciate the work put into this though, I can finally get what I need out of my G5!