Hi, I had a problem with my Axon 7.
I have an Axon 7 A2017 the Chinese version, and I intended to root it so I could install another Rom that had Android 8 and a better layer of personalization.
I was reading several forums and pages on how to do the process because before all this I knew nothing.
The first thing I did was unlock the boot manager, installing the TWRP, which did not have any problem.
After this I root it by installing the SuperSU zip, when doing this, everything was deleted in my cell phone and when I started it again it did not have a signal.
AND I DIDN'T BACKUP THE EFS FOLDER.
I recently installed the original rom to see if esque could return the signal but it did not work.
The problem is that I'm not sure if the folder efs is deleted or not.
If I write on the numeric keyboard * # 06 # to see the imei of the phone, it appears on the screen imei1: unknown and imei2: unknown
But if I go to configurations, in phone information, I can see both Imei, IP address, Wi-fi Mac Address, and the baseband version, but I can not see the bluetooth address or anything that has to do with the Mobile Network.
Also through the twrp I pressed the backup option and to my surprise if it lets make a backup of an EFS folder which weighs 6MB. I made a backup on my sd card and when opening it with Root Explorer, I only see files like efs1.emmc.win and other similar ones, persist.ext4.win, recovery.log, etc ...
I tried to copy that efs folder to the root of the phone but when it is restarted it is deleted and it does not appear in the root.
My doubt is that I do not know if the folder efs was deleted, or I have to do some other process
thanks for the help
sebv_n said:
Hi, I had a problem with my Axon 7.
I have an Axon 7 A2017 the Chinese version, and I intended to root it so I could install another Rom that had Android 8 and a better layer of personalization.
I was reading several forums and pages on how to do the process because before all this I knew nothing.
The first thing I did was unlock the boot manager, installing the TWRP, which did not have any problem.
After this I root it by installing the SuperSU zip, when doing this, everything was deleted in my cell phone and when I started it again it did not have a signal.
AND I DIDN'T BACKUP THE EFS FOLDER.
I recently installed the original rom to see if esque could return the signal but it did not work.
The problem is that I'm not sure if the folder efs is deleted or not.
If I write on the numeric keyboard * # 06 # to see the imei of the phone, it appears on the screen imei1: unknown and imei2: unknown
But if I go to configurations, in phone information, I can see both Imei, IP address, Wi-fi Mac Address, and the baseband version, but I can not see the bluetooth address or anything that has to do with the Mobile Network.
Also through the twrp I pressed the backup option and to my surprise if it lets make a backup of an EFS folder which weighs 6MB. I made a backup on my sd card and when opening it with Root Explorer, I only see files like efs1.emmc.win and other similar ones, persist.ext4.win, recovery.log, etc ...
I tried to copy that efs folder to the root of the phone but when it is restarted it is deleted and it does not appear in the root.
My doubt is that I do not know if the folder efs was deleted, or I have to do some other process
thanks for the help
Click to expand...
Click to collapse
You installed "the original ROM"? Which ROM version did you install?
If you installed a G or U package your modem is wrong, you just need to flash the A2017 modem via TWRP. i don't think it's EFS at all, though it may be it as well
Even if you flashed an A2017 ROM, just get the Nougat A2017 modem (from the LineageOS 14.1 thread for example) and flash it via TWRP. It may or may not fix your signal problems
Related
Hey guys,
I'll put it as simple as I can :
-no SIM service whatsoever. Happened a few hours after i flashed Androidmeda ROM. no clue if thats the reason
I tried:
- restart
- wiping all caches and data
- factory reset ( 3 different ways )
- flashed 3 other ROM's
- recovered a very old nandroid backup i found
- drained the battery, recharged fully
- left battery out for a few hours
- slapped it around (gently)
Im drained out of ideas. Any clues? anyone?
Thanks in advance
Sim card in slot .
Check you have the correct network settings .
Check IMEI is the original one .
Wrong IMEI restore your backed up EFS folder .
jje
hey. u were right about the IMEI. It says unknown/unavailable on all IMEI, IMEI SV, WiFi MAC, Bluetooth addr. and baseband.
Just one Q.
what is and EFS folder and what if i did not back it up?
JJEgan said:
Sim card in slot .
Check you have the correct network settings .
Check IMEI is the original one .
Wrong IMEI restore your backed up EFS folder .
jje
Click to expand...
Click to collapse
How can I back it up?
bahkata said:
hey. u were right about the IMEI. It says unknown/unavailable on all IMEI, IMEI SV, WiFi MAC, Bluetooth addr. and baseband.
Just one Q.
what is and EFS folder and what if i did not back it up?
is rule one backup efs folder so you can restore your IMEI ..
The /efs folderThe /efs folder is a folder in your phone that contains information specific to YOUR phone, for example your IMEI number, product number, Wireless MAC addresses, and much more. There have been reports of people messing up their /efs folder when unlocking their phone or flashing new ROMs, here is an example from the Nexus S development forum (jump to page 111 to see everyone start to panic):
http://forum.xda-developers.com/show....php?t=1034130
Therefore, it is important to make a backup! Instead of just regurgitating guides on the forums already, here is a link to a very good one by Rawat:
http://forum.xda-developers.com/show....php?t=1068193 (Rawat)
The easiest way of doing it is by using terminal emulator rather then ADB (unless you have ADB all up and running and are confident with it)
You need to search the other multitude of IMEI posts see if you can find a fix .
If not its a service centre repair if you have proof of ownership and no custom rom and no root and custom rom counter set to zero .
jje
Click to expand...
Click to collapse
Hi,
I own an Samsung Y DUOS GT-S6102.
Have Successfully Rooted it years back in one attempt. Thanks to XDA team & their members.
After installing Apps many times my memory gets full.
I have discovered on my own that whenever I do an Factory RESET, post which I get 60 % Free Phone Memory. & I can install even more apps again which I was unable to do earlier.
Hence this time I have done factory RESET through settings menu as usual. It was done successfully. However post reboot of device this time I found that my both SIM were NOT able to latch on to network [have checked sim on other device its working fine]
When tired to access data connection via wifi, I found that even WIFI is not working. It shows as Obtaining IP Address, however it doesn’t get connected even tried with OPEN Wifi.
Unknown reflects when checked in SettingsAboutStatus for IMEI & Wifi MAC Address.
*#06# shows blank.
Gone through many forums & its post & found that EFS folder is blank when checked with Root Explorer.
Now I have NO backup of /EFS Folder. How to overcome this issue?
Pl help at earliest.!!
Bhouteshd said:
Hi,
I own an Samsung Y DUOS GT-S6102.
Have Successfully Rooted it years back in one attempt. Thanks to XDA team & their members.
After installing Apps many times my memory gets full.
I have discovered on my own that whenever I do an Factory RESET, post which I get 60 % Free Phone Memory. & I can install even more apps again which I was unable to do earlier.
Hence this time I have done factory RESET through settings menu as usual. It was done successfully. However post reboot of device this time I found that my both SIM were NOT able to latch on to network [have checked sim on other device its working fine]
When tired to access data connection via wifi, I found that even WIFI is not working. It shows as Obtaining IP Address, however it doesn’t get connected even tried with OPEN Wifi.
Unknown reflects when checked in SettingsAboutStatus for IMEI & Wifi MAC Address.
*#06# shows blank.
Gone through many forums & its post & found that EFS folder is blank when checked with Root Explorer.
Now I have NO backup of /EFS Folder. How to overcome this issue?
Pl help at earliest.!!
Click to expand...
Click to collapse
You can restore your IMEI by using Galaxy Toolbox.
But you don't have the EFS partition right.........
Don't worry you can still restore your IMEI........
Instructions:
1. Download and install the program
"HexWorkshop Hex Editor v6.7" on PC
(Googling).
2. Download the app "Galaxy Toolbox" of
Google Play Store.
- Install the application on Android and open,
accept, and select "Back up", and exit.
- See his backup file in / sdcard/SGYunlock/
bml15.img.SAVE
- Move the file to your PC (Make a backup of
his again, this is just in case)
- Open the hex editor program that was
already installed on the PC.
- Open file backup his
- Make sure the filter character remains on the
"Legacy ASCII"
- Write: 0x80000 in the blank box (Go to)
- Click ENTER
- Press the IMEI number which is 15 Digits.
- SAVE, then close the program.
- Move the file "bml15.img.SAVE" to /sdcard/
SGYunlock/HERE.
- Open the "Galaxy Toolbox" it, agree, and
RESTORE, and exit.
- Reboot, and enjoy..
This method is only for restoring imei but i might suggest you to get to stock rom via odin if above metod don't work........
Hit thanks if helped....:good:
Its an dual SIM, were to update another IMEI?
Also suggest as in Recovery mode I am getting error as E:/ mount failed /sdcard. I can't even work with updates,etc.
Didnt Work with Galaxt Toolbox
Dear Piyush
I tried same. However Galaxy Toolbox is not able to back-up.
NO such folder found in /sdcard.
Bhouteshd said:
Dear Piyush
I tried same. However Galaxy Toolbox is not able to back-up.
NO such folder found in /sdcard.
Click to expand...
Click to collapse
If you have the updated vesion then it should be like this
mnt/sdcard/ GalaxyToolbox/ EFSpart.img.SAVE
thats ur backup file
---------- Post added at 09:33 PM ---------- Previous post was at 09:17 PM ----------
Also it seems that your efs partition is currupt which may have happened due to a bad factory reset....
so first do a factory reset again but from recovery ....
and if it doesn't work try odin
Resolved. with some link in XDA forum.
Thanks Piyush. But I have already Solved using some link in XDA forum in month of DEC'13. It was gr8 help from you.
Bhouteshd said:
Thanks Piyush. But I have already Solved using some link in XDA forum in month of DEC'13. It was gr8 help from you.
Click to expand...
Click to collapse
Sir,
Could you share the link? Mine old Y lose imei too.
Thanks
offset
Folks,
i did it BUT i changed last two hexa codes after SIM2# and didn't backup (at EFSpart.img).
Someone could, please, share with me?
Resume: need to know original value at offset 80036 and 80037
Cheers
Piyush Pastor said:
You can restore your IMEI by using Galaxy Toolbox.
But you don't have the EFS partition right.........
Don't worry you can still restore your IMEI........
Instructions:
1. Download and install the program
"HexWorkshop Hex Editor v6.7" on PC
(Googling).
2. Download the app "Galaxy Toolbox" of
Google Play Store.
- Install the application on Android and open,
accept, and select "Back up", and exit.
- See his backup file in / sdcard/SGYunlock/
bml15.img.SAVE
- Move the file to your PC (Make a backup of
his again, this is just in case)
- Open the hex editor program that was
already installed on the PC.
- Open file backup his
- Make sure the filter character remains on the
"Legacy ASCII"
- Write: 0x80000 in the blank box (Go to)
- Click ENTER
- Press the IMEI number which is 15 Digits.
- SAVE, then close the program.
- Move the file "bml15.img.SAVE" to /sdcard/
SGYunlock/HERE.
- Open the "Galaxy Toolbox" it, agree, and
RESTORE, and exit.
- Reboot, and enjoy..
This method is only for restoring imei but i might suggest you to get to stock rom via odin if above metod don't work........
Hit thanks if helped....:good:
Click to expand...
Click to collapse
My MXPE "Arrived" with a scuff on the aluminum frame. Luckily I relayed the aforementioned to moto and I am being given a cost free exchange. I am on an unlocked BL running MM deodexed/rooted. I'm wondering if my LP & MM nandroid will suffice once I unlock my new x and TWRP it? Any thoughts or suggestions?
Yes. Nandroid backup (through a custom recovery like TWRP) is the way to go.
To use a computer analogy, a nandroid backup is equivalent to running a computer drive image clone. You make a perfect copy of the storage contents, so that you can easily backup / restore a system configuration to a device (or move devices).
The one thing I want to mention is that TWRP creates backup folders according to the serial number of the device itself. So when you restore to the new device, you will need to rename your TWRP backup folder name to the new device's serial number. To find out the serial number of the new device, just run a quick backup (e.g. boot info only) just so it creates some folder with the appropriate serial number. Then just rename your existing backup folder to that new serial number, and you can restore.
That's what I was concerned about; ie backing up and restoring device specific info onto a different device. When switching devices I generally like to set them up as a new device and redownload my apps, in my past experience(KK and below) that generally tends to eliminate errors/bugs associated with a nandroid flash. That being said Android has advanced quite a bit since then so I'll give it a try.
This guide is for those who have lost their IMEI, have corrupted EFS, or erased EFS partition. So, follow these under your own risk, it may or may not work, and if something happens or doesn't happen, then i am not to blame. So, once again i will not take credit for bricked phones or something along those lines, however i will take full credit if this works for you. I will also provide assistance to those who could not restore their EFS following this guide.
Before proceeding with this guide, backup what you have left. Use twrp to backup and in case something goes wrong and your problem escalates, you can restore using twrp backup.
Restore EFS
Change IMEI Number
Restore EFS
Do this if and only if you believe your EFS is corrupted, or you somehow erased it. If you are not sure about it, then simply follow the next guide to change you IMEI number. In most cases people loose their IMEI only and not the whole partition. Again, it may or may not work, so do this on your risk, and i am not to blame if anything bad happens, but if you do succeed, then don't forget to give me credit.
Note:
If your EFS is erased or corrupted, your IMEI and Baseband will be shown as unknown. In this case recover the EFS following this post, and then change the IMEI following the next post. If your IMEI is shown as 0, then you EFS is safe and most probably your IMEI is gone. In that case, no need to recover EFS, only change the IMEI number following my next post.
In TWRP, backup of kate wont show on kenzo and the backup up kenzo wont show on kate. In case no backup is shown even if you are using the right device, then try the dump flashing method or try changing the TWRP recovery.
Flashing this will only restore your EFS partition, but the IMEI will still be gone, so you will have to follow the next guide to change your IMEI.
Even after flashing a new EFS, you Mac and BT address will not recovery. The android system will assign a software generated address to both devices. Dont worry cause even without the EFS partition there will be a Mac and BT address assigned to your device and both the things will work normally.
If your Baseband is still unknown, even after flashing a new EFS, then try flashing latest radio file. It can be found in any firmware update package, either the official or the one from the strix.
1. Download the required files from the link given below.
EFS Backup[Kenzo] - Contact me if someone has backup of this.
EFS Backup[Kate] - Contact me if someone has backup of this.
2. Extract the Dump Backup files and flash them using the following commands.
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
3. Now reboot and voila you have you a new EFS partition at your disposal.
Change IMEI Number
Requirements:
Root
USB Debugging is turn on
Windows Driver Signature is turned off
ADB and Fastboot Binary Files
Latest MiFlash Installed for the latest drivers
1. Connect your device to pc and open the adb folder. Then open a command promt window.
Code:
>> [B]Shift + Right Click[/B] anywhere in the adb folder
>> Click on [B]Open Command Window Here[/B]
2. Type the following command to enable Diagnostics mode. Allow debugging if asked.
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Download the IMEI Changer from the link given below.
IMEI Changer [Credit: Archeolot]
5. Now, open the imei changer, and enter imei number in both the fields. And click on start. After a moment it will show as passed. If it fails make sure that you have followed the points i stated.
Note: Make sure that the driver in driver management under ports is listed as "Qualcom HS-USB Android DIAG 901D" and not as "Marshall London HS-USB Android DIAG 901D". If it is listed in any other name, then go to driver management and update driver. Select browse driver, then let me pick driver from a list. Then select "Qualcom HS-USB Android DIAG 901D" and then finish.
WOW.. Thanks mate..
It's gonna very Helpful for me & other ppl.. ??
Sent from my Redmi Note 3 using Tapatalk
didn't work..
showing error as no diag even after typing those commands
kindly help me
nuk.nama said:
showing error as no diag even after typing those commands
kindly help me
Click to expand...
Click to collapse
At what part, the imei change or flashing.
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Broski32 said:
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Click to expand...
Click to collapse
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
archit.bajpai.ab said:
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
Click to expand...
Click to collapse
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Broski32 said:
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Click to expand...
Click to collapse
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
So, using this way, one can change the IMEI no. also?
mGforCe said:
So, using this way, one can change the IMEI no. also?
Click to expand...
Click to collapse
Yes, just use the imei changer in the rar file to change your imei. But make sure to backup or atleast note down your imei before doing so.
archit.bajpai.ab said:
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
Click to expand...
Click to collapse
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Broski32 said:
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Click to expand...
Click to collapse
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
archit.bajpai.ab said:
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
Click to expand...
Click to collapse
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Broski32 said:
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Click to expand...
Click to collapse
Enjoy your revived phone buddy.
Thanks buddy!!!!! you saved my phone
pandyajoe said:
Thanks buddy!!!!! you saved my phone
Click to expand...
Click to collapse
It do what i can do buddy...
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
chr0m said:
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
Click to expand...
Click to collapse
Have you checked with miui7 stock rom. As far as i know there are three sensor modules for fingerprint, on of them is goodfix which is currently not supported by many roms. If your is goodfix then it will not be supported too. You can flash miui rom to check whether the fingerprint works or not...
If it doesnot work, then try to resotre your nandroid backup agaian. This tym simply untick efs.
Hello folks,
I ran into a poblem with my old Samsung Galaxy Grand Prime Plus. 3 years ago I was messing up with the phone and I ran into an invalid IMEI problem. As I was a real newbie, I brought it straight to a friend of a friend of a friend who had a phone shop, and he fixed it for me.
Everything OK until last week, when I suddenly realized that probably the guy had flashed the wrong IMEI to it, mistyping 2 numbers of one of the two IMEIs.
Currently, I then have a perfectly working phone, but the IMEI is incorrect and I need to fix it.
I don't have the box anymore, but luckilly the numbers under the battery are perfectly clear and readable, although this is quite an old device.
As the shop of the guy who did the work is long gone, I started to look around for instruction on how to deal with the problem, and I followed all the possible tutorials, but apparently I'm not able to fix the issue.
I just know it can be done, as this was done to the very same phone in the past, creating the problem. I just do not happen to know how he did...
Here's what I tried so far:
1. APP: Mobileuncle Tools
Whenever I tap onto "IMEI Backup Restore (MTK)" I get an error message that says "No support".
2. APP: MTK engineering mode
I open the app, and whenever I tap onto "MTK Settings" I get an error message that says: "Cannot find EngineerMode App - Mediatek chipset is mandatory and stock ROM must be installed".
I tried both Mobileuncle Tools and MTK Engineering mode with 3 different ROMs downloaded from different sources, before and after rooting the device with Super SU, but to no avail.
3. With any xposed module
This could be a solution... but not a real one.
At least according to all the documentation I found (also here on the forum), any xposed module like "IMEI Changer", "chamaleon", "device changer", "hijack suite free" etc only mask the IMEI in front of other apps, but do not really change the IMEI of the phone.
So basically I would still have a phone with an illegal IMEI on it.
Not ideal: this is not what I am looking for.
4. IMEI Maker and IMEI Repair
I followed the tutorial I found here:
https://forum.xda-developers.com/showthread.php?t=2399037
I encounter no errors at all, and TWRP shows a clean log, nothing seems to be wrong. But after flashing the new IMEI, nothing changes: with *#06# I can still see the wrong IMEI there.
The file in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 just remains the same, dating 2016, and does not get replaced by the new one.
I tried to replace the file manually, using ROM Toolbox Lite. At the beginning I could not delete the original MP0B_001 file, even after changin permissions to 775. It kept saying "File deleted" but the file remained there.
I then installed BusyBox Free, and it did the trick: now using ROM Toolbox Lite I definitely can delete the MP0B_001 file. The problem is that the original file keeps coming back again and again, after every reboot.
Nevermind if I place the new MP0B_001 file in the folder copying and pasting it or flashing it with TWRP, it will get overwritten by the old file with the wrong IMEI.
5. Flashing a Combination ROM
I didn't find a specific tutorial for this one, but I just tried to flash the combination ROM and see whether I could get any luck touching things in there.
No luck!
6. With SN write tool (windows software)
Here the big problem is, I can't find the BP file anywhere.
No AP_BP_database seems to contain the BP file for the MT6737T (that is the chipset of the G532F). As I am writing, I am thinking about trying to use a different BP file, from a different chipset. This will probably won't work, but after trying all of these, I mean, why not...
I also tried to look for the BP file into the folder /system/etc/mddb/ , as advised here: https://forum.hovatek.com/thread-11609.html . I looked for ir with any of the 3 different stock ROMs I tried to install. Yet again, absolutely nooooo luck here.
7. MTK Droid Root & Tools (windows software)
This won't even connect to the phone. That is, whenever I connect the phone to the PC, I get the following errors:
" --- Estructura de ROM desconocida, no se puede hacer backup ! "
That would be something like: "Unknown ROM structure, cannot perform backup"
The device gets recognized (hardware, model, build number...), so it should be a problem of drivers, cable or USB port. Also because I used the same setup to install all the stock ROM, TWRP, Super SU etc...
---------------------------
And here I am. After one week of try and fail, getting tired of all this!
I'm surprised on how persistent that wrong IMEI is, as I can't get rid of it in any way.
Do you have ANY kind of idea of what can I do?
As the points 1, 2, 4, 6 and 7 are specifically advised for MTK chipset. I'm starting to doubt that this is an MTK chipset altogether!!!
Thanks for your help
Peter
Update:
I tried with NCK Dongle AndroidMTK 2.5.6.2
Still no success (phone apparently not supported).