Hello everyone,
N7000, rooted, on stock 4.1.2
In my EFS folder (which is already backed up), I find nv_data.bin, nv_data.bak and nv_core.bak, alongwith their corresponding md5 files.
The only problem with my phone is a dead gps. After much googling and trying out different hardware/software solutions, I am convinced the nv_data file might be the cause.
I compared the nv_data.bin and nv_data.bak files (both 2mb each) on a windows machine and find a lot of differences. Also, the .bak is dated 01/01/2012, while the .bin carries the current date.
So, would it be safe to try out the .bak file by renaming it to nv_data.bin? I can always go back to the original, right?
Also, the 3rd file I mentioned, nv_core.bay (also dated 01/01/2012) is just 1 mb in size. What exactly is its purpose?
Thanks for any advice, I'm very eager to get the gps working and I love my phone!
N7000, rooted, on stock 4.1.2
In my EFS folder (which is already backed up), I find nv_data.bin, nv_data.bak and nv_core.bak, alongwith their corresponding md5 files.
The only problem with my phone is a dead gps. After much googling and trying out different hardware/software solutions, I am convinced the nv_data file might be the cause.
I compared the nv_data.bin and nv_data.bak files (both 2mb each) on a windows machine and find a lot of differences. Also, the .bak is dated 01/01/2012, while the .bin carries the current date.
So, would it be safe to try out the .bak file by renaming it to nv_data.bin? I can always go back to the original, right?
Also, the 3rd file I mentioned, nv_core.bay (also dated 01/01/2012) is just 1 mb in size. What exactly is its purpose?
Thanks for any advice, I'm very eager to get the gps working and I love my phone!

0 commentaires:
Enregistrer un commentaire