yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] smvsmv:
Maybe... but I've been able to flash TWRP while being on Havoc OS. Don't flash F2 TWRP, flash the one I linked to before.

If you are flashing TWRP through fastboot, make sure you use the below command.. including the verity and verification disable options

fastboot --disable-verity --disable-verification flash recovery recovery.img
[Android Q&A, Help & Troubleshooting] radikal-pr:
C:\android>fastboot --disable-verity --disable-verification flash recovery recovery.img

Sending 'recovery' (23014 KB) OKAY [ 0.717s]

Writing 'recovery' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed

thats the error i get
[Android Q&A, Help & Troubleshooting] smvsmv:
Are you in fastboot or fastbootd?

I suggest that you follow the F2 rooting process as I indicated in an earlier post, starting with a fresh ROM install. That way, you will understand the required steps and process and can tweak it for your GSI install.
[Android Q&A, Help & Troubleshooting] radikal-pr:
aparently this phone doesnt have a recovery partition, the recovery is in the boot partition, in the stock firmware boot and recovery look the same filesize. i did get it to flash twrp on boot partition but the phone goes on a bootloop and wont go to the splash screen. if somebody knows a command on fastboot that i can change gsi without having to delete user data ill will be better i tried going from havoc 3.6 to havoc 3.7 it took to long on the splash screen i dont know if i have to leave it alot of time or was it bootlooped. so i just deleted data and flashed agaian and phone booted up in a few minutes
[Android Q&A, Help & Troubleshooting] nobreak1970:
not true. I have flashed boot and recovery seperately numerous times testing verity checks, etc. I also flashed a working TWRP to recovery, not boot.
[Android Q&A, Help & Troubleshooting] smvsmv:
Yep I've flashed the unoffice TWRP and stock recovery multiple times separately too. I've even listed the exact steps in sequence to install a GSI, in an earlier post. Not sure where the disconnect is.
[Android Q&A, Help & Troubleshooting] flashallthetime:
Have you tried flashing the magisks patched boot image to gain root access on a GSI ROM?
[Android Q&A, Help & Troubleshooting] radikal-pr:
thank you guys i finally got it to work, here is how if anybody else has the same problem

1. i rename recovery.img to twrp.img

2. go to recovery, enter bottloader mode,

3. fastboot --disable-verity --disable-verification flash recovery twrp.img

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

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

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

7. fastboot reboot
[Android Q&A, Help & Troubleshooting] smvsmv:
I tried the stock magisk, magisk patched boot image, 2 other patched magisk versions. no luck.

edit: so, looks like magisk doesn't work well with gsis.. none of the gsis make it clear in their thread. found an old thread and this which I assume would only help if you are able to boot after flashing magisk in the first place.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Just flashed Android 11 Google GSI beta 2. Will report back. It IS booting as we speak.

