Related
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Keep up the experiments!
Thanks!
keep up doing it, you are great
thousands of people hope this work in the future...
i think unrevoked is not doing anything now
we r 4 months from 2.2....
Any more luck? How is this getting on?
dannyjmcguinness said:
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Click to expand...
Click to collapse
I tried this a week ago and it does not seems to work :S
cid version is on "ro.cid" prop. Change cid on mtd0, flash it and then try a "getprop ro.cid"
Of course, you'll get the original CID, not the supercid. You cannot change these properties (ro.secure is another one. The ONE that prevent us from writing on system, etc)
I think these properties are Read-Only and are loaded into the system from the hboot at boot time.
I managed to change the default.prop on "/" from ro.secure=1 to ro.secure=0 but every time you reboot your phone this file goes back to ro.secure=1, so I think hboot re-load every file and prop needed for their security lock at boot.
I repeat, even with root access you won't change a single property with "ro." before.
Not a single one.
Sorry guys, we'll have to wait more...
For more information abot the proccess read my post: http://forum.xda-developers.com/showthread.php?t=1042077
As you can see, no one has answered yet so I think this is useless...
Looks promising!
Sent from my HTC Wildfire using XDA App
Think I've discovered a bit more, I'm absolutly posotive that this is the way forward. Problem is not enough people seem interested in this post.
It would appear that this can be used to issue a boot message, so please share your knowledge on what you know of boot messages, coz I'm pretty sure a boot message could be used to override certain parameters.
Please people, if you read this, HELP ME OUT
I know what are you talking about,and I think that might help you
http://runtimeworld.com/2011/04/a-complete-list-of-hboot-commands/
I could work with you on this, PM me if you are interested
edit: this command has 8 letters (like cidnum):
writemid // write model ID
The best thing u've found.. I'm feeling like we'll oly root wildfire before unrevoked.,
It'll be good if we do it our self as unrevoked has tried hard but not succeeded due to heavy lock of hboot.. If there is a luck and ability to do it, we can do it..
I dont hav knowledge in linux and android much elz i would hav joined to root wildfire with u all..
Best of luck for rooting and make sure not to brick the phone..
God, I must follow this post.
Thanks for your hard work.
Sent from my HTC Wildfire using XDA App
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
ejnreon said:
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
Click to expand...
Click to collapse
cant be THAT new if you joined in 2009 :L
Hi Guys, I have been having major issues since upgrading the firmware from the Kies software as a standard firmware upgrade....
Just no wifi or bluetooth as soon as you click on the buttons it reboots sometimes several times....heres a link of whats been done so far from a guy that has been helping me on the Vodafone eforum.....
http://forum.vodafone.co.uk/t5/Sams...nger-update/m-p/761803/highlight/false#M16520
Currently running
I now have Firmware 2.3.4
Baseband I9000XXJVP
Kernel 2.6.35.7. XXJVP
Gingerbread XXJVP
I hope someone can help as I am lost without my phone because thats how I get my work...
Regards Lee
Ok found this how can I put these settings on my phone.
Error initializing Wifi scan
Symptom: trying to enable wifi shows scan initialization error message.
Solution: Requires root. Remove /data/wifi/bcm_supp.conf - the file contains wifi access points definitions and will be regenerated. You'll need to re-enter pin codes for known networks.
[edit] GPS lock problems
Come on guys some one must know the answer to this, you lot can hang bells and whistles on your phones and hack NATO
find 3 file froyo tith your csc flash it via odin with pit and pick desired csc
then flas 2.3.4 from samfirmware - any problems should be gone
That's exactly what I done over the weekend went back to 2.2 and installed 2.2.1 then 2.3 etc..
Its seems to be the same faults, someone has suggested its the Antenna that's at fault
adb logcat c:\logcat.txt
produce the bug and so it restarts
ctrl+c to stop writing logcat and pm it to me
I have sent you the logcat txt as an email as it was far to big to send as a pm and I was unsure what parts were not needed...
The wifi is not mentioned but path to bus for bluetooth is a constant failure
( E/BluetoothEventLoop.cpp(125): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
06-14 11:27:15.546 E/BluetoothEventLoop.cpp(125): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
I tried to get the wifi to log but everytime the phone locked up
Thanks for taking a look at this for me...
fast google search revealed two fixes for bt:
- hard reset - *2767*3855# - this will wipe your phone stats but most probably will fix both wifi and bt
- http://blog.pfuender.net/?p=61 - this will fix bt alone
also note that adb logcat c:\logcat.txt will log everything till you stop it or phone shuts off so produce wifi bug let it do its reboot or whatever and then ctr+c
- hard reset - *2767*3855# - this will wipe your phone stats but most probably will fix both wifi and bt
Tried these already before and after I put the new software on and have just tried again no difference at all problems still exactly the same...
so pick option #2 and report
It wont connect to my pc to run catlog.
I had to download via 3G and run it on the phone from there so I can not use Ctrl+C unless you know how to bring up a window with in the samsung.
I only got the log by sending it via 3G as an email....to my desktop then copy and pasting to a notepad doc
why cant connect to pc ?
Mine works fine and the one of a friend of mine works fine too wifi and bt on xxjvp
Dont know just finishing my chores around the house and will get onto it!
as an additional after moving file mentioned in article you might want to do 'fix permissions' in cwm recovery
I am also having the same issue:
E/BluetoothEventLoop.cpp( 469): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
However, my wifi does work. I have a Bell Samsung Galaxy S I9000M. The XXJVP modem didn't work for me (no HSDPA), so I flashed the UGJK3 modem and my connection was back. I followed the instructions on blog.pfuender.net/?p=61, blog "Android/Milestone bluetooth not working", but my '/data/misc/bluetoothd/' directory is empty, thus cannot perform the following step:
‘mv /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp.bak <ENTER>’
I will continue to research this issue. I only realized it this morning as an app I am working on requires Bluetooth, and logcat went nuts with error logs (shown above). I will also keep this thread updated with whatever I find.
Cheers,
vinpa.
huh that was htc desire fix =)
lulz understand this - bt should be working out of the box and is working on stock - i can also confirm that it works on cfroot as i use it flawlesly
if you got bt not working now think about what else can be not workign that you do not notice...
imho best way is to make a PROPER system install
basicly youre misising bt deamon or a start link for it = broken system
i am out of this thread, consider yourselfs helped (install stock+cfroot)
Got it working...
I first made a backup with CWM, then flashed PIT512, CODE_I9000XXJVP..., GT-I9000-CSC..., and my original modem.bin.
After it rebooted, I skipped through the setup and rebooted once more into Download mode, flashed CF-Root and then restored. Bluetooth is now functional.
Cheers,
vinpa.
hi, i have updated to 2.3.4 jvp from js3 telenor
all is fine, battery usage is much much better, no laggs, and no FC/FR..
i have turned on the bluetooth once set the name, and turned it off....
after i rooted and brought backups back,i cant use BT anymore. it just stands and turning on for a min or two, and than goes to TURNED OFF state...
any help? any ideas?
Just got a text to say my phone is ready for collection.....
Bet it's not repaired properly and it has to go away again for the same faults..
Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).
Skellums said:
Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).
Click to expand...
Click to collapse
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!
KingDaedrix said:
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!
Click to expand...
Click to collapse
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
All credit to the original devs of the unlock, fix is the same, just different source files were used.
Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.
KingDaedrix said:
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.
Click to expand...
Click to collapse
Unfortunately no. Windows Phone 7 is not open source so there is no easy/legal way to port the OS over. There are launchers that have been made so the Android interface mimics Windows Phone 7, but it's still Android running under the hood.
Help!
Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
I have followed the instruction you posted but i still cant boot into recovery. I have used adb command reboot bootloader and it gets stuck on a black and white screen tht says fastboot processing.
I am not sure if there something wrong with my device.
Thanks!
Me again, just replying to confirm that following the steps posted I successfully unlocked the bootloader of the phone. Not very much use however as there is very few ROMs for the model. Thanks a lot though OP!
I also successfully unlocked the bootloader using your binary. Thank you!
I wrote an article here on getting it all running with CM10.1 on the L5 E617G!
Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?
Did you ever get any info or help with this?
poopsmcgee said:
Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?
Click to expand...
Click to collapse
I did the same thing. I did make a NV Backup. Copied them back but that didn't change the no signal problem. I have tried odin back stock root and unrooted. Some how you have to get out of the DM/DUN/RmNet over HSUSB setting and back in DM/DUN over HSIC but I can't find a way. Can you get into the *#9090# without it being blanked out settings?
Did either of you ever manage to solve this? I have the same problem.
I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app
Great news! Any chance of getting a copy of the NV items so I can try this aswell?
madmediapro said:
I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi , can u plz tell me where is nv_data on s4 i9505 bcoz i can't see nv_data on i9505 efs folder.
If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app
That would be amazing. I look forward to your post.
i'm looking forward to your post.
madmediapro said:
If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.
madmediapro said:
I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.
Click to expand...
Click to collapse
Thanks for sharing and i don't think it will work on my device i9505 but i do appreciate the work u have shared thumbs up.
I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.
d3v147 said:
I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.
Click to expand...
Click to collapse
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..
AlanDS said:
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..
Click to expand...
Click to collapse
I did seem MadMediaPro did not encounter this. Also it is unlikely to occur if a SIM is never inserted in the phone. The other possibility is hex editing out the IMEI in the backup.
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).