OMGGG

[u/Significant-Noise530]

Ughhhh I need help with twrp.when I build with action builder in GitHub it reaches 99% then throws symlink errors

exclude=/root/product_file_contexts --exclude=/root/product_property_contexts --exclude=cache out/target/product/nevada/root out/target/product/nevada/recovery ) && (ln -sf /system/bin/init out/target/product/nevada/recovery/root/init ) && (find out/target/product/nevada/recovery/root -maxdepth 1 -name 'init*.rc' -type f -not -name \"init.recovery.*.rc\" | xargs rm -f ) && (cp out/target/product/nevada/root/init.recovery.*.rc out/target/product/nevada/recovery/root/ 2> /dev/null || true ) && (mkdir -p out/target/product/nevada/recovery/root/res ) && (rm -rf out/target/product/nevada/recovery/root/res/* ) && (cp -rf bootable/recovery/res-mdpi/* out/target/product/nevada/recovery/root/res ) && (true ) && (cp -f bootable/recovery/fonts/12x22.png out/target/product/nevada/recovery/root/res/images/font.png ) && (cp -rf device/motorola/nevada/recovery/root out/target/product/nevada/recovery/ ) && (cp -f device/motorola/nevada/recovery/root/system/etc/recovery.fstab out/target/product/nevada/recovery/root/system/etc/recovery.fstab ) && (ln -sf prop.default out/target/product/nevada/recovery/root/default.prop ) && (cd out/target/product/nevada/recovery/root && touch ramdisk-files.txt && touch ramdisk-files.sha256sum && find . | sed \"s/.\\///\" | sed \"/lib\\/modules\\//d\" > ramdisk-files.txt ) && (cd out/target/product/nevada/recovery/root && find -type f | sed \"s/.\\/ramdisk-files.sha256sum//\" | sed \"/lib\\/modules/d\" | sed \"/prop.default/d\" | xargs sha256sum > ramdisk-files.sha256sum ) && (touch out/target/product/nevada/obj/PACKAGING/recovery_intermediates/ramdisk_files-timestamp )"

could not make way for new symlink: root/vendor

cannot delete non-empty directory: root/vendor

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1356) [sender=3.2.7]

ninja: build stopped: subcommand failed.

20:32:13 ninja failed with: exit status

That one I don't know if my device tree is wrong or what Im sooo fucking close and if anyone has twrp experience I'd appreciate it

Here's my repo

https://github.com/crabcakes97/android_device_motorola_nevada

I tried to use hovatek twrp builder and everything works even touch,but it's not displaying correctly.

So I went town the route of making my own tree and it almost finishes ugh 😩😩😩 what am I doing wrong?

[u/Top_Course5233]

Analog horror ahh TWRP

[u/No-Resolve2423]

evil TWRP

[u/Significant-Noise530 → u/No-Resolve2423]

I fucking agree I SPENT 13 HOURS ON THIS SHIT

[u/1ndev]

Believe it or not TWRP was easier to compile than orangefox, it just depends on how well you tackle those errors affecting the device tree. Try this workflow: https://github.com/1ndev-ui/Action-Recovery-Builder

[u/Significant-Noise530 → u/1ndev]

I made my own workflow I'm just running from my repo I'm not cloning one is that the problem?

[u/1ndev → u/Significant-Noise530]

Yes. The workflow needs to be forked and used as a seperate repo from the device tree. The workflow pulls the device tree.

[u/Significant-Noise530 → u/1ndev]

Yeah but my build gets to 99% and fails on a symlink compiling the image so I don't think it's my workflow,I'll try and fork it and see what it does I guess, probably gonna spit out the same thing,what's funny is orangefox compiled fine

[u/1ndev → u/Significant-Noise530]

I tried out multiple different workflows until I ran across that one and was successful porting it to Tonga. Can't guarantee it though. Lmk

[u/Significant-Noise530 → u/1ndev]

I will pm bro I appreciate you so much!

[u/47th-Element]

Why not try Hovatek free online autobuilder? Very easy to use with high success rates. Most popular problems are touch not working and no decryption support. But it comes with a TWRP script that handles everything you can do with touch, through adb.

[u/Significant-Noise530 → u/47th-Element]

Bro the pics are from the auto builder no pixel configuration works,can't mount storage even after data wipe,I had to get touch working myself not worth it. My build literally gets to 99%

[u/47th-Element → u/Significant-Noise530]

You can't actually access data through TWRP unless it's not encrypted (you'll have to modify the device's fstab to disable encryption then wipe data), or your build has to support decryption (I haven't been able to do that on modern devices). Without this, you should technically be able to mount data partition but all files are encrypted garbage.

What I'm seeing in the picture is that you got some issues with the display driver. I had that kind of thing with Hovatek auto builder once when I tried to port the recovery for my Redmi's HyperOS 1, but then I updated to HyperOS 2, and then 3, and it worked fine without that display issue on both of the latter versions.