[RECOVERY][h815] TWRP 2.8.6.0 touch recovery [2015-06-02]

[Dees_Troy]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Phone look:


Tablet look:


CHANGELOG for 2.8.6.0:

-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

CHANGELOG for 2.8.5.0:

-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements

CHANGELOG for 2.8.4.0:

-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

CHANGELOG for 2.8.3.0:

-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements

Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.

DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

 

[Dees_Troy]

Note, only for H815 with bootloader unlocked!

Device specific page.

Download page with current and past versions.

Thanks to @wolfgart for testing!

 

[poczynek]

Yes yes yes!

 

[wolfgart]

Note, only for H815 with bootloader unlocked!

Device specific page.

Download page with current and past versions.

Thanks to @wolfgart for testing!

:good:

TWRP'd and rooted

 

[nickfury]

Great work guys.

Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.

But how do we get root @wolfgart?

 

[wolfgart]

Great work guys.

Getting my device soon hopefully. I understand that we can unlock the boitloader via the unlock.bin file and the fastboot flash the twrp recovery.

But how do we get root @wolfgart?

once you have TWRP'd just flash supersu.zip

 

[nickfury]

I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.

Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version

 

[Daptonic]

I was thinking exactly that. Thanks for confirming @wolfgart Much appreciated.

Now to see if it will work for h815t variant. I will try try it on my h815 and then my cousins t version

Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though

 

[nickfury]

Awaiting the outcome of your testing ... I have an 815T as well. No bootloader unlock for that one yet though

So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?

Sorry I don't have the t version on me right now to try it out, but will do in a couple of days

 

[the_scotsman]

So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?

 

[Daptonic]

So have you tried the official unlock method that has been outlined by lg for unlocking the bootloader for the h815 ( but in your case the h815t)? As in have you tried to enter the device Id of the h815t to see if you are actually able to download the unlock.bin file from the lg website or whether the website denies it?

Sorry I don't have the t version on me right now to try it out, but will do in a couple of days

I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.

 

[nickfury]

So we just unlock at the LG website (any other way to unlock yet?), then TWRP, then root?

Correct, if you have the h815 model

 

[the_scotsman]

Correct, if you have the h815 model

Yep, sure do. Tempting...not too fussed about about warranty, but would rather not void it if another way is found soon. What are the chances of this? I'd guess not very likely? I'm only familiar with HTC, no LG dev.

 

[nickfury]

I haven't as it specifically states " G4 (H815) for EU open market " ... which is not what I have. I'm in no rush and I'd rather get an exploit that doesn't officially void the warranty.

I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.

As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process

---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
@the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.

As for me I am importing the devices, so I don't have warranty to start with lol

 

[the_scotsman]

I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.

As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process

---------- Post added at 11:45 AM ---------- Previous post was at 11:41 AM ----------
@the_scotsman
As mentioned above, if warranty is your priority, then you shouldn't go down this path.

As for me I am importing the devices, so I don't have warranty to start with lol

Nah, warranty isn't a priority. I always unlocked and rooted my HTC flagships on the day I got them. I'm just new to LG, but it's not really any different. Just need to take that step and void it :laugh:

 

[Daptonic]

I think you misunderstand the very first bit of the unlocking procedure. Before you do any messing around ie flashing twrp, root etc, you need the unlock.bin file to unlock your bootloader, which is a very straightforward method outlined by lg.

As for your other concern, you can kiss your warranty goodbye as soon as you unlock the bootloader, as stated by lg. So if that is your worry then don't even bother with this process

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

As mentioned above, if warranty is your priority, then you shouldn't go down this path.

As for me I am importing the devices, so I don't have warranty to start with lol

I understand that I need the file ... for the official method. But that doesn't mean some crafty dev here @ XDA won't come up with a way that doesn't need it. Also, since the 815T, which I have, is NOT currently supported by the official unlock tool, your reply is moot.

There is subtle difference between going to their site, putting in my info and clearly voiding my warranty versus using an unofficial method and maybe sneaking in a replacement if things go pear shaped. I'm not worried about voiding my warranty, but why burn a bridge for no reason?

I thank you for your concern, but this isn't my first rodeo.

 

[calchung]

Can i use unlock the bootloader for h815t from LG?

Arent they (h815t & h815 for eu) the same?

I am confused....

 

[r3pwn]

EDIT: Ignore, didn't see the multiple pages.

 

[climo]

Can i use unlock the bootloader for h815t from LG?

Arent they (h815t & h815 for eu) the same?

I am confused....

No the H815T is for the Hongkong market not EU. I too have the H815T interesting to see if the unlocking tool works for this version. It might since its a 815 base model. :good:

 

[somboons]

Waiting for 818P