yashsingh1/xdaforums huggingface dataset:
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
I simply can't get access to my phone, so the only improvement Havoc has made over Stock is no G**gle. For some reason setting in Developer options, Default USB Config|File Transfer, does not result in a block device being recognized when I plug in.

SSHDroid gets permission denied no matter what directory I set it to, I suspect because I can't root this phone. And no devs are helping us. I am really quite sick and tired of phone problems. Looks like many ppl have just given up. I wonder if Lineage is stable yet?

I keep a Notes file for everything, in this case in ~/utilities/hardware/phone/xt2041-4 Moto G Power. That way I can later retrace my steps. Without the nandroid password that data is lost.

I use Nova too, mainly because you can actually back up your settings and desktop. Haven't had time to look into the widgets as, frankly who knows how long these things will be around.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] JPutz:
I'r trying to upgrade to 4.12. The only problem is I can't remember when I updated to 4.10 if I installed the vanilla with Flame or the regular GApps version. My last update went to crap because I was using the rom from the other developer and had to start from scratch, but I don't remember which image I used.

Also, if it is the Flame image, do I flash the Havoc zip, then Flame, or do I reboot in between flashes? Or do I even re-install Flame for an update?
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
This is why I have a special phone directory.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I had a hunch that I chose no password for TWRP, and I was right. What a miracle! However, the TWRP Backup Page lists the following partitions:

Boot

DTBO (?)

Super

(Metadata (0MB)

Data (excl. storage) (128MB)

Recovery (64MB)

Persist (1MB)

Bluetooth (4MB)

DSP (?) (32MB)

EFS (?) 8MB)

Logo (32MB)

super (9312 MB)

I selected Boot, Super (with the capital "C" & 3rd from the top of the list), Data, Recovery. Super (with lower case "c" & at the bottom of the list) was selected by default even though that seems to be a dup to me. The backup failed. Any ideas? By the way, Slot A is active.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
I don't know anything about nandroid.

But here's a secret no one will tell you: TWRP and Magisk can NOT co-exist on the same partition. So it's as I've always said: Do NOT install TWRP. You have to, in fastboot, # fastboot boot twrp.img, so it's running in memory rather than on the flash. This way it's not in the way of Magisk.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
Hmm. I've never uninstalled TWRP. How would I do that? Also, could you expand on this sentence so that I can attempt your suggestion? "You have to, in fastboot, # fastboot boot twrp.img, so it's running in memory rather than on the flash."

Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] JPutz:
Yeah, I have one for that. Unfortunately I downloaded both to it. 🤦‍♂️

Speech is not working on my phone, and if I remember right it does not with Flame, but when I installed the GApps image it did, so I think this is a vanilla rom +Flame. Good thing I have a good Nandroid backup.

So, when I upgrade, do I just install the vanilla zip or do I have to also reinstall the Flame GApps? And if I do, do I reboot after the vanilla zip install or just install after the main zip.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
jhford: the only way to overwrite TWRP is to install Stock 10, but you can't do that already being at 11. One of the commands is # fastboot flash recovery recovery.img which lays down the stock recovery over TWRP on whichever slot is inactive.

JPutz: I'm getting too drunk to answer these questions, but I don't understand what you mean by "Speech is not working on my phone". Does this mean that you can only use speakerphone? Or that speech-to-text isn't working?

No idea what "Flame" is, and I haven't used GApps for years because G**gle is a travesty of Nature and the Greatest Data Mining Operation In The History Of The World.

So when you 'upgrade to'... what? Whatever you do do NOT install Stock 11 or 12. They will ruin your phone. I don't understand the rest of what you are talking about.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I hope you aren't developing a drinking problem. :unsure:
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
"Developing"?!

It's the only way I can manage!
[Moto G Power ROMs, Kernels, Recoveries, & Other De] JPutz:
I mean updating the rom. I am on 4.10 right now and am trying to update to the latest.

As far as speech I meant speech-to-text. FlameGApps doesn't work with the speech-to-text, at least with my experiance, and only the full google one does.

I am assuming the way to update is to flash the zip file in TWRP, that there is now way to actually do it in the rom.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Beetle84:
Rename the latest magisk.apk to magisk.zip, the file is one and the same now
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
Havoc 4.12 just can not work with Magisk.

I booted into fastboot (VolDown+Pwr) and plugged in.

I laid down Stock just to be sure and start from scratch. I finally got smart and made a script, "flashall":

# fastboot set_active a

# ./flashall

# fastboot set_active b

# ./flashall

#!/bin/sh
echo "Flashing to Stock Android 10..."
echo ""

fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear

# fastboot boot twrp-3.5.0-0-rav-sofia.img

But when I Wipe (Factory Reset) in red I get that it is unable to mount /data and /metadata ! This should not be. This is a pure stock image.

So I Format Data and it clears that error but /metadata is still a problem. I tried an Advanced Wipe of everything; no change. I tried Repair, and Change Filesystem, everything but the kitchen sink, and nothing fixes the /metadata problem. So I give up and:

# adb push Havoc-OS-v4.12-20211221-sofiar-Official.zip /external_sd/

# adb push Magisk-v23.0.apk /external_sd/

And Installed Havoc and Magisk. Cleared Dalvik and rebooted.

It tries and tries to boot to the new slot but eventually falls back to the old slot. 4.12 looks nice and all, but I must have root. And the dev has absconded and/or doesn't know what he's doing.

JPutz, why not just install the Havoc which has GApps? Looks like you've downloaded the wrong one. I know nothing about Flame or text-to-speech.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
Ok I'm back on the air, rooted, and functional.

Went back home to momma, Havoc 4.8.

Agh, what a relief! I could even restore my Signal backups. THANK YOU Beetle84!
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Leroy_Sparks:
Following up (and still wishing for FM radio 😉): I had occasion to revert my phone back to stock A10 and found the FM reception on it was strong and clear so the hardware isn't incapable. For some reason Arrow ROM (same phone & wired headphones) had very poor reception.

BTW, phone is now on Havoc 4.13

EDIT (29 Jan): With Havoc 4.13 running, I did a test based on something ph4n70m has mentioned - I installed SELinux Switch app and used it to set permissive. Sure enough, the FM radio worked! After it was functional I could switch back to enforcing and it continued to work. Now the bad news - while the FM radio worked, the reception was distorted the same as in ArrowOS. Apparently there is something different between the OEM implementation and the AOSP/Lineage implementation.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] :
I REALLY hope someone figures out why radio is so bad soon. It's the only thing keeping me on stock. Some people might scoff at getting bent over a half-functioning fm radio, but it's more a matter of "if service is down (especially due to weather or God forbid something worse), I need information somehow".
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Leroy_Sparks:
I noticed that the radio app included in havoc is a few versions older than the most current one I can find online. Out of curiosity, on the stock ROM which version of FM Radio is installed? (on havoc it's 02.04.0001). Also, I presume you've experienced the difference in reception quality between stock and custom?

Count me as another that really wants a good FM radio. It's far more important to me than most I guess...
[Moto G Power ROMs, Kernels, Recoveries, & Other De] :
On A11 the fm radio version is 02.04.0013, but I've tried older versions out of curiosity and noticed no functional differences on stock. And yes, the difference between custom roms and stock reception is night and day. On stock when I scan I find around 20 stations, on customs I find 8-10, and there's so much static when they're perfectly clear on stock.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Baja24:
Flashed this a couple of days ago. Everything seems to work good, except all volume levels are really low ? I see there was a few glitches with this build, was this one of them ? if so was previous build sound better ? I like this Rom, but may have to go back to Lineage 18.1 or Stag because of the low volume on everything.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] ph4n70m-404:
I'm guessing you're noticing the removal of Moto Dolby which would increase audio levels but also mess up other audio mods and ruin the audio quality a bit. You can check the telegram and there's a note about it.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] ph4n70m-404:
Probably some hal related stuff if theres a difference between the stations and clarity, the reason fmradio isn't working in general is selinux related stuff. Not exactly worth touching right now.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] ph4n70m-404:
The best bet for anyone running into issues is for them to join the official Havoc-OS Sofiar telegram channel.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] :
I respect the work you've done, and I love the rom, but in my case a proper functioning FM radio is a must, and that's keeping me on stock. I realize it isn't at the top of your priority list (and for good reason), but expect a donation if a fix ever materializes :)
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Ryu945:
1) Can I use this OS on the Moto G Power 2021? There are many versions of the Moto G Power and I am not sure which ROMs work on this Moto G Power.

2) Can I install this ROM with no Gapps?
[Moto G Power ROMs, Kernels, Recoveries, & Other De] ph4n70m-404:
1. no only the 2020 variant is supported.

