yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] nobreak1970:
Just really need a decent laptop and time. I don't have either :(

There are a lot of sites out there, mainly overseas for doing stuff with MTK devices.

I ported a working cm13 to an old BLU phone a few years back. Just takes time and patience. Lot's of files to replace and you have to know the MTK flash tool. Forgot it's name. Gathering driver files for all the sensors, etc. Opening base roms and replacing files, flash to test, wipe, do it all over again. Now I know nothing about GSI stuff. So that'll just take research.

The main thing is getting this device into a state where flashing a rom won't brick it. I don't know anything about the current Mediatek security loaders, etc. Unlocking the bootloader is easy peasy, don't even need root for this type of stuff really. I want to wait for the next official update from Umidigi, supposedly coming the end of May. IF we can flash GSI's onto this phone, we don't need to worry about rom updates from Umidigi in the future, ie Android 11, etc. There's no required file manipulation on our part to get a project treble GSI to work for us. the PHH GSI's are legit. Phil doing great work. We don't even NEED a TWRP to flash gsi's either since this phone is responsive to fastboot commands I think.
[Android Q&A, Help & Troubleshooting] smvsmv:
[MENTION=2930839]nobreak1970[/MENTION]

yeah, did some research and it seems to be quite cumbersome. Would've tried it if it was a bit easier. I'm actually surprised that it takes so much effort. Maybe it will be easier if UMIDIGI just gave us the code (not sure if Mediatek will allow) for Power 3 and we can just build it from there.

I tried to install a GSI and didn't get too far. Was able to start flashing using fastboot, but I got stuck somewhere saying that a system partition was not found.
[Android Q&A, Help & Troubleshooting] Fazee99:
Did anyone face issue related to microphone? Mine stopped working suddenly after month of use. I tried to flash it many times but same issue. Also my fingerprint option get lost from the phone after flashing.
[Android Q&A, Help & Troubleshooting] nobreak1970:
My phone had sound/mic issues but they seem fixed for no reason. what I did was disable assistant (JUST assistant "hey google" function) for a week. after about a week the issue with the bad speaker quality popped back up randomly, probably after a phone call or something. So I turned it ALL BACK ON, tried hey google...and haven't had the issue since. SO yeah..mystery fix.

PS: I just got a Pixel so Im moving on from this phone. Gonna use it as a backup battery. Peace guys.
[Android Q&A, Help & Troubleshooting] nobreak1970:
well I missed this big phone....so decided to try to activate my fi account on it. Works. I'll switch between my Pixel 2XL and this when I'm in the mood :)
[Android Q&A, Help & Troubleshooting] nobreak1970:
Welp someone on the official Umidigi forums posted a supposedly working TWRP for our device. PM me for the link. I don't know if I am allowed to link it here.

I don't have time right now to try it, but if someone wants to do it? It requires SPFT and a scatter file which is provided.

Not for the newbie flasher. ;)

---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------

If we can successfully do the basics on this phone eventually leading to a successful GSI flash....the world is ours. We'll be onto android 11 when it's ready and won't have to worry about umidigi updating ever again. :)
[Android Q&A, Help & Troubleshooting] flashallthetime:
Flashed the recovery IMG through fastboot and it just sits on the TWRP splash screen.
[Android Q&A, Help & Troubleshooting] nobreak1970:
ok ty for taking the time to try it.
[Android Q&A, Help & Troubleshooting] flashallthetime:
They're maybe a trick to booting TWRP that I'm not aware of. That's the problem when development is non existent on a device or not enough info available
[Android Q&A, Help & Troubleshooting] nobreak1970:
the person on the umidigi forum posted a scatterfile and said to flash it with the MTK tool.
[Android Q&A, Help & Troubleshooting] flashallthetime:
Shouldn't make any difference, I've always flashed recovery through fastboot. It flashed fine just hangs on TWRP boot screen
[Android Q&A, Help & Troubleshooting] Bratzilla:
A few (hopefully) helpful notes for rooting the Power 3

Just wanted to chime in, as I've just finished the Magisk procedure for my new Umidigi Power 3, with a few hiccups (but nothing terribly painful). I can verify that the procedure documented here and in the Umidigi F2 thread do work. The issues I had came with certain things that aren't detailed or otherwise took me quite some time to find. I've just plopped what I learned here for future reference just in case.

TLDR: SP Flash Tool method did not work because simply flashing the patched boot image caused a bootloop (my phone did not like the smaller/compacted boot image resulting from Magisk patch); Get full ADB Fastboot platform tools for Android, because the minimal version (Minimal ADB and Fastboot) didn't successfully run the --disable commands); make sure that Magisk is stored on actual internal phone memory NOT the SD card

Platform Tools-level ADB is needed: Minimal ADB and Fastboot don't seem to have the needed --disable commands required to flash the Magisk-patched boot image (I got unknown command notices). I had to download the full developer ADB found as part of Android Platform Tools and use that. Once I did, the various needed commands (--disable-verity, etc.) worked perfectly. I used the 2018 version available for download here. Yeah it's older but it does the job, and I've posted the link for that download just in case it proves helpful.

DO NOT use the SP Flash Tools method that you may find on the Umidigi official site or elsewhere. Through my adventures, I can verify that, indeed, you must use the

ADB Fastboot method

to avoid getting a bootloop (this was well explained earlier in this thread).

If you are using an SD card, make sure that Magisk is installed on your INTERNAL memory. It MUST NOT reside on the SD card!!! After re-flashing the patched boot image several times in frustration, I just found this nested deep in a thread at the official Umidigi site. I checked and, sure enough, Magisk was installed on the SD card. Once I moved it to internal phone storage, all worked as it should. Cost me hours of time due to this dumb oversight.

My phone is now rooted with Magisk (confirmed with various root checker apps) and running perfectly.

Hope this helps.

Regards,

Brat
[Android Q&A, Help & Troubleshooting] Apipote:
Good data.

Will I keep the OTA?

Thank you.
[Android Q&A, Help & Troubleshooting] Bratzilla:
I'm not sure. However based on information noted earlier in this thread, it seems that chances are you should be able to get OTA updates. But you should also be prepared to have to redo the root process as well.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Can someone post the boot.img unpatched? from v1.2. I got the file from umidigi but it's a boot.p file

NVM opened the wrong file.

---------- Post added at 10:39 AM ---------- Previous post was at 10:19 AM ----------

OK I'm rooted with Magisk. lol now what?

---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------

I'm old school rooter...is flashfire still a thing so we can flash stuff without a custom recovery? Or is it built into magisk? can we even flash magisk modules w/o TWRP? answer is YES.
[Android Q&A, Help & Troubleshooting] nobreak1970:
anyone playin with magisk modules?
[Android Q&A, Help & Troubleshooting] flashallthetime:
Some modules flash, problem I've run into is not all folders a rewriteable too , you only have read privileges in priv-app for example.

As for magisk boot img, I flashed it fine through minimal ADB fastboot and I had no issues at all

As for root at this point root for me was only required for substratum and android 10 has system wide dark mode now.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Well I guess I inadvertantly did a project treble test lol. I installed a module, pixel-something....can't remember full name, anyway it bootlooped me. so I was like, alright let's install a gsi..didn't work, partition issues but anyway I did a factory reset in recovery? Works fine, even AFTER doing a fastboot erase system command prior. So yeah...yay project treble! Phone recovered just fine with out having to flash a system image from umidigi via spflashtool.

welp, back to the gsi drawing board.
[Android Q&A, Help & Troubleshooting] flashallthetime:
It's going to be trial and error to get treble working that is if it will even work.

Let us know how you're making out cause 11 would be nice to have on this device.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Umm....this IS NOT MY WORK...but we got a booting TWRP!

flash it with:

fastboot --disable-verification flash recovery <filename>.img

filename=name of file

I renamed it to twrp.img on my laptop.

https://unofficialtwrp.com/root-twrp-umidigi-power-3/

It actually boots! Can't see system tho it seems.

DISCLAIMER: AGAIN, I didn't create this...the maker is in the link. If this screws the pooch for you ain't my fault. :)
[Android Q&A, Help & Troubleshooting] Apipote:
In my case, follow all the steps carefully and it gives me error when trying to unlock the bootloader. Any suggestion? Thank you.
[Android Q&A, Help & Troubleshooting] BigBlackMac:
TWRP System

Me too i've been able to successfully boot twrp with the DM-verity line but it can't see system partition, i too have tried to flash many GSI treble roms ( A and AB ARM64 ) in both sp flash tool and ADB , it always boot then directly goes to fastboot mode, anyone have got any custom rom working ? any information will be greatly appreciated

