[Recovery][ROOT] Twrp v3 For LG K20 PLUS

[ninjasinabag]

what i dont get is while ur k20 is off in fastboot i cant make any selections using volume keys can barely even see what it says the letters are so small nor power it off with the power button let alone have a keyboard accessible to issue a cmd in adb

help plz

What?
No.
Once in fastboot, don't touch the device.
Just use a command prompt on your computer.

Drop the recovery in your C:/
Change the name of the recovery to recovery.img
Now, using a command prompt with administrative privilege (since the recovery is in a protected filesystem) type in "fastboot flash recovery C:/recovery.img"
Don't include quotation marks in the command, please.

If you followed the directions, you have recovery.

---------- Post added at 12:09 PM ---------- Previous post was at 12:04 PM ----------

I have removed everything uninstalled delete everything and redownloaded it 3 times. I don't know why it doesn't see a device. I bought a brand new cord tried all the ports and I can't get it.

Install this specifically https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832

Go to your phone settings and set display to never turn off.
Go into developer options, tick OEM unlocking and adb debugging.
Connect your phone, open up an administrator command prompt. (Always use administrator mode. Always)
Type "adb devices"
Look at your phone, it'll show the device fingerprint.
Click on "always allow" then click the affirmative button.
Now it should show your device.

 

[josh2020glacier]

This is like the 5th k20 plus ive done and this giude works like a charm ty again lol

Now for my next one im gonna use magisk instead of su so i can still play my pokemon go without tripping it and not be able to play

 

[ninjasinabag]

This is like the 5th k20 plus ive done and this giude works like a charm ty again lol

Now for my next one im gonna use magisk instead of su so i can still play my pokemon go without tripping it and not be able to play

For starters, nice to see a fellow Josh.
Also, magisk will trip Pokemon go.
Remember to activate magisk hide, use the "change package name" option from the settings menu, then go into your file browser and delete any packages in your download folder from magisk.

That's what I had to do to get it to run.
Also, I'm pretty sure unlocking the bootloader breaks the GPS slightly, so use a GPS test app like GPS fix/options from the play store. Set it up, then use the test option from the overflow menu. Once it turns green, GPS has a lock and you can play.

 

[josh2020glacier]

For starters, nice to see a fellow Josh.
Also, magisk will trip Pokemon go.
Remember to activate magisk hide, use the "change package name" option from the settings menu, then go into your file browser and delete any packages in your download folder from magisk.

That's what I had to do to get it to run.
Also, I'm pretty sure unlocking the bootloader breaks the GPS slightly, so use a GPS test app like GPS fix/options from the play store. Set it up, then use the test option from the overflow menu. Once it turns green, GPS has a lock and you can play.

Good looking on the heads up but gos has been fine ty. Now on the other stuff def good looking almost forgot how been awhile lol

 

[zlost1]

Took me 99 tries but it worked. only thing i changed is how fast i clicked the power button

 

[Sugondese]

nvm

 

[messi2050]

nvm

Lol

 

[GXDA3]

Trying to root with broken power button...

im happy i got to test this out thanks for allowing me to

Hey so I have an lg k20 plus with a broken power button unfortunately I cant reboot into twrp after first flash... tried reboot recovery command in fast boot mode to no avail... anyone have any suggestions?

---------- Post added at 06:13 AM ---------- Previous post was at 05:45 AM ----------

I have flashed twrp successfully... but unfortunately I cant boot back into recovery for the first time because the power button is broken. Tried fast boot reboot recovery command and that's not working either... any suggestions? Please help.

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

I have flashed twrp successfully... but unfortunately I cant boot back into recovery for the first time because the power button is broken. Tried fast boot reboot recovery command and that's not working either... any suggestions? Please help.

 

[scorpio76r]

Hey so I have an lg k20 plus with a broken power button unfortunately I cant reboot into twrp after first flash... tried reboot recovery command in fast boot mode to no avail... anyone have any suggestions?

---------- Post added at 06:13 AM ---------- Previous post was at 05:45 AM ----------

I have flashed twrp successfully... but unfortunately I cant boot back into recovery for the first time because the power button is broken. Tried fast boot reboot recovery command and that's not working either... any suggestions? Please help.

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

I have flashed twrp successfully... but unfortunately I cant boot back into recovery for the first time because the power button is broken. Tried fast boot reboot recovery command and that's not working either... any suggestions? Please help.

Have you tried holding the volume up while connecting the USB cord to the pc?

 

[GXDA3]

Tried that

Have you tried holding the volume up while connecting the USB cord to the pc?

Yes all that does is put the phone into download mode...

 

[scorpio76r]

Yes all that does is put the phone into download mode...

I'm sorry, I forgot to twrp isn't flashed on the laf partition on this device. You may just have to fix the hardware button

 

[megaloli]

i cant get it to work

 

[messi2050]

i cant get it to work

There are some reports that lg is no longer allowing bootloader unlock after oreo update on this device so you may need to downgrade before you can be able to install twrp.

 

[Travisholt92]

There are some reports that lg is no longer allowing bootloader unlock after oreo update on this device so you may need to downgrade before you can be able to install twrp.

This device hasn't gotten an Oreo update from LG

---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------

i cant get it to work

