that's the tmobile version?

If a modified boot.img runs, sounds like we're at the home stretch. If adb_debug.prop exist, it should be loaded if we create /force_debuggable in the boot.img ramdisk. This should run adb as root and get us started. Or maybe even just changing cmdline from "buildvariant=user" to "buildvariant=eng"
I couldn't find a new T408DL locally so I purchased online last night. Will be a few days for me to join back in the fun.

    Yes, it worked on my flip phone without any problems but problem is, when I attempted to use su on the adb shell, it gave me a "Permission denied" error. I suspect that it's because of the operating system's file system restrictions.

    • yeti replied to this.

      EnriqueMcquade

      it's suspected that the su binary is denied because the magisk app isn't installed.

      usually in a case of running su from adb shell, the magisk app will launch a prompt asking you to confirm su access for the shell application. Essentially, the device is rooted, but until we have some kind of write permission to the system, or can in some other way disable the app install block.

      I've been experimenting with magisk's Root Directory Overlay System to achieve this but haven't found much success.

      I've also played around with what neutronscott was talking about, but the image fails to boot on my device when the cmdline is set to eng.

            yeti So to have the su binary running, the Magisk app must be installed?

              Um, yes. But I don't have any problems flashing a patched image with an unlocked bootloader on my T408DL.

              yeti Sorry I looked back at the code and it checks for "userdebug" not "eng"

              Also Magisk comes with resetprop. [Login to see the link] can you use resetprop to set ro.vendor.tct.endurance to true or ro.build.type to userdebug

                  lgexalter1 I don't have additional steps. So anyway how the error looked like. It might be an incompatibility with the boot image I've provided to you because this boot.img is presumably tied to the T408DL.

                    EnriqueMcquade you mean it has an error or does it not set the property? After you set these you can try an apk install?

                      lgexalter1 I've heard that there are slight differences between the walmart family mobile t408dl and the tracfone t408dl. Which one do you guys have?

                        In fact, I have a Walmart Family Mobile version of the T408DL. Which I got from a local Walmart Supercenter in Georgia.