• Flip Phones

  • Instructions for installing a kosher ROM on TCL Flip2/Classic T408DL

VeeKay I think I got it already I didn't extract the files from the folder to the same folder as adb, looks like it's working now.

    It finally finished however after doing reboot< I see on my phone
    Secure Boot Failure!
    dm-verify corruption

    Your device is corrupt.
    It can't be trusted and may not work properly.
    Press power button to continue.
    or device will power off in 5 s

    Doesn't look good, any idea?

      VeeKay Lock and unlock the bootloader. Once you're rooted, the bootloader must remain unlocked.

          VeeKay I'm not exaclty sure where you're up to in regard to this phone, but if you've already flashed stuff to the phone, this may be the problem.
          Fastboot is the mode you boot into with autobooter. With your phone off, run autobooter and plug it in. Once you're in fastboot, run fastboot flashing unlock and see if it fixes the issue.

              what can maybe be done wrong is about the MTKMeta and Drivers, was anything supposed to be done with them?

              Biden2020prez To be more specific just seeing now On the post mentioned I missed number 2. "Open the MTK Meta Tool that you downloaded above and select ‘Reboot Fastboot Mode’"
              I realize now thats because I followed partially the instructions in the beginning of this post, that didn't mention anything about #2 in the post.
              but I mixed the instructions of both.
              What now?

                  VeeKay Don't follow that guide, its outdated. Try following Dartths guide on the top post here from start to finish.

                  also, are you on the latest software update?

                      Biden2020prez Not sure about the software it was brand new out of box not yet any service connected.
                      Now it's too late I cant access the phone.
                      I can try to start over again I hope it's gonna work.

                          VeeKay Yes try starting over again using the instructions here. It's actually good that you aren't on the newest update, which caused issues for some people.

                              Jumptoheaven Well, not exactly sure. [Login to see the link] mentioned to me in private that he bricked some phones when flashing certain partitions from a previous update to a phone with the newest update. Also, someone emailed me about bricking two phones when installing a kosher rom, and I suspected that maybe it was because he was on the newest update, but he never replied back to my email (so far)....

                              So I guess I am just not sure whether or not it's safe to flash the old super with new update.

                              (on a side note, the new update relocks the bootloader, which is a little strange).

                                  • darthLevel 6 - Platinum Elite Member

                                    • Post #671

                                    VeeKay It finally finished however after doing reboot< I see on my phone
                                    Secure Boot Failure!
                                    dm-verify corruption

                                    Your device is corrupt.
                                    It can't be trusted and may not work properly.
                                    Press power button to continue.
                                    or device will power off in 5 s

                                    Doesn't look good, any idea?

                                    Biden2020prez Try pressing the power button. The phone should then boot normally.

                                          darth I tried that several times, also tried to start over but the same message pops up instead of asking permission to unlock bootloader.

                                            VeeKay The phone is off and you're plugging it in when it's saying that?

                                                VeeKay Are you sure you're plugging the phone in while autobooter is running (dots should be poping up)? I had the same error before.