2. yes.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Ryu945:
How do I navigate this site to find the ROMs for Moto G Power 2021 then?
[Moto G Power ROMs, Kernels, Recoveries, & Other De] :
If there are any (and I don't think there are) they'd be here -> https://xdaforums.com/f/moto-g-power-2021.12069/
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Quantumstate:
I notice that this is for the sofiar. Will it work on the sofia xt 2041-4?
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I have your same phone and I also flashed Beetle84's build of Havoc 4.8 the day the phone arrived. I love Havoc, but Beetle64 stopped supporting it. So, I tried an LOS ROM but it screwed up my device, because I was on A11 and not A10. So, I rebuilt it as stock and customized it using Nova Launcher 6.x with auto updates disabled in the Play Store, because Nova 7.x was incompatible with certain of my fav widgets. The phone works fine as stock, but Moto will not update this phone. So, I'd like to install a custom ROM, but I understand that I would have to downgrade to A10 first, and that scares the hell out of me after my first debacle. So, since you appear to be very knowledgeable about this device, can you help me downgrade to A10, if that's still required, and point me to bulletproof flashing instructions? Thanks. Much appreciated.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I finally successfully downgraded my 2020 XT2041-4 from A11 to A10 stock, and the phone works perfectly. My primary reason to flash a custom Rom is that Moto no longer supports the 2020. But what's the likelihood that devs will? Am I right that the OP's installation instructions provide for flashing using TWRP only? If I recall correctly, I used Fastbootd to individually flash several img files when I flashed Beetle64's version. Also, I don't understand Slots A/B. So, I'd appreciate it if someone help me with real simple install instructions. Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jsputnam:
What is the proper way to upgrade the rom? Here is how I am assuming:

Download rom

Reboot into recovery

Flash rom

Clear cache

Reboot into system.

This is the non-GApps version with Flame Gapps installed. Do I need to reboot back into recovery like I did with the original flash and reinstall GApps or am I good without updating it?

Thanks.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
@ph4n70m-404. Sorry to bother you. I'm an experienced Rom flasher. I've been flashing Rom on my Nexus 7 (2013) deb tablets forever, and I immediately flashed @Beetle64's Havoc Rom about a year and half ago on my XT2041-4, and I liked it. But then I noticed an LOS Rom. So, I tried to flash it but it failed and I had to restore the stock OS which went from A10 to A11. It took a while, but I successfully downgraded to A10 stock and souped it up to behave almost like a custom Rom. But I would like to flash your Havoc Rom so I can receive patches, etc. I just flashed Vache's TWRP and am ready to flash your Rom, but is it as simple as your OP:

1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.

2. Wipe System, Data, Dalvik, Cache.

3. Flash the ROM, GApps (Optional), Magisk (Optional).

4. Reboot and Enjoy????

What about the slots of which I'm unaccustomed?

I dread screwing up the flash and having to downgrade to A10 again.

Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I had Lineage 11 installed on this phone, but today I flashed this ROM. Everything went well except the ROM doesn't detect my SIM card, but Lineage 11 always detected it. Ideas? Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] 64Star:
Man, i've been on a wacky adventure trying to install Havoc OS this entire day.

I updated to android 11 (again) cause i thought you needed to do it to install this OS, but turns out I didn't, so I had to downgrade to android 10 (again) then I went in circles cause i can't seem to install it when i booted into it, then i managed to flash twrp (specifically "twrp-3.5.0-0-rav-sofia.img") to recovery, but then when i installed the zip file, it got put in a boot loop, and after i force restarted my phone, not only did the orignal recovery thing came back, it also went back to a fresh stock android 10 i had at the beginning before i started. (whichat least isn't a brick)

So tldr: i have no clue how to install this darn thing cause there's no clear, concise guide to install it and i'm pretty much back to where i started: a freshly factory reset stock android 10. What do I do now?

(To note, i have a Moto G Power 2020 with sofia XT2041-6 64GB PVT)
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
I'm in the same boat, except I have an XT2041-4. I flashed @Beetle64's Havoc immediately when I received my phone and should have left it alone, but I tried to flash LOS and screwed it up, and had to do a rescue which installed A11. So, I downgraded to A10, on which I'm currently running a highly modified stock ROM. Although my current setup is fine, i want to flash Havoc also but I can't abide going through the above process all over again. Any help will be greatly appreciated. Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
@PH4N70M. Forgive me for bothering you, but I have a lot of experience flashing Roms and I want to flash your Havoc on my XT2014-4, but I'm reticent for the following reasons. I immediately flashed Beetle64's Havoc a few days after I received the phone and everything went perfectly and I liked it a lot. But Beetle64 posted that he would no longer support it. I've used LOS a lot and thought I flash it. Somehow I screwed up the flash, which may have been your build, and had to run the Lenovo Rescue & Smart Assistant (LRSA) to rescue the phone but LSRA installed A11. After great effort, I successfully downgraded it to A10 which I'm still running with it setup to emulate the pure Adroid UI. I can live with it as is, except Moto has stopped supporting the device, and I'd like to be able to flash future patches.

So, I would appreciate idiot proof step-by-step flashing instructions, so I don't have to downgrade to A10 again

Thanks. Much appreciated
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
Since my post is over a year old and no one has either responded to my post or independently posted since then, is it safe to assume that this ROM is dead and is not being maintained? If so, is anyone using any ROM for the XT-2041-4 Sofia that has a future?
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Leroy_Sparks:
Yes, this ROM is essentially "dead". Havoc quit work on it some time ago.

I still use it. The only function that it lacks is FM radio equal to the OEM builds.

And, as far as I know, there are no Sofia ROMs with full functionality being offered, developed, or supported. The amogus stuff has been out for months but will probably never have speakerphone support for Sophia as the original "developer" doesn't seem inclined to care.
[Moto G Power ROMs, Kernels, Recoveries, & Other De] jhford:
Are you going to keep your Sofia or buy a new phone? If the latter, which phone and why? FM radio isn't important to me. That said, and I want to flash this dead ROM anyway, could you layout the foolproof flashing steps? I ask, because I immediately flashed Beetle64's Havoc (also dead) when I received my A10, XT-2041-4, 2+ years ago. But then I flashed a Lineage ROM which failed and had to do a rescue which installed A11. But I successfully downgraded to A10 which I'm currently running with the stock ROM. I dread another flash failure.

Thanks
[Moto G Power ROMs, Kernels, Recoveries, & Other De] Leroy_Sparks:
I have no reason to buy a new phone. This still ROM works quite well for me.

I have a newer Galaxy tablet with OEM android 13 and honestly the newer android version add nothing particularly useful. Worse yet, that device has -zero- ROMs available.

On this phone the OEM software may still get security updates, this Havoc version is dead.

As for flashing it, I did the initial install almost 2 years ago and it was nothing unusual as I recall.
[Google Pixel 6 Pro] nighthawk626:
This wallpaper takes me back to the first Nexus device. Hard to believe how far phones have come since the first one. Anyone else around since the G1 era?
[Google Pixel 6 Pro] tids2k:
https://play.google.com/store/apps/details?id=com.xdevl.wallpaper.nexus&hl=en_AU&gl=US
[Google Pixel 6 Pro] skimminstones:
They haven't asked for anything though? Apart from who else has been around since the early days
[Google Pixel 6 Pro] kboya:
Is the old Nexus wallpaper built in? I only have a chess thing for Alive wallpaper
[Google Pixel 6 Pro] DinarQ8:
i am here :ROFLMAO: Nexus One made by HTC
[Google Pixel 6 Pro] tids2k:
Me too from HTC HD2 times.
[Google Pixel 6 Pro] tids2k:
My Bad..
[Google Pixel 6 Pro] paysen:
Can you Link the wallpaper?
[Google Pixel 6 Pro] Golf c:
My boss had that phone. I was so jealous. Lol
[Google Pixel 6 Pro] ggrant3876:
That's the phone that started me on android, had two G1's, one rooted and one stock. Was fun back in those days with all the development going on. Cyanogen Mod and waiting for the weekly updates, can't remember who but I did some testing for one of the recoveries used on the G1.
[Google Pixel 6 Pro] kboya:
I had an N1, but only after the original HTC Desire as that was more widely available in the UK and, after using both, somewhat more refined than the N1. That said, the physical trackball was far easier to use than the optical on the Desire.

I was also a fan of the Nexus S and its curved front, but I know I'm in the minority on that one🤣
[Google Pixel 6 Pro] roirraW "edor" ehT:
Second post in this thread. https://xdaforums.com/t/nostalgia-overload.4354343/post-85857495

My first Android was the HTC Droid Eris (rooted, of course). The trackball was interesting although it gave me problems eventually, and I then had to abuse it to get it completely disabled instead of giving me the constant problems when I wasn't trying to use it.
[Google Pixel 6 Pro] galaxys:
Add me to the infamous Nexus One! Trackball ftw😎
[Google Pixel 6 Pro] belair56:
JesusFreak I believe was the recovery Kingpin, right?

Yes I had to go to Columbus, Oh. to buy the G1 because the Cincinnati area didn't have 3G and T-Mobile only sold the phone in 3G coverage areas.
[Google Pixel 6 Pro] ggrant3876:
yeppers that was it, I even tested a Rom for him that partially worked!
[Google Pixel 6 Pro] idbl_fanatic:
I had a G1 as well.