sadly i know of none other than aurora store. i usually use aurora, apkmirror and apkpure. do note that apkpure recently had a malicious telegram apk

neat domain you got there!

huh? no i was just sharing my ideas… skimming thru the feed in thumbnails without reading the post its easy to misidentify your post as spam, that’s all i tried to say

i think it’s because your post does feel like spam at first glance. the title feels like clickbait (‘this card’ instead of smth like ‘wise’ card) and the image also kinda feels like an ad

are people downvoting because it feels like spam? seems legit to me, i doubt spammers are gonna care about microg lol

in some cases it’s not very complicated. i think your tcl ir blaster app might just work. (if you have ir blaster, ofc)

for camera i recommend using gcam port (like bsg mgc… search xda) they tend to not work without gapps but actually works fine after installing gcam services provider from fdroid, no need for even microg

lemmy because it has the old.reddit style frontend (mlmym)

it’s not the lemmy network, it’s the fediverse

well that’s a big F you for people enjoying freedom at work by using linux instead of windows and avoiding corpo bs

ah, damn. it seems like it completely failed to boot…

i’ll try another go at making a new boot.img and let you know soon. kinda out of ideas at this point tbh.

in some cases i’ve seen fastboot command return error on console but actually succeed in executing the wanted behavior, so it might be the case here that our boot.img did successfully boot.

by ‘device reboots and trying to start android’, do you mean the device actually rebooted again to bootloader stage (e.g. vibrate and show manufacturer logo), or just boot android without that step? an easy way to confirm this is by holding fastboot or recovery hotkey right after fastboot command. if it did reboot and start again from bootloader it will enter fastboot/recovery, but if it didn’t and actually booted our new boot.img it would just boot android

pipepipe is the best imo

it’s the instance made by lemmy developers, i don’t think they host any third party frontend

i’m in east asia myself, i think more than half the people on threadiverse are USA-based though.

found this from my bookmarks

(i personally haven’t ever used llms personally but) i’ve heard many negative things about ollama from the localllama comm, may be worth searching before using it

hmm that’s weird.

after the fastboot boot command fails, what does the device show on screen? is it stuck on fastboot? or reboots?

perhaps doing fastboot boot as sudo might help.

did you install fastboot from your linux distro’s repo? what version is it? (it might be very outdated and be the cause of issues)

i use slackware. the init system here is extremely easy and simple. (mostly shell scripts)

i see no reason to use systemd on my machine. it’s an unnecessarily complex beast i can’t fully understand myself… i get it there’s some useful features included but i don’t need them. and i personally had issues with machines using systemd (waiting for some daemon to start with some timer going and hanging there, idk if it’s a config issue but it was a vanilla debian box with barely anything changed)

i’m not from the US and i feel it all the time here on the threadiverse. in most cases i don’t feel there is any malicious intent so i don’t nitpick(?) about it though

sorry for keeping you wait for so long. please try downloading this boot.img file and booting it. i’ve modified the original boot.img’s default.prop to enable ADB.

boot that using fastboot boot tecno-ki7_boot_adb.img, and right after that run sudo dmesg -w to see any new USB device appearing. Also open another terminal and try adb devices, adb shell etc and see if you can communicate with the device while it’s in the boot animation stage.

if the new boot.img i provided doesn’t work please let me know, we might need to nullify vbmeta