update: worked smooth as silk EXCEPT calls. :(

flashing Efran's Pixel 11 GSI now. will report back
[Android Q&A, Help & Troubleshooting] smvsmv:
What was the issue with calls?
[Android Q&A, Help & Troubleshooting] nobreak1970:
Just would not connect.

---------- Post added at 08:28 PM ---------- Previous post was at 08:21 PM ----------

oh and fingerprint didn't work but everything else was so smooth. no laggy graphics, etc.

wish they could get calls working :(
[Android Q&A, Help & Troubleshooting] smvsmv:
Too bad.. but it's beta, so should be better soon. What about root. did you try Magisk? Based on what I'm reading, not too optimistic about Magisk... may have to go Supersu route.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Nah didn't try root yet. Just was wanting a working 11 on the device first. :)

I did just read on the android dev site that the current gsi has issues with telephony anyway. So, it's confirmed lol.
[Android Q&A, Help & Troubleshooting] nobreak1970:
Just flashed Descendent X rom android 10 version. THIS is an impressive piece of work.
[Android Q&A, Help & Troubleshooting] smvsmv:
You were able to boot. Mine was stuck at boot logo a few days ago. Voice and wifi all working well? What about ADB debugging. that seems to be a common issue.
[Android Q&A, Help & Troubleshooting] nobreak1970:
yep all the basics worked. now it doesn't seem to have all the us lte bands, or at least as much as our stock rom offers so signal in the house was nonexistent.

I read Havoc 3.7 is out. That rom has very good coverage band-wise.
[Android Q&A, Help & Troubleshooting] radikal-pr:
There seems to be a bug in havoc 3.6 and havoc 3.7 with out vendor file the bluetooth headset when in a call you can hear yourself and makes it a little difficult to hear the other person because of the background noise. Does somebody know how to fix it in the telegram group they say it is our vender file
[Android Q&A, Help & Troubleshooting] geoffwdixon:
flashing GSI roms

First off thank you to everyone here for your awesome work and contributions!

My device currently has stock version UMIDIGI_Power_3_V1.1_20200319 and smvsmv guide mentions flashing to stock UMIDIGI_Power_3_V1.1_20200328.

Is there a specific guide or best guide that I could follow for this part?

Sorry im a noob at this.
[Android Q&A, Help & Troubleshooting] smvsmv:
try this

https://community.umidigi.com/forum.php?mod=viewthread&tid=19232&extra=page=1
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Thank you smvsmv for your reply. I've been looking at this page and it provides multiple ways to update the stock rom.

Am I correct in assuming i'm to use the SP Flash Tool method? The page states (in tiny writing) the Manual (local) OTA update method can only update version 20200116.

Thx again for your assistance.
[Android Q&A, Help & Troubleshooting] smvsmv:
Yes, with the SP flash tool, you should power off your device, connect the USB cable and then flash it. That works for me. It should work with an earlier version of ROM too, but I'm not sure if there are any updates to vendor or other partitions in the later versions. I would just try with your current stock ROM and go from there.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Unfortunately without the vbmeta files required for the installation of the GSI ROM I would rather not risk breaking from your outlined instructions.

Either way I have now completed reading the SP flash tool tutorial and successfully flashed the FIRMWARE UPGRADE to stock UMIDIGI_Power_3.E_V1.2_202003282206.

(FYI opening YouTube I can confirm i now have the audio issue, i did not have the speaker issue on the older firmware.)

I will now continue the process of flashing GSI. Will report back on my progress.

THx again for all the help.
[Android Q&A, Help & Troubleshooting] smvsmv:
Glad you got that part done. Also, when you unzipped the ROM, in the folder you will find the boot, vbmeta and recovery images. Those are the file you want to use. Keep the ROM folder and the SP Flash tool folder. You will invariably revert to stock multiple times. I've done so at least 20 times so far.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Think I hit a snag.

I found OEM unlock but am unable to locate bootloader unlock. I continued regardless.

I completed this step and it seemed to error out saying:

Formating /data...

Formating /cache....

E:Fota installation aborted.

E:: No such file or directory

Formating /metadata...

Datawipe complete.

...:Fota instalation aborted.

...No such file or directory

I used the menu option and it seems to get stuck on a black screen that only says very small at the bottom FASTBOOT MODE....

I call also hear windows chime every couple of seconds like its recognizing the device over and over again.

Im doing all this from my \platform-tools folder where I extracted platform-tools_r30.0.3-windows.zip

I also installed ADB and FASTBOOT Installer 1.0.5.exe (But not sure where this installed to)

Any thoughts?

All the best
[Android Q&A, Help & Troubleshooting] smvsmv:
[MENTION=10807141]geoffwdixon[/MENTION] Step 3 should be to enable OEM unlock and USB debugging enabled. You should get a popup on your phone to authorize your PC/laptop. Authorize before proceeding. Unlocking bootloader will need you to press the volume up button when in bootloader(fastboot). The factory reset should not show any errors. Bootloader does show the "fastboot mode" you see. So, you are not stuck. You should proceed.
[Android Q&A, Help & Troubleshooting] smvsmv:
Deleted because duplicate post
[Android Q&A, Help & Troubleshooting] geoffwdixon:
omg omg omg omg DID IT !!!!! WOO HOOOOOOOooooo

The key was when you said:

I then focused on the constant usb connecting sound.

I opened device manager and found android icon disappearing and reappearing.

I thought was driver related so i installed: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip

This immediately stopped the usb connection issue and I was able to type fastboot commands finally.

I attached a screenshot... hopefully it worked.

Now im on Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img (PS i had to unzip the file.... whoops)

Thank you thank you thank you... cant wait to play with this.
[Android Q&A, Help & Troubleshooting] smvsmv:
[MENTION=10807141]geoffwdixon[/MENTION] - Glad to be of help. I've updated instructions based on your feedback. Hope it makes it smoother for others. Keep us posted on any issues you may find with Havoc. Personally, I want Magisk, but I understand SuperSU is an option. May go that route if there's no other option.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Ive only been playing around in the settings so far. This is so damn cool having a proper OS on this phone.

Not really Havoc related I but I can report I now get this audio issue everyone is talking about. I got it upon first booting the phone after flashing Havoc and after I reboot.

I got it to stop by calling my voice mail and clicking the speaker button on and off a few times then click the dial pad until YouTube sounded OK.

Makes me wonder if I should have followed your advice and just tried installing GSI without updating the stock rom first.

I will keep up my testing and report back.

Thx again.
[Android Q&A, Help & Troubleshooting] smvsmv:
I never faced this audio issue.. but I use Lawnchair launcher and always disable Google voice. Try that without changing anything else. Maybe that's what helps me with audio.
[Android Q&A, Help & Troubleshooting] smvsmv:
Anyone tried to lock the bootloader after you root it with patched magisk boot image? I got as far as typing in the command to lock, but backed off at the confirmation dialog because I was not sure what would happen.

What I'm hoping to accomplish is get Magisk installed for controlling root privileges and then lock the boot loader. That way upcoming google changes to detect unlocked bootloader is taken care of and I don't have to worry about Magisk hide not working.

When you lock the bootloader, I know it clears out user data, but does the rooted ROM still qualify as "Stock"? If yes, then the boot image should be Magisk Patched image and theoretically I'm still rooted.... All this is of course speculation. Wondering if someone tried this accidentally or intentionally.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
GSI Havoc Testing

This is only for informational purposes. The tests were ran only once on each machine.

Here is my Havoc Rom score: https://browser.geekbench.com/v5/cpu/2939424

Geekbench 5 Score

262 Single-Core Score

1254 Multi-Core Score

Here is my stock Rom (V1.1_20200319) score: https://browser.geekbench.com/v5/cpu/2939464

Geekbench 5 Score

294 Single-Core Score

1443 Multi-Core Score

On a side note with Havoc rom installed I ran music to the car radio over Bluetooth for over an hour without any issues. Where as the stock rom skips several times during playback of a song.

EDIT: Ran test 2 more times on havoc rom. The second i rebooted the phone before running GeekBench and scored:

294 Single-Core Score

1372 Multi-Core Score
[Android Q&A, Help & Troubleshooting] radikal-pr:
thank you for the score, i think its a little heavier but still has a few bugs on our phone (bluethooth headset, you hear yourself, wired headset doesnt work) also I notice a little more of battery drain, like 10% more than stock. or maybe its because the bluetooth improved its comsumes a little more,
[Android Q&A, Help & Troubleshooting] bauxitoid:
Root with Custom ROM

Hi, you were able to run custom rom (havoc, descendand) with magisk patched stock boot image? I had no luck with that and i tried patched boot, patched recovery and nothing. TWRP is, if i understand correctly, also unusable, as it is unable to mount system, right?

Or you are back on stock rom? On stock i was able to use magisk patched boot image with modules, everything.

Descendand is really impresive, what bothers me is that i am not able to use google pay because of custom rom, which i normally solve with magisk hide. Or there are other ways to use google pay on non stock rom?

Thanks if you have same new information about using magisk (or at least google pay) with custom roms.
[Android Q&A, Help & Troubleshooting] nobreak1970:
I think the battery drain issue with havoc is simply to the the fact that it seems to be searching more for radio frequencies than the stock one does. Perhaps it has less lte bands than Stock rom? I use opensignal, netmonster and a couple other things to monitor my radio connections. Each of their log files are much longer with Havoc than with stock rom. The log file captures connect/disconnect, etc of the cell radio.
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Afternoon all.

Before I try flashing another custom ROM over the Havov ROM I would like to make sure I don't make any mistakes. Would this be the best and simplest method?

1. adb reboot recovery

2. Select Factory reset and reset.

3. fastboot -w

4. fastboot reboot fastboot (you MUST be at the fastbootd menu now. If not, you will not be able to flash the GSI successfully)

5. fastboot erase system

6. fastboot delete-logical-partition product

7. fastboot --disable-verity --disable-verification flash system CUSTOM_ROM_NAME_HERE.img

8. Reboot to system.

PS I borrowed this part from smvsmv amazing instructions provided on page 1.
[Android Q&A, Help & Troubleshooting] smvsmv:
That should work. Really, you should be able to just do step #7 directly in fastbootd. But that's dirty flashing.

The only reason I hesitate flashing 2 GSIs in sequence is because I don't know if the first GSI's "something" gets carried over, making the 2nd GSI unstable. Stock would just give me a clean slate.

For e.g. the first time I flashed Havoc, it was really laggy. Even changing the animation scales didn't fix that. But I went to LOS and then stock and then again flashed Havoc.. the lag was gone.. no idea why. These kind of things is what will trip you.
[Android Q&A, Help & Troubleshooting] smvsmv:
I'm back on stock because Magisk works on it. GSIs are not yet ready for me :cowboy: The Magisk hide option is going to be obsolete soon, based on how Google plans to identify rooted devices. That is why I was exploring the re-locking bootloader option. I've asked UMIDIGI support about it, waiting to hear back. But I doubt anything helpful will come of that.
[Android Q&A, Help & Troubleshooting] nobreak1970:
TIp of the Day: if you want your 1080p HD videos to POP! Be it Youtube or your own homemade vids....go into Developer Settings and turn ON sRBG.
[Android Q&A, Help & Troubleshooting] DragonPitbull:
I suppose it is necessary to change the important part in build.prop for the system to be certified.

Check the GSI ROM [system\system\build.prop] and change:

ro.product.brand=
ro.product.name=
ro.product.model=
ro.product.device=
ro.product.manufacturer=
ro.build.fingerprint=

Push the modified file back with stock parts modified into the source folder and give the necessary permissions: 0644 = -rw-r--r

I'm not going to write the commands by fastboot here because I hope an experienced guy knows what I wrote about!
[Android Q&A, Help & Troubleshooting] geoffwdixon:
descendant-X-20200710-arm64-ab

First impressions with this Descendant ROM is it looks very robust, modern, scored similar on Geekbench 5 to Havoc and had some nice features like the volume bar pop up. Unfortunately I encounter a few issues with this ROM causing me to flash something else:

Could not read the SD card. After inserting a new SD and formatting to fix it hung up at 20%. (As a result could not test Bluetooth music in the car.)

Opening some games resulted in error "The device, OS, or software is not compatible" (Pokemon Go lol)

Could not open in settings the display color section. It was there but would not open.
[Android Q&A, Help & Troubleshooting] bauxitoid:
1. Haven't tried, internal memory was big enough for me so far

2. If i remember correctly on my previous custom rom device (huawei nova lineage os) i had to magisk-hide Pokemon so they couldn't see custom rom, plus i had to hide the magisk manager app and delete MagiskManager folder from internal memory - lots of little steps, but it could have been changed since. As far as I am unable to install magisk on Descendant i can't advice more.

3. As your screenshots are not available for viewing, i am not sure what setting you mean. I have Wallpapers and screensaver section with Wallaper and Screen saver subitems, then empty Color settings section, then Lockscreen with Lock screen display...
[Android Q&A, Help & Troubleshooting] smvsmv:
If you are interested in trying some hacks for getting Magisk on GSIs, check out this thread. It gives you some visibility into why GSIs and Magisk don't get along well, without getting to an actual solution.

I haven't tried any of the hacks yet. If you find something that works, please post here.
[Android Q&A, Help & Troubleshooting] bauxitoid:
Prerooted ROM
[Android Q&A, Help & Troubleshooting] radikal-pr:
Hello does somebody know what is the code name for power 3 to download ROMs, or what other can we use or just gsi arm64 ab?
[Android Q&A, Help & Troubleshooting] bauxitoid:
Hello, I tried

descendant-X-20200710-arm64-ab.zip and

Havoc-OS released /arm64-ab/Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz and

system-quack-arm64-ab-gapps.img.xz
[Android Q&A, Help & Troubleshooting] BigBlackMac:
Update

Hey Guys, any update of your custom roms ? :)

Curious about this

Thank you
[Android Q&A, Help & Troubleshooting] geoffwdixon:
Android 11 beta

Afternoon Umidigi Power 3 Users.

Ive been having an absolute blast with custom roms thx to everyone on this thread. Havoc Rom is now my daily driver :)

Does anyone know what I have to differently to install the android 11 beta? I have not had much success copying the steps to flash the havoc rom.

Here are the android 11 beta roms I tried to flash unsuccessfully:

Pixel-AB-11-20200709-ErfanGSI.img-0455

gsi_gms_arm64-exp-RPB2.200611.009-6625208

Generic-AB-11-20200618-ErfanGSI.img-2335

ALl the best guys and stay safe in these times!

Geoff
[Android Q&A, Help & Troubleshooting] radikal-pr:
hello i have a problem with the twrp on power 3 when im going to flash a gsi rom (dirty flash) i cant doing because it wont mount the system, if you click on mount and try it says system read only is useless to flash something in system with trwp is there anyway to fix this
[Android Q&A, Help & Troubleshooting] smvsmv:
GSI

TWRP is very basic and unofficial at this point. Follow the steps outlined in the first post.
[Android Q&A, Help & Troubleshooting] smvsmv:
I think [MENTION=2930839]nobreak1970[/MENTION] was able to test it out. But had issues making calls.
[Android Q&A, Help & Troubleshooting] DragonPitbull:
May be you can test something: Magisk Canary
[Android Q&A, Help & Troubleshooting] nobreak1970:
'Yeah it was so smooth yet calls had no audio and most of the time didn't connect.

