Android
DROID DOES
Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
view the rest of the comments
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 runsudo dmesg -wto see any new USB device appearing. Also open another terminal and tryadb devices,adb shelletc 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