[Q] Micromax A110(Canvas 2) WiFi NVRAM WARNING: ERR 0x10 - Micromax A110

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

Related

How to change MAC address on V970 (MTK6577)?

Hello,
I have two ZTE V970 phones and I copied the contents of one to the other (by backing to nandroid on one, copying the backup to the other and restoring there).
All i sine except that it copied also the IMEI numbers and the MAC address.
I succeeded to chage back the IMEI but the MAC stumps me.
I tried all the methods I found on the net but to no avail.
Is there someone who changed the MAC on a V970 or similar?
Thankfully yours,
Base
Try this: http://forum.xda-developers.com/showthread.php?t=1385577
You have also restored userdata, haven't you? That's most likely the problem. Using a root explorer just go to /data and delete nvram folder. Let it be created from scratch.
hey dev.. please help me.. i have a micromax a110.. mtk6577 device.. unable to change mac using ifconfig, ip link etc.. please help...
Ya please pllzzzz plzzzz help to do it(((
vaidhy2007 said:
hey dev.. please help me.. i have a micromax a110.. mtk6577 device.. unable to change mac using ifconfig, ip link etc.. please help...
Click to expand...
Click to collapse
Even i am facing the same problem unable to change my mac id in MMX A110
baseh said:
Hello,
I have two ZTE V970 phones and I copied the contents of one to the other (by backing to nandroid on one, copying the backup to the other and restoring there).
All i sine except that it copied also the IMEI numbers and the MAC address.
I succeeded to chage back the IMEI but the MAC stumps me.
I tried all the methods I found on the net but to no avail.
Is there someone who changed the MAC on a V970 or similar?
Thankfully yours,
Base
Click to expand...
Click to collapse
Hi! I have a ZTE V970, did you restored the IMEI or changed the IMEI? Is possible change the V970 IMEI?
May Thanks!
Make V970M IMEI & MAC's "permanent"?
bgcngm said:
You have also restored userdata, haven't you? That's most likely the problem. Using a root explorer just go to /data and delete nvram folder. Let it be created from scratch.
Click to expand...
Click to collapse
Hi Bruno, I love your work, specially with V970M phones. Great job by the way.
I have a big problem with one of my phone, broken screen etc., I manage to repair it, format the NVRAM and installed your v1.2. But then I have a similar problem, IMEI's all gone, Wifi with NVRAM ERROR 0x10 and Bluetooth NOK also (these last two keep change everytime I turn them on), since I have 2 phones, I read a bit about this and tried to change de MAC's for the Wifi and BT. Restored the IMEI with Engineer Mode, I then copy the \Data\nvram\APCFG\APRDEB\ folder content, it worked but there's two problems:
1st Both MAC for WIFI and BT are the same as the other device... not good.
2nd Everytime I make a full system reset, it losts all the data EMEI's and MAC's... and I need to input everything again.
I red somewhere, that we can edit the BT_Addr and WIFI (files with APRDEB) with HxD Hex Editor, search for the MAC's and change it, replace the files, but after reboot, the Mac's continue to change everytime I connect the WF & BT (and the error 0x10 appears again).
My question is, there's anyway that I can change the MAC's in MTK Enginner Mode, or use some tools that really work (tried a couple like MAC_Spoof and others but they cannot read the MAC's) and if there's anyway (after all been corrected IMEI & MAC's) to make it "permanent" and everytime I make a full reset or install a new ROM, don't loose all these data?
Thank one more.
Best regards everyone.
JJ
I had the problem with my MMX A177
I was not able to change MAC add in terminal emulator and MAC spoofer
But guys try MTK engineering mode its working for MMX devices.
I was doing this to hack WhatsApp but it verify the device and u register previous device.
Is there any new trick to hack WhatsApp?

Custom ROM for THL W1+

I hope I've posted this in the correct place. Apologies if not... I'm sure a moderator will move to correct place.
Hi everyone,
I’d like to share my THL W1+ custom ROM with you all.
It is based on a CJ ROM which I believe is the international ROM version.
Natively, the CJ ROM had some benefits over the stock standard Chinese THL ROM such as not showing Chinese cities in call log etc.
I cant remember all of the tweaks I've made in this custom ROM as it was "cooked" over an extended period of time but here are a few…
Google Apps working and upgraded
Default IME keyboard upgraded
Removed Chinese Apps and input methods
Removed factory reset option from settings to prevent reboot loop (use custom recovery to reset)
Improved screen brightness
updater-script changes for Wi-Fi fix
Included Facebook, Skype and Flash in DATA partition (can be uninstalled)
build.prop changes: font size, English language is default, time zone default to Pacific/Auckland
Download and use at your own risk. No responsibility is taken for damage done to your phone through using this ROM.
I’ve included in this download package everything I can think of that you'll need including the CJ ROM, a version of SP Flash Tool, the update.zip file, zip files to root and unroot the phone plus ADB and VCOM drivers.
The all-inclusive package can be downloaded from here…
http://www.mediafire.com/?p08zo4jwypz23
It is split into four compressed files. Use software such as 7zip to uncompress.
#1 First, flash your phone via SP Flash Tools with the stock CJ ROM. I’ve added a custom recovery to the ROM which you will require later to install the update.zip file.
If you do not know how to flash your phone here is a great tutorial... http://bm-smartphone-reviews.blogspot.co.nz/2012/05/mt6575-flashing-tutorial.html
#2 Once you have successfully flashed the CJ ROM you need to install the update.
Copy the update.zip file to your microSD card or power on the phone and copy to internal storage.
Remove your battery and reinsert it.
Hold down the Vol+ button and power on. You should boot into recovery mode.
Now using your volume keys you can select the update from zip option (power button is select). Choose the update.zip file you copied to your phone and confirm.
Wait for the update to complete and then reboot.
That should be it!
Hope you enjoy this ROM.
Invalid imei
I install your rom and is perfect. i manage to unbrick my W1+ with this rom. only the imei is invalid and i cant restore them. i see a folder named imei drivers (something like that ) in your pachage. how i can use them to restore the imei. i tried meny tutorials from the net but still nothing
thanks for your time
Aris
Hello, it is good to hear people are using the ROM.
I think the folder you are referring to is one inside the DRIVERS folder and simply contains CDC driver files.
I've not had any IMEI issues on the W1+ so can't speak from experience but I would suggest trying the following...
ROOT the phone using the root update.zip in the package.
Download MTK Droid Tool... http://www.mediafire.com/download/a41a0u73dc7rw2h/MtkDroidTools_v248.zip
MTK Droid Tool has a Write IMEI function.
Once your phone is rooted make sure USB debugging is turned on (Settings > Developer options).
Failing that, another option would be to download Mobile Uncle Tools from Google Play. Again, this requires root privileges and you'll need to connect to a Wifi network as your SIM's are not working. I understand this app also has IMEI tools.
Hopefully this works for you.
marsian720 said:
I install your rom and is perfect. i manage to unbrick my W1+ with this rom. only the imei is invalid and i cant restore them. i see a folder named imei drivers (something like that ) in your pachage. how i can use them to restore the imei. i tried meny tutorials from the net but still nothing
thanks for your time
Aris
Click to expand...
Click to collapse
inspectaclueso said:
Hello, it is good to hear people are using the ROM.
I think the folder you are referring to is one inside the DRIVERS folder and simply contains CDC driver files.
I've not had any IMEI issues on the W1+ so can't speak from experience but I would suggest trying the following...
ROOT the phone using the root update.zip in the package.
Download MTK Droid Tool... http://www.mediafire.com/download/a41a0u73dc7rw2h/MtkDroidTools_v248.zip
MTK Droid Tool has a Write IMEI function.
Once your phone is rooted make sure USB debugging is turned on (Settings > Developer options).
Failing that, another option would be to download Mobile Uncle Tools from Google Play. Again, this requires root privileges and you'll need to connect to a Wifi network as your SIM's are not working. I understand this app also has IMEI tools.
Hopefully this works for you.
Click to expand...
Click to collapse
Thanks for youe reply. mtk droid and mobile uncle didn't work. Finally i found this "THL W1 INVALID IMEI TOOL 4.0.4" and i cewate a new imei file and replace it inti the phone root and now everything is ok.
your rom is smooth. hope to upgrade it to android 4.2 .....
Thanks for the update and info. Glad you got it sorted.
No plans to release another ROM for this phone as it is no longer available.
Cheers
marsian720 said:
Thanks for youe reply. mtk droid and mobile uncle didn't work. Finally i found this "THL W1 INVALID IMEI TOOL 4.0.4" and i cewate a new imei file and replace it inti the phone root and now everything is ok.
your rom is smooth. hope to upgrade it to android 4.2 .....
Click to expand...
Click to collapse

[Completed] format all + download , sim not detected , no baseband

OK,
First of all it seems you are my last hope. Yes i know there are similar posts, yes i know that i m making another one (i m sorry for that), yes i belive that i have exhausted options from those posts.
i used sp flash tool with format all + download option (yes i did not had idea that it would cause that much trouble). I have much snail 78P01 phone. As everyone is expecting , no imei, no baseband.
Phone is rooted (of course), things that i tried and they did not worked (becouse file pttycmd1 will be deleted everytime after reboot - maybe someone can explain):
1. mtkdroid tools (dont see band, imei is null) after i try change imei, there in log i can see that pttycmd1 could not be found (which is true, if i use root rexplorer its not anywhere near where it should be).
2. echo 'AT+....1,7,"IMEI..." > /dev/ptt... - yes its there (and mtk droid tool can confirm that , becouse its not giving you error, but thats all...)
3. *#*#3646633#*#* , .... AT+.... i will get error with sending command (yes i tried it as someone suggested with space, )
4. creating your own imei file MP0B_001 and placing it to /data/nvram/md/NVRAM/NVD_IMEI/ (btw my md folder is blank , there is nothing there)
5. downloading and flashing nvram (hope so that is nvram) "All Mtk BPLGU Modem files for Imei change.rar"
6. maybe something that i have forgot
btw:cpu mt 6592
I should be sleeping for like 4 hours now, but i m not, working (googling) on this like 10 hours straight. Any advice would be most welcomed.
Hi,
Thanks for using XDA assist.
I couldn't find any useful information on XDA regarding to your problem. If you haven't already, please create a XDA account and post in the following forum:
Android Q&A, Help & Troubleshooting
Good Luck! - gsstudios

After flashing flashtool whole format No network on wcdma mode in a177 juice

2-11-2014, 06:49 AM |#1
OP Member49 posts Thanks: 20
Hi All,
I'm having this issue for last one month
When ever I select WCDMA option, I lose network. (sometimes I will get n/w for short period)
If i'm using WCDMA/GSM option, I'm able to connect to 3G.
So I hope the antenna is working fine.
I have already formated my phone using SP flash tool and installed latest rom.
I have used the format all which will corrupt the IMEI and installed IMEI back using maui tool .
I have replaced the modem.img file with latest one but the issue persist.
Since my phone is not under warranty. Could anyone please help to to correct the issue.
Solved the issue.. ..
the issue is because when we flash the mobile, its calibration data got corrupted.
EVEN if we reinstall the imei no. the calibration will not be there....
Those who got issue with 3G in "WCDMA" option can use the tool MAUI META to fix it..
Connect the mobile in MAUI tool -> Select the update parameter option .
click the "Change NVRAM DB FILE" and select the "BPLGUInfoCustomAppSrcP_MT6589_S00_MOLY_WR8_W1248_ MD_WG_MP_V6_P18" file .
click on "from file option " and select attached file.
then click "Download to flash."
Please check this link if you got any doubt in using maui tool
Guyz i have copy this solved issue from anthor thread but it is for a210...
Please check this fix & give me for a177 juice..
Attached Files
Need stock a177 parm.zip

Help,how to fix this sp flash tool error? STATUS:DA_HASH_MISMATCH 0xC0070004

Hello to all,
firstly i hope i am opening this thread correctly because i am a junior member here at XDA.
Secondly,i recently bought an CUBOT P20(mt6750t) which so far has been a great device according to me. After installing so many apps i decided to re-flash it,and after doing so there was no sim signal. In the quest of fixing this problem i formatted my device following a thread here at XDA about restoring my device's imei which is in the purchase's original box. At the moment that i formatted my device using "AUTO FORMAT FLASH-FORMAT WHOLE FLASH" in SP FLASH TOOL,i was running AOSP Android 9.0(GSI image) which i flashed using ADB(these actions didn't fix the signal issue related to nvram.bin too),this is where i decided to restore the imei directly.
-The grave mistake : so after no success with trying to fix the sim signal by flashing AOSP Android 9.0 i decided to follow this guide in XDA : Link to tutorial. After following the extreme method, this annoying error started to appear when trying to re-flash in order to perform the 2nd step in the extreme guide: Error : STATUS_DA_HASH_MISMATCH(0xC0070004).
-My phone is still responsive,it is not totally dead.
-I've tried almost everything,i even formatted my laptop because after so many attempts i lost track of my actions.
After re-installing windows 8.1 i retried to flash my phone again,but i encountered the same errors as above(before trying to re-flash my cubot,i installed the drivers,re downloaded the firmware from the official site,etc).
I am mentally devastated now because this is not my device,it is my brother's...I would be really grateful if anybody helps me fix this.
Thanks in advance to all.
cundr said:
Hello to all,
firstly i hope i am opening this thread correctly because i am a junior member here at XDA.
Secondly,i recently bought an CUBOT P20(mt6750t) which so far has been a great device according to me. After installing so many apps i decided to re-flash it,and after doing so there was no sim signal. In the quest of fixing this problem i formatted my device following a thread here at XDA about restoring my device's imei which is in the purchase's original box. At the moment that i formatted my device using "AUTO FORMAT FLASH-FORMAT WHOLE FLASH" in SP FLASH TOOL,i was running AOSP Android 9.0(GSI image) which i flashed using ADB(these actions didn't fix the signal issue related to nvram.bin too),this is where i decided to restore the imei directly.
-The grave mistake : so after no success with trying to fix the sim signal by flashing AOSP Android 9.0 i decided to follow this guide in XDA : Link to tutorial. After following the extreme method, this annoying error started to appear when trying to re-flash in order to perform the 2nd step in the extreme guide: Error : STATUS_DA_HASH_MISMATCH(0xC0070004).
-My phone is still responsive,it is not totally dead.
-I've tried almost everything,i even formatted my laptop because after so many attempts i lost track of my actions.
After re-installing windows 8.1 i retried to flash my phone again,but i encountered the same errors as above(before trying to re-flash my cubot,i installed the drivers,re downloaded the firmware from the official site,etc).
I am mentally devastated now because this is not my device,it is my brother's...I would be really grateful if anybody helps me fix this.
Thanks in advance to all.
Click to expand...
Click to collapse
Here is a list of errors, their meanings and their solutions.
https://forum.hovatek.com/thread-439.html
Sent from my LGL84VL using Tapatalk
I've already tried to fix the error following that guide.
Droidriven said:
Here is a list of errors, their meanings and their solutions.
https://forum.hovatek.com/thread-439.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,thank you very much for trying to help me out.
I've read the meaning of that error and i've tried to follow the instructions on that page too,but the version of sp flash tool stated in the solution throws an error related to my scatter file,it says it's not valid.
I've opened the scatter file to see if it is valid or not,and it seemed fine to me. Also the same scatter works fine with other versions of sp flash tool too.
Also can you tell me what threads are those where i can get this post shared? I thought that posting in QA was the right place.
cundr said:
Hello,thank you very much for trying to help me out.
I've read the meaning of that error and i've tried to follow the instructions on that page too,but the version of sp flash tool stated in the solution throws an error related to my scatter file,it says it's not valid.
I've opened the scatter file to see if it is valid or not,and it seemed fine to me. Also the same scatter works fine with other versions of sp flash tool too.
Also can you tell me what threads are those where i can get this post shared? I thought that posting in QA was the right place.
Click to expand...
Click to collapse
Try different versions
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try different versions
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I've tried at least 5 different versions already
cundr said:
I've tried at least 5 different versions already
Click to expand...
Click to collapse
install driver : WIN7-WIN8 驱动_EXE_v5.1453.03 .rar
uses spflashtool : SP_Flash_Tool_v5.1804_Win
turn off your mobile
lunch splashtool with administration .
set download agent as : MTK_AllInOne_DA.bin
set scatter file from downloaded ROM. (s590ak-p20-fhdp-512g32g-Discrete-O0-bom11_CUBOT_P20_8023C_V14_20181011_user_20181012)
select (firmware upgrade)
click download button.
connect phone to pc.
wait until finish (big green ok sign)
regards.
This is the standard guide bro.
albatron34000 said:
install driver : WIN7-WIN8 驱动_EXE_v5.1453.03 .rar
uses spflashtool : SP_Flash_Tool_v5.1804_Win
turn off your mobile
lunch splashtool with administration .
set download agent as : MTK_AllInOne_DA.bin
set scatter file from downloaded ROM. (s590ak-p20-fhdp-512g32g-Discrete-O0-bom11_CUBOT_P20_8023C_V14_20181011_user_20181012)
select (firmware upgrade)
click download button.
connect phone to pc.
wait until finish (big green ok sign)
regards.
Click to expand...
Click to collapse
Thanks for trying to help me out i appreciate it,but your instructions are standard,i think that my problem is out of league and that's why i don't know what to do.
-I've done this step by step all day long :/
Regards.
cundr said:
Thanks for trying to help me out i appreciate it,but your instructions are standard,i think that my problem is out of league and that's why i don't know what to do.
-I've done this step by step all day long :/
Regards.
Click to expand...
Click to collapse
Factory reset your PC or backup your data then wipe and reinstall Windows, your drivers and SPFlashtool then try again.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Factory reset your PC or backup your data then wipe and reinstall Windows, your drivers and SPFlashtool then try again.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I've done that too as described above when i first posted my problem,i wiped windows and reinstalled it...then i retried from the beggining.
cundr said:
I've done that too as described above when i first posted my problem,i wiped windows and reinstalled it...then i retried from the beggining.
Click to expand...
Click to collapse
Disable antivirus?
Try a different PC with different versions of SPFlashtool?
Factory reset device if you can get to recovery?
Sent from my LGL84VL using Tapatalk
Checksum
Droidriven said:
Disable antivirus?
Try a different PC with different versions of SPFlashtool?
Factory reset device if you can get to recovery?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Have you ever heard that calculating a checksum for the scatter file can fix this?
I'll also try with windows 7 in a couple of minutes.
cundr said:
Have you ever heard that calculating a checksum for the scatter file can fix this?
I'll also try with windows 7 in a couple of minutes.
Click to expand...
Click to collapse
If the file is not complete and doesn't equal the checksum, then yes, this means you need to download the file again and then verify the checksum, if it is a match, Try flashing it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If the file is not complete and doesn't equal the checksum, then yes, this means you need to download the file again and then verify the checksum, if it is a match, Try flashing it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I generated an checksum.ini for the scatter file and now SPFT throws this error : ROM[preloader] checksum mismatch : checksum_config[0x0], checksum_val[0x54e8]
I know i have to edit the checksum.ini file and replace 0x0 with 0x54e8,but the checksum_config is nowhere to be found.
Is this an indication that the preloader is causing all this? And also where can i find the checksum_config?
I also have to mention that this is a fresh download of the phone's firmware.
this is my checksum's content :
[VERSION]
VERSION=V1
[IsEnableChecksum]
CHECKSUM_SWITCH=1
in the scatter file,this is the preloader info :
partition_index: SYS0
partition_name: preloader
file_name: preloader_k50v1_64.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT1_BOOT2
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
is_upgradable: true
empty_boot_needed: false
reserve: 0x00
cundr said:
I generated an checksum.ini for the scatter file and now SPFT throws this error : ROM[preloader] checksum mismatch : checksum_config[0x0], checksum_val[0x54e8]
I know i have to edit the checksum.ini file and replace 0x0 with 0x54e8,but the checksum_config is nowhere to be found.
Is this an indication that the preloader is causing all this? And also where can i find the checksum_config?
I also have to mention that this is a fresh download of the phone's firmware.
this is my checksum's content :
[VERSION]
VERSION=V1
[IsEnableChecksum]
CHECKSUM_SWITCH=1
in the scatter file,this is the preloader info :
partition_index: SYS0
partition_name: preloader
file_name: preloader_k50v1_64.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT1_BOOT2
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
is_upgradable: true
empty_boot_needed: false
reserve: 0x00
Click to expand...
Click to collapse
Edit : I modified the preloader's checksum inside the checksum.ini and set its value to preloader=0x54e8.
After doing so and choosing the scatter inside SPFT for reflash,it throwed another nearly similar error as above but with changed values : ROM[preloader] checksum mismatch : checksum_config[0x0], checksum_val[0xb530]. This is weird.
Please Help
cundr said:
Edit : I modified the preloader's checksum inside the checksum.ini and set its value to preloader=0x54e8.
After doing so and choosing the scatter inside SPFT for reflash,it throwed another nearly similar error as above but with changed values : ROM[preloader] checksum mismatch : checksum_config[0x0], checksum_val[0xb530]. This is weird.
Click to expand...
Click to collapse
Is there anyone that can help me?
In the same boat
keydr said:
Is there anyone that can help me?
Click to expand...
Click to collapse
I'm in the same boat. My phone bricked itself after a bootloop issue, trying to flash the official ROM and I get the ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004) every time, I've tried different versions of SP flash tool, different release versions of the ROM, with the mediatek drivers and with the standard windows 10 ones (andrid recognised in the device manager correctly).
Did you have any luck fixing it?
Thedonqt said:
I'm in the same boat. My phone bricked itself after a bootloop issue, trying to flash the official ROM and I get the ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004) every time, I've tried different versions of SP flash tool, different release versions of the ROM, with the mediatek drivers and with the standard windows 10 ones (andrid recognised in the device manager correctly).
Did you have any luck fixing it?
Click to expand...
Click to collapse
No,i couldn't fix it bro.Calculating a checksum for the scatter file maybe can fix that,it didn't work for me...but it doesn't necessarily mean it won't work for u too.
Tried and tested
keydr said:
No,i couldn't fix it bro.Calculating a checksum for the scatter file maybe can fix that,it didn't work for me...but it doesn't necessarily mean it won't work for u too.
Click to expand...
Click to collapse
I tried that but just got errors from the checksum generator. The ROM is a version that does require checksum so it shouldn't make a difference with that.
Im going to try installing Windows 7 with the VCOM drivers as windows 10 seems to be using its own. My phone gets recognised by the pc when plugged in so I know it's still being detected.
This error code seems to have no fix yet.
This is my plan to ty find a solution &what has already been tried (for the devs to help diagnose and those with the same problems):
1: Try different versions of SPFT - DONE
2: Try different release versions of the ROM - DONE
3: Try installing MTK drivers manually - DONE (windows 10, already has them but tried anyway)
4: Try different USB ports - DONE
5: Try different cables - DONE
6: Try different PC - DONE (were all windows 10 though)
7: Try different button press combinations - DONE
NEXT STEPS:
1: Try Windows 7 which require drivers to be installed manually
2: Disassemble phone to remove battery
3: Try removing drivers in windows 10 using USBDeview to force manual VCOM drives install
4: Try to regenerate Checksum and fix the error displayed when it fails
5: Use specific .BIN as download agent instead of the Mediatek_ALL one (as referenced in the error codes list of meanings)
6: Try installing Linux to test that
7: order a new motherboard
8: Curse the fact that I have come across the only error that seems to have no solution available and no forum with an actual working option (despite them being listed as solved).
I'll keep you updated if I find one. Hopefully a Dev will be able to help with more input.
There seems to be an increase in this error over the last 2/3 months, I'm wondering if that's windows 10 /driver related. There is 1 video on YouTube that solved it in 2018 but that's in hindi and has a link to 2 download files that are no longer available.
Thedonqt said:
I tried that but just got errors from the checksum generator. The ROM is a version that does require checksum so it shouldn't make a difference with that.
Im going to try installing Windows 7 with the VCOM drivers as windows 10 seems to be using its own. My phone gets recognised by the pc when plugged in so I know it's still being detected.
This error code seems to have no fix yet.
This is my plan to ty find a solution &what has already been tried (for the devs to help diagnose and those with the same problems):
1: Try different versions of SPFT - DONE
2: Try different release versions of the ROM - DONE
3: Try installing MTK drivers manually - DONE (windows 10, already has them but tried anyway)
4: Try different USB ports - DONE
5: Try different cables - DONE
6: Try different PC - DONE (were all windows 10 though)
7: Try different button press combinations - DONE
NEXT STEPS:
1: Try Windows 7 which require drivers to be installed manually
2: Disassemble phone to remove battery
3: Try removing drivers in windows 10 using USBDeview to force manual VCOM drives install
4: Try to regenerate Checksum and fix the error displayed when it fails
5: Use specific .BIN as download agent instead of the Mediatek_ALL one (as referenced in the error codes list of meanings)
6: Try installing Linux to test that
7: order a new motherboard
8: Curse the fact that I have come across the only error that seems to have no solution available and no forum with an actual working option (despite them being listed as solved).
I'll keep you updated if I find one. Hopefully a Dev will be able to help with more input.
There seems to be an increase in this error over the last 2/3 months, I'm wondering if that's windows 10 /driver related. There is 1 video on YouTube that solved it in 2018 but that's in hindi and has a link to 2 download files that are no longer available.
Click to expand...
Click to collapse
I've tried absolutely all of the steps that you have described,and nothing worked for me.
As per the checksum,u got to try different versions,because some of the checksum calculators are faulty...and calculating the checksum only for the scatter should do it(if the problem is being cause by the checksum),but u need to try out whatever solution u can imagine because at this point there aren't much bad things that can still happen to your device.
I'll try generating some others then. I've posted in my phones official community group asking for answers as well. It's the official release (2 of them) and 2 unofficial versions, all are having the same issue so I don't think it's related to the files themselves, rather some issue with the way SPFT and windows. The S2 Pro has efuse protection which might be an issue but that is just the bootloader. I cannot believe every forum post online has no actual solution. I'll keep trying and see if something will work.

Categories

Resources