IMEI repair issue

[HASHOO]

I am using a Redmi Note 15 Pro+ 5G Global model (Fluorite) not the Chinese version I had its bootloader unlocked through a paid service when I first bought the phone.


The first time I repaired the IMEI, the process was completed successfully with dft pro . And phone boot normally I'm using kernel su on that time and before repairing, I also created a complete backup of the EFS partition and the original IMEI using dft pro . After the repair was successful, I'm using my phone normally but after some time I restored the original IMEI using my DFT Pro, backup and it was restored without any issues and phone work normally.


Now, after some time, I am trying to repair the IMEI again using DFT Pro, but I am facing a problem. The phone no longer boots properly—it keeps restarting on the MI logo (bootloop). I also try flashing eng firmware but nothing could work issue remain same phone not boot also with eng firmware after repairing IMEI

And I do a temporary fix ?


I have done some research myself and found that the issue seems to be related to the root solution being used. APatch is one of the root solutions that patches the boot image. If I perform the IMEI repair with APatch, the repair completes successfully and the phone boots normally. However, root does not work properly with APatch specialy modules and hiding features not working .


The first time I repaired the IMEI, I used KernelSU, and everything worked correctly. But now the phone does not boot with KernelSU, nor does it boot with any other root solution. Only APatch allows the phone to boot, but root functionality is broken.
If anyone face the same issue and found any solution please let me know thanks

 

[loniryan]

i think they changed the repair algo..wait for updates to fix

 

[HASHOO]

I don't think this is a repair algorithm error because, a few days later, I worked on another device of the exact same model that my friend had purchased brand new. I repaired its IMEI using the same method, and it also had KernelSU installed. I used DFT Pro with the exact same procedure, and the IMEI repair was successful. That phone is still working perfectly.I think the real issue is that once you repair the IMEI on a brand-new phone for the first time, DFT Pro doesn't allow you to repair it again. This appears to be a software glitch Even if you back up the original EFS and later restore it, it still won't let you repair the IMEI a second time. This seems to be a bug in DFT Pro. In my case I already restore original efs after repair so second time it is not possible to repair using dft pro i really don't know what is going on what is main issue let's hope for the best

i think they changed the repair algo..wait for updates to fix

 

[Hostekibi]

I don't think this is a repair algorithm error because, a few days later, I worked on another device of the exact same model that my friend had purchased brand new. I repaired its IMEI using the same method, and it also had KernelSU installed. I used DFT Pro with the exact same procedure, and the IMEI repair was successful. That phone is still working perfectly.I think the real issue is that once you repair the IMEI on a brand-new phone for the first time, DFT Pro doesn't allow you to repair it again. This appears to be a software glitch Even if you back up the original EFS and later restore it, it still won't let you repair the IMEI a second time. This seems to be a bug in DFT Pro. In my case I already restore original efs after repair so second time it is not possible to repair using dft pro i really don't know what is going on what is main issue let's hope for the best

It has been tested multiple times on many devices and has been successful in all of them. And no negative opinions have been encountered regarding the issue in question. I think there is a problem with your device. I don't know where you got the idea that Dftpro only works once, but that's not the case at all.

 

[HASHOO]

It has been tested multiple times on many devices and has been successful in all of them. And no negative opinions have been encountered regarding the issue in question. I think there is a problem with your device. I don't know where you got the idea that Dftpro only works once, but that's not the case at all.

 

[HASHOO]

It has been tested multiple times on many devices and has been successful in all of them. And no negative opinions have been encountered regarding the issue in question. I think there is a problem with your device. I don't know where you got the idea that Dftpro only works once, but that's not the case at all.

I have attached screenshots showing the phone's original IMEI numbers, the box, the purchase date, and the results after the patch.

As you can clearly see from the screenshots, the purchase date is visible, and the phone is brand new and don't have any issues and is currently using its original IMEI numbers on KernelSU.

The problem is that whenever I try to repair the IMEI while keeping the phone on KernelSU, the device gets stuck in a random boot loop at the Mi logo and never boots into the system.

If I perform the IMEI repair using Magisk instead, the phone boots successfully. The IMEI numbers are repaired correctly, they are displayed properly, and everything works. However, after the patch, root access is lost. As you can see in the attached screenshots, Magisk root is removed after the device boots. And if I reflash magisk using fast boot the phone IMEI turn back to it's original state

What confuses me is that the very first time I repaired the IMEI using DFT Pro, this issue did not occur. At that time, the phone booted normally with KernelSU, and the IMEI repair was successful without any problems.

Later, I restored the phone's original IMEI numbers. Since restoring the original IMEIs, every attempt to repair the IMEI again has failed on KernelSU. The phone no longer boots and keeps restarting at the Mi logo. On Magisk, the phone does boot after the repair, but root access is automatically removed after startup, as shown in the attached screenshots.
Also one more thing whenever I use gki wild kernel I'm getting an error 773 in dft pro initial boot write failed error whenever I tried to repair IMEI