UMIDIGI F1 Play

Search This thread

PunkJax

Member
Mar 10, 2013
21
4
Damn this is awesome. Should be pinned or put on first post.

Now that the F1 Play has its own forum/tag, it could probably just use its own thread so people can document their results with different GSI builds.

I'm a little busy this week to do anything more than just reply to stuff, but I may get around to making the F1 Play its own Treble/GSI thread when I get the chance to install one myself (unless someone beats me to it).
 

cml.snc

Member
Dec 26, 2015
47
3
Does anybody have issues with the fingerprint ...?? I'm able to wake up the phone but not to idle
Even if I change the "touch function" to have different choices in "click" "double click" and "long press"...
How to do implements this functions... ??
 

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Now that the F1 Play has its own forum/tag, it could probably just use its own thread so people can document their results with different GSI builds.

I'm a little busy this week to do anything more than just reply to stuff, but I may get around to making the F1 Play its own Treble/GSI thread when I get the chance to install one myself (unless someone beats me to it).

Where is the forum? I can't find it.

EDIT: Welp, rooted and got twrp on this thing from the UMIDIGI forums.... now I guess just wait for stable GSI for this phone and profit?

Anything I can do right now to exploit my root, besides greenify?
 
Last edited:

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Is the stock kernel controllable with Kernel adiutor? Is it possible to just flash a custom kernel? I guess we'll need a MTK specific kernel?
 

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Front camera does not work. Neither does night mode nor video.

Portrait, panorama and sphere view do work though.

It's made for a different hardware, therefore it's understandable that a few features don't work. But it gives me hope that we'll see a version for the Umidigi F1 Play, too.

I am using various camera apps, each serving its purpose. [emoji991][emoji4]

Gesendet von meinem F1 mit Tapatalk

Try this one:
https://f.celsoazevedo.com/file/gcamera/GCam_6.1.021_Advanced_V1.5.190418.1850.apk

Can take full 48 MP shots.

Works: Lens Blur, Pano, Camera, Photo Sphere.

But I really wanted night sight... I wonder how the p30 pro does it. It uses the Sony IMX 586, which other than being a true 48mp sensor as opposed to our fake stuff... We should have similar results, no?
 

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
Just received an OTA update. Despite the device being unlocked and rooted.
Screenshot_20190712-093059_1.jpg

Root is lost, so is unlock.

New camera app on top of the old one (which is still there).

New camera has night mode (working quite well).

All my custom ringtone settings have been overwritten with stock ones.

Android security patch STILL on January version. :mad:

EDIT: And STILL not able to connect to WiFi with hidden SSID. smh
Good job, Umidigi, good job. Thank you very much.

Gesendet von meinem F1 mit Tapatalk
 
Last edited:

BZ0RG

Senior Member
Jan 28, 2018
58
18

BlurtFlabber

Member
Jun 6, 2019
46
11
Just received an OTA update. Despite the device being unlocked and rooted.


Root is lost, so is unlock.

New camera app on top of the old one (which is still there).

New camera has night mode (working quite well).

All my custom ringtone settings have been overwritten with stock ones.

Android security patch STILL on January version. :mad:

EDIT: And STILL not able to connect to WiFi with hidden SSID. smh
Good job, Umidigi, good job. Thank you very much.

Gesendet von meinem F1 mit Tapatalk

After you mentioned this I went into the System Update option and "checked for updates".

Settings / System / Advanced / System Update

It said my system was up to date.

So, I went into:

Settings / System / Advanced / About Phone / Wireless Update

.... and it found the update!

Mine updated and added the new camera app, not to the main screen, but to the app list screen. It still isn't the most functional app (and yes, now there are TWO camera apps). I agree, night mode is amazingly good.

My system info is different than yours! It doesn't have an E in the number and ends differently. I'll attach a photo in my follow up post. I can't seem to locate where I saved it at the moment.

Oh, and the reason it's still on the old security patch, is that it seems this update was created back in January!

Not sure why they're sending out updates from January, and different versions as well.

---------- Post added at 11:04 AM ---------- Previous post was at 10:54 AM ----------

Can you report if geo-tagging is working ? I'm not able to have it with stock camera ?


Try to backup saved WiFi networks with another device using Swift Backup, then restore on F1 (require root).

geo-tagging works perfectly!
 
Last edited:

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
I didn't say that. But the phone is neither unlocked nor rooted anymore after the update. To root it again I would have to unlock it once again and that would mean another factory reset. And I don't feel like going through all the pain again to set up my phone like it is right now. All the settings, all the apps would be gone. [emoji20]

