Do I need to unlock the bootloader in order to modify the system.img file in the firmware?

[MasLnd]

I'm trying to add an APK to /system/priv-app in a Droid Maxx by modifying the firmware.

Using simg2img and make_ext4fs on ubuntu, I can unpack and repack the system.img file, place it back into the firmware, and flash it successfully.

But when I do the same thing, and add the APK to /system/privapp, I get the following errors:

Invalid entry hash for system: index=0

and

Preflash Validation failed

There were more steps than this, I just didn't want to get too detailed, in case there was an easy answer to this question.

The original firmware file is: CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml.zip

Thanks

 

[B. Diddy]

Moved to the Maxx Rooting forum.

 

[doogald]

Speaking as somebody who has not unlocked the bootloader or rooted the phone, so I can't say from experience - but, yes, the bootloader must be unlocked. As far as I know, the bootloader is insistent on images signed by Motorola's private key.

That said, the current root method somehow gets around it. If you can figure out what the rooter did, you could possibly create your own image and load it. I'm not 100% sure about that, but that person figured it out.

See [ROM] Droid Mini/Maxx/Ultra L!te FW 6-7-3 ML | Motorola Droid Ultra and Droid Mini/Maxx/Ultra Root / XPosed / BusyBo… | Motorola Droid Ultra

Maybe if you contact that OP you can either get instructions or he/she will create a build for you?

 

[MasLnd]

Yes, I have been looking at CrashXXl's work too.

No luck yet. With my particular issue.

Thanks for replying