ps: i've got rooted with magisk and running fine

Update : root will work fine exept if it's system partition related, Adaway will not work and i can't modify any file in system , thinking it could be because the partition name on this umidigi is SUPER instead of SYSTEM

From my searches , devices that comes with android 10 is partionned way differently the partition SUPER is in fact smallers logicals partitions that makes one
[Android Q&A, Help & Troubleshooting] Tatsun0x0:
Research about Umidigi Power 3 (Global)

I had to do some research, myself, but it turns out that the latest stable shipped build for this phone isn't available for the community to download. You can compare this to the ROM details found in the Umidigi Power 3 Community forum.

[IMG="Umidigi Power 3 Shipped OS Build"]https://drive.google.com/uc?export=view&id=19CCg97Auv5LL5XAMxn2LxlHDvvnWtka-[/IMG]

I've been collating more information on this device and seeing that there is a TWRP recovery built for this phone without its sources is a big red flag for me. I would rather find a device tree containing this device and build it for myself just to be sure or if anyone has a device tree for this specific device then that would be nice. Also, I'm linking here the Device Specifications (GDrive) just for our reference
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

I tried a few of these ROMs too.. no luck. Per this article, if your phone doesn't support seamless update, LOS cannot be installed. Not sure if that's true and if it is, if it applies to other ROMs. UMIDIGI Power 3 doesn't support seamless. So, haven't bothered to try it. If you have any luck, please post the process here.
[Android Q&A, Help & Troubleshooting] Tatsun0x0:
Device tree for Umidigi Power 3 (TWRP)

Recently, I've got my hands on the actual device but I'm currently lacking the necessary information about it. Instead of facing multiple issues without any means to get back to the actual stock build, this should be the primary focus before delving into system modifications.

Device tree for Umidigi Power 3
[Android Q&A, Help & Troubleshooting] DragonPitbull:
Thanks for the instructions. They were very useful!
[Android Q&A, Help & Troubleshooting] DragonPitbull:
Since these informations by recovery stock and mine by mount partitions in TWRP.

Here's the recovery stock and recovery.fstab same by your?!

rename recovery.fstab.txt to recovery.fstab.

Maybe we have different models but the same partitions.
[Android Q&A, Help & Troubleshooting] smvsmv:
[MENTION=10612755]DragonPitbull[/MENTION] Have you flashed a GSI and it worked? If yes, which GSI?
[Android Q&A, Help & Troubleshooting] DragonPitbull:
I haven't tried anything!

But a guy who has the phone wrote about.

- unlocking the bootloader via fastboot (all data will be cleared), first enable the procedure in the developer menu by moving the slider:

fastboot flashing unlock

fastboot flashing unlock_critical - disable

boot verification by reflashing vbmeta.img:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

(but I still ran the following commands - not sure if they were necessary, but it didn't get any worse -

fastboot --disable-verity --disable-verification flash boot boot.img

fastboot --disable-verity --disable -verification flash vbmeta_system vbmeta_system.img

fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img)

-clean all data:

fastboot -w

-reset in fastbootd:

fastboot reboot fastboot

-clean system:

fastboot erase system

-GSI firmware-system:

fastboot --disable-verity --disable-verification flash system ***. img (instead of asterisks real file name)

-if there will be an error lack of system size, then run:

fastboot delete-logical-partition product, and then again flash the system-

reboot into the system:

fastboot reboot

======================= ======================= I

strongly recommend that before all experiments make sure you can flash through SPFlashTool (all necessary drivers are installed and smart connects for firmware), make backup via FT (Readback function) at least until the userdata section - not all sections participate in the stock firmware. And I also recommend making a backup copy of the settings of the MauiMETA radio module - they are individual for each smartphone, they can come in handy to raise the connection.

Naturally, all the bootable files boot, vbmeta, vbmeta_system, vbmeta_vendor and ***. img should be in the folder with the adb-fastboot files.

==============================================

If you do not know what do and are not ready to "raise a brick", then it’s better not to touch it - everything is at your own peril and risk .

To make you more informed and make everything more interesting:

fastbootd

gsi#flashing-gsis
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

[MENTION=10612755]DragonPitbull[/MENTION] Yeah, I tried that a while back.. didn't get too far and had to roll back to stock.
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

