Hello,
I hope someone still using this old mobile phones and can help me with my problem.
I have a lumia 800 and going crazy because i´m not able to restore a backup with WP7EasyBackup.
The backup was created also with WP7EasyBackup 3 days ago, then I have installed a custom rom and want to recover my old data but only got the error code 801812E0 in the WP7EasyBackup log.
I thought my Backup was not compatible to the backup version, so I flashed the stock rom orignal firmware to my Lumia 800. Unfortunately I still got the same error code 801812E0 if I try to recover my device.
Could anyone help me with this problem?
Update 30.03.2018
After flashing several firmwares from lumiafirmware.com to my device and trying to restore my backup I still get the same error code with 801812E0.
I know my device is very old but I hope here are still some experts who can help me with this problem.
I also spent some hours by searching for some solutions for the error code 801812E0 in WP7EasyBackup but I just found some answers where they used different firmware versions for backup and restore (e.g. backup from firmware 1600.2479.7740.11451 trying to restore to 1750.0805.8773.12220). In my WP7EasyBackup log file I can see that the backup was made from the firmware 1600.2479.7740.11451, so I flashed this firmware to my device but the restore from my backup is still not working. I used a different product code for the firmware because the firmware 1600.2479.7740.11451 is not available for my product code "059M0C7". If there is anyone who has the firmware 1600.2479.7740.11451 for the product code 059M0C7 (T-mobile brand) available it would be very nice to share this with me. But I think this not my problem and I´m really going crazy on that
So if someone has a hint for me to solve this problem please let me know.
Many many thanks in advance.
Related
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
amita74 said:
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
Click to expand...
Click to collapse
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
New inputs
GamingDj said:
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
Click to expand...
Click to collapse
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
amita74 said:
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
Click to expand...
Click to collapse
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
status update
GamingDj said:
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
Click to expand...
Click to collapse
Hi,
Just want to update that its been about a week that the phone works without me doing anything, therefore not proceeding with the recovery process you suggested.
I will update if the problem will be back.
Thanks.
Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
hawjz said:
Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
Click to expand...
Click to collapse
It's better to instal CWM on your phone adn then flash any Stock Custom Roms. May be then your prob gets solved.
hawjz said:
Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
Click to expand...
Click to collapse
Please read the faqs and guides first.
EFS
/IMEI is very important .
Ok so recently I was successful to root my SM-J110F (Vodafone, AUS).
I had found a forum on xda for a custom ROM for SM-J110M.
(link) - https://forum.xda-developers.com/android/software/rom-cleanertlite-os-j1-ace-t3585567
I flashed the ROM using TWRP and it worked.
However sadly, the ROM isn't really that great. The IMEI shows it's "null / null"
so I cannot fix it. The forum hasn't been active so I cannot get a response from the person who made it.
I was wondering if there is any way to fix it and I know I have a custom ROM for SM-J110M but I just want to know if it can be fixed.
Also, since I installed the ROM, the phone says it is a SM-J110M. I was wondering if I could flash in a stock SM-J110M ROM from SamMobile. I tried flashing it using ODIN, but it didn't work.
I really need your help, because I want to stay in 5.1.1. otherwise I'm just going to have to go back to 4.4.4. which is really old.
Problem can be solved and to fix that problem you need manualy to write IMEI and Serial number .
To write IMEI , and S/N you can use Octoplus but Changing IMEI or S/N number which doesn't belong to you is Ilegal so do at your own.
Here is steps for you to follow.
https://www.youtube.com/watch?v=F5k-jKCruv8
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
No one here to reply!!!! where are the huawei developers or experts kindly help
hazemnada said:
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
Click to expand...
Click to collapse
R u on stock recovery...
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
why no one here replies where r the experts here
hazemnada said:
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
Click to expand...
Click to collapse
Which firmware number you tried via dload??
hassanjavaid8181 said:
Which firmware number you tried via dload??
Click to expand...
Click to collapse
first i restored the backup in the Repository that mentioned my phone model
GR5 KII-L21
GR5+TWRP+backup_KII-L21C185B130.rar Thanks to Under World
and it changed everything then
Hello there,
Recently I was on one of the custom ROMS and I wanted to go back to stock. The stock firmware I downloaded was for G965F Indian region but somehow it still erased my IMEI.(all zeros) I tried few documentations and guides here on XDA and messed up my EFS as well. KG STATE in boot-loader mode has gone to 'prenormal' so I can't install twrp and phone is also not booting anymore as EFS partition is corrupted. I tried flashing many stock firmware's but none of them got flashed.
Does anyone has idea how to fix my phone. All your help will be much appreciated. I know combination file could fix this but right now I'm on android 10 and there's no combination file for that released yet. Can anyone give me EFS backup? or does anyone have any solution? Please help !
fyi: "SM-G9965F_G965FXXSBETH2_Q(Android10)_INS_Factory ROM(5 File)_20200915" is the only firmware that is getting flashed with odin. I got it from Samfirm. But phone doesn't boot because EFS partition is corrupted.
Thanks,
Andromuks
Combination files are out ?
andromuks said:
Hello there,
Recently I was on one of the custom ROMS and I wanted to go back to stock. The stock firmware I downloaded was for G965F Indian region but somehow it still erased my IMEI.(all zeros) I tried few documentations and guides here on XDA and messed up my EFS as well. KG STATE in boot-loader mode has gone to 'prenormal' so I can't install twrp and phone is also not booting anymore as EFS partition is corrupted. I tried flashing many stock firmware's but none of them got flashed.
Thanks,
Andromuks
Click to expand...
Click to collapse
Hey guys, I'm recently seeing these files floating 'https://support.halabtech.com/index.php?a=downloads&b=file&id=332402' . Could this help for those memebers who have recently updated to Android 10 and has broken their IMEI?