UMIDIGI F1 Play

Search This thread

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
Thanks for the explanation.

In other words, there is no getting back to root without wiping the phone and reinstalling/setting up everything from scratch?

I'll pass then. :(

Gesendet von meinem F1 mit Tapatalk
 

mrmazak

Senior Member
Jun 16, 2013
3,260
1,342
Blu Vivo XL
BLU R1 HD
Thanks for the explanation.

In other words, there is no getting back to root without wiping the phone and reinstalling/setting up everything from scratch?

I'll pass then. :(

Gesendet von meinem F1 mit Tapatalk

Choose your own, but that is not quite what I am said.

Well, if the bootloader is getting relocked, then yes, that forced locking step , most likely will trying force a wipe. HUM, which might be what is causing the bootloop.

. ok , im off the download the update so i can read the updater-script.

--- nothing special in the script.
;(
 
Last edited:

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
Choose your own, but that is not quite what I am said.

Well, if the bootloader is getting relocked, then yes, that forced locking step , most likely will trying force a wipe. HUM, which might be what is causing the bootloop.

. ok , im off the download the update so i can read the updater-script.

Alright, I checked again and take back everything.

In the developer settings the switch "OEM unlock" is disabled and says bootloader is unlocked. Therefore I rebooted the phone and the splash screen still shows the warning message that the device is unlocked and can't be trusted.

I'll push the modded boot.img again and see if that works.

EDIT: IT DID! Hooray! As easy as 1, 2, 3... Indeed the bootloader unlock was left untouched by the OTA update. I managed to flash the patched boot.img again, and back I have my root access. Yay!

Now I can try to change the WiFi settings according to the recommendation of @BZ0RG

---------- Post added at 15:09 ---------- Previous post was at 14:28 ----------

Can you report if geo-tagging is working ? I'm not able to have it with stock camera [emoji848].
CONFIRMED! I just shot a photo with geo-tagging enabled, and Google photos shows me my location on the map.

Try to backup saved WiFi networks with another device using Swift Backup, then restore on F1 (require root).
Didn't work. I backed up the WiFi connection from my old Samsung Galaxy S4, which is able to connect to the hidden network, and restored it onto my F1 Play. But alas, it behaves the same way as if I entered the details manually. Shows the network but does not connect to it. :(
 
Last edited:

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Was on sale at Amazon for 20% off for Prime Day. Bought another one, returning it again at the old price for my first order. $239 CAD no tax for phone with 5000 maH and 6 GB RAM. No brainer.
 

BZ0RG

Senior Member
Jan 28, 2018
58
18
Didn't work. I backed up the WiFi connection from my old Samsung Galaxy S4, which is able to connect to the hidden network, and restored it onto my F1 Play. But alas, it behaves the same way as if I entered the details manually. Shows the network but does not connect to it. :(
Sorry to hear this ??
Worked for me with a WPA2-TKIP hidden SSID WiFi.

---

Can someone share the new camera package please ?
 

Attachments

  • Screenshot_20190716-182731.jpg
    Screenshot_20190716-182731.jpg
    126.8 KB · Views: 114

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
Sorry to hear this ?
Worked for me with a WPA2-TKIP hidden SSID WiFi.
But does the F1 Play connect to that network, too? Saving it does work for me. The device also recognizes when the network is in reach and tries to connect, but seems to give up after a while. :(

---------- Post added at 18:52 ---------- Previous post was at 18:47 ----------

Can someone share the new camera package please ?

Do you need an apk or will a .tar.gz do as well (backed up with Titanium)?
 

BZ0RG

Senior Member
Jan 28, 2018
58
18
Yes, flawlessly !
I restored the settings as previously said, and every time I turn on WiFi it does connect to the network asap.

Do you need an apk or will a .tar.gz do as well (backed up with Titanium)?

APK would be easier to deal with, choose the easiest method for you ??
 
Last edited:

InTheY2K

Senior Member
Oct 20, 2017
765
365
Tønder
hundebetten.shop
Yes, flawlessly !
I restored the settings as previously said, and every time I turn on WiFi it does connect to the network asap.



APK would be easier to deal with, choose the easiest method for you [emoji1303]
This is the apk but zipped (as it was 115MB when I exported it as apk).You need to unzip it first.


Tell me when you have it, so I can delete it from my drive.

Gesendet von meinem F1 mit Tapatalk
 
Last edited:

Coffee Freak

Senior Member
Sep 22, 2014
165
53
Boykins, VA.
Sorry if this sounds a little nooby but does this device support Substratum theming? I love the phone but not all the bright white theme. Just can't see going to the trouble of rooting it if I can't change that. If a rom came out I liked then I can see it but not yet if it can't be themed. Thanks in advance for any input.
 

d1876j

Member
Jul 2, 2018
47
9
Sorry if this sounds a little nooby but does this device support Substratum theming? I love the phone but not all the bright white theme. Just can't see going to the trouble of rooting it if I can't change that. If a rom came out I liked then I can see it but not yet if it can't be themed. Thanks in advance for any input.
It can't be themed google block pie unless you root the device
 

Coffee Freak

Senior Member
Sep 22, 2014
165
53
Boykins, VA.
Well, since nobody knew, I bit the bullet and rooted the phone. Tried Substratum. It doesn't work on this device. The firmware isn't stock enough I guess. So in my opinion it's a good device but what's the point of rooting if you can't mod it. Maybe custom ROMs in the future but right now it's a waste of time. I have been buying Umidigi devices for 3 years now. They never get security patch updates or major os updates just minor bug fixes. When they get to be a year out of date on the security patch I give them to my kids. Shame, because they are good solid hardware.
 
  • Like
Reactions: carl.13

convolution

Senior Member
Nov 17, 2010
798
166
Vancouver
Anyone having settings force closing when you insert an sd card and try to click on "storage" in settings?

I'm trying to install a 128 Gb Samsung EVO sd card in the phone...
 
Last edited:

PunkJax

Member
Mar 10, 2013
21
4
GSI ROMs are available, you may have to deal with backing up and restoring IMEI beforehand.
Ask umidigi advanced user about what is currently (/not) working ?

You don't lose your IMEI as long as you properly read the instructions on how to use SP Flash Tool (their translation on the app itself is weird and the "obvious selection" in English is the wrong option and deletes your IMEI). Regardless, you should make a copy of your IMEI or take a pic of it when you get a new phone.

I WOULD still look into ways of backing up stuff because unlocking the bootloader factory resets the phone.

From what I hear, GSI ROMs generally have issues with VoWifi and VoLTE. There may be ways to get around this, but I am not too familiar at the moment. Will have to do some tests when I get the chance next month.
 

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