Give it time. :)
[Android Q&A, Help & Troubleshooting] smvsmv:
Another day of frustrating updates.

Tried CAOS and Havoc 3.7. Both were installed and seemed to work well. However, rooting was frustrating. Even the Magisk canary version for 11. I tried the patched boot image and also tried flashing the Zip. Interesting finding though... when I tried to flash supersu zip, it failed with the same Error 21. Not sure how to enable root in the pre-rooted ROMS, but I thought that you should still flash the zip.. Anyone know?

Also, don't try installing the magisk for android 11 on your stock ROM.. that didn't work either.
[Android Q&A, Help & Troubleshooting] smvsmv:
A bit off topic - Any of you considering getting the upcoming Bison? It looks like the device will come with Android 11. With Google forcing seamless updates in 11, maybe custom ROM migration maybe easier? Given the issues with power 3, I'd be hesitant to drop anything more than $150-$200 on it.
[Android Q&A, Help & Troubleshooting] flashallthetime:
Not interested in the bison, I bought the S5 PRO so I'm not upgrading till at least winter or early spring
[Android Q&A, Help & Troubleshooting] geoffwdixon:
PART ONE:

I followed smvsmv instructions on page 1 to try and install the android 11 beta without any luck. Did you do something different I can try?

---------- Post added at 08:04 AM ---------- Previous post was at 07:30 AM ----------

PART TWO:

So I am trying very hard to correct the audio issues plaguing the Power 3 without any luck.

I have tried flashing almost every version of the STOCK ROMS and many GSI ROMS.

Now I cant say anything for certain but this is what I can report:

Different versions of the STOCK ROM contain different kinds of audio issues.

Early STOCK ROMS have NO audio at times.

Later STOCK ROMS have heavily distorted audio.

The audio issues would usually occur after rebooting the device.

After perfectly following the guide provided in this thread the audio issues would continue to affect the custom ROMS.

The audio issue affecting the custom ROM would mimic the issues plaguing the STOCK ROM. For example if you had an early STOCK ROM with the no audio issue and proceeded to flash a custom ROM over it you will have the no audio issue on the flashed custom ROM.

From what i can make out a version of Google Assistant comes preinstalled on all stock STOCK ROMS.

I can not update the preinstalled Google Assistant.

The play store says Google Assistant is not installed. I only have the option to download and install Google Assistant.

I found that i recieved audio issues the most after installing Google Assistant from the play store over the preinstalled Google Assistant.

Unfortunately my expertice ends here and I was not able to resolve the audio issues outside of the allready known methods.

All the best.
[Android Q&A, Help & Troubleshooting] smvsmv:
[MENTION=10807141]geoffwdixon[/MENTION] - I haven't tried the 11 GSI myself. Not sure if something's missing. Although, I'd be surprised if the process is different for it.

Regarding the sound issues, have you tried using a different launcher? I have always used Lawnchair and never had a sound issue and read somewhere that it fixed it for some people. Something easy for you to try.
[Android Q&A, Help & Troubleshooting] smvsmv:
I believe Spring is when the Bison will be available anyway. Just curious how many people are going to stick with UMIDIGI after the latest sound and update fiasco.

The phone specs are fantastic, but without a good stock ROM or custom ROM, I'm reluctant.