Gesendet von meinem F1 mit Tapatalk
 

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
flashed the latest OTA update and now I can't boot into system; only boot into TWRP... Guess I'll take this opportunity to flash a GSI bliss rom.
Anyone know what ROM I should pick? Are we A or AB Rom?

EDIT: Fastboot flashed Bliss ROM, when I rebooted it automatically took me to TWRP recovery again instead of booting up system.
EDIT: Flashed other other stuff too, but they all brought me back to the modded twrp during reboot to system... Is the F1 Play an A/B Slot device?
EDIT: Had to finally resort to flashing stock 2019070915 UMIDIGI ROM via flash tool; finally worked. Got Magisk back up and running, but I think I'm going to avoid TWRP. God damn, I spent so long setting up my phone.
 
Last edited:

amdeng

Member
Nov 28, 2017
6
2
Not sure if it was the update or not, but I was also stuck booting to TWRP no matter how many times I selected to reboot to system. Used flash tool to just get a fresh install and then rooted without TWRP instead. So far, I haven't had any recovery bootloop issues, so maybe there is a problem with TWRP and latest update right now. Anyone else have similar issues or know why this might have happened?
**After update and rooting via TWRP, I was able to boot into system for a few restarts but then got stuck booting to TWRP only.
 
Last edited:

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Not sure if it was the update or not, but I was also stuck booting to TWRP no matter how many times I selected to reboot to system. Used flash tool to just get a fresh install and then rooted without TWRP instead. So far, I haven't had any recovery bootloop issues, so maybe there is a problem with TWRP and latest update right now. Anyone else have similar issues or know why this might have happened?
**After update and rooting via TWRP, I was able to boot into system for a few restarts but then got stuck booting to TWRP only.

Must have been the OTA update... Do you have the Ghost#45 modded twrp from umidigi forum?
 
Last edited:

mrmazak

Senior Member
Jun 16, 2013
3,260
1,342
Blu Vivo XL
BLU R1 HD
These recent post , about loosing root after an OTA , are , well obviously correct.

OTA update is supposed to update the system and boot partition (even though this is system as root device). And this update process will remove root.
Because magisk root is on the boot.img.

