FORUMS

[UNOFFICIAL][DECRYPTION WORKS] TWRP 3.3.1 for UMIDIGI F1 [20191103]

240 posts
Thanks Meter: 735
 
By PeterCxy, Senior Member on 2nd November 2019, 02:39 PM
Post Reply Email Thread
Introduction

This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.

Known Bugs

- Screen may flash on the password-input UI. Anything else is fine though.

This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/and...gi-f1-t3997827) and it works fine.

This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.

Why Bother

Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.

Instructions

1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons

Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.

Downlaods & Sources

20191103: https://github.com/PeterCxy/android_.../20191103-twrp
- Fixed issues with Magisk and OpenGAPPS

20191102: https://github.com/PeterCxy/android_.../20191102-twrp

Device Tree: https://github.com/PeterCxy/android_.../tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery
The Following 5 Users Say Thank You to PeterCxy For This Useful Post: [ View ] Gift PeterCxy Ad-Free
3rd November 2019, 09:00 AM |#2  
PeterCxy's Avatar
OP Senior Member
Thanks Meter: 735
 
More
Updated to 20191103
The Following User Says Thank You to PeterCxy For This Useful Post: [ View ] Gift PeterCxy Ad-Free
8th November 2019, 12:14 PM |#3  
mrmazak's Avatar
Senior Member
Thanks Meter: 1,351
 
More
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img

This works good on my F1,

But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
9th November 2019, 06:41 AM |#4  
PeterCxy's Avatar
OP Senior Member
Thanks Meter: 735
 
More
Quote:
Originally Posted by mrmazak

I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img

This works good on my F1,

But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.

Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`
The Following User Says Thank You to PeterCxy For This Useful Post: [ View ] Gift PeterCxy Ad-Free
17th November 2019, 07:03 PM |#5  
Shadow Of Leaf's Avatar
Senior Member
Flag Casablanca
Thanks Meter: 346
 
Donate to Me
More
hello

im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???

thanks
17th November 2019, 10:08 PM |#6  
mrmazak's Avatar
Senior Member
Thanks Meter: 1,351
 
More
Quote:
Originally Posted by Shadow Of Leaf

hello

im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???

thanks

on other releases, no change was needed to boot on both. I would try as is first.

as long as you have working sp flash tool in case of issue.
17th November 2019, 11:35 PM |#7  
Shadow Of Leaf's Avatar
Senior Member
Flag Casablanca
Thanks Meter: 346
 
Donate to Me
More
Quote:
Originally Posted by mrmazak

on other releases, no change was needed to boot on both. I would try as is first.

as long as you have working sp flash tool in case of issue.

Cause i test it without changes , it reboot to system
I think because they have different kernels
15th December 2019, 08:05 AM |#8  
Junior Member
Thanks Meter: 0
 
More
I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?
16th January 2020, 10:26 PM |#9  
tarvoke's Avatar
Senior Member
Flag Slightly Outside America
Thanks Meter: 51
 
More
no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.

probably something stupid I'm doing wrong, will keep trying...
18th January 2020, 05:51 AM |#10  
SubwayChamp's Avatar
Senior Member
Thanks Meter: 1,001
 
More
Quote:
Originally Posted by tarvoke

for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.

probably something stupid I'm doing wrong, will keep trying...

You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.

Try installing:
- https://androidmtk.com/download-15-s...-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/downlo...-vcom-drivers/

Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices
The Following User Says Thank You to SubwayChamp For This Useful Post: [ View ] Gift SubwayChamp Ad-Free
18th January 2020, 03:12 PM |#11  
tarvoke's Avatar
Senior Member
Flag Slightly Outside America
Thanks Meter: 51
 
More
Quote:
Originally Posted by SubwayChamp

You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.

thanks!

adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.

this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)

like I said, pilot error lol. but thank you again for the reply!
The Following User Says Thank You to tarvoke For This Useful Post: [ View ] Gift tarvoke Ad-Free
Post Reply Subscribe to Thread

Tags
umidigi-f1

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes