Update
That Github link doesn’t work anymore, find the download link here. Also, no need to compile it apparently. They have two different GSIs now, one or the other might work. The last one I tried didn’t work. May or may not try again. Phone is mostly working, stock ROM sucks though.
I was able to download this finally. Was flashing the stock ROM, and tried one more time to download that.
Well, it’s the worst one yet, it doesn’t boot, just gets stuck at the boot logo. I also flashed the stock in fastboot, forgot you need to be in bootloader. So I reflashed it in bootloader, then flashed the GSI ROM in fastboot, and it still doesn’t work.
So back to stock I go. Not going to see if that other ROM I was trying works now that I reflashed the stock ROM, I’ll just disable crap instead. Not worth my time to keep trying to get a GSI ROM to work right. Some people want incoming calls. And they all probably use the same or similar ims apk anyways.
Maybe the img file is corrupt. If it doesn’t mount, it definitely is.
Well it mounts, so might not be corrupt.
Guess adb install did work, for the magisk apk. Clicked ctrl + c, it seemed to be stuck. But then magisk showed up on the phone. That’s lucky, thought I might not be able to install it. That means I’d have to compile TWRP most likely.
And you might want to install FakeGapps before flashing noogle-magisk. Luckily it still boots, even though it removed some Google stuff.
Lots and lots of rebooting.
Damn mobile data, it already connected to internet. Guess I could just connect to WiFi before disabling a bunch of crap.
What happens if you disable stuff that says “replace with alternative” or whatever in App Manager? I’m too lazy to look for replacements, so I just disabled everything safe and replaceable.
And how do I disable a protected app?
Well, can’t setup a work profile. Bummer.
Debloating will make the stock ROM way faster. No wonder I wanted a custom ROM. But maybe they would work now, maybe the eSIM wasn’t fully setup or something stupid.
Cool, adb root is working now. Used this.
Nice it just rebooted for some reason. Just rebooted it with adb reboot, unlocked screen, still plugged in by USB, verified it’s me, so I can enable file transfer, then rebooted. Oh yeah also tried restoring the data that might have my text messages. Guess that didn’t work. No texts or call logs.
Just read the info when opening Shelter, you might need a AOSP non vendor ROM.
Well, the custom ROMs are way better. You don’t have to disable crap, and wonder what you need to enable to attempt to use Shelter.
Maybe this will fix it. AI crap on search engine said I need a MDM. Good job Motorola. Why do I need that? I don’t need any remote crap. And if you use it, it’ll have access to erase all data.
Somebody said you need Google’s device policy, looking for an alternative. Might be the same thing as MDM.
Only use that root adb enabler when you need root, might break adb install. Rather run adb install on computer. After disabling it, and rebooting, adb install works again.
Not sure multiple users is the same thing, enabled it and rebooted. First time, I didn’t reboot.
But it isn’t going to work, if I can’t use Shelter, or something like it.
When searching for work in settings, it finds a work profile thing now, wasn’t there before, but crashes if you try accessing it.
Apparently you need this, to fully debloat. If you have protected crap. App Manager can’t disable or remove it. Well, that suspicious PAKS crap might be disabled now. It didn’t actually have permission to do the things it can.
How do I install security updates? The latest one is from August, if you use a custom ROM, you can get a newer update.
Can malicious system services or drivers bypass Afwall+? If so, you need a custom ROM, and not a GSI ROM.
Shelter might need the GApps the phone comes with to enable the work profile, unless you use a custom ROM.
Nice Shelter might be working now. I installed the microG updates from F-Droid, different signature, so had to click install only. Says it’s downloading something. That took a long ass time. Not sure you are supposed to do that, if using noogle-magisk.
And it failed. Said Downloading, then failed. Maybe you aren’t supposed to update the microG apps if using the “LSPosed + FakeGapps” method. Or maybe I needed to run their script, or click action in magisk by the module. Or disable multi user option in settings.
I think my noogle-magisk install is broken anyways. So I removed it, and will reinstall. I installed it before FakeGapps. And I don’t think the action button fixed it.
Must have reinstalled the Google crap it removed, phone is super slow now. Well, that would explain why cheap Android phones can be slow. Thank Google for that.
And I might need to reinstall again. There should be two microG updates, so one thing is still the newer version. Well, I installed the other update anyways. And I need to debloat again, cause Google Play Store. is trying to run.
And that might be a fake Google Play Store or something.
There’s also this for debloating, can use computer instead, using adb.
Lots of rebooting to reinstall noogle-magisk and remove the newer versions of microG apks.
Hmm, maybe I need to erase the cache. F-Droid says there’s an update for something, that I can’t find. Not in settings under apps, and not with that debloater for the computer. Might have to manually delete from the folder, which will require root.
Why is Neo Backup so slow on the stock ROM?
Maybe to update it, you need the Gms whatever file, and F-Droid didn’t say anything about that. So just manually install the apks.
If I can’t make it work, I should look for some other magisk solution. Or just compile TWRP and hope it works.
Hmm, maybe those are the ones on F-Droid. They just call is GmsCore. Well, installed manually, from their GitHub apks.
I enabled the permission to interact with the work profile, that option wasn’t there before. Should have checked that before reinstalling and crap.
Now to lookup how to manually grant the permission, says it has no permission. Oh wait, I think you click action button on the module in magisk. Another reboot.
But if it’s installed as a user, it won’t work anyways.
LOL one of the microG apps got frozen. Didn’t realize I did that.
I’m trying to install using this method. But does that work with stock ROMs?
Used the Universal System App Installer. Well it’s booting.
And it’s finally working possibly. Didn’t just say Downloading and then failed when setting up Shelter. Nice.
If using Universal System App Installer, place com.android.vending-84022614.apk and com.google.android.gms-250932014.apk in system/app/priv-app/GmsCore/, just make the folders that don’t exist, inside the Universal System App Installer folder.
I might use it for other stuff too.
Well debloat, and install microG at your own risk. I’m reflashing the stock ROM, says no SIM card. Can’t access network settings. WiFi works, but can’t connect to anything else. And I forgot to look at that debloater computer program, to see if maybe it can fix it.
com.android.bluetoothmidiservice
com.android.egg
com.android.role.notes.enabled
com.bluetooth.aptxmode
com.google.android.apps.nbu.files
com.google.android.apps.restore
com.google.android.marvin.talkback
com.google.android.projection.gearhead
com.google.android.safetycenter.resources
com.motorola.bach.modemstats
com.oem.euiccpartnerapp
Hmm, it removed something for euicc.
I think what may have happened, is magisk crashed. Well, it did crash at least once.
Thought maybe the Universal System App installer thing did it. But it might have just been magisk crashing for some reason. magisk didn’t even show that module either, I tried removing all modules in Termux, and that didn’t work either. I then installed that module again, and it showed up that time. Didn’t fix anything though.
Removing all modules didn’t remove microG either. I guess that permanently installs stuff.
Going to flash it after I install magisk, and see if the same thing happens, so I know if I need a new method of installing it.
The Google thing in stock ROM looks what I thought was microG, so I doubt it was installed.
Disabling the RAM boost first. Then debloating with that computer program, so I can remove the Google crap before trying to install microG.
Got to reboot for magisk now as well, forgot about that.
All the RAM boost is, is like swap in Linux. It’s using disk space. A total of 8 GB should be plenty for me.
android.autoinstalls.config.motorola.layout
com.android.bluetoothmidiservice
com.android.calllogbackup
com.android.cameraextensions
com.android.cellbroadcast.overlay
com.android.cellbroadcastservice.overlay
com.android.egg
com.android.hotwordenrollment.okgoogle
com.android.hotwordenrollment.xgoogle
com.android.providers.partnerbookmarks
com.android.providers.settings.auto_generated_rro_product__
com.android.rkpdapp
com.android.role.notes.enabled
com.android.systemui.accessibility.accessibilitymenu
com.android.systemui.plugin.globalactions.wallet
com.android.theme.font.Exo2Regular
com.android.theme.font.RobotoSlabRegular
com.android.theme.font.RookeryRegular
com.android.theme.icon.pebble
com.android.theme.icon.round
com.android.traceur
com.android.virtualmachine.res
com.aura.oobe.motorola
com.bluetooth.aptxmode
com.dti.motorola
com.facebook.appmanager
com.facebook.services
com.facebook.system
com.google.ambient.streaming
com.google.android.accessibility.switchaccess
com.google.android.adservices.api
com.google.android.apps.docs
com.google.android.apps.googleassistant
com.google.android.apps.maps
com.google.android.apps.nbu.files
com.google.android.apps.photos
com.google.android.apps.restore
com.google.android.apps.safetyhub
com.google.android.apps.tachyon
com.google.android.apps.wallpaper
com.google.android.apps.youtube.music
com.google.android.as
com.google.android.as.oss
com.google.android.calculator
com.google.android.calendar
com.google.android.federatedcompute
com.google.android.feedback
com.google.android.gm
com.google.android.gms.location.history
com.google.android.marvin.talkback
com.google.android.ondevicepersonalization.services
com.google.android.onetimeinitializer
com.google.android.overlay.gmsconfig.asi
com.google.android.overlay.gmsconfig.photos
com.google.android.overlay.modules.captiveportallogin.forframework
com.google.android.overlay.modules.documentsui
com.google.android.overlay.modules.permissioncontroller
com.google.android.projection.gearhead
com.google.android.safetycenter.resources
com.google.android.tag
com.google.android.videos
com.google.android.youtube
com.google.ar.core
com.google.mainline.adservices
com.inmobi.installer
com.mediatek.apmonitor
com.mediatek.carrierexpress
com.mediatek.gbaservice
com.mediatek.MtkSettingsResOverlay
com.mediatek.SettingsProviderResOverlay
com.motorola.actions
com.motorola.actions.overlay
com.motorola.aiservices
com.motorola.android.coresettingsext.overlay.doubletap
com.motorola.android.fmradio
com.motorola.android.nativedropboxagent
com.motorola.android.overlay.crystaltalkai
com.motorola.android.providers.chromehomepage
com.motorola.android.systemui.overlay.sprint
com.motorola.android.systemui.overlay.tmo
com.motorola.android.systemui.overlay.usc
com.motorola.android.systemui.overlay.vzw
com.motorola.appdirectedsmsproxy
com.motorola.appforecast
com.motorola.attvowifi
com.motorola.bach.modemstats
com.motorola.bug2go
com.motorola.callredirectionservice
com.motorola.ccc.devicemanagement
com.motorola.ccc.notification
com.motorola.comcast.settings.extensions
com.motorola.contacts.preloadcontacts
com.motorola.demo
com.motorola.dynamicvolume
com.motorola.enterprise.adapter.service
com.motorola.enterprise.service
com.motorola.fmplayer
com.motorola.gamemode
com.motorola.genie
com.motorola.gesture
com.motorola.help
com.motorola.help.extlog
com.motorola.hiddenmenuapp
com.motorola.lifetimedata
com.motorola.livewallpaper3
com.motorola.mobiledesktop.core
com.motorola.moto
com.motorola.motocare
com.motorola.motocit
com.motorola.nfwlocationattribution
com.motorola.omadm.service
com.motorola.overlay.launcher3
com.motorola.paks
com.motorola.paks.notification
com.motorola.revoker.services
com.motorola.safetycenter.resources.overlay
com.motorola.securevault
com.motorola.securityhub
com.motorola.setup
com.motorola.slpc_sys
com.motorola.spaces
com.motorola.systemserver
com.motorola.systemui.desk
com.motorola.timeweatherwidget
com.motorola.vzw.pco.extensions.pcoreceiver
com.motorola.wifi.motowifimetrics
com.oem.euiccpartnerapp
com.verizon.loginengine.unbranded
That’s what it wants to remove, in the recommended section.
I doubt the paks thing caused my issue, I restored it, and it was still broken.
Couldn’t remove three things.
And you can change that program to disable instead of uninstall. Oh well, too late now.
Google is still in settings.
com.google.android.contacts
com.google.android.gms
com.google.android.gsf
com.google.android.overlay.gmsconfig.common
com.google.android.overlay.gmsconfig.comms
com.google.android.overlay.gmsconfig.geotz
com.google.android.overlay.gmsconfig.personalsafety
com.google.android.overlay.modules.permissioncontroller.forframework
com.google.android.partnersetup
com.google.android.printservice.recommendation
com.google.android.tts
com.google.mainline.telemetry
I removed all that too.
Will need that debloater thing to disable paks, or find another way to disable it.
That magisk debloater could have broke it too maybe. Probably not though.
Says “Phone is starting”. Might test my luck with the OneDrive ROM again. Cause debloating is a pain in the ass.
After root, maybe backup system. And it might be rebooting, nice. Nope, screen was off. But I don’t think it’s going to start.
Stupid key combo didn’t boot the bootloader. But might be booting correctly this time. Nope.
Is VN the right one for my phone? If not, I should just compile it myself.
Maybe I’m just too impatient, maybe it takes an hour or longer to boot.
Oh wait, did I reflash the stock ROM after it was taking forever to start? Maybe not. Guess I should do that, then flash that other ROM.
But I can possibly make a build for just my phone, won’t work for any other phones though, not many people seem to run custom ROMs on the moto g power 5G 2024. Probably because GSI kind of sucks.
Nope, still doing nothing.
Well, the stock ROM is basically clean now. So I could try other GSI ROMs on system.
Hmm the XDA post says “A/AB ROMS”, I think mine is A/B.
Would just a treble build be 64bit?
Seeing how much a pain debloating is, compiling a ROM seems like the better option now. Except, I have to manually compile every update.
What is A/AB? Should lookup how to tell. Or does that mean it’s for both? Ones with just A and AB? According to the AI, that’s the case. No idea why it won’t boot then.
I already tried not being rooted, or at least flashing original boot.img. Guess I’ll flash stock fully, including boot.img, and not change vbmeta this time.
A old post says to do the vbmeta thing though.
You can also use TWRP, but I’d have to compile it, and it’s more complicated if it’s encrypted.
Looking for a script to flash GSI, maybe somebody else knows what they are doing.
LOL, AI thinks a .bat file is a Linux script. Sure it is.
Here is a Linux script.
Looking at the script, it flashes everything in the folder, so I probably need to move a file out of there. And then move vbmeta out of there.
Hmm don’t think it’s working. Maybe I should read the instructions, and maybe I shouldn’t have deleted the file that was in there, some txt file. Maybe you put in the text file what you want it to do. I didn’t look that closely at script.
Nope, it’s looking for “vbmeta”, just search script for img, or vbmeta.
flash_image "${partition}${active_suffix}" $file
So it’s flashing whatever the file name is, and the slot. Cause partition is the filename without .img or .bin.
So you probably don’t want more then one system.img file in there.
You can uncomment something to see if it’s even finding the vbmeta file.
vbmeta_files:
Guess not. Yes, I’m restarting the script, over and over again, just like my phone. Not sure this script is easier. Might need to enhance it. But I’m lazy. Instead I’ll figure out why it’s finding nothing.
ls image_files/
vbmeta.img
There’s an image in there. I have sed and basename. Don’t tell me I have to run it in Distrobox.
I added “echo “$flash_files”” and it’s finding it.
But is it supposed to be “./image_files/vbmeta.img”?
Need to look at $img_files.
Hmm “${img_files[@]}”, not sure how for works in bash.
Either I’m blind, or it’s an empty array, because img_files isn’t declared anywhere. Might work for fastbootd, because it’s in another for loop. But that one isn’t.
Might be an easy fix, put the flash_files array, in the img_files.
Is this an incomplete script or something? Cause I can’t figure out how it’s supposed to get any vbmeta.img files.
vbmeta_files: ./image_files/vbmeta.img
Flashing vbmeta_a with ./image_files/vbmeta.img...
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.001s]
Finished. Total time: 0.004s
vbmeta_a flashed successfully!
Fixed it.
Add “img_files=$flash_files” to the right place, since they insist on using that variable, and I’m too lazy to change it to the right one, even with search and replace, I put it after the if that checks if there’s any img files. But I think I should have put quotes around it. And don’t use KWrite, it is annoying as fuck what it does, adds a bunch of unwanted quotes. Now to add quotes, but with nano.
Still works with quotes.
And if you’re lazy, and want to keep a shit ton of images in there, just add an extension to the end, like .bak, or .fuck, or .no.
You really do have to run 5 before 6, just look at script. But I only want to flash system. Or does the img file have more then system? In that case, I’ve been flashing wrong.
First I’ll see what it’s going to do though.
partition=$(basename "$file" | sed -E 's/\.(img|bin)$//')
Damn it, it needs system in the file. There’s an easy way to make the folder, use an ln -s, put every ROM in it’s own folder, with system.img and vbmeta.img, well vbmeta.img can be an ln -s too. Write a script to do all the work for you, just put the name of the folder in it, and it can rm the current ln, and make a new one.
But I’m lazy. And doubt this will boot anyways.
ln -s /run/media/external_ssd/gsi/lineage-22.2-20251015-UNOFFICIAL-gsi_arm64_vN.img /run/media/external_ssd/gsi/Android-Image-Flasher-main/image_files/system.img
That’s what I did.
If making a script, you just need “$1” and then pass the folder name to it.
And it isn’t working again, guess too many files, or you might need to use @ to get the entire array.
img_files=("${flash_files[@]}")
That should work, don’t copy what they use in the for loop. It’ll just be a string of everything in it, not an array. No I don’t know about bash arrays. I looked it up. Let’s see if the AI was right, too lazy to click every link to find the right answer.
And the vbmeta part works now.
Script doesn’t delete the product crap, so it has enough room.
Doubt the script does much more then I was doing, but I’m lazy, so I might make another script so I can be even more lazy. Or add it to that script.
Maybe make it reload the img files too. A menu option to do so.
Don’t think it erased userdata. It still doesn’t boot either.
Oops, you’re supposed to flash an empty vbmeta.img file..
Will touch vbmeta.img be good enough? Probably not, LOL.
But it might be empty, it’s only 8 Kb. But the one in the firmware folder, might work with other ROMs. No idea why though.
You can get a vbmeta.img from here. Even smaller then the one in the firmware.
Pretty sure that’s what I did with /e/OS, and it worked, but maybe magisk patched it or something. Do I have to reflash after doing that? Also I don’t think userdata got erased.
I think I’m going to modify the script to erase system before flashing it. And then flash it again, well it’ll do every img file, except for vbmeta.
Haha, haven’t seen that screen before, bootloader said it failed to boot.
Oh nice, it can’t boot at all, not even into fastbootd. Does that vbmeta.img kill fastbootd?
Well, time to reflash stock yet again.
Said to hook up to computer and run their software, that’s probably Windows only. I ran an old script that still works, you just need the firmware files. That’s how I updated it, without connecting it to internet.
fastboot erase "${partition}${active_suffix}"
In the script works. But I forgot to delete the product and product_a, maybe I only need to delete product_a.
Only need to delete a or b, whatever you are flashing to.
Damn, no official version of OrangeFox Recovery for moto g power 5G 2024. Trying to find a recovery, that I don’t have to compile.
Well, that ROM still won’t boot. And I flashed userdata before rebooting too.
Might just look at that other installer for microG. Maybe I don’t have to manually remove anything. And I don’t know what I’m doing. Don’t follow the above instructions for Universal App Installer, it probably won’t work.
Might just use Noogle microG again, if I go stock. Maybe try the crDroid or whatever.
Well, I finally took a dump, didn’t take one yesterday.
And that script doesn’t need a reload function, just delete system.img and make a new link.
Flashing crDroid now.
If I had a backup of the stock system, I could just flash that, instead of everything. Well, it might be in super. So either find a way to get it from that, or just flash super.
LOL this might not boot either. There it goes.
Where the fuck are these ROMs getting the IMS apk from? Cause it ain’t working. Going to install it manually, since wherever these ROMs are downloading IMS from doesn’t work anymore. Probably Amazon, they had a big outage. And Amazon sucks too.
And microG doesn’t have all permissions, was able to enable one, but apparently you have to tap in the exact right spot to get the popup. The permission to find accounts needs to be enabled.
I think the ims-mtk-r apk is wrong for the moto g power 5G 2024, not working in this either. Where’s the R+ vendor one? Or is it the same one?