As for the bootloops to recovery after the update, well that a known issue. And a somewhat simple solution.
The Stock system sets a reboot code into the misc partition. Or call it the " para" (parameter) partition. Stock recovery wipes this data on an update or reset. Twrp is not doing this. But you can clear the reboot recovery command using terminal in twrp.
I have even added the wipe command to my Own port Of twrp. (Added to fstab).
Code:
dd if=/dev/zero of=/dev/block/platform/bootdevice/by-name/para count=1 bs=32
Same thing I mentioned in this post a while back in the F1 thread.
https://xdaforums.com/showpost.php?p=79638705&postcount=2
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    New UMIDIGI F1 Play


    New thread for the new model UMIDIGI F1 Play Helio P60 Octa core Mtk 6771

    Umidigi F1 Play MT6771 Octa Core 4G LTE 802.11ac 6GB 64GB Android 9 Smartphone 6,3 inches

    black.jpg


    Attention this UMIDIGI F1 play is different from UMIDIGI F1 .
    the two models have different hardware and different Kernel !




    Everybody are Welcome!:good:



    MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
    More attention to the Xda-developers Rules:
    http://xdaforums.com/announcement.php?f=256
    Many thanks to "SUPER ADMIN" MR. MIKE​
    5
    Recovery modded +
    How to receive Right Root in this new Device
    F1_Play From UMIDIGI Brand


    Attention this UMIDIGI F1 play is different from UMIDIGI F1 .
    the two models have different hardware and different Kernel !


    This Thread is not for beginners and all the steps made will be down the warrancy at own risk.
    This tutorial will guide you through the process of installing a custom recovery image
    on your MediaTek based UMIDIGI smartphone and to receive right root access.


    Some possible issues that might need your attention:

    Custom recovery images of different Android versions are not always interchangeable. For example, you can't install an Android 5.0 recovery on a 4.4 system and so on. Any exceptions are mentioned in the list of recovery images.
    At most of the devices, after flashing the TWRP image, first you have to boot into recovery (TWRP) or the stock recovery will be restored.
    At some devices, after flashing TWRP, first you have to root your phone (install SuperSU or Magisk) or it won't be able to boot into the system.
    Once you've rooted your device, you won't be able to install OTA updates anymore but the only way to update your phone is flashing with SP Flash Tool. Flashing a stock ROM (with the stock recovery) will make you able to install OTA updates again.
    At some devices (or specific ROM versions), when powering on your phone to boot into TWRP (power + vol-up), after about 3 seconds, you have to release the power button (even if your screen is still black) and keep only the vol-up button pressed until the TWRP welcome screen pops up or the recovery will be skipped and your phone will boot into the system.


    What you need:


    Driver for Preloader USB VCOM mode:
    Windows 10 already can automatically install it or you can use this:
    MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe

    SP Flash Tool application:
    SP_Flash_Tool_v5.1812.rar
    Adb Command for Windows pc:
    Command adb for dos/windows


    A custom recovery image that fits your phone
    Scatter + Recovery twrp




    161731xmkc0140dfkkm0qk.jpg


    Test 1 Phase......



    @Everybody
    the custom recovery twrp test1 is already in testng phase.....................
    5

    Procedure to how to flash the Recovery into Umidigi F1 Play

    Now is not possible to flash the recovery throught flashtool because there is a bootloader locked so we must go ahead with adb command.

    1) download all the previous files;

    2) in Android F1 Play in "Settings System details" enter in about phone ot make visible the developer options click several times on about phone ....

    3) in Setting System will be now shown the developer menu' enter and switch to visible OEM unlocking allow the bootloader to be unlocked.

    4) reboot the phone and with power menu' and volume + in the same time enter in booting menu'.......select fastboot mode.

    5) Now in windws pc run the commad cmd or open a ms-dos window and enter in the adb folder ;

    6)write the command fastboot devices...and the phone connected with the usb cable must answer the command that is connected..

    7) use the command fastboot oem unlock and wait....

    8) copy with windows command the recovery twrp.img in the adb folder and renamed it with recovery.img
    to flash in the phone use this command : Fastboot flash flash recovery recovery.img
    the process will start ...and wait it...

    9) make this command to reboot into recovery mode: fastboot reboot.
    10) now take the buttons pushed with power menu' + volume + and select recovery mode....

    11) in recovery mode will show probably russian language...skip the alert with the arrow back and enter in details menu' on the right top to change the language...

    NOW NOT REBOOT INTO ANDROID SYSTEM WITHOUT MAKE THE ROOT STEPS
    because the android system protection will flash automatically the recovery original and all of you will lost the recovery twrp flashed before
    and all of you will repeit all the preious steps again

    How to Root your Umidigi F1 Play

    How to Root:
    Enter in the Recovery mode.....
    You need to FORMAT the partition given TWICE a simple deletion is not enough it seems in Android 7 and upper.
    Follow this procedure in this exact order and should solve most problems.

    1. Install TWRP through flashtool or adb command and then directly restore in recovery (twrp) do not enter in android system under penalty of twrp deletion and restoration of the original recovery.
    2. Select Wipe / Advanced / select date Yes to confirm. When finished, choose Restart, then always in recovery.
    3. Choose Wipe Advanced Format DATA again type Yes to confirm When it ends choose Restart always in recovery.
    4. Select Wipe and select cache and Dalvik scroll to confirm When it finishes choose Restart and always in Recovery.

    5. Now install Magisk 17.1 use this version tested
    Magisk 17.1 (Tested)

    you can restart in the android system and you will find magisk installed.

    For a full root you have to install from the play store busybox app and install the busybox binaries at least in sbin and bin (system folders) the app will guide you
    Busybox see here:
    lCkpBdZUgO3lB-ANrvlp0RE7D9w_LN3AUjYbRF3tgf4CizLs_xQiz1LwB5_GKiWPs_w=w300

    Busybox in the google playstore
    I prefer this app to others because of its track automation that doesn't require much experience.

    @Everybody
    the custom recovery twrp test1 is already in testng phase.....................

    4
    These recent post , about loosing root after an OTA , are , well obviously correct.

    OTA update is supposed to update the system and boot partition (even though this is system as root device). And this update process will remove root.
    Because magisk root is on the boot.img.

    As for the bootloops to recovery after the update, well that a known issue. And a somewhat simple solution.
    The Stock system sets a reboot code into the misc partition. Or call it the " para" (parameter) partition. Stock recovery wipes this data on an update or reset. Twrp is not doing this. But you can clear the reboot recovery command using terminal in twrp.
    I have even added the wipe command to my Own port Of twrp. (Added to fstab).
    Code:
    dd if=/dev/zero of=/dev/block/platform/bootdevice/by-name/para count=1 bs=32
    Same thing I mentioned in this post a while back in the F1 thread.
    https://xdaforums.com/showpost.php?p=79638705&postcount=2