yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] geoffwdixon:
I found all stock roms contained audio issues with early stock roms sporadically losing audio altogether.

Can you please advise the exact stock rom you flashed?

UMIDIGI Power 3 E_V1.1_20200116_2148

UMIDIGI Power 3 V1.1_20200116_2033

UMIDIGI Power 3 E_V1.1_20200112_2306

UMIDIGI Power 3 V1.1_20200112_2010
[Android Q&A, Help & Troubleshooting] guigui31140:
Solution for headphone

Just download "Lesser AudioSwitch" on playstore ;) it force sound on jack
[Android Q&A, Help & Troubleshooting] radikal-pr:
Hello does somebody know how to fix the Bluetooth for headset? I'm using LG tone on the power 3, I'm on havoc 3.8 everything is well for hearing music the problem is when I'm in a call I can hear my own voice on the headset and the background noise doesn't let me hear the other person well, that doesn't happen on stock rom and had happened on havoc gsi 3.6, 3.7 and 3.8. somebody told me that it could be the vendor file. That's the only bug I found the rest is ok
[Android Q&A, Help & Troubleshooting] Compacthack:
I had similar issues with 3.7 on my Umidigi F2, could listen to podcasts and audiobooks no probs in the car on bluetooth, but phone calls were the same as You described .

I haven't tried 3.8, whats it like ? Much different than 3.7 ?
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Audio Issue Chart

Morning All.

The chart below shows what sound issues are produce when specific settings are used. Youtube and a music app was used to produce sound though the phones physical speaker.

Please note this is not 100% complete and I am assuming everyone has the same sound issues on there devices.

I would love to test Bluetooth and phone calls but this took many hours of testing. Maybe in the future.
[Android Q&A, Help & Troubleshooting] radikal-pr:
Well I haven't found a problem yet, the only problem is with the Bluetooth headset, but I think the speaker is a little lower than stock and there's no way to go to engineer mode to fix it but besides that the rom is great
[Android Q&A, Help & Troubleshooting] radikal-pr:
Hello can you share the command you used to flash the vbmeta.img, from your post. I try to flash it but it doesn't let me, it only lets me flash stock vbmeta, with yours it gives me an error in fastboot
[Android Q&A, Help & Troubleshooting] smvsmv:
I used the same format - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Make sure you are in fastboot and NOT fastbootd. What error are you getting?
[Android Q&A, Help & Troubleshooting] jdrom:
Thanks for doing this, reflects my experiences so far too, though I didn't bother trying the EU firmwares.

One thing I'd like to add though, I had done a "format all" flash with the SP Flash Tool [do not do this!] (had to send Umidigi Ben $15USD to get my fingerprint re-activated), but I noticed when I had the so-called "blank" NVRAM data (IMEI was some generic looking one, no serial number, no fingerprint), the audio was fine even on firmware V1.2. Kind of leads me to think the issue lies there, and would explain why having V1.2 and moving to Treble ROMs still has the audio problems.

I will stick to V1.1 for now as it seems to mostly work, and disable the Google Assistance voice on every screen option.

I tried building an overlay for Phh-Treble but I can't figure out how to get it copied to /system... anyone have any ideas? Tried as adb root, adb remount, chmod 755 but it doesn't survive a reboot.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Thank you for letting me know you has a similar experience with the different firmware versions.

I would just like to note the dangers in using this "Format All + Download" option. I do not recommend it be used at this stage as a solution for the audio issues .

Correct. I am using version V1.1_20200116_2033 with google assistant on but the voice match option off. This seems to be the most reliable version.
[Android Q&A, Help & Troubleshooting] jdrom:
True enough, edited my post to add a note to not do so :)

In my case, I was trying to get the phone back to stock, but for whatever reason it kept saying the image was corrupt on boot and I had to press a key to continue anyways. Format All fixed it, but in turn "broke" the IMEI/MAC/GoogleKey/Fingerprint. Thankfully Umidigi has a recovery process.

Sounds like they're still working on an update to fix the speaker issue though, as I mentioned it to Ben at Umidigi when I requested the fingerprint activation.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Glad you were able to get it fixed. Any tips if someone here finds themselves in the same boat?

I know its super easy to select the wrong option from the list. I myself have come close many times already.

Im happy to hear there might be some hope. But April is the last we heard from them on there website so im not holding my breath.

