I currenty running Thor rom 14.2 and i want to return to stock 3.1.
I have a nandroid backup but accidentally i deleted .txt files inside.
Could i restore it or my tablet will brick
anyone??
First of all: Remember xda-developers is quite international so the person with the answer to your question may be asleep or working at the time you post...
Other than that: If you deleted part of your backup that's bad. You may get away with a partial (possibly non-functional) restore, or restore may fail altogether... Both shouldn't brick your tab, but you might have to do a full wipe and configure your rom from scratch; it may well be worth trying a restore, though, as you won't be causing any more damage anyway if your tab doesn't work anymore. Just make another nandroid backup in case you decide things were better before you hit the restore button... As long as you don't accidentally kill your recovery, android devices are incredibly hard to brick.
jimmis1996 said:
I have a nandroid backup but accidentally i deleted .txt files inside.
Could i restore it or my tablet will brick
Click to expand...
Click to collapse
I just checked a number of nandroid backups of mine and the only ".txt" file that I could see was uid.txt in the main backup directory that contained the ".img", ".tar", and ".md5" files.
You could just run another nandroid BU of your current system and copy over the uid.txt file from that one to replace the one that you deleted. The uid.txt file should be the same from one BU to the next.
Jeff.
Thanks
Thanks for your help
So if i create a .txt file with my id number my restore will work?
Is there another way to restore to stock.
jimmis1996 said:
Thanks for your help
So if i create a .txt file with my id number my restore will work?
Is there another way to restore to stock.
Click to expand...
Click to collapse
If you just put a text file with some random information in it, it may not work right.
Here is the procedure that was suggested:
Make a backup of your current settings
make a copy of the text file in that most recent backup
place that copied text file in the backup with the missing text file
try to restore the backup that was missing the text file, which you just copied the text file to
Psichi said:
If you just put a text file with some random information in it, it may not work right.
Here is the procedure that was suggested:
Make a backup of your current settings
make a copy of the text file in that most recent backup
place that copied text file in the backup with the missing text file
try to restore the backup that was missing the text file, which you just copied the text file to
Click to expand...
Click to collapse
I will try it.
I remember when i downgraded to 3.0 from 3.2 i use something called APX mode could this restore my tab to full stock
problem solved
ok backup my rom copy uid file and everything is ok.thanks
Related
I downloaded the jboogie's deblur nandroid backup but now the problem is, i don't know how to restore it because when i get to clockword mod recovery, i have "backup and restore option" then i go to "restore" and it just says "File not found". the image files are in \sdcard\goapkrev\backup\2011-02-18.23.25.47
I also made a new directory because some people posted to hve the image files in that directory which is \sdcard\clockwordmod\backup\2011-02-18.23.25.47
But it still says "fill not found" also one thing, i don't have a nandroid option in clockwordmod recovery...only "backup and restore"...what should i do?
Have you solved your problem? I think the directory should be "clockworkmod".
sunoldman said:
Have you solved your problem? I think the directory should be "clockworkmod".
Click to expand...
Click to collapse
Yup, that did work for me. I had the exact same problem. I didn't get to see the backup to restore.
Here what you should do. Delete the folder (Clockworkmod) in your memory card.
Restart the phone and go into custom recovery - restore/backup. Perform a backup.
Your phone will automatically generate a new folder Clockworkmod. After this you can just paste your jboogie's deblur nandroid backup in this folder and start your restoring the right way.
farsight73 said:
Here what you should do. Delete the folder (Clockworkmod) in your memory card.
Restart the phone and go into custom recovery - restore/backup. Perform a backup.
Your phone will automatically generate a new folder Clockworkmod. After this you can just paste your jboogie's deblur nandroid backup in this folder and start your restoring the right way.
Click to expand...
Click to collapse
You sir, have saved my a$$, THANK YOU
For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS
Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs
Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2
Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?
Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now
jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..
stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium
vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium
jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.
vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Does K-Tool work with CF-Root kernel?
HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar
Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there
Hi,
I've flashed a new ROM, and found that my IMEI is now 004999010640000 (Generic)
I have a backup of my efs folder.
How do I restore it from the backup?
It looks like when I delete the efs folder, the system recreates it automatically...
What's the way to do it?
Thanks
Gil
I fixed this problem and it took me 4 hours to fix it!
Your real IMEI show on under the battery where you see the model phone.
You need to copy the numbers (without the / if u have this) to this website http://www.adamek.biz/md5-generator.php this website make ur imei to md5 .
After you have created the md5 go to efs folder via root explorer and you need to see the file (.nv_data.bak.md5 or nv_data.bak.md5) On this file you see the md5 of the currety copy the md5 u created to the files and close everything and restart ur phone
I already have a working efs backedup
I already have a working efs backed up!
The thing is that when I copy the files from the backup on the efs folder, they get reverted automatically... I don't know what's doing it...
The backup date is older than the current files... this might be the problem...
but how do I make it work?
Is the security and permissions set up correctly on your backup efs?
gilamran said:
I already have a working efs backed up!
The thing is that when I copy the files from the backup on the efs folder, they get reverted automatically... I don't know what's doing it...
The backup date is older than the current files... this might be the problem...
but how do I make it work?
Click to expand...
Click to collapse
Did you tried to delete the folder and replace the efs folder backup?
I think you have to copy both the files and the hidden files (starting with a dot) from your backup..
The files with a dot are there to prevent you from accidentally deleting your originals and be left with nothing
The only files I see are:
1) .nv_state
2) bluetooth
3) imei
4) lost+found
5) nv.log
6) nv_data.bin
7) nv_data.bin.md5
Should I choose the file that says: "nv_data.bin.md5"?
If you have backuped your efs folder, this thread can help you:
http://forum.xda-developers.com/showpost.php?p=22195291&postcount=1008
I think there is a lot of confusion going on around here... so just to be clear...
What file should I have in my efs backup, including the hidden one?
Thanks!
No backup of EFS folder. I believe it was during my attempt to backup that I corrupted the folder.
tamaratee said:
No backup of EFS folder. I believe it was during my attempt to backup that I corrupted the folder.
Click to expand...
Click to collapse
I have the same situation, same files as posted above, anyone has any idea?
I just rooted my brand new note3 but I forgot to backup my EFS before flashing X-note... Now I made a backup on X-note rom, is it still ok for restore if I ever lost my EFS? Thank you
As long as you have the EFS file then it should be OK, keep it seperated from your internal HD if possible also!
EDIT: Btw the EFS file is around 14MB or so -
darn,.. my backup only 408KBs. I use this method http://forum.xda-developers.com/showthread.php?t=2447342 result said Everything is OK..
any idea why my file is so small?
from my root explorer ... the efs folder only 1.4MB big
OH! when i decompressed the file, there is disk image file is around 14MB
how do i restore it? btw.... I throw this compressed winrar file into ODIN? or decompress first, and then select these individual files accordingly
h3nyr said:
darn,.. my backup only 408KBs. I use this method http://forum.xda-developers.com/showthread.php?t=2447342 result said Everything is OK..
any idea why my file is so small?
from my root explorer ... the efs folder only 1.4MB big
OH! when i decompressed the file, there is disk image file is around 14MB
how do i restore it? btw.... I throw this compressed winrar file into ODIN? or decompress first, and then select these individual files accordingly
Click to expand...
Click to collapse
Sounds like it's OK.
Restoring I'm not so sure, due to me not having done it myself, I know you need busybox installed though or you'll encounter problems. Be warned EFS cause be a major ballache to do from people I've seen trying to restore, some have no issues though.
I was trying to disable the hardware buttons, the one next to the home button, and use on screen buttons. But when I edited the file the first time the back button was disabled which is what I wanted but not the other button (menu?). So I tried again and when es file explorer saved it, it saved it as a empty text document. So what I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout. Im sorry if this is in the wrong place im just kinda scared about what could happen, like not being able to power back on. Thank you!
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Just dirty flash the rom you have (without a wipe).
fffft said:
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Click to expand...
Click to collapse
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
xada162 said:
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
Click to expand...
Click to collapse
I thought you knew exactly what file you accidentally corrupted. In your original post you said
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
So on that basis, you could extract the cited file from the TWRP system image. Or temporarily restore it and copy that file. Or for that matter simply restore the entire /system partition. The latter would cover you even if you weren't positive which system files were corrupted.
So boot to TWRP, wipe your system cache, then restore the system partition from a known good backup and call it day.
.