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

  • darthLevel 6 - Platinum Elite Member

    Always That looks like you miss typed a command.

    • darthLevel 6 - Platinum Elite Member

      I can confirm these Roms work on the 4058l (UScellular version). I am now confident they should work on all 4058 variants also.

        darth It didn't work even before I got to that step.

        darth Great work, I do have 1 question though, my phone model is the TCL Flip (4058E) you said it was tested on t408dl and 4058I so would it brick my phone if i try it on my model?

        EDIT: I saw your latest comment that it should work on all 4058 models, what happens in the case of a brick though? or if i want to revert to the Original firmware, how would i go about doing this?

        Proflip I have the exact same version as you (4085E), have you managed to get the kosher rom working?

          darth
          my phone is finally being recognized by my computer. but when I run the voice access in the cmd, it says "adb" is not recognized as an internal or external command, operable program or batch file". what do I do? Thanks!

            • darthLevel 6 - Platinum Elite Member

              joe1234 Are you running the commands from the directory you have adb in?

                Did anyone have success with installing a Hebrew keyboard on the TCL Flip 2?

                  • darthLevel 6 - Platinum Elite Member

                    AShayish The a4f Hebrew keyboard works fine it just doesn't have t9.

                      joe1234 If you are using PowerShell instead of command prompt you may have to type .\adb or you could open a command prompt in the adb directory by typing cmd in the bar on top where the file path is.

                        whynot

                        whynot open a command prompt in the adb directory by typing cmd in the bar on top where the file path is

                        I tried that..

                          joe1234 was the folder where adb is stored open? it should be something like C:\Users\Username\Desktop\platform-tools_r33.0.2-windows\platform-tools and not C:\Users\Username\Desktop\platform-tools_r33.0.2-windows

                            manyhill
                            set your gmail account using @googlemail.com instead of @gmail.com using a app password and it won't try to jump to the browser. You may need to enter the imap settings manually.
                            It worked for me.

                            Just got this phone and did allot of diff flashing, the custom roms are nice, and especially when they can be flashed in under 2 min by using the recovery method. Thanks everyone for your work.
                            Just wanted to know:
                            Is there a more conventional way to list apps installed other than dialing a code on the keypad?
                            Once i flash one of the custom roms, can i flash this phone back to original stock rom?
                            i also would like to test apps on this phone, but flashing [Login to see the link] img didn't work for me, i tried to flash it after i flashed one of [Login to see the link] roms. If anyone can help me get [Login to see the link] img to work i would appreciate it.
                            Also, seems that usb debbuging post flashing is not so simple, if you reboot the phone a few times it might work if your lucky, maybe that can be fixed.

                              • darthLevel 6 - Platinum Elite Member

                                MXRJR For listing apps and installing apps ask on the other thread. These Roms that I made dont allow for app installation even with [Login to see the link] img. [Login to see the link] made an app that works as a shortcut for dialing the keypad code which you can use one of your directional keys to launch, again I think thats posted on the other thread!

                                While attempting to flash one of the roms, I'm having weird issues. mtk meta boots it into fastboot mode, but there I run into issues. This is whats happening.
                                (It does prompt me to unlock using volume keys, which I do.)
                                `C:\Users\g\Documents\My Programs\adb\platform-tools>fastboot flashing unlock
                                FAILED (Write to device failed (no link))
                                fastboot: error: Command failed

                                C:\Users\g\Documents\My Programs\adb\platform-tools>fastboot flashing unlock
                                FAILED (remote: 'unknown command')
                                fastboot: error: Command failed

                                C:\Users\g\Documents\My Programs\adb\platform-tools>fastboot flashing unlock
                                (bootloader) Start unlock flow

                                OKAY [ 0.006s]
                                Finished. Total time: 0.016s

                                C:\Users\g\Documents\My Programs\adb\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.bin
                                (bootloader) Start unlock flow

                                Rewriting vbmeta struct at offset: 0
                                Sending 'vbmeta' (1024 KB) FAILED (remote: 'GetVar Variable Not found')
                                fastboot: error: Command failed

                                C:\Users\g\Documents\My Programs\adb\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.bin`

                                If anyone has any ideas I'd be grateful....

                                  whynot C:\Users\Username\Desktop\platform-tools_r33.0.2-windows\platform-tools

                                  thats what it is

                                  [Login to see the link] I was having issues flashing super on my T-Mobile 4058 using the recovery method, getting this error:

                                  adb: error: failed to copy 'super.bin' to '/dev/block/mmcblk0p41': remote write failed: No space left on device

                                  After much back and forth, I found the issue. I ran:

                                  adb shell readlink /dev/block/by-name/super
                                  //And it returned: 
                                  /dev/block/mmcblk0p42

                                  So I ran the commands as mmcblk0p42, and it worked.