Related
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
I am having this problem, but on a vibrant that has not been rooted yet.
I cant seem to find the wpa_supplicant.conf, I have tried browsing for it using the built in file manager and using ASTRO, but the data directory is always empty.
Is there a way to fix this without rooting the phone?
if your phone has not been rooted then that means your phone is f**ked up and might need to be exchanged. but this is the evo forum not vibrant. the only way to mess with system files is to be rooted
Appreciate info*, worked in a heartbeat, saved from reloading everything from scratch, which was my way out last time. Witstech A81E Froyo 2.2
*renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak
Good eye there mate!!!!
InstantKarma said:
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
Click to expand...
Click to collapse
I was experiencing the same issue and read this and it works, good looking out.
same issue on mytouch 4g
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Who But BilL$ said:
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Click to expand...
Click to collapse
It just recreates the file when your phone gets rebooted. My Thunderbolt is having the EXACT same issue. Ive tried renaming this and deleting as well and still no luck. Im now kicking over any rocks that I can find to get my wifi working.
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
shoppy said:
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
Click to expand...
Click to collapse
I actually ended up having to get a whole new phone. My insurance company couldnt fix it.
joeavery2 said:
2. I've had this issue a number of times now specificly the "unable to turn on" ......... but I am not sure what causes the unable to scan for networks to happen.
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I had the same problem. I installed the software from the sony erikcon website to my computer, and then followed the process for updating the phone software. That did not work, since I had the latest software already. So then, I tried to REPAIR my phone software, and after that was done, my phone was functional again, and the wifi works without any problems.
Requirements:
* A PC connected to the Internet (preferably broadband)
* USB phone-to-PC connection. Please see the accessories compatibility list for your phone.
1. Run the software on the computer after it is installed.
2. Follow the procedure for UPDATE or REPAIR (if you already have the latest version).
SOLVED WIYH THIS D12r a33_8723-8703_v11_0312 20141211.IMG
joeavery2 said:
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I SOLVED WITH FLASH THIS: D12r a33_8723-8703_v11_0312 20141211.IMG
People still use this phone?
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Im pretty sure you just need to repartition the sdcard. Its under advanced in cwm.
butchconner said:
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Click to expand...
Click to collapse
CWM .12 (the newest one) actually reads from the microSD. But (and this is a big BUT) it has issues with non-padded boot.img files, which is what TnT Lite, and TnT stock based 1.01a1, and stock itself, use. So it's a double edged sword. I still use .08 because of this issue.
I would also recommend the SD card re-partition. You have cwm already so you are halfway there. Worst case it's nvflash time - I have a post on that process, as well.
Fate Zero,
Thanks for the quick reply. I had that post laying on the desk before I even started. It wouldn't work because the G-Tablet would not read or access SCCARD2 as I mentioned in the first post.
Rev
GideonX,
It wasn't that simple, but your suggestion was part of the solution!!! Thanks!!!
Rev
P. S. -- See answer to Roebeet for more info.
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
Bleary eyed as well (time for sleep) -- I personally use Titanium Backup for the (primary) Market fix. Has worked every time and I've done it a alot, as you might expect. I'm not sure why the file manager won't let you run an apk from the downloads section, but I believe you can download (and run) the TB apk right off their web site.
I'm guessing from the root explorer comment that you are trying the additional Market fix, for even more apps? Maybe you can get it working enough with the primary fix, to get root explorer? I see it in my own Marketplace, although it's not a free app.
Sounds like you are getting there. I replied back to your PM but I guess I saw it a little late
I was hoping you wouldn't run into a bunch of issues when I wrote you back. You will get it. I think you are almost there.. And I have been in the same boat myself a bunch of times. Nothing like thinking you just wrecked your new toy....
You can use the microsd to load the Vanilla with ClockworksMod, but you are still in a boot loop. So, like others stated format the internal SD. Then use your USB mount option to copy over the stock rom and flash. This will get you back up and running.
Reboot, install TNT lite using Clockwork, reboot, skip Google sign in. Install Titanium and clear that google process. Create a Google Account and reboot.
Market should work after that.
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
FateZero said:
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Click to expand...
Click to collapse
Worked flawlessly for me. Thanks!
All,
Thanks to those who replied for help, moral support, suggestions, and whatever.
I have been up on 2.2.0 ever since the malfunction that started all this and now have added my desired software, etc.
Bottom line is that with this experience I now think I know enough to hold things together and do whatever testing I want to do. I hate to have learned it the hard way. And I wish I had known enough about CWM to load it first and preserve the stock hardware on it.
I will say that IMHO the G-Tablet rocks. Yes, the screen is substandard, but I usually hold it in front of me or set it up on a stand anyhow. And straight on it's not bad. I will keep following watching for a screen mod.
Again, thanks all.
Rev
**This requires root.**
The file you need to delete to stop the sprint activation has changed for 2.3.4
it used to be:
/system/app/sprintadroidextension.apk
now it is:
/system/app/DeviceManagement.apk
-------------
If you don't know how to delete files from your internal memory, use Root Uninstaller and look for the the white check in a green circle. It will be the same icon that is in the taskbar after you cancel the activation.
-------------
I renamed the SprintAndroideExtension.apk in 2.3.4 and I'm no longer nagged. DeviceManagement.apk handles firmware/PRL updates etc.
I agree that renaming the file is a wise idea. There might be a time where you might need it or maybe regret erasing a file. I have experienced this in the past.
Thanks for this, I just added .bak using ES Explorer and on reboot no nagging...
DanielNTX said:
I renamed the SprintAndroideExtension.apk in 2.3.4 and I'm no longer nagged. DeviceManagement.apk handles firmware/PRL updates etc.
Click to expand...
Click to collapse
DanielNTX said:
I renamed the SprintAndroideExtension.apk in 2.3.4 and I'm no longer nagged. DeviceManagement.apk handles firmware/PRL updates etc.
Click to expand...
Click to collapse
I'm pretty sure you're wrong here.
My setup:
EA24 tar flash -> EB28 OTA -> GB update.zip -> zhangqip's root.tar
There was definitely no SprintAndroidExtension.apk on my phone. I know because I triple checked, deleted everything with sprint in the name, and it was still trying to activate. I finally used Super Manager to check the package name on the Activator app and that's how I found out it was now in DeviceManagement.apk.
---------
On a side note, I also deleted: phone.apk, hiddenmenu.apk, and messaging.apk, and now it no longer does the 3G thing. It seems to save battery when the screen is off (it used to drain if I left it sitting) and it allows me to use BT without having to turning off airplane mode. The only problem I've noticed is that settings will crash if you try to open the mobile network settings. I imagine that could easily be fixed with a null phone.apk (one modified to return no signal/activity instead of accessing the modem.bin). Anybody know of one. I imagine one for any device would be suitable.
Alternatively (and maybe easier) you can go into Titanium and freeze the same stuff that you froze on Froyo.
I did EA24 tar flash -> EB28 OTA -> Zhangqip's root.tar last night and the SprintAndroidExtension.apk was right where he said it was. And I renamed this file using ES Explorer (have to turn on Root options and read-write to system; forgot to do this at first and the rename failed but worked the second time) and the nagging is gone. Your suggest file is still there untouched. So he's not wrong, but somehow your Tab is different.
jiminitaur said:
I'm pretty sure you're wrong here.
My setup:
EA24 tar flash -> EB28 OTA -> GB update.zip -> zhangqip's root.tar
There was definitely no SprintAndroidExtension.apk on my phone. I know because I triple checked, deleted everything with sprint in the name, and it was still trying to activate. I finally used Super Manager to check the package name on the Activator app and that's how I found out it was now in DeviceManagement.apk.
---------
On a side note, I also deleted: phone.apk, hiddenmenu.apk, and messaging.apk, and now it no longer does the 3G thing. It seems to save battery when the screen is off (it used to drain if I left it sitting) and it allows me to use BT without having to turning off airplane mode. The only problem I've noticed is that settings will crash if you try to open the mobile network settings. I imagine that could easily be fixed with a null phone.apk (one modified to return no signal/activity instead of accessing the modem.bin). Anybody know of one. I imagine one for any device would be suitable.
Click to expand...
Click to collapse
Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)
Hi!
When removing Bloatware with Titanium Backup a while ago, I accidentally missed a click (never used a touch screen...) and uninstalled MediaProvider, which I have not been able to recover since.
I tried putting the files back from a friend's HTC, which didn't work; after that I was told even the packages differ between manufacturers, so I tried getting them from a stock Bell Atrix .zip posted on these very forums, which didn't help either. Neither #android-root nor AndroidForums were able to help, thus I ask here: Can anyone tell me how to either make my system accept Bell's files, or where I can find a "vanilla" Motorola build?
(Problem is, the phone didn't come from a phone company, a friend of mine got it pre-release from his uncle who is with Motorola, so it may even be different from what hit the market later on...)
I guess the following information will help, it's a Titanium Backup info file for another componend I backupped shortly after:
#Titanium Backup
#Sat Feb 25 03:28:43 MEZ 2012
app_gui_icon=[...]
sys_ro.build.date.utc=1302536066
app_version_code=8
sys_ro.product.model=MB860
has_prefsdata_jpu=0
sys_ro.serialno=<xxx>
sys_ro.build.description=olympus-user 2.2.2 OLYEM_U4_0.44.0 578673 ota-rel-keys,release-keys
has_prefsdata=0
app_gui_label=com.android.providers.applications 2.2.2
sys_ro.build.version.release=2.2.2
app_apk_md5=1989ff2476ee73ad445760b9bef5f44e
has_dbdata=0
app_apk_codec=GZIP
app_is_forward_locked=0
app_is_system=1
app_label=com.android.providers.applications
app_version_name=2.2.2
generation=1
app_apk_location=internal
(Most of this is unnecessary, I guess, but I can't really be sure what you might need to judge what I would have to to...)
I would be very grateful for any help, it is extremely limiting not to be able to use any media capabilities.
So, thanks in advance,
David
maybe flash a new rom if your contacts are all backed up?
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Intelensprotient said:
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Click to expand...
Click to collapse
Yes, but you have to set the permissions same the other files in .system/app folder.
I have attached the missing files to this post. My gingerbread version is 2.3.4.
Good Luck!
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Intelensprotient said:
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Click to expand...
Click to collapse
I would hard reset too at this stage. I'm sorry it didn't work out.
Now, that's interesting. Factory reset didn't change anything.
Sorry for reply to self, but I was less than clear, so - help?
My next step would be to try to unlock the bootloader, then flash CWM and see if anything can be fixed that way; then, I would try flashing CM7 (or, more specifically, the Neutrino GT ROM) by CWM; then, I would try flashing it without. Is that a safe progression of attempts? Or have I possibly broken anything that would hard-brick it by any of these methods? And can you recommend any finer increments what I could do before / between / after those mentioned? I still have the option to apply an update in Recovery - is it possible, for instance, to put a .zip onto my SD that has 0 Byte MediaProvider files in it?
(I have thought about installing Neutrino for a while, and this seems to be a good time to flash it, as my data is cleared now anyways. To my understanding, this should not be any more dangerous than just re-flashing the Froyo that was there before, right?)
As an additional fact, ADB now doesn't detect any devices any more, even with Early USB. This could be because USB Debug is not a factory standard setting, though, as I reset it to factory defaults.
Also, the startup Moto screen behaves differently: It doesn't go to the point where the logo disappears in a flash, the background light switches off before that. As far as I can tell, the display still shows the animation, though, but it is not lit. Furthermore, the reboot seems to happen immediately after the animation has ended, and not 1-2 minutes later, like it was before the reset.
I would be grateful if anyone could explain what happened. To my understanding, a factory reset should clear /system, and the error started when I put some non-compatible .apks there, so I thought this would fix things. Is it possible something broke on the hardware side, when (for instance) 2.2.2 called a function that has had its parameters changes in 2.3.4?
[If a moderator reads this - does this qualify as a general Android question? I have no experience with different devices, so I'd be glad if you could decide if this thread has to stay here or if it can go to a sub-forum with a wider audience - General Android Q&A, for instance.]
Bump...
Success Neutrino up and running!
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).