yashsingh1/xdaforums huggingface dataset:
[Android General] Weegee1:
If you go from a gsi rom back to stock, is there a way to fix the fingerprint that's not working
[Android General] d1876j:
I didn't experience that try doing a factory reset or use sp to flash stock select firmware upgrade
[Android General] wizbang80:
reread 12 times

after I read your response at least 12 times in passing it up on the page. I noticed the very first thing you said was camera app. if this is the factory-installed camera app then you should probably download a 3rd party camera app. the camera app as soon as I opened it started to freeze and I remember shutting it down and directly downloading a different camera. so I never experienced the bootloop or I would have returned the phone.
[Android General] Weegee1:
Flashing stock rom with sp flash tools restores fingerprint function, but when i try to flash eragon 1.0 it goes away again. Know of anyway to fix this or should I just stick to stock?
[Android General] d1876j:
Linage GSI is good Android 10
[Android General] txenglan:
For fingerprints? Didn't work for me and neither does Android Auto.
[Android General] Dalgorix:
Does someone have done a overclock version of kernel? I had try and nothing work...
[Android General] BZ0RG:
As far as I know, nobody has made a custom kernel for F1 play (and neither recent umidigi devices)
[Android General] nsiti:
Hi, my Umidigi F1 Play indicates it is on build number UMIDIGI_F1_V1.0_20190724

The wireless update says no update available and shows a longer build number: UMIDIGI_F1_V1.0_20190724_20190903-1850

Can anyone clarify whether I have the latest update? Thanks.
[Android General] InTheY2K:
Yes, that was the last update. Since September, 3rd (.... 20190903) the F1 Play has been abandoned.

Gesendet von meinem F1 mit Tapatalk
[Android General] nsiti:
Hi, and thanks for your response. So what ROM are you using since support stopped? I see there is an Eragon thread. I also picked up on an article citing an Android 10 GSI build by phhusson:

https://www.getdroidtips.com/android-10-umidigi-f1-f1-play/

Please fee free to share your recommendation as to which one I should switch to, or should I just stay put with the stock ROM?

Cheers!
[Android General] zironia:
I really like the umidigi devices but the updates end a couple months after they release. The gsi ROMs I have tried all have small issues that keep them from being daily driver for me. Eragons Rom is great. It's a tweaked stock rom. I plan to use the Eragon Rom then get a new phone next year.
[Android General] InTheY2K:
I am still on Stock ROM. As the current version of TWRP is not capable of doing backups/restore and the modified version, which does, isn't capable of flashing img files, I am still on hold until there is a fully functional TWRP for the F1 Play. Once that is available, and I can easily and safely go back to my backed up ROM, I might try something different.

As the Stock ROM is working fine for me I don't feel the pressure of moving to a Custom ROM, which might bring annoying bugs. Currently I live by the rule "never change a running system". :)
[Android General] txenglan:
FWIW, despite the issues with both variants of TWRP, I decided to make the switch from Eragon to the Lineage 17 GSI. What I've been doing is to back up using the modified TWRP then flash the img via fastboot. Not as convenient as being able to do all of it via TWRP but I feel better having security updates as opposed to running something that hasn't been updated since May of 2019. The only issue I have with Lineage 17 is that Android Auto doesn't work. Fingerprints don't either but then again, I had started to use other unlock methods on this phone since the FP sensor sucks anyway so I'm not bothered by that part.
[Android General] InTheY2K:
OK, if fingerprints don't work on Q then I'll stick with Pie. I use those a lot in various apps.

Gesendet von meinem F1 mit Tapatalk
[Android General] txenglan:
Fp might actually work for you. I think I may have lost them when I was messing around with the Dragon ROM. You might be able to keep them on Q as long as you Flash back to stock before trying the GSI. Not sure but worth a try.
[Android General] BZ0RG:
Hi there,

I didn't knew about the .img issue, but fastboot is a nice alternative if you don't want to switch between recoveries (or flash a ROM given in zip format).

GSI have working fingerprint, you may have messed up something.

From my point of view GSI offers higher customisation at the cost of some performance/battery backup. Some of them are bugless, but do not expect to have stock camera, which by the way isn't really reliable in all uses.

I personally run Eragon, skeleton1911 made an amazing job ??