[MENTION=5312578]mrmazak[/MENTION]

I tried your instructions.. The GSI flash didn't work with "system". It worked when I replaced it with "super". The rest of your instructions, I followed as-is. I even tried with flash tool to replace "super". no luck.

However, even after that, the devices bootloops into fastboot. Tried at least 3 GSIs... any idea hot to fix this?
[Android Q&A, Help & Troubleshooting] mrmazak:
Flash tool and stock ROM package didn't restore it.?

I was told there may be 2 fastboot interfaces.

Fastboot that you get to from button combo reboot or adb reboot fastboot,

And

Fastboot.d that you get to by booting to recovery , and use the reboot fastboot option from recovery.

This fastboot.d is supposedly should recognize the system partition location.

If you took a gsi system.img and flashed it to super, that is a problem.

Super has more than system inside.
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

Thanks [MENTION=5312578]mrmazak[/MENTION]

I am able to revert back to stock without problems and also got Havoc GSI installed. Will keep this thread posted on how it performs.

Everyone,

Below is what I did. Some of these steps may not be required. I don't know which.

1. Download a AB GSI. I used Havoc-OS-v3.6-20200613-Official-GApps-arm64-ab.img

2. Flash the stock ROM. I used UMIDIGI_Power_3.E_V1.2_202003282206.

3. Boot into the stock rom. In developer settings enable OEM unlock and bootloader unlock.

4. Perform the below commands in adb

5. adb reboot recovery

6. Select Factory reset and reset.

7. adb reboot bootloader (or use the menu option)

8. fastboot flashing unlock

9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (from stock ROM)

10. fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img (from stock ROM)

11. fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img (from stock ROM)

12. fastboot -w

13. fastboot reboot fastboot (you should get to fastbootd menu)

14. fastboot erase system

15. fastboot delete-logical-partition product

16. fastboot --disable-verity --disable-verification flash system Havoc-OS-v3.6-20200613-Official-GApps-arm64-ab.img

17. Reboot to system.

Thanks to [MENTION=5312578]mrmazak[/MENTION] and a few other people on the internet. I just did this by trial and error. So, unable to help you with any troubleshooting. If you follow the above steps, things should work.

6/30: The above process works for all AB GSIs. However, getting root is an issue in all of them. There are modified magisk versions available, but no way for us to flash it. You can't flash it from the unofficial twrp because it says that system is not found. From stock recovery, sideload doesn't allow it to be flashed either.. so, I'm back on stock for now.
[Android Q&A, Help & Troubleshooting] nobreak1970:
can you provide some screenshots of the gsi installed?

:) :) :)

---------- Post added at 03:29 PM ---------- Previous post was at 03:29 PM ----------

because the command fastboot reboot fastboot never worked for me from day 1.

---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------

I'm mainly interested in using android 11 GSI's when they are out/proven/totally stable because god knows Umidigi won't upgrade us! ;)
[Android Q&A, Help & Troubleshooting] Tatsun0x0:
As far as I know, the recent TWRP version still does not support android 10 completely mainly because of the super partition and several others in comparison to android 9. Other devices or SoC's under android 10 may have gotten this to work but none that I know of utilizing MTK SoC's. I could be wrong though :confused:
[Android Q&A, Help & Troubleshooting] nobreak1970:
Don't even care about root to be honest...long as we can eventually get android 11 and beyond on this device.
[Android Q&A, Help & Troubleshooting] nobreak1970:
15. fastboot delete-logical-partition product

doesn't work
[Android Q&A, Help & Troubleshooting] DragonPitbull:
Maybe it's help you. Only testing you know!

#1.0.5

Updated to latest version again (07/05/2020);

Fully support for dynamic partitions.

[TOOL][WINDOWS] Adb and Fastboot Installer (Latest SDK update)
[Android Q&A, Help & Troubleshooting] nobreak1970:
I feel like such a noob! rotfl. I didn't even think about updating my fastboot and adb!

---------- Post added at 04:59 PM ---------- Previous post was at 04:57 PM ----------

So now my question is this: does the GSI roms make the phone any better performance wise?

---------- Post added at 05:10 PM ---------- Previous post was at 04:59 PM ----------

