yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] wenyendev:
Have you tried flashing boot.img in fastboot to sort out bootlooping?
[Android Q&A, Help & Troubleshooting] JamesDBartlett3:
I managed to get it booting again, but I'm now dealing with an entirely different problem. The FLIR camera is highly unstable (it frequently crashes, and sometimes stops working completely until I reboot the phone), and I cannot get the infrared image to line up with the camera image. I've tried the automatic calibration and the image realignment utility. No matter what I do, the infrared image is always way too big to line up with the camera image.

This only started happening after I flashed the phone back to "factory" using the ROM provided by Ulefone on their Google Drive. The ROM that was on the phone when it arrived didn't have any problems, but I don't have a backup of that because I assumed that it would be the same as what I could get from Ulefone. But the ROM that Ulefone provides has a bunch of weird stuff, like a red "未写入google key 和tee key" watermark on the screen that can only be removed by running a command in a root adb shell, as well as this thing with the FLIR camera.

Anyone know where I can get a copy of the ROM that was actually installed on the phone when it shipped, as opposed to the one provided by Ulefone on their Google Drive?

Yes, I was the person replying to you on Reddit. Thank you again for the help over there.

The problem was that I couldn't even get to fastboot. The device was softbricked. I had to use SP Flash Tool to get it back into a condition where I could even use fastboot at all.
[Android Q&A, Help & Troubleshooting] wenyendev:
I am no specialist in unbricking devices. But you may try as follows

- Download the ROM, GApps (Optional), Magisk (Optional).

- Wipe System, Data, Dalvik, Cache.

- Flash the ROM, GApps (Optional), Magisk (Optional).

- Reboot and Enjoy.
[Android Q&A, Help & Troubleshooting] H2Owned:
I tried to root mine, but I was unsuccessful.

I used mtkclient to pull out the boot_b.img and vbmeta_b.img from my device. Having these backups were helpful to get me out of bootloops.

I tried 3 different magisk versions: 24.3, 25.2, and a patched version linked in mtkclient's github readme.

I also tried the vbmeta recommendations described by OP in this thread, but I still could not get myself past the 'android system may be corrupt' loop.

I reverted my boot and vbmeta partitions back to the version I backed up via mtkclient, and escaped the bootloop. But no root.

Interestingly, the checksum of the boot_b.img in my phone does not match the checksum of the boot.img provided in Ulefone's official release. I am assuming my phone received an OTA update while the version in the Ulefone official GoogleDrive remained old, but I was not able to track down a changelog for rom updates/release history.

Unsure what to try next, open to ideas.
[Android Q&A, Help & Troubleshooting] 914mrx:
Hello, try this page i think the firmware is more update (have all models), is also from Ulefone.

File folder on MEGA

mega.nz

I have donwload a new firmware to my Armor X7 Pro and is very stable. ;)
[Android Q&A, Help & Troubleshooting] H2Owned:
I checked the Mega link you provided, and the latest version for the Power Armor 18T is the same as in the Ulefone Google Drive location. I did not compare checksums though, so I cannot confirm the content is identical.

Where did you find this mega folder link? Any chance Ulefone also publishes a changelog or provides older firmware releases in the same location you found the Mega link?
[Android Q&A, Help & Troubleshooting] 914mrx:
Hello, found this link on 4PDA a long time ago, about the others questions i don´t know. Sorry.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
I spent whole night doing everything but all failed. Unlocked OEM and Usb debugging enabled, tried kingroot, vroot, supersu, downloaded drivers and everything...but somehow I couldn't get through any of it.

Any idea anyone how to do this?
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Here's why the phone is not being rooted as per the customer service.

View attachment 5803961
[Android Q&A, Help & Troubleshooting] Samo-z:
hello,

i download ROM file from mega. I have SPMDT tool. Scatter files can be to set. DA files is not correct to select. What is wrong?
[Android Q&A, Help & Troubleshooting] 914mrx:
Hello, i don´t know, there is also a video and a instruction sheet, as I said on Armor 7 Pro everything went well 100%.
[Android Q&A, Help & Troubleshooting] Samo-z:
Hello,

I am solved problem with upgrade. Now have problem with FLIR kamera. No have icon for start IR camera. I can't start it.I think that new upgrade no made for all ulefone model.

How is Foamrotreturns solved problem with FLIR camera?
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Were you able to root the phone and flash custom ROM?
[Android Q&A, Help & Troubleshooting] hitanshugaur:
I am trying to rot my mediatek device following the instruction on this page:-

Unlock Bootloader on MediaTek Devices using MTKClient

In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.

Everything has went smooth but I am getting I/O error and I am not sure how do i unlock bootloader, and hnce install TWRP to install a better ROM.

Here is the log:-

Port – Device detected

Preloader – CPU: MT6877(Dimensity 900)

Preloader – HW version: 0x0

Preloader – WDT: 0x10007000

Preloader – Uart: 0x11002000

Preloader – Brom payload addr: 0x100a00

Preloader – DA payload addr: 0x201000

Preloader – CQ_DMA addr: 0x10212000

Preloader – Var1: 0xa

Preloader – Disabling Watchdog…

Preloader – HW code: 0x959

Preloader – Target config: 0xe0

Preloader – SBC enabled: False

Preloader – SLA enabled: False

Preloader – DAA enabled: False

Preloader – SWJTAG enabled: False

Preloader – EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False

Preloader – Root cert required: False

Preloader – Mem read auth: True

Preloader – Mem write auth: True

Preloader – Cmd 0xC8 blocked: True

Preloader – Get Target info

Preloader – BROM mode detected.

Preloader – HW subcode: 0x8a00

Preloader – HW Ver: 0xca00

Preloader – SW Ver: 0x0

Preloader – ME_ID: 32993668EB4B4D231D8C1EBAAE7B7B58

Preloader – SOC_ID: 70D2AEEC41FAFC8277AC77DAC843F110913450DFDAC62279F70FD82135670657

DA_handler – Device is unprotected.

DA_handler – Device is in BROM-Mode. Bypassing security.

PLTools – Loading payload from mt6877_payload.bin, 0x264 bytes

PLTools – Kamakiri / DA Run

Kamakiri – Trying kamakiri2..

DeviceClass – USBError(5, ‘Input/Output Error’)

Traceback (most recent call last):

File “C:\Python 3.10.9\mtk”, line 814, in

mtk = Main(args).run(parser)

File “C:\Python 3.10.9\mtkclient\Library\mtk_main.py”, line 615, in run

mtk = da_handler.configure_da(mtk, preloader)

File “C:\Python 3.10.9\mtkclient\Library\mtk_da_cmd.py”, line 101, in configure_da

mtk = mtk.bypass_security() # Needed for dumping preloader

File “C:\Python 3.10.9\mtkclient\Library\mtk_class.py”, line 155, in bypass_security

if plt.runpayload(filename=self.config.payloadfile):

File “C:\Python 3.10.9\mtkclient\Library\pltools.py”, line 102, in runpayload

if self.kama.payload(payload, addr, True, exploittype):

File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 139, in payload

if self.exploit2(payload, addr):

File “C:\Python 3.10.9\mtkclient\Library\kamakiri.py”, line 117, in exploit2

ptr_send = unpack(“<I", self.da_read(self.mtk.config.chipconfig.send_ptr[0][1], 4))[0] + 8

TypeError: a bytes-like object is required, not 'NoneType'

What do i do now? I've followed all the steps, not sure why is it giving I/O error. I tried with second usb on other port but got the same message.

Kindly suggest how to rectify this.

My device is Ulefone Armour 18t, Processor: MediaTek Dimensity 900

Phone tech specs:-

Ulefone Power Armor 18T

Please help.. :-(

Kind Regards

Hitanshu Gaur
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Hi mate, I patched the boot.img of the official ROM with Magisk after installing it on the phone and then selecting 'install' button and selecting boot.ing file of the official ROM and it was successful. But what do I do next? How do I root the phone after this?
[Android Q&A, Help & Troubleshooting] joke19:
Here a complete how to https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
[Android Q&A, Help & Troubleshooting] hitanshugaur:
I have been able to do everything, now the instructions in the last one are confusing.

Step 2A and 2B are causing confusion and hence a bootloop error.

In 2A he is asking to 'copy' the patched file to the platform-tools folder and the file as per him is stored by the name of magisk_patched.img whereas in reality when I did it was saved as magisk_patched._1vjUh.img. I have copied this to the platform-tools folder as directed

In 2B he is asking to patch again with a newer version and yet again as per him that file will be saved as magisk_patched.img too. Now how can one folder have two files with the exact same name?

Now the confusion is: Does he want us to 'cut paste' the patched image from the older version to the platform-tools folder and rename it to magisk_patched.img ; and leave the new version's patched file in the phone's internal memory and rename that one too magisk_patched.img as well?

If this is done then won't there be a conflict while rooting? because two patched .img are from different versions of a software?
[Android Q&A, Help & Troubleshooting] hitanshugaur:
so in this step, when you patched the image with 24.3 version, did you rename it to magisk_patched.img? Did you 'copy' or 'cut paste' it to the platform-tools folder?

After this step and updating the magisk to version 25, did you repatch the boot.img and renamed that one to magisk_patched.img and let it sit in the internal memory?

If you 'cut paste' the older version patch to platform-tools folder and let the newer version patch sit in the internal memory, did it create a bootloop issue?

This is where it is confusing.

In my phone the older version patched img file and newer version patched img file were named as magisk_patched_1vukl.img (older version patch) and magisk_patched_2500ihs.img (newer version patch)

What should I do? Should I rename magisk_patched_1vukl to magisk_patched.img and cut paste it in platform-tools folder and then rename the magisk_patched_2500ihs.img to magisk_patched.img and continue with the process ahead? I am apprehensive of the bootloop error due to 2 patched files being from different versions of the magisk.

Please help.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
C:\Program Files\Android\platform-tools>fastboot flash boot magisk_patched.img

Sending 'boot_b' (40960 KB) OKAY [ 0.976s]

Writing 'boot_b' FAILED (remote: 'not allowed in locked state')

fastboot: error: Command failed

This is the error I got... I am able to restart the phone normally.
[Android Q&A, Help & Troubleshooting] Generic123.:
Did you unlock the bootloader yet? The error code seems to indicate that might've not been done yet.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Yeah, it wasn't unlocked. Unlocked it and the phone is now rooted. Thanks for your help man :-)

How do I record the other party's voice over the call? The call recorder in this is just a mere 64kb one that too a non functional one.

Also, anyway to install a custom ROM in this?
[Android Q&A, Help & Troubleshooting] Generic123.:
Nice, glad you got it to work. I sold off the 18t a while ago so I no longer have the device. From what I recall thought, the only "ROMs" you could possibly use are probably GSIs (check the project treble XDA fourms for more info), but they never were able to boot on my device so you should stay with stock unfortunately.

For phone recording, you can look at this reddit post. I don't make many calls so I don't know much about call recording apps sorry.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Did you try installing any open source ROM? I'm fed up of this disabled call recording crap. I need call recording... Idk what to do...
[Android Q&A, Help & Troubleshooting] JamesDBartlett3:
Nope, I still haven't solved the FLIR camera problem, though it sounds like my problem isn't the same as yours. I can open the MyFLIR app and take IR photos and videos just fine. But the MSX feature (which uses the visible light camera to find all of the edges of the objects in the picture and overlays those edges on the image from the IR camera) is broken.

MSX mode requires both the IR and visible light cameras to agree with each other about how far away the objects in the photo are. If the IR camera thinks the object is 0.5 meters away, but the visible light camera thinks the object is 1.5 meters away, the outlines won't line up properly because one will be way bigger than the other. There's a feature called "Image Alignment Utility" in the MyFLIR app, and it's supposed to let you manually correct any discrepancy between the two cameras. When I first got my 18T, I played around with the FLIR camera, and the Image Alignment Utility worked just fine. I was able to adjust the distance discrepancy between the two cameras, and the outlines on all of the objects in the photo were lining up perfectly.

But then when I was trying to root the phone, I got stuck in a bootloop and had to re-flash the "factory" ROM using SPTools. That solved my bootloop problem, but now the distance slider in the Image Alignment Utility doesn't do anything. It moves back and forth, but the outlines don't move at all. Something is definitely different between the "factory" ROM that Ulefone provides on Google Drive and the ROM that shipped installed on the phone, because both the FLIR camera alignment bug and the red "未写入google key 和tee key" watermark on the screen thing that I mentioned earlier are present in all of the 18T ROMs Ulefone has published on their Google Drive to date, but not in the ROM that comes installed on the 18T from the factory.

Something is definitely hinky here, I just don't have enough spare time right now to get to the bottom of it. But I'm not giving up, and I'll post back here when I have more information.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Nothing worked. This is just a better battery. Nothing else. I'll probably sell it off too. Xiaomi is the best. It has everything in it and no need to root plus fits budget too. This just a joke of a phone
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Hi man,

I'm trying to lock the bootloader but I'm unable to. When I lock it, the device in fastboot mode displays a message that I need to download official rom and install that one and then it gets stuck in the bootloop.

Nothing can be done with this device, this is just a useless device. I want to lock bootloader and unroot and sell it off. Any idea on how to unroot phone, lock bootloader and then flash the official ROM?
[Android Q&A, Help & Troubleshooting] Generic123.:
I would try using SP flash tool (I think that's what it was called). The flash tool requires a scatter file, which you get from ulefones stock firmware. Download the stock firmware from ulefone, unpack it, then take the scatter file from the firmware (should be a txt file) and insert into SP flash tool. Turn off your 18t, plug it into your PC and then you should be able to flash the stock firmware. I will warn you , The SP flash tool likes to spit out your scatter file as invalid; I would just try different versions of SP flash tool until you find one that works (make sure not to get any viruses of course).

EDIT: if you want to lock the bootloader, UNINSTALL MAGISK FIRST, then just do the same steps as unlocking the bootloader, but replace the word "unlock" with "lock".
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Thanks for point that out bro :-)

Corrected it. Thanks for the directions. Will try today.
[Android Q&A, Help & Troubleshooting] Harlock1978:
Which version of SP Flash Tool do you use because I always get an error message when I try to lad the the scatter file of the ROM on the ulefone site
[Android Q&A, Help & Troubleshooting] JamesDBartlett3:
I'm using MediaTek SP Flash Tool v5.2216.00

Two other things:

I should reiterate that I've only been able to successfully flash this phone using a PC running Windows 7. All of my attempts on Windows 10 failed. So if you're having trouble, you might want to try running Windows 7 in a VM or find an old laptop lying around and use that.

It looks like Ulefone quietly uploaded an updated Non-EU firmware version into their Google Drive share on March 2nd, but didn't update the support page on their website to match. I'm not sure what to make of that, but I'm downloading it now, and I'll be giving it a shot as soon as I have some free time, hopefully this weekend.
[Android Q&A, Help & Troubleshooting] Harlock1978:
After some attempt I was able to update and revive my Telephone even on Windows 10.

The telephone enter a booloop after flashing an empty vbmeta
[Android Q&A, Help & Troubleshooting] hitanshugaur:
Any luck with that one? Any tips on the procedure to flash that one?
[Android Q&A, Help & Troubleshooting] pbsavages:
Hello, can you clarify your number 2 point about the updated firmware? Have you tried it? Is it the same as the firmware it was shipped with or the weird one with the Chinese letters mentioned on page one? Also, does the flir adjustment slider work on this version? I'm very tempted to get this phone but I just want to make sure the flir app works with root before doing so.
[Android Q&A, Help & Troubleshooting] hitanshugaur:
I've tried the gdrive uploaded rom. Seems more stable. Custom ROM can't be installed on win 10 as this is Mediatek chipset and they are fcukheads coz it's not open sourced.

I rooted on win 10 but couldn't install custom rom. Twrp too isn't available for this model.
[Android Q&A, Help & Troubleshooting] pbsavages:
I wasn't planning on a custom ROM, just wanted to make sure the flir overlay adjustment worked after root
[Android Q&A, Help & Troubleshooting] hitanshugaur:
I'm not much of an FLIR user but as and when I have used it I haven't had any issues with it...it worked well....
[Android Q&A, Help & Troubleshooting] JamesDBartlett3:
No luck so far. The latest firmware still has all that crazy red Chinese text on the screen and the FLIR calibration still doesn't work. I've started a warranty replacement claim.
[Android Q&A, Help & Troubleshooting] pbsavages:
Gained root after tense moments and many resets. Running the March 11 23 version of the firmware. At first I was nervous as I always am with new unfamiliar devices so I read every possible post about rooting the 18T and found so much misinformation and extra unneeded steps. I know there's more than one way to go about these things.

First, I tried to extract the firmware from the device which didn't work. I'm not sure if rom2box is even legit, there's so many fake sites out there trying to install malware. Windows defender kept quarantining Trojans it contained even though I got it from an official looking site. Not only that, the GUI looked like a 2 year old designed it. Went to the Ulefone site and got the latest firmware. Ulefone firmware page had terrible documentation for updating and looked like it was translated by a 2 year old. They linked a terrible flashing app that might have worked if I messed around with it, but I just ended up using SPflashtool 5.2216 which I already had for when I was using my BV9900 pro.

Almost bricked it when I used x-plore to extract the firmware tar.gz and almost flashed it. X-plore, as great as it is and always has been, truncated a lot of file names and had 0 byte files. Literally hovered the mouse over the flash button. Realized something was off through my whiskey glasses, so I re-extracted it with 7zip and everything went smoothly. Flashed new firmware with SPflashtool. Patched the boot.img with Magisk 24.3 like everyone recommended, I wasn't taking any chances. ADB reboot to bootloader, Fastboot flash boot patchedboot.img and voila, sweat lost over something easy as pie.

About the device, feels solid so far after a couple days. Tons of neat features, like FM radio without needing to plug in headphones. I'm not going to do a comprehensive review here, but I played around with the flir, and other things people have mentioned they had problems with after rooting, and so far there are no issues. No red Chinese text on the screen. The 9600 ma battery is absolutely mind-bogglingly massive and I'm still on the same charge it shipped with on the 2nd day after using it heavily, resetting and transferring 176 apps several times. I'm happy with it so far.
[Android Q&A, Help & Troubleshooting] kareem.tawab:
Glad to see the 18t gets root. However, has someone tried to root the 19t? It only differs from the 18t, as it lacks 5G and has the G99 SoC.

I recieved it last month and I am having issues with the microphone audio and video playback. There are some other issues but are not that critical. Audio from the internal microphone sounds low bitrate and muffled. Video playback breaks after heavy usage of videos in the gallery and most social apps. It needs a reboot before it breaks again. I contacted the customer service and they keep on replying regarding entirely different issues. Not sure what the deal is!
[Android Q&A, Help & Troubleshooting] kareem.tawab:
Any thoughts?
[Android Q&A, Help & Troubleshooting] BiscuitUnicorn:
Hello, I was trying to get my phone rooted, but official links are dead. Can you share the stock ROM please?
[Android Q&A, Help & Troubleshooting] pbsavages:
Sure. What's the best way to share it? Never shared a file that size.
[Android Q&A, Help & Troubleshooting] BiscuitUnicorn:
Im usually using mega.nz for this. You may choose google drive or dropbox if you want (Im not sure about their file limitations, i think, dropbox would be too small)
[Android Q&A, Help & Troubleshooting] pbsavages:
Here you go. I'll host these temporarily until I need the space and pass the torch to you, I've moved on to a different phone. Maybe put them somewhere more permanent for the future?

The 3/11/23 version was stable, the couple after weren't. I got the 11/3 release but haven't tried it.

The fix for the red Chinese letters Tee Key is to simply disable the com.mediatek.factorymode service.

Ulefone 18T - Google Drive

drive.google.com
[Android Q&A, Help & Troubleshooting] BiscuitUnicorn:
Thank you very much. For the ones in need for this rom I reuploaded them to https://mega.nz/folder/9i0xTATB#OlKbR97BYwYqX2T_10dLdg (Currently 1/2 is uploaded, second is on the go, (sudden 100kB/s is no joke)).

Also, another guy also reached out for me (https://4pda.to/forum/index.php?showtopic=1058316&view=findpost&p=128162964), so here are another links (although he repacked them in rar for some reason), aaand those may be another versions: (edit: yeah, seems like they are)

18T_A12___2023_11_03__V21_NonEU.rar

Посмотреть и скачать с Яндекс Диска

disk.yandex.ru

18T_Ultra_A13__2023_11_15_V03_NonEU.rar

Посмотреть и скачать с Яндекс Диска

disk.yandex.ru
[Android Q&A, Help & Troubleshooting] pbsavages:
Cool. The 18T Ultra firmware should be android 13. That was never on their official site, I wonder where it came from. I'm hesitant to install it. Are you going to try that one? I think the only difference with the Ultra was that it's got more memory and the Android 13..
[Android Q&A, Help & Troubleshooting] BiscuitUnicorn:
18T has thermal camera. Ram is the same 12g, and i think they both have 12 in swap. Also, they both listed as 256 gig, but there are different modifications, and i got one with 512. I was hesitant to install it, but I tried. Don`t you have rom for PA18, not PA18T by any chance, because flashing stock for 18T bootloops my device?
[Android Q&A, Help & Troubleshooting] pbsavages:
Oh, I thought you were trying to root the 18T, that's what this thread is. I don't have the 18.. one time I accidentally installed the 18 firmware on my 18T and it worked, it only didn't have the FLIR app. Sorry, I don't have the PA18 firmware.
[Android Q&A, Help & Troubleshooting] CXZa:
https://www.needrom.com/download/ulefone-armor-18/

https://firmwarefile.com/ulefone-armor-18/