I hoghly recommend his ROM if you don't mind sticking with Android 9.

Hence this device has an mtk chipset, it is really hard to brick it. You can use SP flash tool to get back on vendor firmware easily.

PS: there is a telegram chat, feel free to join us and keep in touch with news, get help or help others! ?

Link: https://t.me/umidigi
[Android General] Deaddpool:
Can we do all those things on xda? Why would I want to go to another venue? :silly:
[Android General] txenglan:
From what I've seen, you wouldn't get much help in there anyway. It's mainly just people posting pointless comments. About 1% of it is on topic and the rest is verbal diarrhea. No idea why people keep pushing Telegram for this kind of stuff. Not at all the right tool for technical discussion and collaboration.
[Android General] Deaddpool:
Agreed! Peeps be Cray Cray! No need to go offsite for that stuff when xda is here for such things! :good:
[Android General] vaderag:
What's the latest version of Google Phone (dialler) that people have working?
[Android General] Petesky:
Thinking of flashing the lineage rom , what camera app works best with it
[Android General] masbass:
Hi all, which version of modded GCamera is usable on this F1 Play? I had MGC_6.1.021_M18_V2e on it, tried some others as an update, none worked and when I went back to reinstall this version... it doesn't work and I'm stuck. Anyone can recommend a version they're using? Thanks
[Android General] Petesky:
Dont know if any work ,the latest port from Parrot043 is supposed to work on all android 9 and 10,

but didnt work on my f1 play, I was going to try flashing lineage to see if it worked on that but I'm holding back the now.
[Android General] BZ0RG:
This version doesn't work on my device neither.

There are very few working atm (no video):

-Gcam_6.1.021_advanced_v1.5.190418.1850

-Hypercam R4 / R6 / E3

Notice that hypercam require a specific XML file to work correctly.
[Android General] txenglan:
I was thinking about the recently disclosed Mediatek vulnerability. My understanding is that the March security patches for Google will address this issue but I'm a bit confused about how this works if it's actually something the vendor is supposed to patch (in the vendor partition). I'm using the Lineage 17 GSI so I assume the vulnerability will be patched but what else is in the vendor specific partition is subject to future concerns and/or can't be addressed specifically by Android security updates? Thoughts/insight appreciated from those more knowledgeable about the security impact of the new system & vendor partition layout.

Incidentally, I ran the script the dev created (diplomatic - https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213/page95) and the output seems to suggest that the F1 Play has already been patched. Would be interested of the output from other folks
[Android General] poog:
Was wondering what the consensus is on the quality of the main camera of the F1 play and what are the options for camera apps?

1) As I understand, there is no usable GCAM so far.........correct?

2) Can RAW DNG be done with any apps with the main sensor?

3) Is there any 4k video stabilization on stock or any apps?
[Android General] InTheY2K:
I am currently having a similar issue.

Previously, I used to be on the Magisk Beta update channel but changed to the "stable" channel. Magisk Manager kept telling me there was an update available (20.4 [20400]), and when I downloaded and installed it, nothing changed, it would still display the previous Beta build.

Then I decided to delete Magisk and re-root the device, took the boot.img from the archive of last Stock ROM update (20190903), patched it in Magisk Manager on my phone, copied it to my computer and tried to flash it, but now SP Flash Tool tells me

What does that mean, anyway? What is PMT, and what does SP Flash Tool mean by "it must be downloaded"? I presume, when I select "Format All + Download", my phone gets wiped to a factory reset.

I flashed Magisk before, without any such problem. Could TWRP interfere here, maybe? Should I go back to stock recovery? I can't boot into TWRP anymore. Using the key combination Vol+ and Power it does nothing, eventually boots into system. The same with TWRP App. When I select "Boot to Recovery" it boots to system. GAAA!

EDIT: Now, it's getting crazy. After several failed attempts to boot into recovery, I went to Magisk Manager once again, and now it shows "Magisk 20.4 (20400)" as installed. How can THIS be? All my flashing attempts were unsuccessful. And before that it would say, that Magisk is not installed. Does anybody have an explanation for this?

EDIT2: I checked Magisk settings, Magisk hide and SafetyNet. All good, all passed, all there. But now, after another reboot into system, Magisk is "N/A" again... what the heck is going on here?

