[LG V20 Questions & Answers] SimpleComplex778:
Hey all -

I'm trying to root my V20 with some complications along the way!

I'm currently at the Recowvery setup (I've tried manual & "Easy Recowvery") and I cannot seem to get past the "adb logcat -s recowvery" step.

On my command prompt, all I end up seeing is:

--------- beginning of system

--------- beginning of main

to no end. I've waited hours. No "successful" message as stated there should be when it finishes what it needs to do.

I have a feeling this is a permission issue, because when I tried to use the "Easy Recowvery" method, it had said it could not create log files, etc in the directory that I was trying to run the easy setup from.

I then tried to run CMD w/ administrative privileges - same problem, still stuck at the aforementioned information displayed. The only way I can then get out of this is escaping via "Ctrl+C", and nothing ends up being done, because when I try the next step "adb shell reboot recovery", my phone goes to a black screen that just says, "No Command" - and then I have to go into the usual recovery by holding the power button, then volume-up.

Are there any suggestions that could be made here? Tips, etc? I'm using the H918 version of the V20 and I would really like to get it rooted - wanted to use crDroid :3

EDIT (Guides I'm following):

The one from theunlockr

and then the dirtycow git page that's linked in another guide (I cannot post actual links yet, apparently :S)

EDIT2 (add'l info):

C:\adb>adb shell

elsa:/ $ cd /data/local/tmp

elsa:/data/local/tmp $ chmod 0777 *

elsa:/data/local/tmp $ ./dirtycow /system/bin/applypatch recowvery-applypatch

warning: new file size (18472) and file old size (165144) differ

size 165144

[*] mmap 0x747ac24000

[*] exploit (patch)

[*] currently 0x747ac24000=10102464c457f

[*] madvise = 0x747ac24000 165144

[*] madvise = 0 1048576

[*] /proc/self/mem 1367343104 1048576

[*] exploited 0x747ac24000=10102464c457f

dirtycow /system/bin/app_process64 recowvery-app_process64 <

warning: new file size (10200) and file old size (18600) differ

size 18600

[*] mmap 0x7331eb7000

[*] exploit (patch)

[*] currently 0x7331eb7000=10102464c457f

[*] madvise = 0x7331eb7000 18600

[*] madvise = 0 1048576

[*] /proc/self/mem -1971322880 1048576

[*] exploited 0x7331eb7000=10102464c457f

elsa:/data/local/tmp $ exit

Not sure if something perhaps went wrong here? Before having to execute the adb logcat -s recowvery command?

EDIT3 (Removed -s from logcat command to see what was going on):

I removed the -s flag from the logcat command to see where it might be stalling..... But after doing this I realized truly what was going on (logcat... duh, logging) - but I never get any kind of message that is said would occur:

adb logcat -s recowvery

"<wait for it to tell you it was successful>"

"[CTRL+C]"

I never get that message, with or without the silent flag.

I feel like the purpose of this step was to log recowvery running? Instead it seems like it's logging EVERYTHING.

Another guide I found said I should be putting my phone in the bootloader/fastloader before running the last bit of steps, but if I do that and try running the adb commands, it will say "null, no device available", or something along those lines.

I no longer know what is going wrong.

EDIT4 (-s is not silent flag when using adb?):

So it turns out the -s flag when using adb isn't the silent flag? Unless it is for logcat? Either way still nothing working. I never get "beginning of crash" like I'm apparently supposed to when running "adb logcat -s recowvery". Halp.