You probably missed the step where you boot straight into recovery using the key commands immediately after flashing recovery when you pull the battery to leave fastboot
Also these twrp builds only work with 32bit (all of my builds worth running are 64bit and require a 64bit recovery. And Google drive flagged my PBRP builds for terms of service violation. I'll get an official build up soon. I already have official status for it, just have yet to compile an official build. I have to disable f2fs for the /data partition as it currently limits the partition to 4GB instead of the actual 20+GB that it is.

 

[messi2050]

This device hasn't gotten an Oreo update from LG

---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------


You probably missed the step where you boot straight into recovery using the key commands immediately after flashing recovery when you pull the battery to leave fastboot
Also these twrp builds only work with 32bit (all of my builds worth running are 64bit and require a 64bit recovery. And Google drive flagged my PBRP builds for terms of service violation. I'll get an official build up soon. I already have official status for it, just have yet to compile an official build. I have to disable f2fs for the /data partition as it currently limits the partition to 4GB instead of the actual 20+GB that it is.

yea i was mistaken between it and aristo 2.

 

[Travisholt92]

yea i was mistaken between it and aristo 2.

Yeah that turned out to be false, I don't know what the user did to allow OEM unlocking again, but he didn't have to downgrade to allow toggling that in developer settings. I've ported to 64bit to Aristo 2 finally, will be uploading the pbrp build here on XDA once I hit up admins to fork my tree. Merged the latest pie CAF tag into the stock oreo kernel, using nougat camera drivers, enabled usage of the DSP for audio on the msm8917 devices. The builds have been extremely smooth in comparison to stock and nougat builds. Also working on pie bringup for all of these devices now too. Its been a great learning process bringing this up by myself.

 

[messi2050]

Yeah that turned out to be false, I don't know what the user did to allow OEM unlocking again, but he didn't have to downgrade to allow toggling that in developer settings. I've ported to 64bit to Aristo 2 finally, will be uploading the pbrp build here on XDA once I hit up admins to fork my tree. Merged the latest pie CAF tag into the stock oreo kernel, using nougat camera drivers, enabled usage of the DSP for audio on the msm8917 devices. The builds have been extremely smooth in comparison to stock and nougat builds. Also working on pie bringup for all of these devices now too. Its been a great learning process bringing this up by myself.

seems you made a lot of progress in the previous months :highfive:, keep up the good work :good:

 

[marcuszmaximus]

What?
No.
Once in fastboot, don't touch the device.
Just use a command prompt on your computer.

Drop the recovery in your C:/
Change the name of the recovery to recovery.img
Now, using a command prompt with administrative privilege (since the recovery is in a protected filesystem) type in "fastboot flash recovery C:/recovery.img"
Don't include quotation marks in the command, please.

If you followed the directions, you have recovery.

---------- Post added at 12:09 PM ---------- Previous post was at 12:04 PM ----------



Install this specifically https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832

Go to your phone settings and set display to never turn off.
Go into developer options, tick OEM unlocking and adb debugging.
Connect your phone, open up an administrator command prompt. (Always use administrator mode. Always)
Type "adb devices"
Look at your phone, it'll show the device fingerprint.
Click on "always allow" then click the affirmative button.
Now it should show your device.

Hey I just wanted to chime in seeing as there are a lot of people who can't seem to get TWRP to open after flashing the recovery partition.

So I followed this guide step by step and could not get it the first time either (although the first time I did not take the battery out of the device). Once I took the battery out (the second try) I still ended up with the blah blah "we can't verify the security of your device so lock the bootloader back up" which prevented me from getting into recovery. The problem is that this screen pops up within a second of the LG logo, and the screen wont go away untill you depress and repress the power button.

Solution: just keep trying. I actually got into TWRP on the second try (each try i flashed recovery and then took the battery out). Needless to say I didn't follow instructions to the T for the TWRP part so I had to redo it again. And again. and again. Every time I would get to recovery it would tell me "No command" which means stock recovery partition. Eventually (after about 15-20 minutes) I was able to get TWRP to show up again. The trick was to make sure the vol down button was fully pressed down. In android prior to this I would always press vol up and then slide my volume bar down manually because the down vol button did not like to work. What I ended up doing was holding it down for the fastboot part and held it down in EXACTLY the same way as I did when I booted to the bootloader, except I applied a bit more pressure to make sure my finger didnt slip. If the LG logo shows up for more than about 3-5 seconds unplug it, take the battery out, go back into bootloader by putting the battery back in, pressing vol down, and attaching the USB cord. Once you re-flash recovery pop the battery out and remove the USB cord, put the battery back in and press vol down before power. When the LG logo screen shows up QUICKLY let go of the power button for a split second then hold it down again. If all goes well you wont get the security message untill AFTER recovery begins to begin Hope this helps!

In summary: just be patient and follow the instructions to a T. This method does work (I have the tmo variant TP260 on android 7.0) without an issue. Remember the old saying, "If at first you don't succeed, try try again".

 

[Travisholt92]

seems you made a lot of progress in the previous months :highfive:, keep up the good work :good:

Slowly but surely making progress. Pie bringup is in the works but not high priority as my desktop can't handle compiling it because of lack of certain CPU features. Will be building a Ryzen rig in the coming weeks so I can switch to pie development for all of these devices (both Aristo devices, stylo 2/3 plus, and the K20 plus). Battery life and stability are much better than nougat. Just lacking FP support right now but its pretty low priority to me.

 

[messi2050]

Slowly but surely making progress. Pie bringup is in the works but not high priority as my desktop can't handle compiling it because of lack of certain CPU features. Will be building a Ryzen rig in the coming weeks so I can switch to pie development for all of these devices (both Aristo devices, stylo 2/3 plus, and the K20 plus). Battery life and stability are much better than nougat. Just lacking FP support right now but its pretty low priority to me.

I have a similar issue, my 8gb ram is no longer good for compiling, it works but it can be much better with more ram.., i need to make an upgrade.