EDIT3: Though I couldn't believe why the scatter file from the ROM that is currently installed would not fit, I downloaded the July version of the ROM (1.4GB over cell *sigh*) and extracted the scatter file from the archive. And wow, this one worked. Magisk would flash successfully! It makes no sense to me. But hey, it's a solution!
[Android General] alec.claire:
Hello

I have UmiDigi F1 Play stuck in a boot loop.

So, the phone was working fine on "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" updated via OTA. One day after a normal restart the phone went into a boot loop (UmiDgi logo, <thinking>, black screen (displayed not turned off), <thinking>, UmiDigi logo, and so on).

So, these are the steps I took so far with no luck:

1. Managed to get into recovery (pressing repeatedly Vol-Up while UmiDigi logo comes on), and did factory settings restart, still boot loop. "Mount /system" still boot loop. "Wipe cache", still boot loop. Also at times when I got into recovery browsing through the options was super slow - one pres vol-up or vol-down and it took three seconds to move to the next option in the menu.

2. Reflashed in Download only mode the ROM "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" via SP Tools, still boot loop.

3. Downgraded using Flash firmware mode to the oldest available ROM - "UMIDIGI F1 Play V1.0_20190409 ROM - SPFT release", still boot loop.

4. Formatted everything including bootloader, flashed again the newest "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release", restored IMEIs, still boot loop.

4. Occasionally the phone loaded the system, but after system restart there is still a boot loop. Moreover, in the top right corner there are two lines saying "TEE: <Chinese symbols> Google: <Chinese symbols>" visible at all times in Android, despite correct IMEIs being present.

5. Flashed again the newest "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release" but this time I've read somewhere to press and hold both vol-up and vol-down before connecting the phone to the computer to supposedly enter safe mode. It only resulted in displaying single green pixel in the top-left corner at all times in boot loop.

6. I've unlocked the bootloader via Developer options in Android when it miraculously loaded. Tried to flash TWRP via ADB - the phone displays that bootloader is locked. Tried flashing TWRP according to the instructions on the UmiDigi forum via SP Tools and there is a text under UmiDigi boot logo saying "Red state <you're using custom recovery use OEM recovery this will not start>". The text is displayed for a very short period of time and the phones goes again into a boot loop.

So to sup up:

- the phone has the newest stock ROM "UMIDIGI F1 Play V1.0_20190903 ROM - SPFT + OTA release"

- is stuck in boot loop (UmiDigi logo, <thinking>, black screen (displayed not turned off), <thinking>, UmiDigi logo, and so on)

- in the boot loop there is single green pixel in the top left corner at all times

- when the system occasionally loads there are two lines visible at all times saying "TEE: <Chinese symbols> Google: <Chinese symbols>"

How do I fix that guys? Any ideas?
[Android General] pro1.yoon@gmail.com:
I have use the method above and successfully rooted my F1 play. Only thing doesn't work is my camera. Camera doesn't focus to close distance, such as I can not take picture of documents. It looks all fuzzy. Any suggestion?
[Android General] scoobysnackster:
Decrpyting data paration and custom rom for Umidigi F1 Play.

I've managed to unlock the bootloader, root the phone, install twrp for umidigi f1 play.

Has anyone managed to solve the issue with the encrypted data partition and install a custom rom?

Any instructions would be appreciated, thanks.

I've tried formatting theinternal mem partition after typing yes in twrp. I've tried wiping data, system, cache and also formatting internal mem with ext4.

If you google custom roms for umidigi f1 play you'll find Andy Yan's personal builds of LineageOS 17 Umidigi F1 play Treble..

Following the instructions on gearallnews: I get stuck at the step which says " advanced wipe then the select system, data, Dalvik/ART cache, cache".. this returns errors with twrp.

Cheers
[Android General] alec.claire:
So, I've selected boot and system in "Download only" mode is SP Tools and did the following combinations:

- Vol-Down holding down before connecting to the PC and releasing as soon as download started, boot loop at the end of the process

- Vol-Down holding down before connecting to the PC and holding it entire download process, boot loop at the end of the process

- Vol-Up holding down before connecting to the PC and releasing as soon as download started, boot loop at the end of the process

- Vol-Up holding down before connecting to the PC and holding it entire download process, SP Tools stuck on a first red bar showing 100%; later the phone wouldn't power up

