Database Develop

[Q] No CF-Auto-Root for XT1064? XT1063 works fine?

Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks

Sakura90 said:
Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Click to expand...
Click to collapse
I have had a huge amount of frustration attempting to root the XT1064 over the past couple of days. If you're not afraid of reflashing your phone then you can try it but I highly doubt you'll be able to get it to work.
You can easily upgrade it to Lollipop with "official" firmware, but rooting has given me bootloop after bootloop.
After purchasing the Moto G XT1064 and spending 8+ hours trying to update and root the phone and remove all of the Motorola crapware, I eventually gave up. Right now I have version 22.11.6 installed, which is named "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip", it makes sense to include the old version number, but they should at least call it "Blur_Version_from.21.11.17.titan...".
I really wish Google would REQUIRE manufacturers to release a stock android rom and an easy way to flash it with every consumer Android phone sold. Then developers could focus on improving the phone instead of millions of programmer-hours wasted on trying to remove the crapware and get it updated.
If you're a developer who wants a clean phone and don't want to waste dozens of hours screwing with flashing roms, just get a GPE or Nexus device, it's not worth saving $200. It's a great phone, but if you were looking for a phone that is easy to develop with, this doesn't seem like the right one. After my Droid X I swore off non-nexus devices, but the Amazon sale got me.
A couple of people claim to be able to get UPDATE-SuperSU-v2.16.zip working, (yes, SuperSU v2.39 exists now, it probably won't work though), but many more people (including myself) were not able to get it working.
Good luck! Please report back if you find a good solution, I'm guessing that many people are tired of the hoops we have to jump through to get a non-crapware stock Andorid device.

The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?

Sakura90 said:
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Click to expand...
Click to collapse
I'll probably try it tonight. Will let you know the result.
You can change the file systems using: TWRP2.7.1.1-titan-motog-2014.img as your recovery.
I agree about the manufacturers. I thought it was growing pains in the early days of Android but we millions of us have to waste several hours trying to get decent security, privacy, and performance out of our phones. All anybody wants is stock Android.

Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.

Sakura90 said:
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Click to expand...
Click to collapse
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.

Can you go back to stock recovery after installing SuperSU? As to have future OTA updates. I'm mean, only use TWRP for rooting.

derekm_ said:
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Click to expand...
Click to collapse
You put SuperSU on internal storage because that's the only way TWRP can flash it or because that's the only way you could get root (I.e., flashing from external storage didn't work)?
I have tried both CFAutoRoot and flashing SuperSU from external storage. SuperSU resulted in bootloop. AutuRoot worked but I couldn't power off my phone without the next power up throwing things into a bootloop. I chose not to leave my phone on all the time, so flashed a non-root backup.
I haven't tried flashing SuperSU from internal storage. So maybe that's something to try.

[Q] Options for Stock Unrooted S5 requiring airwatch and encryption

I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.

I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.

Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?

Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0

Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?

sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.

OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!

Root w/ Encryption

I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt

cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hello Hiatt,
Thanks for using XDA Assist. What specific device do you currently have? There are so many devices here and each might deal with your question differently. I moved your other thread to off topic since it was referring to iPhones, but this one seems to have a more specific device in mind.
Thanks,
coal686

I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).

cwhiatt said:
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
Click to expand...
Click to collapse
Lol, that's what I said. The other post was more about the iPhone issue so I moved it to off-topic. Since you have a Galaxy S6, I'll move this thread there so people with that device can give you a more personalized answer.

I don't think that having root is an issue with encryption. I Had my S5 encrypted only problem was a ui crash when entering the boot password. That was specific to the rom I was using and simply had to enter password 1 or 2 characters at a time between errors.
But I do think there may be a problem with custom recovery and encryption.
My S5 was verizon, thus still locked bootloader and used safestrap to get to a custom recovery which wasn't always active.
I would talk to someone with a lot more knowledge then I about this further. But pretty sure just having root is not a problem the recovery is where you can have issues

cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hi there,
Root + Encryption can work together as long as no custom recovery involved, so if you get your root by exploit instead of installing custom recovery almost 99% chance you can have your phone encrypted while preserving the root privilege.
My case explained here : http://forum.xda-developers.com/galaxy-note-3/general/success-root-encryption-t3372958

I didn't have a problem with encryption and root. The only problem that I had was that my Galaxy S6 Edge needed to be encrypted before root. I could not encrypt my phone with the "stock" rooted kernel. Once I was encrypted, I could install TWRP and root via supersu systemless root.
Once I had root, I would use flashfire to back up and install because TWRP could not read the DATA partition since it was encrypted. For some reason, it seems once the phone has been decrypted, the data partition could be backed up with flashfire, and I would be able to restore a backup as well.
This is where I ran into issues. If you are flashing a custom rom that will require you to wipe data, your device will lose encryption. Because I can be somewhat of a crack flasher at times, and that I am too lazy to deal with having to re-encrypt and reinstall all my settings, I just opted to stick with an unencrypted phone.
Hopefully at some point, TWRP will be compatible with encryption so that lives will be easy for us crack flashers..until then, I will probably stick with an unencrypted device unless I just want to stick with a stock rom, or a custom rom that I can load up and not have to wipe data every time there is an update.

Restoring XT1900-1 to stock with no backups

I lent a phone out to a friend and received it back with the boot loader unlocked and the system, data, and internal storage wiped. I don't know if they were trying to run custom firmware or what.
I was thinking of just flashing something on it, but I was wondering if there would be any way to return it back to stock (or as close as possible). It was purchased from Google. Confirmed to be an Android One Moto X4, 32 GB from my order history.

I'm assuming that this is a US version XT1900-1.
The firmware is here: https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Here is a possible guide, I haven't done any this myself.
https://forum.xda-developers.com/moto-x4/development/rom-moto-x4-retail-android-pie-t3876156

dougo007 said:
I'm assuming that this is a US version XT1900-1.
The firmware is here: https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Here is a possible guide, I haven't done any this myself.
https://forum.xda-developers.com/moto-x4/development/rom-moto-x4-retail-android-pie-t3876156
Click to expand...
Click to collapse
Thank you so much. I was finding links to that repository, but I couldn't get any of the links to work. Yours did.
Edit: Just got it flashed and started it up. I'm a bit confused. The order screen shows it's an Android One Moto X4 from Google, but I know when I originally got it the bootup screen would play the Motorola "Hello moto" with the people flipping the f out. This one's just the Android One logo. Do I figure this out just by seeing if the OTA updates fail, and then I try a different channel?
Also, this dm_verrit notification, I'm guessing this would be because encryption was removed when he wiped it. Is there a way to re-enable that and remove the message?
I remember on the Nexus 5x there was an image you had to flash to avoid the notices about having a modified system image. Is there a similar way for me to get rid of the message stating that the phone is running different firmware after I've locked the bootloader?

Question US Unlocked but using T-Mobile SIM - How to Root safely, many ??s

Long story, but after travails with an Amazon-purchased Oneplus 9 Pro due to it being locked (T-Mobile!) and them refusing to unlock it....
I went to OnePlus and got myself a OnePlus 10 Pro Unlocked. Still have the T-Mobile sim, though.
My question....
I have been out of the rooted phone scene for some time. I had a Oneplus 2 rooted and a Samsung Note 4 and 5 rooted. But things are different now, I'm gathering. Plus this is a new phone and I don't want to toss away hundreds of dollars by bricking it.
I used TWRP back in the day. Flashed many a custom rom back then. But with this OnePlus, I already unlocked it which... is that the same as rooting it? And what are the benefits of rooting / flashing roms vs just going with what is currently on this US phone (Oxygen 13 but not 13.1 yet)? I kinda want to see TWRP on here, and back up my whole set up into files I can then copy to my computer(s) for safety's sake. At least I liked that feature when I had it w/ the OP 2 and others.
Trying to get back up to speed in the world of rooting as it stands now.
Thanks.

TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.

Prant said:
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Click to expand...
Click to collapse
Thanks for this.
I got as far as unlocking the phone and installing Magisk. But haven't gone further until I understand what the next step is.
Can I root non-destructively? Or is the phone wiped?

If you're unlocked and have Magisk installed, rooting is as easy as booting a patched boot image, then using Magisk to install it to your boot image. You have the choice of finding a matching one in one of the guides or pulling your own from a full zip.
It must match the firmware revision, I know for a fact personally that region matters little in case of NE2215/3, as you're only doing a one time boot.
I recommend @g96818 's guide here, you can find almost every firmware's boot image posted there if you prefer patch it yourself using Magisk or just boot an already patched one.

I have a 10 Pro (NE2215) rooted as a daily driver using TMO US.
Unlocked means 2 things in the android phone scene. Either it's carrier unlocked and can take any sim from any phone company or it bootloader unlocked which is needed to root and load custom roms.
There aren't any custom roms for the 10pro because of the lack of a full recovery system. Basically the ability to force full flash a stock rom in case the custom ROM soft bricks the phone. So that leaves rooting as the reason to unlock your bootloader.
I suggest reading the guide for rooting this phone, it's relatively easy. TWRP is unnecessary as it doesn't offer much without custom ROMs. Also you should back up everything on the phone that you don't want to lose because during the rooting process a factory reset will occur (android safety feature).