It's working THANK YOU SO MUCH! ITS BOOTING WOOT WOOT!
[Android Q&A, Help & Troubleshooting] DragonPitbull:
I feel happy that you did it.

Keep in mind about backing up phone files and always remember about the security of trying new GSI ROMs.

Maybe now you can install android R (11) by erfanoabdi?!

Generic-AB-11-20200618-ErfanGSI.img-2335.7z
[Android Q&A, Help & Troubleshooting] nobreak1970:
I am going to wait a bit on installing an 11 GSI. I have a pixel 2xl and am beta testing it now. Still a bit buggy but cool

ty again!

This phone will have life even tho Umidigi says no it won't lol

---------- Post added at 06:55 PM ---------- Previous post was at 06:04 PM ----------

OK so Havoc OS android 10 GSI:

amazing.

Fixes all issues that we dealt with using the stock rom.

Bluetooth range is improved.

Cam is better.

Volume and sound issues are gone.

NOTE: turn down animations to .5 or less in dev options. IT was .5 on our stock rom default so yeah...I guess the gpu is a bit wonky.

Question: updates? are there security updates built in via fota? or do we just flash the new version when they release em?
[Android Q&A, Help & Troubleshooting] nobreak1970:
ok so the audio issues still exist. hmm and the headphone jack doesn't work.
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI
[Android Q&A, Help & Troubleshooting] radikal-pr:
hello i followed the steps unlocked bootloader and did all the steps but the last step doesnt go thru to flash the system img

C:\android>fastboot --disable-verity --disable-verification flash system Havoc-OS-v3.6-20200613-Official-GApps-arm64-ab.img

fastboot: error: cannot load 'Havoc-OS-v3.6-20200613-Official-GApps-arm64-ab.img': No such file or directory

in the folder "android" i put in the havoc image i tryied renamed it in a shorter name but still it doesnt find it no matter what i try in doesnt flash....

this steps worked...

9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (from stock ROM)

10. fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img (from stock ROM)

11. fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img (from stock ROM)

does somebody know what am i doing wrong?
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

What about steps 12 through 15? You MUST be in fastbootd (not fastboot) to flash to system. If you are unable to get to fastbootd, you probably have to update ADB and fastboot. Install latest version.
[Android Q&A, Help & Troubleshooting] nobreak1970:
I reverted back to stock for now but its' a fun experiment. VoLTE and WiFI calling are too important to me and it seems no GSI can implement them currenty.
[Android Q&A, Help & Troubleshooting] radikal-pr:
Thank you it was my fault, I just changed windows and didn't see the extension I needed to extract the system IMG, it looks ok now to find a way to change the time on the notification bar it's right in front of the punch hole camera
[Android Q&A, Help & Troubleshooting] nobreak1970:
some really cool magisk mods that work for our rooted phone?

Google Dialer Framework so you can install actual google dialer, use call screening, etc.

Motorola Clock/Weather widget. works very well

umm....that's about it to me lol. anyone got other suggestions?
[Android Q&A, Help & Troubleshooting] smvsmv:
magisk

App Systemizer - allows you to systemize apps
[Android Q&A, Help & Troubleshooting] radikal-pr:
hello does somebody know if there is a twrp working for umidigi power 3, im flashing gsi roms and they updated quite a bit, but everytime i have to erase data
[Android Q&A, Help & Troubleshooting] smvsmv:
TWRP

This is the only one available. It doesn't give you anything that ADB/Fastboot doesn't give you.

I've tried the GSIs and was unable to get root on any of them. I think without deleting data, your results will be unpredictable given that GSIs are wonky in the first place. Let us know how it goes for you.

https://unofficialtwrp.com/root-twrp-umidigi-power-3/
[Android Q&A, Help & Troubleshooting] radikal-pr:
i just used that one and got bootloop i also flashed vbmeta but still boot loop. strange i put stock recovery and boots right away
[Android Q&A, Help & Troubleshooting] smvsmv:
unlock bootloader

Make sure you follow the steps listed here exactly how it's listed. It's for F2, but I can confirm that it works for me.

https://xdaforums.com/android/general/guide-rooting-umidigi-f2-t4030407
[Android Q&A, Help & Troubleshooting] radikal-pr:
ok thats to install magics i just need twrp, can i install twrp from f2? ok maybe the problem that i have is that im already in gsi not in stock thats why it doesnt boot en twrp