This is an attempt at rooting the UMIDIGI F2. Caution be advised, we are not responsible for your mistakes; but rest assured, most of them can be corrected.
Rooting the F2
Disclaimers
This is important, please read thoughtfully.
whatever you do, never ever use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never relock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like bootloops, if that happens to you don't freak out and reflash stock, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
Latest unofficial TWRP
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your packet manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT by selecting the scatter file, pressing download an rebooting the phone (Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
You can try without --disable-verity --disable-verification if those commands are not recognized. I have not tested without them.
6) fastboot --disable-verity --disable-verification flash boot magisk_patched.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img (recovery.img from stock)
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (vbmeta.img from stock)
9) fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM ("SPFT .zip") on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
TWRP
Device Tree
>> Download my latest build here <<
Flash in Bootloader mode with fastboot flash recovery twrp_f2.img
Android 10 and TWRP aren't compatible yet. /system and /vendor cannot be mounted. /data partition is encrypted. You can still flash .img and some zips that alter different partitions. Nothing I can do about it.
Misc
Different boot modes
Recovery / TWRP :
Turn off the phone (or reboot)
Press Vol+ and Power until some choice comes up to you
Navigate using Vol+, select Recovery Mode using Vol-
Bootloader mode :
Boot into TWRP, select Reboot, Bootloader
Or use adb reboot bootloader either in recovery or system
Or use fastboot reboot-bootloader in fastboot mode
Magisk and EdXposed
Fixing Magisk bootloop
Two techniques that could work after installing a module that broke everything :
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot.
Click to expand...
Click to collapse
-----
You could also try :
If you can't boot your device, this can be done by placing a file in /cache (/data/cache on A/B devices) named ".disable_magisk" (without quotation marks and with the leading dot). This will enable Core Only Mode and you can boot up your device, uninstall the troublesome module and then go into the Manager settings, disable Core Only Mode and reboot. In TWRP you can create the file through the TWRP terminal with the touch command, see below for an example.
Click to expand...
Click to collapse
Installing EdXposed
Please use the latest YAHFA or Sandhook canary build. I have a report of Xposed-SandHook-v0.4.6.1 (4504)-tdgptedc-release working.
_cab13_ said:
This is an attempt at rooting the UMIDIGI F2. For now, unsuccessful. Any help would be appreciated!
Click to expand...
Click to collapse
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate the "for developers" item in the settings (7 times click on the "build number" in the "about phone" settings at the bottom)
2) Go to "Settings"(the main screen of the application) go to "for developers" and move the switches to the enabled position near the items "USB Debugging" and " Unlocking the bootloader"
3) Then download platform tools from here https://developer.andr...eleases/platform-tools
4) Unpack the archive from platform tools to the root of the C: drive(so that the platform-tools folder is in the root of the C drive: )
5) if the process does not go install VCOM driver
6) Switch your smartphone to fastboot mode:
6.1) connect the included phone to the computer
6.2) Open the command prompt
6.2.1) Click Win+R
6.2.2) in the window that appears, write "cmd" and click " OK"
6.3) in the command line when the phone is turned on, write(without quotes)
6.3.1) " cd " (note that there is a space after "cd") and drag the "platform-tools" folder with the cursor to the command line window, press Enter
6.3.2) the Following command "adb reboot bootloader"
6.3.3) Your phone should reboot into Fastboot mode or a window should appear on the phone asking for debugging permission for this computer - put a check mark "Always allow debugging from this computer" and click "OK", repeat point 6.3.2
7) After that, on the computer in the same command line, enter " fastboot flashing unlock"
8) when the smartphone screen will prompt confirm by pressing vol+
9) after you see Finished, restart your device
Now the logo will be labeled Orange state when loading
I've rooted my F2. I used magisk to patch the boot.img then flashed the boot.img through fastboot on Linux. It didn't work with magisk 20.1. Had to used the newest magisk manager. I am interested in your twrp if you have one to try. Would you upload it so I may try to flash it.
Please upload your patched boot.img file. Thanks
I would love to have that boot image as well! What magisk version did you use then ? I can start crafting a guide.
EDIT: what boxes did you tick in Magisk Manager ?
EDIT 2: did you pad the boot image with DD ? Or maybe you wiped the boot partition beforehand to make it all zeroes ? It seems to be the missing thing and a known bug in Magisk.
Magisk 20.2 was what I used. Then flashed the boot through fastboot using Debian Linux.
Rooted f2 boot IMG
I've tried everything to get it rooted but any magisk patched boot image I flash just sends it into a bootloop including the one posted in this thread. It doesn't matter whether I flash it in Linux or Windows, in fastboot or in SP Flash Tool. What stock build are you guys on, the European or the Global? It seems that the boot.img is the same in both.
Apparently the issue is that the bootloader really doesn't like the fact that the image is not the full size of the partition. I'll try to dd it to the "max" size so it completely replaces the boot image and not only parts of it.
Seems to be an issue with the bootloader which doesn't like being flashed with a smaller boot image than it's partition size. Could you try padding it ? https://github.com/topjohnwu/Magisk/issues/2005
With this command
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
EDIT: Double post, my internet is pretty bad, I thought the first one didn't go. Can't delete apparently.
When I unlocked the bootloader I also unlocked critical areas
fastboot flashing unlock_critical
Warning---- this will wipe your phone again just like the bootloader unlock.
Haha seems to be the key to it ! Thanks for the update !
I've tried everything as well. Still bootloop. Your patched image doesn't work for me. I've unlocked critical as well as regular unlock.
1. Did you tick any box in Magisk Manager ?
2. Did you relock afterwards ?
3. What firmware version ?
I downloaded the new update today and I haven't been able to root the boot.IMG so far. I will keep trying and note anything that is successful.
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
This worked for me to reroot after the update today. Not sure what part of it is necessary for the boot image to work right though. I left off the userdata.img so I could keep my files in place.
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
Confirmed working, thanks. I ended up patching the new boot.img myself and that also worked. I own a Note 10 + and OnePlus 7 Pro and honestly I think the Umidigi is an awesome deal, everything is pretty good on the device. It's something I wanted to try out and I'm actually impressed.
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
ubuntuh said:
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
Click to expand...
Click to collapse
Currently there is no twrp recovery for the f2. I've tried a couple ports of twrp but can't get past the splash screen.
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
_cab13_ said:
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
Click to expand...
Click to collapse
True. Twrp just makes it quicker and has easier backup option
I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help
Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.
twelfth said:
Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.
Click to expand...
Click to collapse
Initially I just flash one slot. Then I read that inconsistency between 2 slots can cause problem, so I have flash 2nd slot also, by copy-partitions-20210323_1922.zip or by "fastboot flash boot_b ...".
Now, I can also recovery and boot back to stock rom, by flash boot.img extracted from stock rom.zip with the same version as mine.
So the KEY problem is:
Under TWRP recovery loader, with ADB sideload turned on, the PC seems cannot connect & send below crucial command to Android:
$ fastboot flash boot lineage-19.1-20220604-recovery-nio.img
N.B. I have already used USB driver from Motorola, so ADB commands can run without problem, except ADB Sideload mode. Also, I have tried using USB 2.0 hub port with 2.0 cable (4-pins) as well.
TWRP for nio is not stable (yet). Use the instructions for lineageos official.
patwwh said:
I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help
Click to expand...
Click to collapse
Late here but on 2a step, you can actually copy the ROM zip to internal storage since windows can detect your phone as storage device when it is in TWRP recovery.
https://wiki.lineageos.org/devices/nio/install is telling everything you need to know.
Though:
NEW:
Code:
fastboot devices
fastboot --set-active=a
// Update firmware
// Files taken from https://mirrors.lolinet.com/firmware/motorola/nio/official/RETEU/
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot erase carrier
fastboot erase ddr
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// First setup
// Files taken from https://mirror.math.princeton.edu/pub/lineageos/full/nio/
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// Install recovery
// Files taken from https://download.lineageos.org/nio
fastboot flash boot <recovery_filename>.img
for example:
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
fastboot reboot recovery
// Be sure all firmware is consistant
// Files taken from https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
adb sideload copy-partitions-20220613-signed.zip
fastboot reboot recovery
FRESH INSTALL OF LINEAGE
Code:
Reboot into recovery
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME A
Goto “Factory reset”
Goto “Format data/factory reset”
Goto “Format data”
Goto “Apply Update”
Goto “Apply from adb”
adb sideload <lineageos.zip>
Goto “Advanced”
Goto “Reboot to recovery” (now active partition is changed to the updated one)
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME SHOULD BE B!!
Reboot to system and setup...
(This is how I do it...)
(On updates, active partition is switching on reboot after you have done a flash of lineageos.zip file)
(Forget TWRP for this device as it is not finished and several bugs are there. Just use Lineage OS)
TWRP only works on Android 11, above that nothing will work and it will be very buggy
bootloader unlock
WARNING! THIS WILL VOID YOUR WARRANTY! IF YOU DO NOT KNOW WHAT THIS DOES LEAVE! THERE IS ALMOST NO SUPPORT FOR THIS DEVICE!
go to developer options and turn on oem unlocking
reboot to fastboot
Windows sucks for this because the drivers that you can find will not work!
install linux or in a vm
install fastboot and adb on linux
fastboot command: fastboot reboot bootloader
fastboot command: fastboot flashing unlock
reboot the phone.
you get a "orange" warning device will reboot it self.
done!
Root:
Hello welcome to this root tutorial of the IIIF150 R2022!
WARNING YOU WILL VOID YOUR WARRENTY!
UNLOCK THE BOOTLOADER FIRST!
EASY WAY NOT RECOMMENDED!
1. https://easyupload.io/0e0o5e MAGISK BOOT IMAGE
2. flash magisk boot image with fastboot
3. reboot phone
I DO NOT RECOMMENDED THIS! WHY WOULD YOU TRUST ME? IF YOU TRUST ME DO THE EASY WAY OTHERWISE DO IT YOURSELF!
NORMAL:
1. first download the STOCK os: https://firmwarefile.com/iiif150-r2022
2. download magisk on your device.
3. copy boot.img to your device.
4. follow the steps on magisk. choose the boot.img and let it patch.
5. put the file on your LINUX pc (windows is possible but it sucks because again drivers)
6. put your device in fastboot mode! NOT FASTBOOTD
7. on pc type: fastboot flash boot magiskbootimgname.img
8. YOUR NOT DONE!!!!!!!!!!
--------------
1. type these commands:
fastboot --disable-verity --disable-verification flash vbmeta (vbmeta file name you have download with the stock rom) click enter
fastboot --disable-verity --disable-verification flash vbmeta_system (vbmeta_system file name you have download with the stock rom) click enter
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img (vbmeta_vendor file name you have download with the stock rom) click enter
---------------------------------------------
YOUR NOW DONE.
IT IS POSSIBLE THAT IT DOES NOT WORK THE FIRST TIME IF IT IS STUCK ON BOOTING REFLASH MAGISK BOOT IMG
I've been waiting for this tutorial since November 2021, although I still have some doubts I'll try to do it.
Hello Any chace to have root tutoriel for IIIF150 B2021 ?
thibbea said:
Hello Any chace to have root tutoriel for IIIF150 B2021 ?
Click to expand...
Click to collapse
Use Magisk flash boot img with magisk
Hello all,
I rooted & unlocked my TMO OP9 using magisk and flashed a stock image.
I'm now trying to install a A13 mod from Pixel Experience. I patched the boot image after running the payload dumper tool. Now I have the patched boot image from magisk copied to my PC. I"m not sure what commands to run now once I reboot into fastboot. Maybe I'm not in the right fastboot (like fastbootd or something)
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> adb devices -l
List of devices attached
6bf0a351 device product:OnePlus9 model:LE2117 device:OnePlus9
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> adb reboot fastboot
<reboots>
<select fastboot from menu, reboots>
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> .\fastboot.exe flash boot .\magisk_patched-25200_aAy2x.img
< waiting for any device >
This fails as fastboot doesn't see my phone. I'm not even sure if I'm supposed to flash to <boot> or recovery.
I remember running this command below for disable-verity in the past but it fails as well. Probably due to a typo. If anyone can confirm that would be great. Do I use fastboot to flash to the boot? Like #fastboot flash boot <magisk_image>. I'm nervous that once I get the fastboot to flash i'll flash it to the wrong place.
PS C:\Users\cterr\OneDrive\Desktop\OnePlus9-December2022> fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
C:\Android\fastboot.exe: unknown option -- disable-verity
Thanks!