hey!
i used this root method (http://www.boerse.bz/boerse/softwar...mini-x10-mini-pro-update-auf-2-1-deutsch.html)
im from germany and i didnt get the update for 2.1 till now. thats why i used this method. now i want to restore to system defaults and get the update the normal way. how can i do this? (cause i got a problem with backup & restore: it does not restore my contacts )
any solutions?
thanks!
jackiie said:
hey!
i used this root method (http://www.boerse.bz/boerse/softwar...mini-x10-mini-pro-update-auf-2-1-deutsch.html)
im from germany and i didnt get the update for 2.1 till now. thats why i used this method. now i want to restore to system defaults and get the update the normal way. how can i do this? (cause i got a problem with backup & restore: it does not restore my contacts )
any solutions?
thanks!
Click to expand...
Click to collapse
Just repeat the process but put your original product code back in. (the SI is printed on the label under your battery, using that you can then get the CDA code from the first post in this thread: http://forum.xda-developers.com/showthread.php?t=824711
)
Edit: if you are with E+ the SI number under your battery should be 1232-2951 or similar and the cda is 1234-4754. So follow the method as you did before but put the number 1234-4754 instead of 1234-8465.
great. thank you i will try this. right now im trying it with the original numer (1232-2950) if that doesnt work correct i will try the number you told me to use.
but why do i have to use this number? (the CDA number)
and do u have any ideas why i cant restore contats, although i saved them ?
Related
I need to make my X10 mini pro like it was when i bought it, software wise for service purposes. Has anybody tried to do so ? I have Root, xRecovery, JIT, app2sd, Generic 2.0.2.A.0.24[rooted](from this forum) and Android 2.3 Ginger Bread Theme Nexus S edition theme. If anybody found a guide or could give me step by step pointers I would be very appreciative. THX in advance.
You might need to swap your build.prop for a Romanian one? (possibly ask on here and someone might be able to give you a copy if you didn't back up yours before you flashed the rooted firmware) or edit yours with the right details then..
Backup your settings, contacts, txt's etc with Backup and Restore. and Flash the phone using SEUS (Sony Ericsson update service) (if it says you are already up to date then use the recovery option) you can download SEUS from here if you don't have it.
hope that helps.
Alexander1988 said:
I need to make my X10 mini pro like it was when i bought it, software wise for service purposes. Has anybody tried to do so ? I have Root, xRecovery, JIT, app2sd, Generic 2.0.2.A.0.24[rooted](from this forum) and Android 2.3 Ginger Bread Theme Nexus S edition theme. If anybody found a guide or could give me step by step pointers I would be very appreciative. THX in advance.
Click to expand...
Click to collapse
Yeap, just do what kiwiBratwurst said... You may want to format your sdcard too to get rid of the ext4 partition...
Sent from my E10i using XDA App
So all I have to do is update/recover using SEUS and that's it ! No traces of JIT or custom prerooted Generic ROM will be left ? About build.prop, why do I have to modify it and how will I know what to modify ? Sorry about all these questions but i'm a newb and my touchscreen is making a buzzing noise whenever I touch it so you understand my concern and why I want to ship it into service. Can't figure out if the problem is hardware or software related, this started happening after .504 SEUS update.
Well you could forget the Build.prop edit and just restore/repair/update (whatever its called) with SEUS (but then your phone will say its from Norway, I think you will have the Norwegian Firmware if you flashed the rooted .24 firmware from here) (you could just try that tho and pretend you didn't know any better)
if you want to try to edit your build.prop (backup the old one first in case you stuff it up!!) I am not sure about the Pro (I have a mini) but pull your battery out and look under it, there should be a sticker with info about your phone.. it has on there an 8 digit number 1234-1234 obviously not that but something with 8 numbers.. this is your kit number, if you are able to modify your build.prop and change the kit number in it to your number then it may work.. (I think from memory the number appears 3 times in the build.prop file. )
There is also a place where it says WORLD Generic or Custom.. I don't know what this should be on Romanian Build.prop.. (it's too late now but.. its always a good idea to backup your system files before playing with flashing that way you have all the original files if you need to revert)
just another thought... if you have updated the phone in the past with SEUS (with the correct firmware) 1.6 or 2.1 whatever.. you could look in the SEUS folder on your computer (program files/sony ericsson/Update service/db) and copy the 2 largest files out of there and use the Converter tool.. Here and you can make your own Original Romanian Firmware to flash with Bin4rys flashtool. (you might need to flick through the post to find x10mini/pro relevant file names.. etc... ) But handy to have because then any time you need to revert back to factory you can just flash the Romanian firmware with Flashtool
Man.. sorry to prattle on.. hope it helps in some way.
Kiwi
I believe the new SEUS doesn´t have repair option anymore.
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 .
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/gala...ackup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you ! :angel:
scratcher1337123 said:
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/gala...ackup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you ! :angel:
Click to expand...
Click to collapse
It as everything to do with the android version.On 4.3 your efs is v2 when you downgrade to below that your phone can't read anything because it is efs v1. Unless your backup was taken while you where on efsv1 then there is no way of restoring it you need to be on 4.3 and above. Also when restoring efs that are backed up via a root explorer you have to make sure every permission is correct when you paste the files back. Hope that helps.[emoji1]
will try it the next days, currently i am pretty busy, thank you, i will let you know how it went... didn't knew efs has versions
Thank you !
P.S. Yes i have backed up the EFS from 4.3, now i was trying it to repair it on 4.1.1, I will try to restore it on 4.3 again ! Hopefully it will work
scratcher1337123 said:
will try it the next days, currently i am pretty busy, thank you, i will let you know how it went... didn't knew efs has versions
Thank you !
P.S. Yes i have backed up the EFS from 4.3, now i was trying it to repair it on 4.1.1, I will try to restore it on 4.3 again ! Hopefully it will work
Click to expand...
Click to collapse
I have the same problema, but I dont have the backup , can you delivery the rom 4.1.1..
thanks ...
If you didn't backup the efs folder then take it to a repair centre, there is no other way to fix it.
Make sure it works on 4.3 before you pay them.
i flashed a friends CWM backup file on my s3 and i lost imei and network mine was 4.1.2 the backup was 4.3 now i reflashed the phone with a 4.3 firmware from sammobiles. i am getting the signal bars but the phone woudnt register on any network and when i take service mode (*#0011#) ath the bottom it says IMEI CERTI : FAIL, what should i do please help me
If flashing 4.3 firmware and factory reset didn't restore imei then take it to a repair centre.
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