Related
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
If your file name has spaces in it, it may cause the MD5 mismatch error.
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I hate windows....it bites! I mean ":cyclops:bytes"
I did it all on my phone using a file manager. So if I change the name to something without spaces it should be fine?
Sent from my SAMSUNG-SGH-I717 using xda premium
I had the same problem the other day - a known good backup wouldn't install. After much searching and asking I ended up considering the backup scrapped and moved on. Then the next day I tried again and it worked fine.
Do you have another backup?
Did you change the name of the backup?
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I have had this issue since I like to store my older nandroids on my Win 7 PC. Do you know of any way to identify or remove the extra bytes? It would have to be after the file is transferred back to the Note I imagine.
Your should try renaming your file.
tmb993 said:
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Hi
if you did your backup using CWM and you renamed it after doing the backup I suggest you use "." instead of spaces; example if you rename it "CM9 ROM" try "CM9.ROM" or if you backup your stock rom and rename it "stock android rom" tried "stock.android.rom"
Cheers from DFW
Ok well I did that and I thought it would fix the problem but now I keep getting this error message in my recovery. Got it when I tried to reflash the recovery that I properly named and then again when I tried to flash on PA's 4.1 CM10. What in the heck does this mean??
Sent from my SAMSUNG-SGH-I717 using xda premium
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
lactardjosh said:
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
Click to expand...
Click to collapse
Aw man. Well I just had the newest version but reverted back to 5.5.0.4 because it game me a lot of issues. Strange but I also got the same error when I tried to restore from that one backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I could be wrong, I don't know for sure.
But, you could see what recovery other people are using in the ROM thread.
I copy my backups from SD to computer and back and have run into this issue. I followed the instructions in this link, http://forum.xda-developers.com/showthread.php?t=714114 and it fixed the MD5 mismatch issue. I guess these commands "clean" the backup of whatever windows does to it when copied. Worked like a charm! Also, I always change my backup names and am sure not to leave spaces. This works even if the name is not what CWR generated.
Bigjoe, can you please add this to your Super Everything page -- probably in the CWM section? Thank you.
http://forum.xda-developers.com/showthread.php?t=714114
Hi, I did a backup using cwm before flashing jelly bean onto my Galaxy S3. Now I'm tryin to restore my backup but its showing md5 mismatch. These are the files I have: boot.img, data.ext4.tar, recovery.img and system.ext4.tar. I changed the name of the backup file but left no spaces in between.. Can anyone help please.
Thanks
jpx2008 said:
Hi, I did a backup using cwm before flashing jelly bean onto my Galaxy S3. Now I'm tryin to restore my backup but its showing md5 mismatch. These are the files I have: boot.img, data.ext4.tar, recovery.img and system.ext4.tar. I changed the name of the backup file but left no spaces in between.. Can anyone help please.
Thanks
Click to expand...
Click to collapse
Anyone please...Easiest solution
Which file is corrupted? If the data files is intact, you could try manually downloading the rom you had installed before. After flashing it, do a selective restore of the data partition. That should get you back to your old system.
Sent from my GT-I9300
If you rename the back up through a file manager, changes its name to "backup" i had a similar problem when trying to restore, i changed the name to s"tock" and it reverted fine without any errors
Try this thread. Helped me once when I needed it. I used the terminal emulator method to bypass the md5 check.
Sent from my GT-I9300 using xda premium
First flash stock rom with Odin, ther root the phone and restore.
sxi200 said:
Try this thread. Helped me once when I needed it. I used the terminal emulator method to bypass the md5 check.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can you teach us on how to use terminal emulator and bypass md5 check? having the same problem now
Can't believe it worked
vengeance1990 said:
If you rename the back up through a file manager, changes its name to "backup" i had a similar problem when trying to restore, i changed the name to s"tock" and it reverted fine without any errors
Click to expand...
Click to collapse
Thanks man, it actually worked.
I've been searching for information about Mobile Odin and CWM, and I remember seeing a post (I think from Chainfire himself), which contained the phrase "MO does not support backups (yet)" - I've searched & searched, but I can't find the post again
Does anyone else remember seeing this, or have any idea when Chainfire is likely to include this capability ?
TomHall said:
I've been searching for information about Mobile Odin and CWM, and I remember seeing a post (I think from Chainfire himself), which contained the phrase "MO does not support backups (yet)" - I've searched & searched, but I can't find the post again
Does anyone else remember seeing this, or have any idea when Chainfire is likely to include this capability ?
Click to expand...
Click to collapse
NO DIRECT ANSWER BUT:
U want to make a Backup, right?
So why u don't use CMW?
If u want to do this while phone is running..
Why u don't use "Online Nandroid Backup"?
CHEERS
Hannibal226 said:
NO DIRECT ANSWER BUT:
U want to make a Backup, right?
So why u don't use CMW?
If u want to do this while phone is running..
Why u don't use "Online Nandroid Backup"?
CHEERS
Click to expand...
Click to collapse
Thanks, but I'm running the leaked JB XXLSJ, with PhilZ Touch 3, so I've already got CWM capability
I just thought it would be "nice" if Chainfire was close to including a backup facility in Mobile Odin, also, I didn't want to rile Chainfire by PM'ing him
ps. I did try Online Nandroid Backup, but I couldn't get round the error "mkyaffs2image not found "
TomHall said:
Thanks, but I'm running the leaked JB XXLSJ, with PhilZ Touch 3, so I've already got CWM capability
I just thought it would be "nice" if Chainfire was close to including a backup facility in Mobile Odin, also, I didn't want to rile Chainfire by PM'ing him
ps. I did try Online Nandroid Backup, but I couldn't get round the error "mkyaffs2image not found "
Click to expand...
Click to collapse
OK.
PS: Did u go first time in settings from app and do the "request device patch"?
CHEERS
Sent from my GT-I9100 using xda premium
Hannibal226 said:
OK.
PS: Did u go first time in settings from app and do the "request device patch"?
CHEERS
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, I did apply the patch, but I've just re-downloaded & installed Online Nandroid Backup, re-patched it, and run another backup, and it completed Ok with no error message this time - I guess it's probably a newer version since I tried it before.
However I am now concerned about my backup sizes ...
OND is reporting that my OND backup is 1.25Gig, but my My Philz/CWM backups are all only about 16-17Mb ?
(see OND screenshot)
TomHall said:
Yes, I did apply the patch, but I've just re-downloaded & installed Online Nandroid Backup, re-patched it, and run another backup, and it completed Ok with no error message this time - I guess it's probably a newer version since I tried it before.
However I am now concerned about my backup sizes ...
OND is reporting that my OND backup is 1.25Gig, but my My Philz/CWM backups are all only about 16-17Mb ?
(see OND screenshot)
Click to expand...
Click to collapse
U can be sure that the 16-17MB backup isn't ok...
So use the OND backup with 1,25GB
CHEERS
Hannibal226 said:
U can be sure that the 16-17MB backup isn't ok...
So use the OND backup with 1,25GB
CHEERS
Click to expand...
Click to collapse
The main backup file is kept in a different place since cwm updated, You can still use cwm to backup and restore safely, and if you like it old school, changing the backup format will do it.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
king_below_my_lord said:
The main backup file is kept in a different place since cwm updated, You can still use cwm to backup and restore safely, and if you like it old school, changing the backup format will do it.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Click to expand...
Click to collapse
I emailed OND's developer, and he confirmed that it's because the CWM v6.x backup data files are now in the clockworkmod blobs sub-folder
I will try changing the backup format though
TomHall said:
I emailed OND's developer, and he confirmed that it's because the CWM v6.x backup data files are now in the clockworkmod blobs sub-folder
I will try changing the backup format though
Click to expand...
Click to collapse
I deleted all my backups using the CWM and OND menus, but there were still loads of files left, so I manually emptied the Clockworkmod and blobs folders, changed the CWM backup to .tar format, and ran a CWM backup followed by a OND backup
CWM .tar backup size is now 1.6Gig, OND backup is now 1.27Gig
TomHall said:
I deleted all my backups using the CWM and OND menus, but there were still loads of files left, so I manually emptied the Clockworkmod and blobs folders, changed the CWM backup to .tar format, and ran a CWM backup followed by a OND backup
CWM .tar backup size is now 1.6Gig, OND backup is now 1.27Gig
Click to expand...
Click to collapse
Maybe it's because of the compression type(onandroid must be using a higher compression method), anyway CWM is definitely more secure.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Hello
i am trying to restore a backup i made this morning prior to trying to upgrade to jellyban
i got into trouble somehow and the phone became a soft brick,
i had to start again via odin , fresh install
i have re rooted my phone ( prior i have a dual boot , which has returned )
via cwm recovery i can see my backup which is located at
/emmc/clockworkmod/backup/2012-12-13.07.36.04/
but what ever i try and do ( wipe data , restore to either rom, advance restore from int sd card) etc
, i get "MD5 mismatch"
its driving me mad, please can anyone help
skycharger said:
Hello
i am trying to restore a backup i made this morning prior to trying to upgrade to jellyban
i got into trouble somehow and the phone became a soft brick,
i had to start again via odin , fresh install
i have re rooted my phone ( prior i have a dual boot , which has returned )
via cwm recovery i can see my backup which is located at
/emmc/clockworkmod/backup/2012-12-13.07.36.04/
but what ever i try and do ( wipe data , restore to either rom, advance restore from int sd card) etc
, i get "MD5 mismatch"
its driving me mad, please can anyone help
Click to expand...
Click to collapse
update, i was running neatrom lite v 3.xx before, so i tried an experiment, i installed
http://forum.xda-developers.com/showthread.php?t=1569686 neatRom Lite v4
this installed ok, when "android updating" , after the initial install, i noticed that it was updating 156 apps ( the amount of apps i had originally)
however when you start you can only see 34 apps, which i guess must be the stock amount of apps with this rom
still cant restore anything , still can see that backup i did this morning, still get the same error message when i try and do any kind of restore ie MD5 mismatch"
is there anyway i can recover:
my contacts, those apps, my messages,
ie just the data and, have the apps ( that were just updated, but not visible) available?
thanks !
skycharger said:
Hello
i am trying to restore a backup i made this morning prior to trying to upgrade to jellyban
i got into trouble somehow and the phone became a soft brick,
i had to start again via odin , fresh install
i have re rooted my phone ( prior i have a dual boot , which has returned )
via cwm recovery i can see my backup which is located at
/emmc/clockworkmod/backup/2012-12-13.07.36.04/
but what ever i try and do ( wipe data , restore to either rom, advance restore from int sd card) etc
, i get "MD5 mismatch"
its driving me mad, please can anyone help
Click to expand...
Click to collapse
this happens so for various reasons ma8
like a corrupt backup, backup folder name changed, kernel mismatch etc
u can use 'Root toolbox' app to restore ur MD5 and then try cwm restore
also visit the link below for some more info on the same (MD5 mismatch)
Sun90 said:
this happens so for various reasons ma8
like a corrupt backup, backup folder name changed, kernel mismatch etc
u can use 'Root toolbox' app to restore ur MD5 and then try cwm restore
also visit the link below for some more info on the same (MD5 mismatch)
Click to expand...
Click to collapse
sorry, but what is my md5? and how am i going to restore it?
ok purchased root toolbox pro version and rom manager Pro
using ROM Manage Pro it says, it says .." this doesnt appear to a valid backup, md5 is missing"
skycharger said:
sorry, but what is my md5? and how am i going to restore it?
ok purchased root toolbox pro version and rom manager Pro
using ROM Manage Pro it says, it says .." this doesnt appear to a valid backup, md5 is missing"
Click to expand...
Click to collapse
but what/where is my "md5"? and how am i going to restore it? and to where?
http://dw.com.com/redir?edId=3&siteId=4&oId=3000-2248_4-10050856&ontId=2248_4&spi=7e4b9ddb94a23ee27dd624960a67d41a&lop=link&tag=tdw_dltext<ype=dl_dlnow&pid=10636571&mfgId=74841&merId=74841&pguid=UMpkXwoOYJIAAFJ6i0EAAAE6&ttag=dl_dldirect&destUrl=http%3A%2F%2Fdownload.cnet.com%2F3001-2248_4-10050856.html%3Fspi%3D7e4b9ddb94a23ee27dd624960a67d41a%26dlm%3D0 <--- link so make new MD5 for it
ok, thanks ... just gone there & d/l that , extracted it , do i need to load it to the phone? and then run it from the phone?
skycharger said:
ok, thanks ... just gone there & d/l that , extracted it , do i need to load it to the phone? and then run it from the phone?
Click to expand...
Click to collapse
Just flash the same kernel you used to to make the backup, then restore your backup with that.
Btw, You didnt have a "soft brick" there is no such thing. Its a made up phrase by n00bs when they dont know what they have done and cant get system to boot so need to label it in some way. A device is either "bricked" or it isnt.
TheATHEiST said:
Just flash the same kernel you used to to make the backup, then restore your backup with that.
Btw, You didnt have a "soft brick" there is no such thing. Its a made up phrase by n00bs when they dont know what they have done and cant get system to boot so need to label it in some way. A device is either "bricked" or it isnt.
Click to expand...
Click to collapse
Yes i take your point about the "soft brick" , same as "she is a little bit pregnant" i guess
Linkhunter sent me a link to re-create my md5 , it's an EXE program, so needs to be run under Windows, im just just not sure how im supposed to get it to make a new md5 for my back up
can anyone give step by step instructions i can follow
re "Just flash the same kernel you used to to make the backup, then restore your backup with that.", are you saying because i made the backup with kernal A ( ICS), then tried to migrate to kernal B" ( Jellyban) , that it was the migration mis-match that is causing it not to restore,. Why i ask, is because i made another backup for some reason last September, and i tried to restore that one and it looked as if it would restore, i didnt get the (using ROM Manage Pro) message saying,." this doesnt appear to a valid backup, md5 is missing" .i stopped at that point, i still would rather get my latest backup (the data and apps restored) if possible
skycharger said:
Yes i take your point about the "soft brick" , same as "she is a little bit pregnant" i guess
Click to expand...
Click to collapse
lol you got it
BTW there is a way to recalc md5sum via terminal emulator, just google it and you'll be able to restore. Happened to me too and solved this way
Sent from my GT-I9100G using xda app-developers app
If you ever run into an md5 mismatch error when trying to restore a backup, you could try the following ^^
Using Terminal Emulator: (mind spaces)
# cd /sdcard/clockworkmod/backup/backup-name-goes-here
# rm nandroid.md5
# md5sum *img > nandroid.md5
Do usual wipes then restore the full nandroid ^^
NB, if it works (it has for me in past) it'll prob only work once for a particular nandroid...
so, after (if...) it works - just del old nandroid & make a new one
Sorry Bout the noob question.. but can we do this using different recovery backups? Like if you wanna restore a backup from twrp in a cwm recovery ?
Sent from my HTC Explorer A310e using xda premium
akshat.shenoy said:
Sorry Bout the noob question.. but can we do this using different recovery backups? Like if you wanna restore a backup from twrp in a cwm recovery ?
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
dunno ^^ might work... someone with more knowledge than myself told me I coud just move a nandroid to the correct folder i.e. the one twrp uses & it would be all good... never tested it myself though
I know many people have already asked about their IMEI disappearing and i managed to restore my backup using Galaxy Toolbox before but i tried to restore my IMEI again and it didn't work. I then decided to revert back to stock via Odin and i successfully went back to a stock ROM but my IMEI is still missing and i am getting quite worried now. Have i lost it for good? I obviously lost it after flashing the data2sd-ext script by Amarullz if this helps towards helping me?!
N8tR1X said:
I know many people have already asked about their IMEI disappearing and i managed to restore my a backup using Galaxy Toolbox before but i tried to restore my IMEI again and it didn't work. I then decided to revert back to stock via Odin and i successfully went back to a stock rom but my IMEI is still missing and i am getting quite worried now. Have i lost it for good? I obviously lost it after flashing the data2sd-ext script by Amarullz if this helps towards helping me?!
Click to expand...
Click to collapse
It happens to ne all the time
Wait for media scanning to complete And wait for a minute and then restore and reboot
iamareebjamal said:
It happens to ne all the time
Wait for media scanning to complete And wait for a minute and then restore and reboot
Click to expand...
Click to collapse
I managed to finally restore my IMEI. It was very confusing but basically i had to delete the old directory/folder i had on my ext-SD and then download Galaxy Toolbox. Then i opened up the app and went to the restore option, it says it could not find the directory and tells you to make one with the backup i previously took beforehand when i had a working IMEI. So i connected my device, transferred the file into a new directory named 'GalaxyToolbox' and disconnected the device. Finally i loaded the app and restored my backup, rebooted and hooraaay my IMEI was back!! I can't tell you how relieved i am! I MUST donate to Doky for making such an amazing app! I think i'm going to leave the data2SD-ext script for now and maybe try other methods if there is any?
Oh and i love your S3 Ripple Mod by the way, i had to go back to Simplicity V5 and flash it again! Lol
galaxcy toolbox
N8tR1X said:
I managed to finally restore my IMEI. It was very confusing but basically i had to delete the old directory/folder i had on my ext-SD and then download Galaxy Toolbox. Then i opened up the app and went to the restore option, it says it could not find the directory and tells you to make one with the backup i previously took beforehand when i had a working IMEI. So i connected my device, transferred the file into a new directory named 'GalaxyToolbox' and disconnected the device. Finally i loaded the app and restored my backup, rebooted and hooraaay my IMEI was back!! I can't tell you how relieved i am! I MUST donate to Doky for making such an amazing app! I think i'm going to leave the data2SD-ext script for now and maybe try other methods if there is any?
Oh and i love your S3 Ripple Mod by the way, i had to go back to Simplicity V5 and flash it again! Lol
Click to expand...
Click to collapse
galaxcy toolbox does not restore imei after flashing with jellybean rom, beware.
gordon52 said:
galaxcy toolbox does not restore imei after flashing with jellybean rom, beware.
Click to expand...
Click to collapse
is it so..?
then we don't have to worry..
cause we don't have jellybean..we don't even have ics ..
so chill
Sent from my GT-S5830i using xda app-developers app
Whenever I lost IEMI, reverting back to stock firmware (Odin restore) sorted it. Strange it doesn't repair yours...
N8tR1X said:
I managed to finally restore my IMEI. It was very confusing but basically i had to delete the old directory/folder i had on my ext-SD and then download Galaxy Toolbox. Then i opened up the app and went to the restore option, it says it could not find the directory and tells you to make one with the backup i previously took beforehand when i had a working IMEI. So i connected my device, transferred the file into a new directory named 'GalaxyToolbox' and disconnected the device. Finally i loaded the app and restored my backup, rebooted and hooraaay my IMEI was back!! I can't tell you how relieved i am! I MUST donate to Doky for making such an amazing app! I think i'm going to leave the data2SD-ext script for now and maybe try other methods if there is any?
Oh and i love your S3 Ripple Mod by the way, i had to go back to Simplicity V5 and flash it again! Lol
Click to expand...
Click to collapse
what is the name of the "old directory/folder" and where do I find it? I really need to resolve this problem
I probably didn't explain my solution very well after reading back through my post.
It has been a long time since I faced this issue but I'll try and explain what I did to resolve the problem...
1) Connect your device to your computer and transfer the GalaxyToolbox folder (should contain 2 files inside) to your computer.
2) Delete the GalaxyToolbox folder on your device once you have transferred it to your computer.
3) Disconnect your device and open File Manager/Explorer app on your device.
4) Create a new folder titled 'GalaxyToolbox' with no spaces on the root of your SD Card.
5) Connect your device to your computer again and transfer only the file titled 'EFSpart.img.SAVE' to the new GalaxyToolbox folder you created on the root of your SD Card.
6) Disconnect your device and let media scanner finish. Open the Galaxy Toolbox app and select restore EFS partition. It will tell you it has found a backup and ask if you wish to restore it, click yes.
7) Close the Galaxy Toolbox app and restart your device.
Type *#06# into your dialer and you should see a small box pop-up with your IMEI number letting you know the restore was successful.
I know it seems strange that this method fixed it for me but I think the app itself creates a 'temporary' backup which is the backup of your currently missing IMEI number and when you try and restore it keeps restoring the EFS backup which has no IMEI... So starting from fresh and moving the original backup I made back into the GalaxyToolbox folder seemed to have fixed it for me.
Sent from my GT-S5830i using xda app-developers app
Hi there,
Rather make a Guide on fixing IMEI, instead of posting here...It would be helpful to many guys.. :beer:
Thank you,
P.007
I will make a guide if someone can follow the steps to restore their IMEI like I did then I'll know it works 100% :thumbup:
Sent from my GT-S5830i using xda app-developers app
Other Way , (1) Backup Ur Data Through CMW And (2) Flash Ur Stock Rom. U Will Get Ur Imei Back Then (3) Flash Ur Current Rom (Ex : Jellyblast ) Note : If Ur Not In Custom Rom Ignore This Step (3). And (4) Go To CMW And (5) Click Advance Restore And Restore Ur Data,Cache,And Other All Except System. Ur Imei Is Back.
Hit Thanks If I Helped U.
Sent from my GT-S5830 using xda premium
Bullit Lee said:
Other Way , (1) Backup Ur Data Through CMW And (2) Flash Ur Stock Rom. U Will Get Ur Imei Back Then (3) Flash Ur Current Rom (Ex : Jellyblast ) Note : If Ur Not In Custom Rom Ignore This Step (3). And (4) Go To CMW And (5) Click Advance Restore And Restore Ur Data,Cache,And Other All Except System. Ur Imei Is Back.
Hit Thanks If I Helped U.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
What if someone doesnt want data to be restored. Of course it was an option when we had no way of backing up IMEI
But now (for over a year), we can work on IMEI independently via Galaxy Tools, then what is the need of this method handling data and it also can cause many FC's
Yeh Bro. Its Just. If They Dont Want Data To Be Restore Just Flash De Stock Firmware. Ur Rite.
Bullit Lee said:
Other Way , (1) Backup Ur Data Through CMW And (2) Flash Ur Stock Rom. U Will Get Ur Imei Back Then (3) Flash Ur Current Rom (Ex : Jellyblast ) Note : If Ur Not In Custom Rom Ignore This Step (3). And (4) Go To CMW And (5) Click Advance Restore And Restore Ur Data,Cache,And Other All Except System. Ur Imei Is Back.
Hit Thanks If I Helped U.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Wrong! I tried to restore my IMEI by reverting back to Stock ROM via Odin and guess what? It didn't work, my IMEI number was still missing! So the method you suggested won't work either. Like Areeb said, Galaxy Toolbox is your only friend here...
Sent from my GT-S5830i using xda app-developers app
N8tR1X said:
Wrong! I tried to restore my IMEI by reverting back to Stock ROM via Odin and guess what? It didn't work, my IMEI number was still missing! So the method you suggested won't work either. Like Areeb said, Galaxy Toolbox is your only friend here...
Click to expand...
Click to collapse
Galaxy Toolbox is not being my friend. I've lost my IMEI and I can't bring it back whatsoever.
Tried flashing stock but the efs folder is always empty. So the 9-step guide doesn't work for me (Or am I missing something?)
Please help guys. I don't have previous efs folder backups. But I do have nandroid(CWM) backups of the rom and restoring them doesn't help.
lmali92 said:
Galaxy Toolbox is not being my friend. I've lost my IMEI and I can't bring it back whatsoever.
Tried flashing stock but the efs folder is always empty. So the 9-step guide doesn't work for me (Or am I missing something?)
Please help guys. I don't have previous efs folder backups. But I do have nandroid(CWM) backups of the rom and restoring them doesn't help.
Click to expand...
Click to collapse
EFS its a partition with raw data, not contain files... so you dont need to see files inside te "folder"... to see if you have your IMEI you have to dial *#06#
Manizuca said:
EFS its a partition with raw data, not contain files... so you dont need to see files inside te "folder"... to see if you have your IMEI you have to dial *#06#
Click to expand...
Click to collapse
Err no...I was following the 9-step process posted by OP to restore my IMEI and I can't find those nv_data and all those files(required in 9-step process)
I've already checked *#06# and it shows an empty box
lmali92 said:
Err no...I was following the 9-step process posted by OP to restore my IMEI and I can't find those nv_data and all those files(required in 9-step process)
I've already checked *#06# and it shows an empty box
Click to expand...
Click to collapse
As I told you... in this model the efs partition has no files, its just data, does not have the "nv_data" file... idk what guide are you following, but its not for our phone... try doing this http://forum.xda-developers.com/showthread.php?t=1968360 and pls read the replys... maybe you can found something that helps you
Manizuca said:
As I told you... in this model the efs partition has no files, its just data, does not have the "nv_data" file... idk what guide are you following, but its not for our phone... try doing this http://forum.xda-developers.com/showthread.php?t=1968360 and pls read the replys... maybe you can found something that helps you
Click to expand...
Click to collapse
this thread really helps. i did not back up efs at first. i lost my imei, follow this guide lads
craidevore said:
this thread really helps. i did not back up efs at first. i lost my imei, follow this guide lads
Click to expand...
Click to collapse
I agree, if you managed to backup your EFS partition via Galaxy Toolbox beforehand and you are facing an issue with your backup not restoring as it should then follow my mini guide on the first page of this thread. If however you didn't take a backup before you lost your IMEI then you'll have to follow the guide from this link -
http://forum.xda-developers.com/showthread.php?t=1968360
Sent from my GT-S5830i using xda app-developers app