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.

      If the image is compatible with the T408DL, maybe I slightly made an error making the image or what could be possibility go wrong with such image?

      It looks like the patched boot img doesn't boot with tracfone, only walmart family mobile

      My phone arrives tomorrow night hopefully. I made an attempt at writing a quick custom script that runs on boot using the patched.img that darth posted. It polls /data/local/tmp for *.sh files every 5 sec. It writes a .out file and skips .sh which already have a .out. Hopefully all running as root. If it works you should be able to do something like:

      cd /data/local/tmp
cat >1.sh <<EOF
resetprop ro.vendor.tct.endurance true
resetprop ro.build.type userdebug
EOF

      Wait 5 sec and check the properties...

      [Login to see the link]

      Maybe I uploaded the wrong one. My phone just arrived and I've lots of ideas so hopefully tonight after work one of them works for us.

      I've uploaded the new image in the same place if anyone wants to play with it. It just runs a script that looks for scripts in /data/local/tmp/*.sh that it will run as root.

      eb50480572980ab6894b08789bbc47f0 neutron.img
      [Login to see the link]

        • darthLevel 6 - Platinum Elite Member

          • Post #357

          neutronscott Your img booted fine but when trying to run su it still says Permission denied. And in /data/local/tmp there are no .sh files all thats showing is: mtk-su myscript.out. Am I supposed to be doing something to make your script run?

            • darthLevel 6 - Platinum Elite Member

              • Post #359
              • Edited

              lgexalter1 I tried pushing a basic script and got the following errors: resetprop: __system_properties_init error
              resetprop: __system_properties_init error               which is the same error it throws when I try using resetprop in adb. (Thanx for asking around for a magisk exploit 😉 )

                • darthLevel 6 - Platinum Elite Member

                  • Post #361
                  • Edited

                  lgexalter1 Interesting... adb shell getprop ro.build.type returns userdebug andadb shell getprop ro.vendor.tct.endurance returns a blank line, in fact it seems there is no prop ro.vendor.tct.endurance.

                    I made it as a way to test things as root until more is discovered. For example:

                    Gflip6_TF:/data/local/tmp $ echo 'cat /vendor/build.prop' > 3.sh; sleep 5; cat 3.out | head

ro.boot.dynamic_partitions=true
ro.product.first_api_level=30
ro.vendor.build.security_patch=2021-09-05
ro.vendor.product.cpu.abilist=armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist64=
ro.product.board=gflip6
ro.board.platform=mt6739
ro.hwui.use_vulkan=
Gflip6_TF:/data/local/tmp $

                    • TechgenLevel 6 - Platinum Elite Member

                    • Post #366

                    lgexalter1 Definitely!

                    darth
                    I'm excited (and waiting) to hear the details of the breakthrough

                        • darthLevel 6 - Platinum Elite Member

                          • Post #367

                          Right now it can be done with using the boot.img neutronscott provided and than running the following commands from adb shell:
                          /data/local/tmp $ echo 'resetprop ro.build.product gflip6gc' > /data/local/tmp/1.sh
                          /data/local/tmp $ echo 'pkill system_server' > /data/local/tmp/2.sh

                          [Login to see the link] is working on simplifying his boot.img to not need these commands.

                            Now that we are able to modify the properties to allow installs, next step is to get a MDM based filter working on it!