- tried connecting phone without holding any buttons, noting happened

- Power holding down before connecting to the PC , device recognised, and releasing Power button as soon as download started, the phone wouldn't power up

- selected all items of the ROM to flash, connected the phone without pressing any buttons, the flashing process started but error popped - ERROR status-download_exception (0x C0050003); changed USB ports, flashed again, powered on, boot loop

- selected again only boot and system, Power+Vol-Down down before connecting to the PC and releasing as soon as download started, error popped - ERROR: status_err (0x C0010001); repeated the process, flashed, boot loop

- Power+Vol-Down holding down before connecting to the PC and holding it entire download process, boot loop at the end of the process, error popped - ERROR status-download_exception (0x C0050003)

- Power+Vol-Up down before connecting to the PC and releasing as soon as download started, boot loop

- Power+Vol-Up holding down before connecting to the PC and holding it entire download process, boot loop at the end of the process

- Vol-Down+Vol-Up down before connecting to the PC and releasing as soon as download started, the phone wouldn't power on; started the download process and had to hold Power for a good 10 seconds before download started, boot loop

- Vol-Down+Vol-Up down before connecting to the PC and holding it entire download process, boot loop

- Power+Vol-Down+Vol-Up down before connecting to the PC and releasing as soon as download started, boot loop

- Power+Vol-Down+Vol-Up down before connecting to the PC and holding it entire download process, ERROR status-download_exception (0x C0050003), boot loop

So, no luck with the above combinations. I disconnected the battery but it didn't help.

Tips:

- if you want to access recovery while stuck in a boot loop hold down Volume-Up while UmiDigi logo displays and when it disappears start fidgeting Volume-Up, eventually after few good seconds recovery will load although it works super slow

- if you have a bricked phone, start the Download only process in SP Tools, hold down Power and connect the phone, give it few good seconds, should eventually start downloading

So, still no luck and still stuck in boot loop.
[Android General] scoobysnackster:
I've managed to solve the boot loop issue thrice. The third time I made a mental note of what I was doing.

1.You need to download the stock rom for F1 play and extract it.

2.You will need to reference three files from the extracted folder on the download tab of SP Flash.

The scatter file. When you select it, all the boxes gets checked. Uncheck all of them except for boot and system boxes.

Then make sure the boot.img is from the same extracted stock rom folder, make sure the box is checked.

Also make sure the system.img is from the same extracted stock rom folder, make sure this box is checked.

3.Click the download button. The stop button turns green.

4. Since the device is in a perpetual boot loop you are not going to have any luck turning it off,

which is why you press and hold down the power button- when the screen goes blank, connect it to the PC immediately, as soon as you see the red appearing, release the power button. Flashing will then commence and should be successful.

5.Also with SP Flash under "options", under connection usb=high speed, under download both checksums are checked.

If you are using Linux you will need to sort out the modem manager for SP Flash to work. If you look around you will find the commands to disable it.

6.If flashing was successful, disconnect. Holding down the vol down + power button you enter the recovery mode in mandarin, select last option and press power button, next screen says rebooting.. then power up, phone powers up with a reset.

You only need to flash boot and system images.

With my device, powering on the phone after fidgeting usually takes about 10-15 seconds. You need to keep the power button pressed for a bit- it may seem like forever.

Please let me know how you open the device. Do you need to unscrew the screws at the both near the usb c port? What screwdriver are you using? I need to open an F1 that I have bricked selecting all options of SP Flash download and flahing.:(

Ta
[Android General] BZ0RG:
Hello,

There is a twrp with encryption support on XDA.

There is only one custom ROM for the F1 play EU version, look up for Eragon F1 play by skeleton on XDA, this is based on stock android 9 and greatly improved.

The ROM you are trying to install is a GSI, you may have to flash permissiver zip. Notice that they are many more GSI available, some more stable than others.
[Android General] scoobysnackster:
Thanks, appreciated.

---------- Post added at 07:18 AM ---------- Previous post was at 07:11 AM ----------

Flash twrp img for F1 play using SP Flash. Download Fdroid apk and install it on the phone, then find Power App on it and install it. All you have to do is select reboot into recovery from it and the phone boots into twrp. This will save you the hassle of fidgeting with the key combo for recovery mode.

I managed to get a store to open the screws. I reckon, I need to buy one of those kits. If I can get the F1 going, I'll install LineageOs on it.

My boot loader is locked, the font is so tiny, I can barely read anything with a magnifying glass. It takes 5 seconds to boot which is when I press vol down + power for recovery.

The internal mem part is encrypted for versions 9 and 10 from the post I have read. Tried everything people have suggested in order to decrypted but no success.
[Android General] alec.claire:
Which one is it? Is it ported for F1 Play? Does in need some encryptions keys or are they auto generated?

1. UmiDigi F1 Play Bootloader Unlock

Make sure you have your IMEIs and MEID in present in the Android>Settings>About the phone.

1) Android>Settings>About the phone (tapping until developer options are turned on)

