[Recovery] [v510_palman] [2014-12-09] TWRP 2.8.2.0

[AndroidUser00110001]

TWRP 2.8.2.0​

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.

This is not an official TeamWin TWRP build. I used TWRP sources found HERE, device tree that I created for TWRP that can be found HERE.

Changelog:
CHANGELOG for 2.8.2.0 - From TWRP webiste...
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates

Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9

So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.

More info and changelog can be found on the official TWRP website HERE

Install Instructions:
With custom recovery already installed.

• Download
• Place zip file on phone
• Reboot into recovery
• Flash zip file through recovery
• Reboot

With stock recovery - Need ADB installed.

• Download zip file
• Extract recovery.zip to a folder on your computer. Example c:\recovery
• Open terminal window/command prompt, browse the the c:\recovery folder to execute following commands
• adb reboot bootloader
• fastboot flash recovery recovery.img
• use vol +/- to scroll through menu to select recovery mode
• press power button to reboot into updated recovery
• profit!

Download:
Download HERE

Credits:
@Dees_Troy
TeamWin
Everyone involved with TWRP.

PS...Working on CM12 for V510 now

 

[NHLWil]

Thanks!

It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.

 

[apvikes28]

Having some difficulty getting this to push through on the V50020d build. Thoughts?

 

[sleekmason]

Having some difficulty getting this to push through on the V50020d build. Thoughts?

This is only for GPE 510 devices. There is another thread for your device.

 

[AndroidUser00110001]

Thanks!

It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.

Can you flash the latest build, has today's date in it and see if it works now?

Thanks!

 

[NHLWil]

Can you flash the latest build, has today's date in it and see if it works now?

Thanks!

It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.

 

[aidfarh]

Can you flash the latest build, has today's date in it and see if it works now?

Thanks!

It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.

@AndroidUser00110001, maybe you need to have fstab.palman in the ramdisk, as described in this commit message: https://github.com/omnirom/android_bootable_recovery/commit/4eca40d7d8ff6968ed68a24686093cfb6f5f6373

 

[AndroidUser00110001]

It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.

Try twrp-2.8.2.0_v510-20141209.zip

 

[NHLWil]

Try twrp-2.8.2.0_v510-20141209.zip

Still no change.

 

[AndroidUser00110001]

Still no change.

What exactly is going on because I am able to mount and do whatever I need to do.

 

[NHLWil]

What exactly is going on because I am able to mount and do whatever I need to do.

And your device is encrypted running Lollipop?

With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.

However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.

 

[AndroidUser00110001]

And your device is encrypted running Lollipop?

With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.

However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.

Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?

I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.

 

[NHLWil]

Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?

I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.

Yes, my data partition is encrypted. TWRP 2.8.2.0 on the N5 supports decrypting data. TWRP 2.8.2.0 on the N5 will ask for your password as soon as it boots, and when you input the proper password, it will decrypt data so it can be mounted.

TWRP 2.8.2.0 on palman does not ask for the password as soon as it boots, thus data is not decrypted. The exact error is:

"Could not mount /data and unable to find crypto footer"

 

[jk8260]

TWRP 2.8.2.0​

PS...Working on CM12 for V510 now

OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...

 

[AndroidUser00110001]

OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...

invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.

I would say CM12 for the v510 in a week.

 

[sleekmason]

invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.

I would say CM12 for the v510 in a week.

Awesome news! That will open up a whole new world for kernel development too. Really looking forward to it. Thank you for your hard work. Takes hours/days to get there.

 

[galaxys]

invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.

I would say CM12 for the v510 in a week.

This would definitely be great for the GPE! Looking forward to updates...

 

[jk8260]

Any news on getting CM12 out for the V510 GPE, fingers crossed…

 

[sleekmason]

The device tree page won't come up. The link is broken.

 

[galaxys]

invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.

I would say CM12 for the v510 in a week.

Bump: Any Status or Beta's??