[EXPERIMENTAL] TWRP Dirty Port for Moto E6

[EnokiPPT]

Try this. It's going to make all modules in vendor load. This should also force the touchscreen to work. Then we just need to narrow down the specifics from there. Shouldn't be too hard. TWRP will probably show some linker errors. It should be safe to ignore. Adb should be forced on by default now.

twrp-edited.img

Still no touch screen.

 

[Spaceminer]

Still no touch screen.

Let me make sure I don't have a typo, we might need to add the kernel from the stock recovery to the split image folder. Try those adb mount commands from my previous post and see if they work.

 

[EnokiPPT]

Let me make sure I don't have a typo, we might need to add the kernel from the stock recovery to the split image folder. Try those adb mount commands from my previous post and see if they work.

I think it's gotten a step further, but now I have this error:

error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

 

[Spaceminer]

I think it's gotten a step further, but now I have this error:

error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I do have a typo in the scripts that load the touchscreen. One moment and I'll fix that. Try running

adb kill-server

 

[EnokiPPT]

I do have a typo in the scripts that load the touchscreen. One moment and I'll fix that. Try running

adb kill-server

I did try that, but I still got the same error.

 

[Spaceminer]

I did try that, but I still got the same error.

Okay, I'll see what I can do about the adb problem. This should at least fix the touch screen. I checked more than once after editing it.

twrp-fixed.img

 

[EnokiPPT]

Okay, I'll see what I can do about the adb problem. This should at least fix the touch screen. I checked more than once after editing it.

twrp-fixed.img

This one isn't working either. Still no touch screen.

 

[Spaceminer]

This one isn't working either. Still no touch screen.

Try replacing the kernel in the TWRP split image folder with the one from your stock recovery.

 

[EnokiPPT]

Try replacing the kernel in the TWRP split image folder with the one from your stock recovery.

The twrp-fixed.img-kerneloff? Because it's the only thing in that folder that says kernel

 

[Spaceminer]

The twrp-fixed.img-kerneloff? Because it's the only thing in that folder that says kernel

It's actually named recovery.img-zImage in aik. I forgot that happens. If magisk unpacks it it'll name it kernel. I think I discovered the touch issue. The scripts were setup to look for a vendor slot, which you guys don't have since you're not a/b. I got another test incoming. This might fix it.

 

[EnokiPPT]

Try replacing the kernel in the TWRP split image folder with the one from your stock recovery.

I replaced the kerneloff file with stock one and still no touch screen.

 

[Spaceminer]

I replaced the kerneloff file with stock one and still no touch screen.

Try this.

twrp-test3.img

 

[EnokiPPT]

Try this.

twrp-test3.img

Still no touch screen.

 

[Spaceminer]

Still no touch screen.

Try the kernel thing with this one too.

 

[koyo]

Try the kernel thing with this one too.

I want to thank you for the hard work you're doing man. Many lurkers are watching this thread and hoping you get to the bottom of this. God speed kind stranger

 

[EnokiPPT]

Try the kernel thing with this one too.

Found the ZImage thing lurking at the bottom and replaced it along with the dtbo, but still nothing.

 

[Spaceminer]

Found the ZImage thing lurking at the bottom and replaced it along with the dtbo, but still nothing.

I'm going to try to find another device with the same soc and TWRP, and rebuilding from that. We're close to fixing this. I'll need to do some thinking though.

 

[EnokiPPT]

I'm going to try to find another device with the same soc and TWRP, and rebuilding from that. We're close to fixing this. I'll need to do some thinking though.

Not entirely sure, but the Aquaris U2 might work. It has a Snapdragon 435 and is officially supported by TWRP.
https://twrp.me/bq/bqaquarisu2.html

 

[Spaceminer]

Not entirely sure, but the Aquaris U2 might work. It has a Snapdragon 435 and is officially supported by TWRP.
https://twrp.me/bq/bqaquarisu2.html

That's a good lead. We can also try the Moto E5 Plus. (Hannah) So we've got 2 matches. The image needs to be arm32. I'll check them out.

 

[koyo]

That's a good lead. We can also try the Moto E5 Plus. (Hannah) So we've got 2 matches. The image needs to be arm32. I'll check them out.

Am I insane or are we taking a TWRP made for a Snapdragon 435 device when we're using a Snapdragon 430? You are the developer guy here so you might know better than me