Related
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Couple of things...
Your backup might be corrupt if the md5 doesn't match.
or you might want to try and make sure you have the latest version of CWM installed on your phone. I read in one of the other threads that someone had an md5 mismatch problem that was solved with a newer version of CWM. I hope this helps.
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I had this happen to me once. Turned out the nand backup was bad....used the previous one I had made and was back in action. Had a few moments to sweat it out though. Just make sure to backup regularly and archives them.
Sent from my SAMSUNG-SGH-I727 using xda premium
same problem
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
bshebib said:
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
Click to expand...
Click to collapse
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Presbycusis said:
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Click to expand...
Click to collapse
This is exactly how I do it. I've never needed it but have always had it for emergency. Now that ICS is out I've been going back and forth from the sandwich to gingerbread because the bugs are well.......bugging me. I odin'd the leak then I backed it up after I installed cwm so I could always go back to that after testing out these other roms, cwm flashes, and even the backups of ICS, then I root. I basically have started from scratch twice and both times I went back to my backup I got the mismatch ( 2 different backups of the leak). I know its me (possibly cwm) because the cwm ics backup that's out there restores fine.
Sent from my SAMSUNG-SGH-I727 using XDA
Are you extracting on your PC? There seems to be some problems with unzips on the phone causing a mismatch
I've been using 7-zip for mine, and it works great. Extract files on the desktop, place on the external SD using USB
Got this from another forum
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Toggle signature works for me alot
Sent from my SAMSUNG-SGH-I727 using XDA
Not totally sure that I'm correct but I had made two backups on one version of cwm and then upgraded my cwm to the touch version and the two backups from the previous version wouldn't restore because of md5 mismatch. Those same two backups had worked several times perfectly on the other version of cwm as well. So I just assumed that maybe the version change had something to do with it.
Sent from a payphone at the quick-e-mart down the street from you
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Just flashed cwm touch from another recovery before trying to flash new rom zip and md5 mismatch accured...after darkwipe..dang..that was close call....think your correct with the change theory...
Sent from my SAMSUNG-SGH-I727 using XDA
Yes
yes that wass the problem. Tnk you NO spaces on backup folder name.
Tnk s
mindmajick said:
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
hisham027 said:
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Worked perfect, thanks
adb Problem
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Isn't that for the international gs2?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Try using terminal emulator from your device
ADB Shell
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
funatkill said:
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
Click to expand...
Click to collapse
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
hisham027 said:
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
Click to expand...
Click to collapse
I fixed my md5 with the adb shell.. but I had to do this in one command . After reading this tut, I think there only has to be the MD5 of *.img, not of the .tar. Am I right?
Maybe its possible to script a zip-file for CWM which recalculates the MD5 of existing Backups?
The bash commands are simple. You only have to do this in a loop for all folders in /sdcard/clockworkmod/backup.
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.
I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?
Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.
dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.
That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.
I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA
Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces
I currently have CWM 6 installed, but prefer the older version's backup method and file structure (don't like the Blob thing). Can I flash CWM 5 over 6? Thanks!
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
apacseven said:
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
Click to expand...
Click to collapse
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
STraver said:
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
Click to expand...
Click to collapse
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Click to expand...
Click to collapse
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
apacseven said:
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
Click to expand...
Click to collapse
Okay thanks. I can't find the option they're talking about. Thanks for your help.
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Sent from my CleanRom'd Galaxy SIII
x714x said:
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Click to expand...
Click to collapse
Thats what it was doing when I stopped using it, but each folder was only 20mb. The rest of the data was going into the blobs folder.
LESSON LEARNT (for everyone): Please make sure to do a complete EFS backup before you do anything or you will end up like me!!!
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
Repair IMEI using EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing stock ROM for Malaysia region (Froyo and GB)
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
Restoring Nandroid backup from other SL user (Thanks Rich'Dawg')
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
Some websites said about fixing IMEI for small fees but in cases of blank IMEI (*#06#), chances are only 30%.
And my last resort would be getting it replaced in Samsung service centre or any repair shop, which I suspect that the motherboard would be more expensive than some simple new Android phones.
Leaving this forum for the moment as to collect more money to get a new phone . . . :crying:
Lastly, thanks for all the input. Greatly appreciated.
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
nicsptl said:
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
Click to expand...
Click to collapse
Nope. I totally lost signal and mobile network.
cheeyeen said:
Nope. I totally lost signal and mobile network.
Click to expand...
Click to collapse
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
chongns said:
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
Click to expand...
Click to collapse
Yes I did but nope I couldn't find. sucks.
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
chongns said:
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
Click to expand...
Click to collapse
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
cheeyeen said:
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
Click to expand...
Click to collapse
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
chongns said:
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
Click to expand...
Click to collapse
Fixed permission.
I found one .nv_data.bak dated year 1994 , which I think came in when I was trying to flash some efs fixes i found in XDA.
Without much hope I tried what you said, but still nothing happened. IMEI blank, baseband unknown.
Is it possible to have the mobile phone repair shop with RIFF or Jtag or some box thingy to have this done?
i think you must change the motherboard
cheeyeen said:
[Request] Is it possible if anyone could send me a Nandroid backup of a working rom, so I could restore it via CWM? (It is a way I found in the XDA forum).
...
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
And my last resort would be getting it replaced in Samsung service centre??
I don't know how much would it cost in Malaysia to change the motherboard but I'm sure it will be stupidly high...
Or.. does that mean my time in i9003 forum is up..? :crying:
Please help me because I don't want to buy a new phone yet! :crying:
Click to expand...
Click to collapse
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
I would try anything as long as it works! Please do!
Best of Luck
a friend of mine ran through the same same problem and i think he did some sort of repair from a shop but later we came to know that the backup can do the task not sure whether that work or not but u can give it a try,, BEST of Luck with that..... Hopit Fix the Issue
Good luck sir! As far as I know, if you would choose to replace the motherboard from repair center, it would cost you more or less 80% of the original price of the phone. So it would seem that you have to buy a new one. I hope that a nandroid backup (as stated above) would solve the problem. God bless you! Think positive
i have the same problem and tried those solution the TS tested and still no luck, i wan't to try those nandroid backup but can't find any.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Xperia.IN said:
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Click to expand...
Click to collapse
can you share it with me if you have nandroid backup, i will try to fix it with z3x and asansam
never thought deodexing gonna brick the phone.. ive deodex once without any problem.. without any doing backup before that.. lucky me.. huhu
try other people's nandroid and see.. i dont think it needs a specific emei or what so ever.. as long as its a backup.. goodluck..
the problem is we can't find someone to lend us their nandroid backup.
I did it!
Bro, try use Efs Pro, http://forum.xda-developers.com/showthread.php?t=1308546
Try the new version, you can choise Qualcom version, write you IMEI number, go back to initial and do NV Restore.
My SG Fit go back to life (after maybe 4 months with 0000000000000 Imei). :good:
I´m very happy
Hope it work for you! Good luck!
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Click to expand...
Click to collapse
Interesting...
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Click to expand...
Click to collapse
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
All the nv_data.bin files I have are 262.1kB.
The tar backups the installtion script creates for you should be 700kB or less.
It sounds like something went seriously wrong with the nv_data.bin file you are trying to restore, so I recommend you follow the advice @champ1919 gave you and go back to gingerbread an flash your ROM again.
After you flash make sure that the nv_data.bin file under /efs/root/afs/settings/nv_data.bin is exactly 262.1kB. If that's the case then save the efs backup the install script made for you in a safe place.
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
champ1919 said:
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
Click to expand...
Click to collapse
Interesting. I think all the ones I got were from phones built at around the same time since they have similar text in the nv_data files.
The locked/unlocked files should be the exact same file size every time. All the tends to change is a single 1 in the file becomes a 0 to unlock it.
I had stored them in Dropbox. I betcha one is from the vibrant I lost, but, I thought I deleted it so I would not goof. As soon as I can get to a PC, I'll dig into it somemore. I wonder who wrote that guide years a go on how to hexedit that file. I should give them another thanks.
bhundven said:
Interesting...
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
Click to expand...
Click to collapse
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
cryzone77 said:
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
Click to expand...
Click to collapse
Nope, that does not work. That is also not what my directions said to do.
cryzone77 said:
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Click to expand...
Click to collapse
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
cryzone77 said:
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
Click to expand...
Click to collapse
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
cryzone77 said:
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
Click to expand...
Click to collapse
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
bhundven said:
Nope, that does not work. That is also not what my directions said to do.
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
Click to expand...
Click to collapse
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
champ1919 said:
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
I have a T959V.
I tried the SlimKat and SlimSabre but I still got no IMEI even after manual restore. I also tried the CM11 and still have the same problem.
So, when you go back to gingerbread, your number is still hosed?
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
Click to expand...
Click to collapse
I have no clue where you got those directions.
cryzone77 said:
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Click to expand...
Click to collapse
Here it sounds like you are mixing up directions.
cryzone77 said:
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Click to expand...
Click to collapse
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
cryzone77 said:
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Click to expand...
Click to collapse
Yes
cryzone77 said:
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
Click to expand...
Click to collapse
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
champ1919 said:
So, when you go back to gingerbread, your number is still hosed?
Click to expand...
Click to collapse
I'd like to know the answer to this as well. Good question!
bhundven said:
I have no clue where you got those directions.
Here it sounds like you are mixing up directions.
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
Yes
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
I'd like to know the answer to this as well. Good question!
Click to expand...
Click to collapse
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
cryzone77 said:
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
Click to expand...
Click to collapse
Ok, so you go back to gingerbread and get your imei back.
cryzone77 said:
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
Click to expand...
Click to collapse
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
bhundven said:
Ok, so you go back to gingerbread and get your imei back.
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
Click to expand...
Click to collapse
1st, YES I got my IMEI and baseband back, but its a shame if I can't upgrade to CM++(because I don't get my IMEI and baseband after flashing meaning I can't use my phone for work.) because it's a cool rom, it has everything I'm looking for in a custom rom.
AND yeah, I wasn't aware that they were THAT different. Anyways, thanks for pointing that out.
Q: Is there an upgrade path or something that I need to do aside from the standard flashing procedure for these roms?
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
champ1919 said:
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
Click to expand...
Click to collapse
Sorry,
What I meant by OneClick is using Heimdall in flashing the purely stock GB rom. After that, I root using Framaroot(successful) then I flash a custom kernel(bhundven's blastoff...IMEI and baseband still ok after this), then I flash CM++ ROM, this is where it gets ugly--I lose my IMEI(null) and baseband(also null). and YES I let the phone fully boot, I even wait around 15mins and try to turn the radio on and off to see if I got my IMEI and baseband back, I also tried taking out the battery and letting the phone loose all it's power and then turning it on, again, to no avail. And to answer the other question, I get CWM through the blastoff kernel.