2) Developer options>OEM bootloader unlock (set to on)

3) Turn on USB Debugging (connect to a computer and when a prompt pops up on the phone tap to remember the computer)

4) Boot to recovery, from recovery boot to bootloader; or connect the phone to the PC and type in the Minimal ADB and Fastboot command "adb reboot bootloader"

5) Connect to the PC, run Miminal ADB and Fastboot.

6) In the ADB windows type "adb devices" press enter (you may have to to this twice)

7) In the ADB windows type "fastboot flashing unlock" press enter

8) The phone will ask you whether you want to unlock the bootloader - press Vol+Up for YES

After that on reboot there should be tiny text saying "Orange State... phone unlocked can't be trusted".

2. How to flash TWRP

1) Unlock the bootloader

2) Download stock ROM - https://community.umidigi.com/forum.php?mod=viewthread&tid=18874

3) https://www.getdroidtips.com/flash-twrp-recovery-mediatek-sp-flash-tool/
[Android General] BZ0RG:
Here is the XDA thread

https://xdaforums.com/android/development/recovery-twrp3-3-1-umidigi-f1-play-t4007315
[Android General] CustomOsLover:
Hello everyone

I have a problem

I wanted to Flash a GSI ROM to my F1 Play using TWRP

but

TWRP cant install .img.xz Files :(

How can I Flash those .img.xz files??

Thanks
[Android General] alec.claire:
Thanks man.

.xz is an archive file. You need to install program called 7z on your PC. Open .xz with 7z and extract the .img file. Then flash it.
[Android General] CustomOsLover:
Oh my God thanks so much!!
[Android General] alec.claire:
No problem. What are you flashing exactly?
[Android General] bentos:
HELP!

Does anyone know why some people are struggling with the bootloop issues and others seem to flash GSI roms without any issues. I tried for 2 days to flash a GSI (pixel experience) and always ended up with a bootloop.

I am not the most experienced but I have successfully installed TWRP/Orange fox and put roms on the following phones in the past: Nexus 4, Oppo Find 7a, Xiaomi Redmi Note 4

Unlocking the bootloader is straight forward. I can install TWRP and the stock rom will still boot. I can reboot to recovery and the stock rom will always work. As soon as I install a GSI I get stuck in a bootloop. I have followed many guides on XDA, Umidigi, and other forums without success.

TWRP being sourced from twrp.me/umidigi/f1play.html

I have used the DMverity patch which I believe should remove encryption but that doesnt seem to make a difference as the rom cannot boot. I have tried to install roms through ADB and from TWRP.

Is there any difference between the phone versions, China, EU, International? I wouldnt think there would be.

I have had to use the SP flash tool to revert back to the stock rom as I needed a phone.

Stock rom: V1.0_20190726

From reading this thread it seems there are many people who can flash roms over and over without being stuck in bootloop. The recent posts are others who are also having bootloop problems. Following the guides other people use are not successful for me and others.

Am I missing something that more experienced users would know? Do I need to install the stock boot.img after installing a GSI?
[Android General] alec.claire:
Try using this TWRP - a great improvement to the one available on TWRP's official website. https://xdaforums.com/android/development/recovery-twrp3-3-1-umidigi-f1-play-t4007315

BTW, I'm stuck on bootloop after ordinary restart on stock ROM. Occasionally like 1/20 times Android will start, but after restart phone goes into bootloop again.

Out of curiosity - does your fingerprint still work after reflashing stock ROM?