Damn its sounding bad already
Sent from my moto g(7) play using Tapatalk
Sent from my moto g(7) play using Tapatalk
It's not looking good at the moment. The scrcpy method won't work with twrp booted up. The OS has to be booted, so it doesn't do me any good. I found an OTG cable and that method doesn't work either. So I'm stuck with the dtbo problem again.
I find it extremely hard to believe that not one person on xda can explain how to build that. (Especially when there's several people building them right now.) There's like one guide for xiaomi devices and it's really not even a guide. The android developer website, just tells you the tool that's used to make it. But... Not how to build the tool, how to use the tool, or where I can download it. They technically tell you how to build it, but it fails to compile due to some python error that no one has a solution to. All I need is information! It shouldn't be this hard... It really shouldn't be this hard.
Damn another set back what was the Discovery you found to making everything work?
Sent from my moto g(7) play using Tapatalk
I figured out how to write the fstabs correctly. But if I can't use twrp at all, I can't really do anything with that knowledge. This is a huge problem, and I really can't find a solution. I've tried to build a dtbo for over 6 months, and haven't succeeded yet. There just isn't enough information. Google did not, and probably never will, provide enough information for people to get into android development. This is a huge reason why good devs are almost non existent.
The people who know how to do it, need to start talking, because without that info I'm stuck indefinitely. There is literally not enough documentation about this. And the little that does exist, is lacking so much, that I might as well sh*t in my hand if I hope to get anything out of it. You guys have no idea how frustrated I am with this BS. I've reached out to many people who I know can do this, and none have responded.
isn't this documented by motorola - you have the sources there should be instructions how to build? why can't you use TWRP it has a command line usage from adb?
I'm going to get my head right... and revisit this tomorrow. I really hate it when crap is this difficult, but if there's a way to make this work I'm going to find it.
As corny as this sounds l believe in you ..
Sent from my moto g(7) play using Tapatalk
Here's Motorola's joke that they call instructions. There are no steps. It's essentially...
Install the tools
(They tell you to check all the readmes to find the tools you'll need. There's thousands of readmes in the documents folder. There's no list of tools either.)
Install the kernel sources, and apply all Linux patches...
(Which patches and where are they? Also, if you do download and extract the kernel sources, you're still missing critical parts they don't tell you about. You'll figure it out when you get errors.)
They tell you that you must have gcc 3.2+ available.
(Not a problem, but go ahead and try gcc 7, 8, 9, or even clang which Android Pie is supposed to compile with by default. You'll get error after error. Look for a solution for days. Finally fix it. Then find a new error 5sec after restarting. Repeat until you're burnt out.)
List a bunch of options and variables that don't apply to your specific device.
Include configs for 90 other devices, in your device specific kernel sources... for no reason.
(Your device's config is also in another folder, and you need to manually move it to the right one for "make" to work. It's not in arch/arm(or arm64)/configs. They don't tell you this anywhere.)
You now have a new kernel.
(No you don't.)
If you have problems email us @ ...
(You will have problems. They won't respond.)
I could write a novel on this stuff.
Last edited:
hm.. other thread from @scritch007 isn't helpful? seems he did it
Yeah building the kernel has been working since the beginning.
I don't know how hell I missed that... Thank you! This is exactly what I needed to see. Round 2 begins now...
Success!
@scritch007
I really can't thank you enough for the info that you left us here. I would've been at this for ages. This was the missing piece of the puzzle that I needed.
@PoochyX
It's all over! I got the touchscreen to work. I can fix everything now. I'm going to burn the midnight oil and try to get working builds up by tomorrow.
@scritch007
I really can't thank you enough for the info that you left us here. I would've been at this for ages. This was the missing piece of the puzzle that I needed.
@PoochyX
It's all over! I got the touchscreen to work. I can fix everything now. I'm going to burn the midnight oil and try to get working builds up by tomorrow.
Attachments
Unofficial TWRP
*Fixed touchscreen drivers for xt1952-4 RETUS
For those of you who know what you're doing, you shouldn't have a problem using this. For anyone else, I will post very detailed instructions when this is more stable.
xt1952-x: twrp.img
DTBO: dtbo.img
For developers:
ilitek_mmi.ko -- touchscreen digitizer
drv2624_mmi.ko -- vibration
*Fixed touchscreen drivers for xt1952-4 RETUS
For those of you who know what you're doing, you shouldn't have a problem using this. For anyone else, I will post very detailed instructions when this is more stable.
xt1952-x: twrp.img
DTBO: dtbo.img
For developers:
Code:
#!/sbin/sh
load_panel_modules()
{
path=$1
panel_supplier=""
panel_supplier=$(cat /sys/devices/virtual/graphics/fb0/panel_supplier 2> /dev/null)
case $panel_supplier in
[COLOR="green"]+ dsbj)
+ insmod $path/ilitek_mmi.ko
+ insmod $path/drv2624_mmi.ko
+ insmod $path/nova_36525_mmi.ko
+ ;;[/COLOR]
djn)
insmod $path/nova_36525_mmi.ko
;;
tianman)
insmod $path/nova_mmi.ko
;;drv2624_mmi.ko -- vibration
Twrp in this post doesn't even format data with the yes option gives crypto header error
Sent from my moto g(7) play using Tapatalk
I'm aware. It's missing f2fs files. The original twrp doesn't format /data for me either for the same reason. I'm working on it.
Also restoring a backup Still doesn't work
Sent from my moto g(7) play using Tapatalk
Try this one. I think I have everything fixed. It bootloops if the stock OS is installed though, and I still can't figure out why. The advanced > fix recovery loop trick in twrp doesn't fix it. This one definitely formats data and mounts all the partitions correctly. I haven't tested backup/restore yet.
By the way, can you link me a GSI that you know will boot up? I tried Phh's Pie GSI and it refuses to start. It doesn't matter if I'm using the stock boot image or a rooted one. Same result. It always loops, even when installed through fastboot with data wipes.
twrp.img
Andy Yans Lineage 17.1 boots up
Havoc 11.19 boots up
Havoc 3.2 with gapps boots up
Extended UI boots up
Arrow Boots up
Android 9 Dot Os Boots Up
Sent from my moto g(7) play using Tapatalk
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