Hi
Here we go this is my first post in XDA..
I Was reading some other phone thread in this forum about WiFi NVRAM WARNING: ERR 0x10 and a, glad that i found a solution for it..
As I fixed the Invalid IMEI issue,now am facing the wifi issue,where in whenever i turn on wifi i get an open network which states NVRAM WARNING: ERR 0x10..
So to fix this issue i need the nvram folder of Mobistel Cynus T2 JB V2.Can someone upload the nvram folder located in /data so that i can replace the whole folder which will fix the wifi warning and then i can restore the IMEI's again using MTK Tools IMEI backup which is on my SD card..
P.S its difficult to find the wifi file in nvram folder which is causing an error thats the reason i want to replace the whole nvram folder and rewrite the IMEI's.
Hit Thanks if it was helpful..
How did you solve it?
Hi, How did you solve this error....? I have the same phone with Cynus T2 ROM and has been facing NVRAM WARNING: ERR = 0x10 since long.
Please guide.
waseer.asif said:
Hi
Here we go this is my first post in XDA..
I Was reading some other phone thread in this forum about WiFi NVRAM WARNING: ERR 0x10 and a, glad that i found a solution for it..
As I fixed the Invalid IMEI issue,now am facing the wifi issue,where in whenever i turn on wifi i get an open network which states NVRAM WARNING: ERR 0x10..
So to fix this issue i need the nvram folder of Mobistel Cynus T2 JB V2.Can someone upload the nvram folder located in /data so that i can replace the whole folder which will fix the wifi warning and then i can restore the IMEI's again using MTK Tools IMEI backup which is on my SD card..
P.S its difficult to find the wifi file in nvram folder which is causing an error thats the reason i want to replace the whole nvram folder and rewrite the IMEI's.
Hit Thanks if it was helpful..
Click to expand...
Click to collapse
Hi rajen
I have been facing the problem since I formatted the phone using sp flash tool and the problem still persists so I want somebody to upload their nvram folder so that I can solve the problem.
Sent from my Micromax A110 using xda app-developers app
Solition
Dear Friends there are two way
1) During Flash Stock File Use Firmware Upgrade ...!!!
2) Go to service center before phone stop working.
Same thing happen with me after that phone was have dumy Charging issue due to PCB of hardware,Changed PCB.
anyone can upload his nvram folder from his micromax a110 ..data/nvram
Solved : [WiFi NVRAM WARNING: ERR 0x10]
Hi All,
nvram warning err = 0x10 solution
Hi Rajen
thank you so much for the solution
I am not that technical
Could you Please give me a detailed procedure to replace files i have upgraded it to jelly beam using sp flash tools and i am not as technical as you are
Any help is appreciated
Thanks in advance
Regards
Anil B
anilb3 said:
Hi Rajen
thank you so much for the solution
I am not that technical
Could you Please give me a detailed procedure to replace files i have upgraded it to jelly beam using sp flash tools and i am not as technical as you are
Any help is appreciated
Thanks in advance
Regards
Anil B
Click to expand...
Click to collapse
Hi Anil,
First of all, to develop your own technical understanding, refer to this thread http://forum.xda-developers.com/showthread.php?t=1960080
Now a solution for your problem.
1. Root your phone. Because you are already on Jelly Bean, follow these steps given on http://www.droidiser.com/2013/02/root-jelly-bean-updated-Micromax-a110.html
2. Install 'Total Commander' from Play Store after having rooted your OS successfully.
3. Download and copy the files on your SD card. These are the files which I have placed (attached) on this thread. Do not forget to unzip/unrar it and then copy to your SD card.
3. Turn off your WiFi (If enabled).
5. Go to system\data\nvram\APCFG\APRDEB by launching 'Total Commander' application.
6. Paste both the files i.e. 'WIFI' and 'WIFI_CUSTOM' from SD card to here in this folder. It will replace your existing files...but let it be.
7. Reboot your phone and check.
P.S. : You need to take a backup of your phone's IMEI as it is unique in nature for each device.
Let me know if you find any difficulties in this.
====================================================================================================
UPDATED AS ON 03rd September 2013
Dear All, My sincere apologies for a delay in updating this post.
Kindly note that due to some issues, I have removed attachments as this solution would duplicate MAC address of WiFi adaptor. I cannot post it here because you all would have MAC address of my phone's WiFi adaptor.
Hence, kindly follow a solution given in here on my following post which is quite permanent.
http://forum.xda-developers.com/showpost.php?p=39313158
Wish you all NVRAM ERR free mobile.
WiFi NVRAM WARNING: ERR 0x10
Hi Rajen
Thanks a million
I followed ur steps it fixed the issue WiFi NVRAM WARNING: ERR 0x10 ,but the wfi range is not that great in jelly bean any solution
a have a few more questions
1) can you tell me how do i unroot the phone so that i have the phone warranty
2) can you tell me how to back the nvram since my phoen is in root
once again thank you very much for helping me out
Regards
Anil B
Hi Anil, It feels good to obituary you have solved the NVRAM WARNING problem. Note followings.
-> WiFi range and It's refresh rate totally depends on particular ROM. These files (which I attached have no role to play in it)
-> Simply flash stock ROM V2 or V3 through SP flash tool and your phone will be unroot.
-> To backup, try backup option from stock recovery by pressing power+volume up+volume down buttons (all three at one time) together to enter in to recovery. Best way to do this is to first switch Off your phone and then follow it.
Sent from my Galaxy Nexus using xda app-developers app
it fixes but changes the mac address.
Jeet Chowdhury said:
it fixes but changes the mac address.
Click to expand...
Click to collapse
Yes, you are right but it doesn't put you in a problem (particularly in getting connected) if the devices with same mac address are not on same network...i.e. same IP range or same DHCP.
Meanwhile I am working out on the steps to solve it.
brother. after every factory reset imei and wifi having issue again? can we solve that? also in jellybean rom the earpiece volume is too low to hear in bus or train on busy day.
Where are the attachments???
rajenpurohit said:
Hi Anil,
First of all, to develop your own technical understanding, refer to this thread http://forum.xda-developers.com/showthread.php?t=1960080
Now a solution for your problem.
1. Root your phone. Because you are already on Jelly Bean, follow these steps given on http://www.droidiser.com/2013/02/root-jelly-bean-updated-Micromax-a110.html
2. Install 'Total Commander' from Play Store after having rooted your OS successfully.
3. Download and copy the files on your SD card. These are the files which I have placed (attached) on this thread. Do not forget to unzip/unrar it and then copy to your SD card.
3. Turn off your WiFi (If enabled).
5. Go to system\data\nvram\APCFG\APRDEB by launching 'Total Commander' application.
6. Paste both the files i.e. 'WIFI' and 'WIFI_CUSTOM' from SD card to here in this folder. It will replace your existing files...but let it be.
7. Reboot your phone and check.
P.S. : You need to take a backup of your phone's IMEI as it is unique in nature for each device.
Let me know if you find any difficulties in this.
Click to expand...
Click to collapse
where are the attachment?
Where is the attachment
rajenpurohit said:
Hi Anil, It feels good to obituary you have solved the NVRAM WARNING problem. Note followings.
-> WiFi range and It's refresh rate totally depends on particular ROM. These files (which I attached have no role to play in it)
-> Simply flash stock ROM V2 or V3 through SP flash tool and your phone will be unroot.
-> To backup, try backup option from stock recovery by pressing power+volume up+volume down buttons (all three at one time) together to enter in to recovery. Best way to do this is to first switch Off your phone and then follow it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Where is the attachment
See the link
rennyc3 said:
Where is the attachment
Click to expand...
Click to collapse
see the attached link u found the solution.
http://forum.xda-developers.com/showthread.php?t=2225757
no attachment
Nishroy said:
see the attached link u found the solution.
http://forum.xda-developers.com/showthread.php?t=2225757
Click to expand...
Click to collapse
I checked the attached link,there is no attachment there also.can u please email it to me,my id is [email protected], thank u
NVRAM ERR & INVALID IMEI both these errors come again after we flash a rom using SP FLASH TOOL....is there any permanent solution to these problems??
Any permanent solution for this problem and invalid imei problem...????
Alternative
Is there any solution without root the phone
Guide - To Solve MTK Devices ~ Soft Bricked from No IMEI, No Baseband, No RIL, No WiFi MAC, BT MAC, comms etc. ​
Note:
This is a "clone thread" from my original thread. I post another guide at here to help those who are in difficulty finding the correct guide to solve this problem. This method probably works on all Mediatek devices. For reference, my Lenovo P780 uses a MTK 6589 chipset.
DISCLAIMER:
*What you done to your phone is at your OWN RISK, you choose to do this modifications to your phone and don't blame me if anything goes wrong.
Preface:
Recently I have noticed many people who tried to flash Custom ROM's on MediaTek devices and causes the phone to lose IMEI, Baseband, RIL, WiFi MAC, BT MAC, SN, comms etc. and causes connectivity issues (including me), which renders our MediaTek devices turned into a "AndroidPod" media device that cannot make calls, SMS etc. As an example, my Lenovo P780 which faced the exactly same problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See the IMEI and baseband are still there in factory mode!!!
What could cause this is problem to occur is probably during ROM flashing process, the installer probably wiped out the /data/nvram (folder/partition). The /data/nvram (folder/partition) is the heart of your phone of all communicating feature, if the (folder/partition) is corrupted, just like I said, no communication features.
*Actually the baseband is there, but because the /nvram (folder/partition) has corrupted, the Android OS were unable to recognize it thus showing Unknown.
So no backup = Phone dead? Nothing but a media player?
First step, ensure your phone:
On Stock ROM
Rooted
PC have ADB drivers installed (If you don't have it please ask Uncle Google :good
Well, that isn't true, recently I found out, the phone can actually be easily recovered (on most MediaTek devices) and gain at least those comm features back by simply delete the whole /nvram (folder/partiton). If your phone coldn't recognize SIM card, wait a while after deleted the folder, your phone should have signal after maximum 10 seconds of waiting.
*In most of the cases MobileUncleTools give AT command failed to send probably the /nvram folder is corrupted, simply delete the NVRAM folder and reboot will do.
For WiFi MAC address fix (WiFi NVRAM WARNING: ERR 0x10), because the solution already been posted, so please click here.
Bluetooth MAC address fix: Firstly, using any File Explorer with Root abilities navigate to /data/nvram/APCFG/APRDEB/BT_Addr and also a BT_Addr file under /data, then copy both files to your PC. Then open up the file by using Hex Editor (HHD Hex Editor). To fix a static MAC address, just simply type in your MAC address on the first row (0000) from column (00-05). That is what your MAC address should be (Edit both files with the same MAC address). After you have modified it, put it back in the exact location and remember to change permission.
Actually you can also get restore your IMEI, WiFi MAC, BT MAC, SN by restoring a backup created by MTKDroidTools with other exact same model as your phone.
Hi,
I have a Pomp W99 (MTK6589T) and it seems this model (or it's software) has the problem, that Wifi and Bluetooth MAC address changes on every activation.
While I was able to fix the changing MAC address with the procedere as described I still have the problem of the changing Bluetooth MAC, which is very annoying.
Any ideas how to fix this?
Thanks & Ciao, Alfred
serpi42 said:
Hi,
I have a Pomp W99 (MTK6589T) and it seems this model (or it's software) has the problem, that Wifi and Bluetooth MAC address changes on every activation.
While I was able to fix the changing MAC address with the procedere as described I still have the problem of the changing Bluetooth MAC, which is very annoying.
Any ideas how to fix this?
Thanks & Ciao, Alfred
Click to expand...
Click to collapse
Hi, I have updated my post.
soralz said:
Hi, I have updated my post.
Click to expand...
Click to collapse
Thanks for this but sadly, this doesn't work, I've already tried it.
I have a BT_Addr in /data/nvram/APCFG/APRDEB but the mac address there is not used.
I also have a BT_Addr in /data and it seems, this one gets updated with the current MAC.
I tried removing the file rights so that the file could not be altered, but now I have a static address in the file that is different from the one shown in the telephone status.
I'm still getting on every enabling of bluetooth a new address, always like xx:xx:46:66:xx:xx (the two bytes in the middle ar always the same).
My only solution at the moment is not to disable Bluetooth and not to reboot my phone, because else I have to re-pair all bluetooth devices.
I would even be lucky with a solution that would change the bluetooth MAC to static one by script after enabling Bluettoth but I couldn't find anything about this, all I could find was about changing wifi MAC address.
Maybe you have another idea?
Thanks & Ciao, Alfred
serpi42 said:
Thanks for this but sadly, this doesn't work, I've already tried it.
I have a BT_Addr in /data/nvram/APCFG/APRDEB but the mac address there is not used.
I also have a BT_Addr in /data and it seems, this one gets updated with the current MAC.
I tried removing the file rights so that the file could not be altered, but now I have a static address in the file that is different from the one shown in the telephone status.
I'm still getting on every enabling of bluetooth a new address, always like xx:xx:46:66:xx:xx (the two bytes in the middle ar always the same).
My only solution at the moment is not to disable Bluetooth and not to reboot my phone, because else I have to re-pair all bluetooth devices.
I would even be lucky with a solution that would change the bluetooth MAC to static one by script after enabling Bluettoth but I couldn't find anything about this, all I could find was about changing wifi MAC address.
Maybe you have another idea?
Thanks & Ciao, Alfred
Click to expand...
Click to collapse
Or you can try editing both files with the same MAC address? Save and set permissions?
soralz said:
Or you can try editing both files with the same MAC address? Save and set permissions?
Click to expand...
Click to collapse
Been there, done this.
Both files have the same address and permissions are set so that they cannot be altered.
Still the OS keeps creating random addresses, so it doesn't seem the files are read by the system but only get written.
Thanks & ciao, Alfred
serpi42 said:
Been there, done this.
Both files have the same address and permissions are set so that they cannot be altered.
Still the OS keeps creating random addresses, so it doesn't seem the files are read by the system but only get written.
Thanks & ciao, Alfred
Click to expand...
Click to collapse
Well that's weird, technically it should be static already. Never mind, I will keep searching for other solution. Sorry for that you can't get it to work.
Or perhaps, do you have any friends / relatives of yours using the same phone? You can try MTKDroidTools to make a NVRAM backup of their phone and restore the settings to your phone. That should fix it.
I get something like that after a STAR N9002 Update, but with something else...
My touch doesn't mach the screen, the screen is normal but the touch point's are out of place... do you understand? like the touch have a resolution diferent from the screen resolution...
Do you think this is caused from a software problem, NVRAM is missing and happen all in the same reboot AFTER the update...
I'm trying to get a backup copy of NVRAM, but I don't know if the touch will be ok after that...
Thanks.
PMoto said:
I get something like that after a STAR N9002 Update, but with something else...
My touch doesn't mach the screen, the screen is normal but the touch point's are out of place... do you understand? like the touch have a resolution diferent from the screen resolution...
Do you think this is caused from a software problem, NVRAM is missing and happen all in the same reboot AFTER the update...
I'm trying to get a backup copy of NVRAM, but I don't know if the touch will be ok after that...
Thanks.
Click to expand...
Click to collapse
I know, I have encountered the problem before on a cheap China tablet. That isn't caused by /nvram corrupt/missing but the touch driver you have are not compatible with your touch hardware. I'd suggest you restore from a backup.
Thank's for your answer. I've already get a NVRAM backup to set me up. That's ok, but the touch is still messed. I don't have a backup... I don't know how I will get it...
PMoto said:
Thank's for your answer. I've already get a NVRAM backup to set me up. That's ok, but the touch is still messed. I don't have a backup... I don't know how I will get it...
Click to expand...
Click to collapse
Do you have any friend's or anyone you know using the exact same phone? My idea is: Find an 100% identical phone (probably from dealer is the best bet). Backup the entire phone using MTKDroidTools, and then restore the backup to your phone. After that just restore back your original /nvram partition (you wouldn't want the same IMEI and related info isn't it?)
Therotically your phone should work/recover.
Yes, I'm waiting for a promised integral backup. That's my final hope now...
PMoto.
PMoto said:
Yes, I'm waiting for a promised integral backup. That's my final hope now...
PMoto.
Click to expand...
Click to collapse
Okay... Good luck bro. Next time if you hands-on with any MTK devices. Be sure backup it first using MTKDroidTools. It's a very useful and powerful backup software.
No luck for me.
Even a full backup did not make the touch work well.
I think a backup is a good way to prevent flash problems, but what I have was far worst than that. Some how, the flash procedure burn the touch driver chip, and there's no way to make them work again...
I'll have to replace it... that's a shame...
Thanks for your support.
PMoto.
PMoto said:
No luck for me.
Even a full backup did not make the touch work well.
I think a backup is a good way to prevent flash problems, but what I have was far worst than that. Some how, the flash procedure burn the touch driver chip, and there's no way to make them work again...
I'll have to replace it... that's a shame...
Thanks for your support.
PMoto.
Click to expand...
Click to collapse
try a TP Upgrade..and might restore your touch screen..
kermage said:
try a TP Upgrade..and might restore your touch screen..
Click to expand...
Click to collapse
What do you mean with a TP Upgrade???
PMoto said:
What do you mean with a TP Upgrade???
Click to expand...
Click to collapse
Touch Panel Upgrade..
Oh, sure. That's my point, if some software bricked it, some software should repost it...
Anyway, I already order a new Touch panel for it, thanks.
PMoto said:
Oh, sure. That's my point, if some software bricked it, some software should repost it...
Anyway, I already order a new Touch panel for it, thanks.
Click to expand...
Click to collapse
:good:
you could have atleast tried it first..might have helped you save
Sorry, i'm missing something here...
Do you know some way to do a touch upgrade with software? I don't. That's why I must buy a new one.
But if you know a way, please post here...
I already flash all possible ROM's, even a full a backup of a similar phone with no results...
Thanks.
PMoto.
In my need of spoofing my mac adddres with legal actionsi came across with my mac addres change whether custom or stock roms is installed so i tried the following and it works, maybe only for me but you never know.
my address is 00:1A:73:XX:XX:XX in stock roms, in custom roms or stock rom with custom kernel the mac change into 84:38:38:XX:XX:XX, i thought that was a flashing bug, but turns out to be that custom kernels read the mac addres different from stock kernels, stock kernels read the mac from these two files using root explorer /efs/wifi/.mac.info and efs/wifi/.mac.info.bak the mac addres is storage in there and editig those files with root explorer to the same mac writen correctly, rember both and delete efs/wifi/.mac.info.bak.bak if created, rebooted and wi fi cant be activated, power of to download mode and flash a STOCK rom with odin the mac address changed permantly unless an efs backup is restored or flashing a custom kernel.
for temporaly mac spoofing try https://play.google.com/store/apps/details?id=com.wireless.macchanger hard change option.
try this at your own risk if needed, and always, always make an efs backup first i recomend efs back up pro in xda forums is a windows tool, this is high risk procedure and can mess your wifi,
Sorry for my english and good luck
If i am mistaken and/or the threat is missplaced please correct it and inform to moderator to change the location, thanks in advance.
I used Pry-Fy from Chainfire. Search it in the Playstore. Here is the Link for discussion. http://forum.xda-developers.com/showthread.php?t=2631512
GTI-9300 said:
I used Pry-Fy from Chainfire. Search it in the Playstore. Here is the Link for discussion. http://forum.xda-developers.com/showthread.php?t=2631512
Click to expand...
Click to collapse
thanks but i used to but pry-fi, it only randomize the mac address not spoof to a specific one. only sharing my history.
Hello xda friends.... im new here and i need a help from u guys. Please help mee..
i just bricked my micromax magnus a117. What i did--- rooted my phone then installed an app meteos6589 (something like that) to increase app storage. Then i restarded my phone(with usb debugging off(if it afffects anything )). And after that it is showing micromax logo only.
so anyway i downloaded stock rom v4 from mounlisky. and tried to flash with sp tools. But but but problem is arising something like "pmt didnt mathched...................." . So sp tools is saying to select and do format+download option. But i have nothing in backup only microsd and internal sd data.
So the point is i dont have backup of nvram or anything else, phone is bricked at micromx logo, usb debugging off. So how do i get my phone back to life.
anyone please....
Any detailed help is appreciated.. thank you..
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
ranganitesh said:
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
Click to expand...
Click to collapse
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
syserr said:
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
Click to expand...
Click to collapse
So what files are needed to be backup along with mtk droid tool, just wanna know.
ranganitesh said:
So what files are needed to be backup along with mtk droid tool, just wanna know.
Click to expand...
Click to collapse
I don't use MTKDT at all. I do see some uses for it though. SPFT is a pain, but I wish every device (SoC maker) had an SPFT so you could read or write any chunk of flash.
If you look at a scatter file you will see lots of blocks/partitions that the flash is divided into. Each of these has a purpose of course, but the one marked NVRAM (a horrible confusing name) is the most important to get backed up, it has unique "calibration data" for your specific unit. You may find a "nvram.bin" that MTKDT created... this may be exactly what SPFT would backup too... if you are lucky.
So if MTKDT made a nvram.bin that is about 100x better than having a nvram.tgz or however he archives the /data/nvram files.