Roughly when did Ben mention this? Recently?
[Android Q&A, Help & Troubleshooting] jdrom:
These 2 posts mostly cover it, though I would recommend selecting IEMI, WiFi, BT, Barcode (serial number) and MEID in the SN Writer tool. The WiFi and BT MAC addresses you can just auto-generate, unless your router happens to have a history of it still. The rest are found on the box/sticker that the phone came with.

https://community.umidigi.com/forum.php?mod=viewthread&tid=1375&extra=page=1

https://community.umidigi.com/forum.php?mod=viewthread&tid=19007&extra=page=1

But of course, do not do a "format all" unless you really have to!

Earlier this week as I mentioned in my email after getting the fingerprint activation file back from him how the sound worked fine in V1.2 when my NVRAM was blank/corrupt. Figured it might be a useful data point for their developers.
[Android Q&A, Help & Troubleshooting] Hobler:
Works perfectly, thank you very much. Only about 5 minutes to root a phone is my new record :victory:

(I patched the boot.img with my old phone which was also rooted)
[Android Q&A, Help & Troubleshooting] radikal-pr:
Somebody know how to raise the volume on gsi rom, engineering code doesn't work and I fell that the sound on the earpiece is a little low but don't know how to raise it a little more. Any suggestions?
[Android Q&A, Help & Troubleshooting] plumpkibbles:
I'm getting FAILED (remote: Operation not permitted) when flashing system image, and I'm not able to issue 'fastboot delete-logical-partition product' either. Command not recognized.. Something I'm possibly doing wrong? Not my first flashing either..
[Android Q&A, Help & Troubleshooting] smvsmv:
Make sure that you in fastbootd menu and not fastboot
[Android Q&A, Help & Troubleshooting] plumpkibbles:
Correct, 'fastbootd' - but before that, my adb doesn't recognize the 'delete-logical-partition product' or 'system' and after issuing the 'fastboot -w' command there's an error for the userdata? I'm doing as stated from the instructions but when I get to fastboot -w that's where the errors start. Or - am I supposed to be in 'fastbootd' the whole time and not the bootloader fastboot?

The failed operation I'm mentioning before was after about the 4th push from ADB flashing system.
[Android Q&A, Help & Troubleshooting] smvsmv:
Interesting.. that never failed for me. Try skipping only the fastboot -w step. You should be in fastbootd only starting the "fastboot erase system" step. before then, only fastboot.
[Android Q&A, Help & Troubleshooting] plumpkibbles:
Weird - I have tried that; skipping the fastboot -w step. But, still get the error when trying to issue the 'delete-logical-partition' - also skipped past that step too - and then while flashing the system, after ~4th fastbootd push, error while sending the system image. (the operation not permitted error)

It does seem like I'm the only one having issues. I'm using the global ROM; while it seems like most are on the European ROM.. .. not sure if that has anything to do with it as well - I'm going to assume so since North American ROMs are all chopped and $h!t anyway lol.. I'm back to stock for now. I flashed my A5 Pro to Android 10 Go. Pretty cool, nice to have another device on hand with something I kind of wanted to try before. No issues flashing the A5 Pro - and I've even ran Lineage-17 but.. camera doesn't seem to work well. I'm not even trying to jump on the Umidigi forums.. no one on there is that insightful lol.. and one last thing - recovery.. when I try to flash recovery to TWRP, I get an error that 'recovery partition cannot be found'..

Thanks for the replies!

I just thought of this: what if I unlock the flashing, and use SP Flash to send over the system image / recovery? .. I don't have 'system' for the default image; it looks like 'super' is the image for the stock ROM? It is the largest, and is around 2-2.5GB.... I may give that a shot and see how it does.. I'll report back to see if I get any further that way or not.

Failed - using the sp flash tool was not helpful at all.. I did notice that my bootloader is indicating 's-on'... that may have something to do with it, but I did issue the flashing unlock command; it is unlocked..
[Android Q&A, Help & Troubleshooting] smvsmv:
Are you saying that you don't have a Power 3? I have multiple Power 3s and the process works fine. Not sure if the same steps would work on other UMDIGI devices. I think someone reported that it works on F2 as well.

The phones also have a super partition, which contains more than just system. Generally speaking, UMIDIGI devices have great specs... too bad the ROM is ****ty. With MTK not releasing the code, we are pretty much stuck with stock. GSIs have one issue or other.
[Android Q&A, Help & Troubleshooting] plumpkibbles:
No no, I'm talking about having issues with the Power 3. I have the A5 Pro as well that does work flashing other ROMs. I just mentioned that it was easy peasy but yeah the Power 3 is getting the absolute best of me lol I've tried multiple things, idk if this is going to happen for me. But, 1.2 is still solid; I'll just wait for a stable 1.3 release...

Thanks for all the help anyway!
[Android Q&A, Help & Troubleshooting] smvsmv:
Sounds good. If you figure out what's going on, let us know. I'll update the instructions accordingly.
[Android Q&A, Help & Troubleshooting] radikal-pr:
hello i need some help... my bootloader i think somehow got locked and i already have havoc os installed now i cannot do the commdands in fastboot, they all give error and using sp flash tools wont flash stock rom it gives error, my phone boots up though everything seems fine i havent tried factory reset from the device im afraid the device will brick itself and wont turn on anybody have a suggestion of what can i do to put it in stock?
[Android Q&A, Help & Troubleshooting] smvsmv:
You should be able to flash stock using SPFT... what error are you getting? I'm assuming you have unplugged the usb and plug it only when the phone is off?
[Android Q&A, Help & Troubleshooting] nobreak1970:
Well all I've moved to the Moto G Power for now. I couldn't resist Google Fi's price. I'll keep in this thread and I'm testing 11GSI on this device but that's about it.

Peace.
[Android Q&A, Help & Troubleshooting] Wotzit:
As entertaining as this thread was to read, has anyone ACTUALLY got a GSI image installed via TWRP on a Umidigi Power 3 phone? I ask because we are guided to download an AB image but, the HW apps I have tried inform me that my Power 3 is an A ONLY device and also, I am reading that it is a known incapability for TWRP to be able to work correctly with devices that were release with the Super partitions installed ( eg. the Power 3). This appears to be correct as the only TWRP recovery for the Power 3 is unable to see or write anything to the system partition so how on earth could this possibly work?
[Android Q&A, Help & Troubleshooting] smvsmv:
TWRP is pretty much useless on the UMIDIGI power 3. Although I don't understand the connection between TWRP and the device type.

The apps that show your device type are not reliable. I've tried various apps and they ended up showing A or AB. The AB GSI works and can be installed following the instructions.. A only fails to install.

GSI reliability is a whole different story. I haven't found a GSI that is stable enough for my use.
[Android Q&A, Help & Troubleshooting] Wotzit:
Thanks for the enlightenment, much appreciated.

So, if I am unable to select the system partition to flash the image to, do I select the super partition?

I'm confused since all guides (including those supposedly specifically for the Power 3) say to flash via TWRP to the system partition, but that is not possible.

Here, I read that I need to delete / resize logical partitions and the like but, if all goes pear-shaped, will I be able to simply flash the stock ROM and all partitions revert back to the correct / default sizes for that? :confused:
[Android Q&A, Help & Troubleshooting] smvsmv:
If you want to understand partitions, check thishttps://source.android.com/devices/tech/ota/dynamic_partitions/implement out

The OP instructions when followed in the exact order will work. Flashing the stock rom will bring back the original partitions.
[Android Q&A, Help & Troubleshooting] Wotzit:
Thanks for your help. I'll take a look at the link you suggest.

I've tried the recommended Treble Check app, which states "Your device does not support Seamless System Updates and is detected to have an A-only system partition" but does confirm that it is Project Treble supported, same info (A-only system partition) as provided by the other couple of HW apps.

In terminal apps I have tried the command getprop ro.build.ab_update as directed here, which "will return true if the device supports dual partitions", without result as well as getprop ro.boot.slot_suffix described here, also with zero result.

Is it normal to flash an A/B image to single partition system?

Which apps did you use that reveal your Power 3 supports A/B (Seamless) System Updates?
[Android Q&A, Help & Troubleshooting] smvsmv:
I took the same path too.. used that app and it said that the device is A-only. But when I tried to flash A-Only GSI, it failed. Tried A/B and it worked. Looking back, it was risky, but it worked.

A few others have tried the A/B successfully too. The size of system is smaller than needed for GSIs. Deleting the product partition seems to give it enough space. If you want to be 100% sure that the Device is A/B, I haven't found an app that have given me that confidence.
[Android Q&A, Help & Troubleshooting] Wotzit:
Many thanks for bearing with me and taking the time to share your findings :good:
[Android Q&A, Help & Troubleshooting] BigBlackMac:
Bluetooth call issue

Hi, here's a little feedback, i am using Havoc 3.8 and it's working very good and is faster than stock rom, no wifi or network problem , everything is working as it should plus it have a lot of customization

My only major problem is that during a phone call, if i am using my helmet bluetooth intercom or any other bluetooth communication devices, i hear a loud echo of myself with about 0.5 second latency, the other person hear me normally, this is happening in bluetooth only and this problem is not there in the stock rom

However, there is a large bulky black bar in apps to hide the camera cutout in the stock rom and it makes me crazy to loose all this precious space on the screen

Anybody have an idea how i could fix this bluetooth problem ?

Any help will be greatly appreciated
[Android Q&A, Help & Troubleshooting] smvsmv:
I doubt this will be fixed until UMIDIGI releases an update. I have some terrible BT experience with stock rom too.

If you are rooted, you can try out some Magisk modules.

At this point, I consider the phone use and throw... and don't look back
[Android Q&A, Help & Troubleshooting] championriki:
This phone does have notification LEDs, it is right between the call speaker and the proximity sensor. but umidigi must make an effort to improve the stock rom greatly. or at least they release the code.
[Android Q&A, Help & Troubleshooting] Wotzit:
The Umidigi Power 3 does not have notification LED. Check out the manufacturers spec ;)
[Android Q&A, Help & Troubleshooting] freechamp:
fasstboot -w error

When I get to fastboot -w in the steps i get this :fastboot -w

wiping userdata...

CreateProcess failed: The system cannot find the file specified. (2)

error: Cannot generate image for userdata

I had to flash my stock rom all over again

Edit: Was using Minimal_ADB_Fastboot for windows instead of SDK Platform-tools. Everything worked flawlessly now. Enjoying Havoc-OS v3.8
[Android Q&A, Help & Troubleshooting] Apipote:
Hello dears!

I have a power 3 at the bottom of a drawer, for the horror of its software (1.3). Is there a solution in sight? From what I read on the Umidigi forums, there is only anger and frustration. They don't seem to mind fixing this mess. Thank you. Best regards.
[Android Q&A, Help & Troubleshooting] xectis:
Cannot boot to TWRP

I have unlocked device, flashed TWRP and vbmeta successfully but everytime I boot to TWRP the phone goes into normal factory recovery (pic attached).

Can anyone please help with this issue.
[Android Q&A, Help & Troubleshooting] smvsmv:
I think TWRP asks to be setup as the default or something similar.. not sure if you are even able to get to that.

But, TWRP is pretty much useless at this point on the Power 3. Because of the super partition and you can't mount system. You are better off using default recovery and SP flash tool. Anything you can do with the phone today, you are able to do it with these.
[Android Q&A, Help & Troubleshooting] xectis:
Thanks for that. So can I install magisk with the SP flash tool as I can't find another way to install it.
[Android Q&A, Help & Troubleshooting] smvsmv:
Yes you can. The first post has the details and links
[Android Q&A, Help & Troubleshooting] xectis:
Ok will take a look. Thanks again.
[Android Q&A, Help & Troubleshooting] smvsmv:
If you are looking for a similar phone with better support, I think Xiaomi's POCO X3 seems to come very close for H/W specs. It's a bit pricier, but frankly after this UMIDIGI fiasco, I'm guessing it is worth it.

The phone does not support Band 66 and 71. I personally want that because I'm on Tmobile and want to future proof the phone for at least 2 years.
[Android Q&A, Help & Troubleshooting] frankbonatelli:
First thanks for this!

I have tons of experience with ROMS and a fare amount of GSI hands on but the device I had was a standard partition layout. Would have been lost with out this post!!! The second fastboot (FASTBOOTD) was killing me till i found your data.

Any ways for those that are having fastboot command issues the answer is simple and maybe could be added this little piece of the puzzle.

I maybe several attempts from three different Linux machines and every time would fall flat at the deleting of the partition product to make room for the new GSI file. Dam rookie move on my part!

So here is the answer and I bet it'll solve everyones issue with failed commands.

UPDATE TO THE LATEST ADB and FASTBOOT on your desktop laptop Linux, windows or osx.

if you see these kinds of errors

ubuntu@ubuntu:~$ fastboot delete-logical-partition product

error i was seeing

fastboot: usage: unknown command delete-logical-partition

Solve it with an update. An update from GOOGLES files, this will give the latest versions of both adb and fastboot.

