I got my moto g power 5G 2024 today, and I set it up offline, no SIM card, or WiFi setup, and I already unlocked the bootloader.
The instructions are on XDA Forums, there’s’ a link somewhere on this site I think.
According to Treble Info, the moto g power 5G 2024 supports GSI, if anybody is wondering. Not like you’ll find this site if searching for that, I couldn’t find shit about GSI for it.
Goodbye warranty. Not that I give a shit.
You can find the firmware here. Or use their shitty Windows program, I can’t though. Probably doesn’t work in Wine.
In the process of rooting it, first I have to download firmware, to get the boot.img.
Can I only use Android 14 ROMS if I don’t update to 15? Hmm, guess I’ll download the newest firmware too.
Haven’t used it enough to know how much slower it is then the iPhone 15, if I care, I wouldn’t have bought a $150 phone.
LOL says to use SP Flash Tool to flash firmware, mtkclient doesn’t work, so I doubt SP Flash Tool does. Get a boot loop. Had to unplug phone, and hold power button down or something.
Which zip file has that DA file? And the moto g power 5G 2024 probably uses a different DA file.
Maybe the firmware file. Slow download speed. My SP Flash folder doesn’t have any DA files. mtkclient is better, not sure SP Flash even works for me, without doing even more work. Might on my desktop, but I mostly use laptop now, even though it has issues.
Not in firmware file, at least not the old version.
Wrong version of SP Flash “SP_Flash_Tool_v6.2228_Linux”, where the fuck did I get that? Cause it isn’t here.
LOL, might explain why it doesn’t work, and might be malware. Got it from the site with an s at the end, most likely.
“error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such fil
e or directory”
It doesn’t work either, cause I have no libpng12. Version not available in Ubuntu 24.04. Might have to use my old Ubuntu Distrobox.
Don’t follow old info to install an old deb file of it, doesn’t work. Trying the compile instructions now.
Maybe this will work, same CPU.
If not, I’ll have to use a script to flash the official firmware, as long as it doesn’t run any lock or unlock commands, it might be safe. But if it doesn’t boot, I’ll have a hard time fixing it.
Now redownloading V6 of SP Flash, apparently that version is needed.
DaHandler - Device is protected.
DaHandler - Device is in Preloader-Mode.
DAXML - Uploading xflash stage 1 from DA_BR.bin
DAXML - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x2000000
Preloader - Jumping to 0x2000000: ok.
DAXML - Stage 1 successfully loaded.
DAXML - Uploading stage 2...
Progress: |██████████| 100.0% Written (0x2A5/0x2A5, ) 6.39 MB/s
DAXML - Successfully uploaded stage 2.
DAXML - Successfully uploaded stage 2
DAXML - SLA is disabled
DAXML
DAXML - [LIB]: DA XML Extensions failed.
Good luck.
DaHandler - Device is protected.
DaHandler - Device is in Preloader-Mode.
DAXML - Uploading xflash stage 1 from DA_BR.bin
DAXML - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x2000000
Preloader - Jumping to 0x2000000: ok.
DAXML - Stage 1 successfully loaded.
DAXML - Uploading stage 2...
Progress: |██████████| 100.0% Written (0x2A5/0x2A5, ) 7.15 MB/s
DAXML - Successfully uploaded stage 2.
DAXML - Successfully uploaded stage 2
DAXML - SLA is disabled
DAXML
DAXML - [LIB]: DA XML Extensions failed.
Dumping sector 0 with flash size 0x400000 as boot1.bin.
Doesn’t work either, that file doesn’t exist. I tried two different preloader files. Hmm, didn’t try the old one from the old firmware, didn’t even extract that I don’t think.
Failed to dump sector 0 with flash size 0x400000 as boot1.bin.
File from old firmware doesn’t work either, does img need to be converted to bin somehow? According to XDA Forums, no, they are the same thing, with a different extension.
MT6855V/AZA
Maybe that’s why it doesn’t work.
And this script might still work, waiting for it to finish booting.
No way to backup phone apparently with mtkclient or SP Flash Tool, unless you can get the right files. Almost done booting. Put the latest firmware from here on it.
(bootloader) Preflash validation failed
So it can’t be rooted?
Checking if OEM Unlock is still on in settings, I tried unlocking it with fastboot again, and said it’s already unlocked.
Says it’s already unlocked in Developer Settings.
Oops, downloaded a pre release, there’s a bug report here. Trying version 27 now.
Nope, that’s broken too.
But update the firmware as Android 15 is faster, then 14 that it comes with.
Trying this now. “A-only device” well, not trying after reading that, LOL. Somebody said to use that, my phone is AB.
Why the fuck do you have to use an ARM64 device to install? Not on my desk. Maybe just push the apk and install that way.
Rooting may be the last thing I do, if it works. Then off to bed. Don’t want my sleep messed up anymore.
Still doesn’t work with version 27. Lots of rebooting too, while reinstalling it.
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Maybe that’ll fix it. LOL, downloaded the wrong 27 too. So I might not have needed to do that. Going to reflash that with enable instead. You have to reset it when doing that too.
Don’t bother, I think if you unlock bootloader, it already did that. So probably was already disabled, LOL.
fastboot flash vbmeta --enable-verification vbmeta.img
Maybe you can do that.
And it finally flashed without an error. No idea if the vmeta was needed, or just the right 27 version.
And another reboot. Maybe I can get the GSI /e/OS installed.
And you might want to extract the archive on your computer first. This phone takes a long time to extract it.
Finally rebooting, to try and boot /e/OS.
It’s booting, slowly.
How do I get root with GSI /e/OS? There’s just one img file in the archive, no boot.img. Didn’t inspect the image file though.
Maybe that adb command works. No adb command, might be in Developer Options though, see here.
Rebooting to see if it worked. And if you run adb reboot, it will reboot into stock ROM, open the DSI Sideloader, and tap reboot to GSI or whatever it said.
Need to go to bed though. Don’t need to stay up till 1 AM.
And the Magisk might work now, makes you reboot. Might reboot into stock ROM though,
If you know the “dynamic_system” partition, you can use adb shell “reboot dynamic_system” to reboot into it. See here. Too lazy to try and figure out which partition it is. Or maybe I should run the other command while /e/OS is booted, or better run mount.
Maybe eSIM only works if you have GApps, lame.
WiFi works, I copied a text file to phone, then copied and pasted the long random password.
Well, look up eSIM real quick, then off to bed.