Help rooting an "Obscure" phone - Android Q&A, Help & Troubleshooting

So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?

---

May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info

---

xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc

---

potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?

---

A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.

---

xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread

---

potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).

---

mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there

---

potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.