TCL Flip 2 Phone (Master Thread)

Only the original one will work?

think so

1 Like

So this is the one?

Yes

1 Like

So just to clarify,

I can take a rom from the updated ones @darth posted

not a difference if KEFS or KEKA,

And repack the super with my vendor.img from my 4058G,

And flash the super, and then flash the boot.img from neutron that made for KEFH,

And it’s supposed to work?

I wasn’t the one that tried it, and i would assume that better to not use KEKA

1 Like

And what about KEFS?

Then maybe try with the kefs boot.

1 Like

Think those 2 are the same. Only keka is different.
Also, I would flash the boot before the super.

3 Likes

If I try one boot.img and then flash a ROM

And it doesn’t work, can I fix it by flashing another boot.img or whatever?

(You all keep saying that I should try it but I’m scared that I’ll brick it and not be able to get it working again)

I don’t think the wrong boot will brick.
Not guaranteeing anything though.

1 Like

It could make sure you have a backup first of the stock boot

1 Like

Always a good idea.
But I was talking about permanent bricking

1 Like

I don’t understand what you mean?

1 Like

Can someone edit the vmouse2 to remove the whole pressing 3 feature because when i press it by accident the mouse stops working until a reboot?
vMouse.zip (29.7 KB)

Hi. I just managed to use the neutronscott guide to install Magisk onto my TCL Flip 2 (model 4058g) but there’s a funny irony… I can’t access the settings in Magisk.

Like, physically, it won’t scroll up. As if it’s not a real button.

Did I mess up somehow or do I need to also install the mouse to actually click on it?

I should note this is my first time EVER rooting a phone so if I’m a bit dense I apologize.

U need a mouse, i think neutron Scott has a guide about putting on a mouse

Dang. Thought I could delay installing another thing (it’s late lol) but I guess I’ll need to get back to it in the morning! Thank you though.

1 Like

Okay, I thought I figured it out, deleted my comment, and was wrong. Now I’m at a loss.

I tried to copy the file for the vMouse to my phone so I could load it using Magisk, but it says it’s a read-only file system. I thought maybe the issue was related to neutronscott’s related comment on the guide about disabling the power-on write protection so I tried to disable it and it didn’t work. Essentially, I tried giving superuser access but my phone went to sleep before I could click allow in the Magisk popup, and it denied it, and I tried giving SU access within the Magisk app but it doesn’t seem to be working? Do I need to uninstall and reinstall Magisk? I’m kinda at a loss here. Feels like I failed a quicktime event

Edit: I realized I could revoke the SU access within Magisk and try again and I did, and I successfully enabled SU. It STILL says it’s a read-only file system. Help

Run adb shell su -c /vendor/bin/write_protect 0 that should disable write protect and install the mouse using the adb commands given not magisk itself, you shouldn’t need to disable write protect

1 Like