after this I was done and thumb walking through the latest GSI!

A million thanks for your guide.
[Android Q&A, Help & Troubleshooting] smvsmv:
Glad it helped you. It was compiled with input from many sources.

The post is specific to windows 10 installation. But, I believe bullet point #4 (04. Perform the below commands in the latest version of adb.) addresses the update issue you had.

If you end up successfully installing a GSI with Magisk root, let us know. For now, a couple of GSIs work (with issues), but magisk bootloop is a major issue.. at least for me.
[Android Q&A, Help & Troubleshooting] Walpurgisnacht_2:
I'm fairly rusty with android boot loaders, and I seem to have soft bricked my power 3 after flashing TWRP. I followed the Instructions from here: https://unofficialtwrp.com/root-twrp-umidigi-power-3/

> fastboot boot recovery.img
Downloading 'boot.img'
OKAY [ 0.614s]
booting
OKAY [ 0.072s]
Finished. Total time: 0.707s

> fastboot boot recovery.img
Downloading 'boot.img'
OKAY [ 0.614s]
booting
OKAY [ 0.072s]
Finished. Total time: 0.707s

The phone is now continually in a boot loop where it flashes:

UMIDIGI

Orange State
Your device has been unlocked and can't be trusted
your device will boot in 5 seconds

for 25 seconds then it goes black for 5 seconds and loops.

If I hold down the power and volume down for one full cycle of flashing, I can get it to flash:

UMIDIGI

Select Boot Mode:
(VOLUME_UP to select. VOLUME_DOWN is OK.)
Recovery Mode <==
Fastboot Mode
Normal Boot

for ~ 0.5 seconds then it goes black for 10 seconds. If I release power during the 1/2 second flash I can get the menu to stay for around a second then it changes back to the first 25 second cycle.

If anyone has any ideas what to do I would love any suggestions, or links to resources. I would HIGHLY recommend skipping any kind of TWRP insulation unless this is just a fluke and others have gotten this working.
[Android Q&A, Help & Troubleshooting] Walpurgisnacht_2:
I feel dumb that I didn't see to hold down volume up and power from: https://unofficialtwrp.com/root-twrp-umidigi-power-3/

but, doing that I am able to get to normal boot select and access fastboot. I am still lost though, and can't get into a recovery, or normal boot. It's getting late so I don't think I can fix this tonight, but if anyone knows what to do from here I could really use some guidance.
[Android Q&A, Help & Troubleshooting] DragonPitbull:
Flash again with fastboot. The file TWRP attached work for UP3 and by nemo-nemo from 4pda.

May be you need more than only flash img file but try.

If not work you can should flash stock recovery. Stock ROM UMIDIGI Power 3 from company
[Android Q&A, Help & Troubleshooting] AlexLy:
Guys, could you help with USB drivers; when I put Power 3 into the fastboot mode, my pc doesn't have the correct drivers. in the device manager, after the phone reboot, i see that there is a new device appears but the system can't identify the device. where I can get the necessary drivers for windows 10.

thanks!
[Android Q&A, Help & Troubleshooting] smvsmv:
Try this - https://mtkusballdriver.com/category/download
[Android Q&A, Help & Troubleshooting] zamjerwin:
hello guys anyone could help me how to increase my partition system i cant install custom rom with sizes of 3.5GB. :D
[Android Q&A, Help & Troubleshooting] smvsmv:
See post #1
[Android Q&A, Help & Troubleshooting] linuxaro:
Hello, has anyone tried to install a version 11 ? and the root works? if it works do you use the same procedure as Version 10 ? I have the phhusson version /

treble_experimentations, with Root working, but I would like to try the 11
[Android Q&A, Help & Troubleshooting] smvsmv:
Yes, Phhuson's 11 works with supersu. But I'm having issues making calls using the phone app. works well on other voice apps though... like google voice
[Android Q&A, Help & Troubleshooting] linuxaro:
I installed the phhusson version /

treble_experimentations AOSP 11.0 v302 system-roar-arm64-ab-floss.img.xz The root works, the wifi also, but does not connect,..internet with phone network works, does it work for you? and what version do you use?
[Android Q&A, Help & Troubleshooting] linuxaro:
I found solution, I had to reinsert data wireless network ;)
[Android Q&A, Help & Troubleshooting] smvsmv:
Why do you need TWRP? I would just flash the stock rom and use fastboot/adb as required. All details in post #1.