Database Info

[Q] Rooting the H60-L02 with EMUI 3.0

Hey there,
I just received a H60-L02 shipped from Mainland China. Being on OS X, I had no trouble installing adb and unlocking the boot loader.
There is something I don't understand though : to gain root access on my phone, I need to install a modified ROM of Huawei's android upper layer ? Why is that so ? Do I need to find a ClockWordMod H60-L02 EMUI 3.0 Rom to root my H6 ?

Dariel0000 said:
Hey there,
I just received a H60-L02 shipped from Mainland China. Being on OS X, I had no trouble installing adb and unlocking the boot loader.
There is something I don't understand though : to gain root access on my phone, I need to install a modified ROM of Huawei's android upper layer ? Why is that so ? Do I need to find a ClockWordMod H60-L02 EMUI 3.0 Rom to root my H6 ?
Click to expand...
Click to collapse
i used multitool and flashed twrp, twrp asked me when i tap on restart if i want to root, thats it :good:

superpfpf said:
i used multitool and flashed twrp, twrp asked me when i tap on restart if i want to root, thats it :good:
Click to expand...
Click to collapse
Thanks, but I can't do that, insofar as I can't run .exe on OS X. Also, I'm trying to understand the basic concepts of rooting on android, in order not to **** things up by doing things I would do on other linux distribs. From what I get, rooting is installing a modified ROM in which everyone is a superuser ?

Dariel0000 said:
Thanks, but I can't do that, insofar as I can't run .exe on OS X. Also, I'm trying to understand the basic concepts of rooting on android, in order not to **** things up by doing things I would do on other linux distribs. From what I get, rooting is installing a modified ROM in which everyone is a superuser ?
Click to expand...
Click to collapse
rooting is getting superuser access to any rom, if you take a look at the batch file, there is a link where you can download twrp, put it in the same directory where fastboot and adb files are
Code:
adb kill-server
adb reboot bootloader
fastboot devices
fastboot flash recovery TWRP_2.8.0.1_h60.img
fastboot reboot
adb wait-for-device
adb reboot recovery
fastboot devices

Ok it works. From what I get, twrp is a manager that enables you, once the boot loader is unlocked, to flash whatever you want on your android system. So you flash SuperSu, and it is done.
Thanks a lot for your help and explanations !:good::good::good:

Question: Rooted Concept?

Hey guys,
I tried out the Android Concept MM when it first came out and i was a huge fan and insanely satisfied due to it's stock-like android experience, however the only thing keeping me away from using it is lack of root and xposed, however i was wondering can i just make a pre-rooted ftf with the ftf of the concept with recroot 4? like i would with a normal Marshmallow ftf or am i completely wrong?
I would appreciate the help thanks!

Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.

Nojus33 said:
Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.
Click to expand...
Click to collapse
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work

Salaminator said:
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work
Click to expand...
Click to collapse
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.

Nojus33 said:
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.
Click to expand...
Click to collapse
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android

Salaminator said:
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android
Click to expand...
Click to collapse
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha

Nojus33 said:
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha
Click to expand...
Click to collapse
Looking into Android 6.0 Complications from this article (http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/)
It states the following:
If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image. While it remains to be seen if this remains true indefinitely, it looks likely to be the case for some time – SELinux changes make it much harder to get root access without modifying the boot image. And as modifying the boot image requires an unlocked bootloader
Click to expand...
Click to collapse
So i'm assuming Z3 Has SELinux thus preventing us from editting the boot image for Marshmallow Concept hence leaving us with the only option to unlock out bootloader?
Lastly: Is there a potential to convert Stock Sony ROM into an AOSP looking/feeling rom?

[Sony Xperia E5][Bootloader][Root][ETC...]

So i was thinking that we dont have any thread to this device so i made this.
Can someone help me to unlock bootloader to this beatiful device. i cant get it open.
when im trying to unlock it with the code(adb or flashtool) it gives me error saying "command not allowed" i have tried many times and re installing the drivers and tried different os and nothing helps.
tried to make some research from google etc like stackflow but just cant find nothing. i have the imei right and everything. and tried to unlock with the sonys dev site. and i did out the device as e4g or e4. nothing

command not allowed
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but

GameboyZA said:
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
Click to expand...
Click to collapse
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out

pottu221 said:
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
Click to expand...
Click to collapse
pottu221 thanks....

Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks

toinedu27 said:
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
Click to expand...
Click to collapse
aint gonna happen. none of the tools doesnt support mtk 6735 with android 6.0. so we should have rooted phone to get recovery.img so i think that our only hope is to wait that kingroot or something will work on our device

You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.

ch3mn3y said:
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
Click to expand...
Click to collapse
The proplem is that cant get the recovery.img out from anywhere :/

So there's still no way to root this phone ? I really need to install Viper4Android on it ^^

Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon

toinedu27 said:
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
Click to expand...
Click to collapse
Have you managed to root your device?
I've been trying to make a working cwm or twrp recovery, but I need to extract the stock recovery.img to do so.
And that requires root.
Can you send me a dm if you managed to root it with the dirty cow exploit? Thanks.

Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.

toinedu27 said:
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
Click to expand...
Click to collapse
Can you check if it works?
I just need a confirmation that you got your phone rooted safely with that fault, then I'll start working on twrp and hopefully we'll have our first rom on this device soon.
But since I recently bought this phone and I can't get my pc to work (for flashtool, in case anything goes wrong), I need someone to test if the dirty cow fault still works on our devices.
If you have time, please check it out.

Hey,
I try but I need to install a tool called "NDK" for the "NDK-Build" command
I'm progressing

I am waiting for a miracle. I also installed Kingroot and in it I found that in 1497 people have applied for root so that we are not alone. ?

Hey there,
I've managed to set up fastboot and finding alternative drivers to work on our device.
Finally, I can now use adb with full fastboot access.
I've also managed to unlock my bootloader, so now I will have to find a recovery that will work on our mediatek 6735 chipset, build based on API 23 (marshmallow).
If necessary, I can try to port cwm from some different device.
When we have a working recovery, we can most likely flash anything, so I might make a prerooted version of the stock firmware.
Expect the first development for this device any soon.
Edit1: Due to health reasons, I might have to delay this for a week, my appologies.

I'm sorry I don't have the time to exploit the Dirty Cow fault (lot of Home Work) and I don't have the knowledges that I need :/
I hope @mrmarvin_16 will got the root access (Thanks a lot )

Hello. Excuse me for my English writing through translayte google. I am writing with Russian Forum 4PDA. We were able to unlock bootloader is a link to my post on this forum 4pda.ru/forum/index.php?showtopic=753685&st=160#entry54277601 . And TWP recovery we also gathered, the download link yadi.sk/d/Vq0jgohxymPCG . Problem Only here we do not know how to sew it into the phone itself.

I flash recovery but i dont have boot to recovery menu

And as you flashed? I just have all the time an error in piercing through ADB.

[SOLVED] Passing SafetyNet

I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.

Devo7v said:
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Click to expand...
Click to collapse
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/

Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Devo7v said:
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse

inteltecra1700 said:
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Click to expand...
Click to collapse
It sounds like you're on a fully functioning stock ROM with an unlocked bootloader. If that is the case, then it's pretty easy to get Magisk up and running. The first thing you need to do is get TWRP on your phone, to do that you need to flash a kernel that supports entering TWRP recovery from boot. There are a few kernels that allow you to do that, I am using AndroPlus v38. There is a newer version of AndroPlus, but there have been mixed reports of being able to enter TWRP.
To Flash a new Kernel and TWRP:
Download the latest kernel from https://kernel.andro.plus/ and place the <boot.img> within the zip file in the same folder with the fastboot.exe
Download the version of TWRP from https://dl.myself5.de/ and place the <recovery.img> in the same folder with the fastboot.exe
In the the folder with fastboot.exe, shift+right click and run cmd as admin
Reboot phone in to fastboot mode (hold down the volume up while plugging in usb)
Once the phone is detected type 'Fastboot devices' to make sure you device is detected.
If it's detected flash the kernel by typing the following command 'Fastboot flash boot <boot.img>' (without <>)
Then type 'Fastboot flash recovery <recovery.img>' (without <>)
Once done flashing type 'Fastboot reboot', and make sure you press volume up when the yellow led is showing
Once you've made sure that you can enter TWRP, things will be much easier from here on out. To get Magisk up and running:
Head over to the official Magisk thread and download both the Magisk Manager v2.1 apk and the Magisk v8 zip file to your phone (http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot your phone and enter TWRP by pressing the volume up key when the yellow led is showing
Flash the Magisk v8 zip file. This will patch Magisk into your kernel (boot.img), so if you ever want to get rid of Magisk and it's mods, just reflash your kernel either by using Fastboot or by flashing the kernel zip file through TWRP.
Once Magisk has been successfully flashed, reboot your phone
When you phone has booted up install the Magisk Manager v2.1 apk that you downloaded earlier. If everything went right, the Magisk Manager should show that everything is installed and up to date.
I hope that helps, let me know if you have any other questions.

When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?

piet3r said:
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
Click to expand...
Click to collapse
Google has added more checks to SafetyNet and the procedure above no longer works. The issue is the AndroPlus kernel does not pass SafetyNet so anything you do after that will pass either. Maybe @AndroPlus will get some time to look into it and add some fixes. In the meantime I need to find another kernel that will pass SafetyNet, but I haven't had time to try.
Maybe you could try some other kernels and let us know if you find anything that works.

[Q] Help with rooting Infinix Hot 11s

Heya!
I was wondering if there are any existing tools or information about rooting Infinix Hot 11s? I've tried searching for anything related to it and I've seen a couple of threads with information about rooting old Infinix phones here, but to my understanding there isn't one related to this particular model.
It's powered by a Helio G88 processor and the operating system is a modified Android build called XOS. Full phone specs are here for anyone curious.
Any help would be greatly appreciated. Thanks!

Rooting Android means installing a ~100KB piece of software ( SU-binary ) on it.
So either push a matching SU-binary onto Android filesystem or replace the pre-installed ( restricted ) version of Toybox with a matching unrestricted one, wil say with one that has SU-cmdlet incorporated.

.

xXx yYy said:
Rooting Android means installing a ~100KB piece of software ( SU-binary ) on it.
So either push a matching SU-binary onto Android filesystem or replace the pre-installed ( restricted ) version of Toybox with a matching unrestricted one, wil say with one that has SU-cmdlet incorporated.
Click to expand...
Click to collapse
Hi, thanks for the response!
I understand, but how would I go about doing that with this particular phone? Because to my understanding, I need TWRP, I haven't found a TWRP version for my phone and I fear using a TWRP build from other phones or older Infinix phone models might brick it. If ever I have to port TWRP, is there some sort of guide for me to follow so I can try making a build of TWRP that works with this?
Thanks!

To add a suitable SU-binary to Android's filesystem TWRP in NO case is needed: you do it via ADB.
Example:
Code:
adb devices
adb push <LOCATION_OF_SUITABLE_SU_BINARY_ON_PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"

I recently bought this phone and is looking for a way to root it safely as i want to remove bloatware and use some apps that need root (like screenrecording without microphone and just internal audio, i heard that needs the magisk module?)
is there a way to root it preferably without a pc and i dont want to wipe my data unless really necessary, i have also unlocked the oem bootloader from dev options as this phone uses a custom version of android 10 (xos dolphin 7.0), processor is mediatek helios something as far as i know, just for reference

xXx yYy said:
To add a suitable SU-binary to Android's filesystem TWRP in NO case is needed: you do it via ADB.
Example:
Code:
adb devices
adb push <LOCATION_OF_SUITABLE_SU_BINARY_ON_PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
Click to expand...
Click to collapse
Hey! I tried following what you said, but unfortunately it did not work. I found a thread with instructions quite similar to what you posted: https://forum.xda-developers.com/t/universal-guide-root-any-android-device-manually.2684210/
The original poster said that this method no longer works. Is this true?
olivermartin0721 said:
I recently bought this phone and is looking for a way to root it safely as i want to remove bloatware and use some apps that need root (like screenrecording without microphone and just internal audio, i heard that needs the magisk module?)
is there a way to root it preferably without a pc and i dont want to wipe my data unless really necessary, i have also unlocked the oem bootloader from dev options as this phone uses a custom version of android 10 (xos dolphin 7.0), processor is mediatek helios something as far as i know, just for reference
Click to expand...
Click to collapse
Heya! We're currently on the same boat, unfortunately there isn't one sure method of rooting this phone at the moment.

SilhouetteMirage said:
Hey! I tried following what you said, but unfortunately it did not work.
Click to expand...
Click to collapse
the 2 lines of code shown above by me always worked for me, at any Android version - at least up to Android 10, and should work on Android 11, too

also do any of you have links to the stock rom for infinix hot 11s nfc? I bricked my phone trying to install the wrong twrp for this phone. Thanks.

So, any luck in rooting Hot 11s? This xos skin is driving me nuts. Always closing background processes, and sometimes even foreground process. We desperately need a twrp for this device.

Here is how to do it
Download your phone's latest firmware (the one you are running ) extract the boot.img from it and put it in your internal storage and install magisk from github
Press install in it and it would prompt you flashing a boot.img do that
Then copy the patched img to your pc
Then in platform-tools (search for it on google) click on the address bar then type cmd
From there type in (adb reboot bootloader) make sure your usb debugging is on
Then when it reboots to fastboot
Type (fastboot flash boot *your patched boot.img*)
That's exactly how i rooted my phone and i have an infinix hot 10s
And this method is universal

I want to install custom ROM on my infinix hot 11s, PLEASE someone work on it. HELP US!

We need developer support for infinix hot 11s please someone make TWRP and custom rom for it

Me to, please anyone develop custom rom and twrp for infinix hot 11s

RadhixAwp said:
Here is how to do it
Download your phone's latest firmware (the one you are running ) extract the boot.img from it and put it in your internal storage and install magisk from github
Press install in it and it would prompt you flashing a boot.img do that
Then copy the patched img to your pc
Then in platform-tools (search for it on google) click on the address bar then type cmd
From there type in (adb reboot bootloader) make sure your usb debugging is on
Then when it reboots to fastboot
Type (fastboot flash boot *your patched boot.img*)
That's exactly how i rooted my phone and i have an infinix hot 10s
And this method is universal
Click to expand...
Click to collapse
Hey! If you successfully do that method, do you know how to fix the problem "<waiting for any devices>" in fastboot? Is it because of the driver for my device or other cases? Thank you in advance.

RadhixAwp said:
Here is how to do it
Download your phone's latest firmware (the one you are running ) extract the boot.img from it and put it in your internal storage and install magisk from github
Press install in it and it would prompt you flashing a boot.img do that
Then copy the patched img to your pc
Then in platform-tools (search for it on google) click on the address bar then type cmd
From there type in (adb reboot bootloader) make sure your usb debugging is on
Then when it reboots to fastboot
Type (fastboot flash boot *your patched boot.img*)
That's exactly how i rooted my phone and i have an infinix hot 10s
And this method is universal
Click to expand...
Click to collapse
Did you face any issues? Is everything working for you just fine?

Lurima24 said:
Hey! If you successfully do that method, do you know how to fix the problem "<waiting for any devices>" in fastboot? Is it because of the driver for my device or other cases? Thank you in advance.
Click to expand...
Click to collapse
because of drivers for your device

pointgourd said:
because of drivers for your device
Click to expand...
Click to collapse
It's fine now, everything is work for the fastboot and I just need to find the right driver for my device. But still...do I need to unlock the bootloader first to be able flashing or do some commands? And since it's hard to find the firmware for my device, how to get the boot.img out of my phone? Knowing that Infinix Hot 11s NFC is a brand new phone and as far as I know it's regional based for Indonesia's market only. CMIIW.

pointgourd said:
because of drivers for your device
Click to expand...
Click to collapse
My ID code for my device is X6812B

Lurima24 said:
My ID code for my device is X6812B
Click to expand...
Click to collapse
Lurima24 said:
It's fine now, everything is work for the fastboot and I just need to find the right driver for my device. But still...do I need to unlock the bootloader first to be able flashing or do some commands? And since it's hard to find the firmware for my device, how to get the boot.img out of my phone? Knowing that Infinix Hot 11s NFC is a brand new phone and as far as I know it's regional based for Indonesia's market only. CMIIW.
Click to expand...
Click to collapse
https://romprovider.com/infinix-x6812b-firmware-support/ check if this is the one?
and I'm not sure but I think unlocking bootloader and rooting your device is totally different things so probably not