[EXPERIMENTAL] TWRP Dirty Port for Moto E6

EnokiPPT

Senior Member
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.
I did a dirty port of the Aquaris U2 image.

What works:
It boots past the splash screen (even without wiping userdata, from my tests), and now the entire screen is used, as compared to a portion of the screen at the top not being used with the one in the past few pages.

What doesn't:
Touch screen, and I'm not sure how to fix it. Can't test anything else because of that.

https://drive.google.com/open?id=1qTT7pZPHcN5J5bTP8y5s6afods_l3ZOk
 
  • Like
Reactions: Spaceminer

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
I did a dirty port of the Aquaris U2 image.

What works:
It boots past the splash screen (even without wiping userdata, from my tests), and now the entire screen is used, as compared to a portion of the screen at the top not being used with the one in the past few pages.

What doesn't:
Touch screen, and I'm not sure how to fix it. Can't test anything else because of that.

https://drive.google.com/open?id=1qTT7pZPHcN5J5bTP8y5s6afods_l3ZOk
You're learning fast... This is excellent work! I can probably make the touchscreen work with this one. Fingers crossed, I'll give it a go. Try those adb commands and see if it'll get you past the swipe screen. I can give you commands to load drivers if adb will work.

---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------

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
You have a snapdragon 435. The US ones do anyhow.
 
  • Like
Reactions: koyo

koyo

Senior Member
Nov 12, 2015
267
43
48
You're learning fast... This is excellent work! I can probably make the touchscreen work with this one. Fingers crossed, I'll give it a go. Try those adb commands and see if it'll get you past the swipe screen. I can give you commands to load drivers if adb will work.

---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------



You have a snapdragon 435. The US ones do anyhow.
Weird. Things like CPU-Z and websites were telling me I have a Snapdragon 430. I was wrong
 

EnokiPPT

Senior Member
You're learning fast... This is excellent work! I can probably make the touchscreen work with this one. Fingers crossed, I'll give it a go. Try those adb commands and see if it'll get you past the swipe screen. I can give you commands to load drivers if adb will work.

---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------



You have a snapdragon 435. The US ones do anyhow.
Can't run the adb commands because now my phone isn't picked up in adb with this twrp img.
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
Can't run the adb commands because now my phone isn't picked up in adb with this twrp img.
If you swapped the default prop from stock then you'll need to change some adb flags. All the needed ones are near the top of the images that I've edited so far if you take a look. Have you tried the kernel trick already with your new one?
 

EnokiPPT

Senior Member
If you swapped the default prop from stock then you'll need to change some adb flags. All the needed ones are near the top of the images that I've edited so far if you take a look. Have you tried the kernel trick already with your new one?
I only changed the stuff in the split_image folder (and possibly changed some text on the splash screen to be something immature), so idk if I changed the prop. If I did, what are the flags I need to change? Also, I did try the kernel trick, as I replaced everything in the split image folder with the stuff from the stock recovery (and added dtbo and something else because they weren't there.)

---------- Post added at 04:06 PM ---------- Previous post was at 03:28 PM ----------

If you swapped the default prop from stock then you'll need to change some adb flags. All the needed ones are near the top of the images that I've edited so far if you take a look. Have you tried the kernel trick already with your new one?
Also, where are the adb flags located?
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
I only changed the stuff in the split_image folder (and possibly changed some text on the splash screen to be something immature), so idk if I changed the prop. If I did, what are the flags I need to change? Also, I did try the kernel trick, as I replaced everything in the split image folder with the stuff from the stock recovery (and added dtbo and something else because they weren't there.)

---------- Post added at 04:06 PM ---------- Previous post was at 03:28 PM ----------



Also, where are the adb flags located?
I'm actually fixing that right now, and making scripts to load your drivers to see if touch will work. It's at the top of the default.prop or prop.default. I always forget which. One is just a symlink.
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
Oh, alright. Thank you!
No problem. This is based off your u2 port. Hopefully touch works this time. I'm thrilled you got it to the point that wiping data isn't needed. You might've lead me to a fix that we need for the G7 Play's TWRP in the process. I have one more test incoming after this. If either of these bootloop, then I might just need to add verity keys.

twrp-touchtest1.img

twrp-touchtest2.img
 
Last edited:

EnokiPPT

Senior Member
No problem. This is based off your u2 port. Hopefully touch works this time. I'm thrilled you got it to the point that wiping data isn't needed. You might've lead me to a fix that we need for the G7 Play's TWRP in the process. I have one more test incoming after this. If either of these bootloop, then I might just need to add verity keys.

twrp-touchtest1.img

twrp-touchtest2.img
It doesn't bootloop, but the touch screen still isn't working and adb won't recognize my phone either.
 

EnokiPPT

Senior Member
Well this is a head scratcher to say the least. I guess we can take a break for now and I'll do some research in the meantime. We're damn close, but something is obviously still off. It's really been a pleasure working with you on this so far.
Yeah. I'm going to find some other phones with the same chipset and also try to learn how to make the touch screen work on the images.
 
Last edited:

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
Yeah. I'm going to find some other phones with the same chipset and also try to learn how to make the touch screen work on the images.
No sooner than I made that statement did I realize something else that might be amiss. The fstabs. I decided to check, and there was a slot select flag for vendor, which might've prevented the touchscreen drivers from loading. I'm really going to take a short break after this one, but I couldn't help but try it.

twrp-touchtest4.img
 

EnokiPPT

Senior Member
No sooner than I made that statement did I realize something else that might be amiss. The fstabs. I decided to check, and there was a slot select flag for vendor, which might've prevented the touchscreen drivers from loading. I'm really going to take a short break after this one, but I couldn't help but try it.

twrp-touchtest4.img
First, I just want to thank you for all you've done so far. You're a legend. Secondly, I'll see how much I can learn by looking at it and trying to get the adb drivers and touch to work. Take as much time as you need on your break, and don't stress yourself.
 
Last edited:
  • Like
Reactions: Spaceminer

Spaceminer

Senior Member
Sep 9, 2016
1,159
548
123
Olympus Mons
First, I just want to thank you for all you've done so far. You're a legend. Secondly, I'll see how much I can learn by looking at it and trying to get the adb drivers and touch to work. Take as much time as you need on your break, and don't stress yourself.
You can learn a lot. Look in /ramdisk/sbin for a file named load_drivers.sh (might be slightly off with the name) Open it with a text editor. That's how drivers are loaded for the G7 Play in twrp. Check one of the recent attempts I made. You should find the script in any of them. My best guess is that you might use a different display panel than wistron.
 

EnokiPPT

Senior Member
You can learn a lot. Look in /ramdisk/sbin for a file named load_drivers.sh (might be slightly off with the name) Open it with a text editor. That's how drivers are loaded for the G7 Play in twrp. Check one of the recent attempts I made. You should find the script in any of them. My best guess is that you might use a different display panel than wistron.
How can I figure out the panel w/o root?
 

EnokiPPT

Senior Member
Run this command. It shouldn't need
root.
Code:
cat /sys/devices/virtual/graphics/fb0/panel_supplier
Seems the panel supplier for my phone is djn. Looking at the code in load_drivers.sh, the panel is a djn nova_36525_mmi.
Then I ran a google search the panel name and found some code you provided on the G7 forum https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page40, which I might be able to use to make the touch screen work! I'll get back to you later to let you know the result.

Edit: Still no touch screen so far, going to keep trying.
 
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone