Related
Hey guys,
asked this question in the wrong section so I'm asking it here.
Is it possible to extract an old nandroid backup to view memos I may have had?
I don't want to restore the backup, I know something in it is wrong as it would freeze on bootup after I tried a restore, that isn't important. What is important is there were memos stored on that backup that I need back.
I used unyaffs to extract system.img, but everytime I try and extract data.img (which is where I'm guessing the memos are stored) I get a popup in windows 7x64 that says unyaffs.exe has stopped working.
I copied data.img off my sdcard and am trying to extract through windows terminal.
Can someone tell me if I am correct in thinking the memos would be stored in the data.img and where they might be located and why I am unable to extract data.img?
Thanks in advance!
Hi all:
I got a new galaxy nexus that i'd like to use as my main phone, but I don't want to go through the trouble of setting it up again, my current gnex is just perfectly setup. They both have the same version of android (4.0.4).
I was going to to a clockwork mod backup of the current phone, move it to the new phone and restore there, but I think I'll mess up the IMEI if I do that?
What additional steps do I need to carry out to preserve the phone's IMEI?
Thanks in advance.
pcbroch said:
Hi all:
I got a new galaxy nexus that i'd like to use as my main phone, but I don't want to go through the trouble of setting it up again, my current gnex is just perfectly setup. They both have the same version of android (4.0.4).
I was going to to a clockwork mod backup of the current phone, move it to the new phone and restore there, but I think I'll mess up the IMEI if I do that?
What additional steps do I need to carry out to preserve the phone's IMEI?
Thanks in advance.
Click to expand...
Click to collapse
If both have absolutely the same ROM, restore just the data backup, not the system backup, and you should be fine.
You can copy the IMEI on the original nexus to the other? Wouldnt that be best?
Is so follow these steps (it may look much, but i dont think it would take long if u want to keep your original imei number!
You must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.
IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:
1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]
2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.
3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.
4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder
7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"
8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:
adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin
9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.
Sent from my LT26i using xda premium
HinotoriBR said:
If both have absolutely the same ROM, restore just the data backup, not the system backup, and you should be fine.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately, it doesn't seem to work, my IMEI gets clobbered to some generic IMEI when I do this.
Off to trying try sikiduck's suggestion.
Sikiduck said:
IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these
Click to expand...
Click to collapse
Stupid question... there is no efs folder. Do you mean /factory? There are nv_data files in /data/radio as well.
I'll play with these a bit and see.
You got root?
Sikiduck said:
You got root?
Click to expand...
Click to collapse
Yes, I do. I tried playing with the nv_data files, but I can't get the original IMEI to come back no matter what I do.
anyone knows anythink about it?? I have tried building a rom from system.tar(backup file from nandroid) but it contains only the stock apps...
Extract the system.tar to get system folder
and if ur using kitchen
then copy it to the WORKING_XXXX folder or create such folder
and there is no other way...all u do is somehow get the system folder and then modify it
and thanks for the help dude
SSSidGGG said:
Extract the system.tar to get system folder
and if ur using kitchen
then copy it to the WORKING_XXXX folder or create such folder
and there is no other way...all u do is somehow get the system folder and then modify it
and thanks for the help dude
Click to expand...
Click to collapse
Already tried that but it contains only the apps which come with the original stock rom(stock apps) and not the ones I downloaded..
The apps that u install after getting the device started are not in the system folder but the data folder which can be found in data.rfs.tar
and then in data folder open app u will find them either there or a backup of those somewhere in the .tar file only dnt remeber properly
your downloaded app is stored in data.rfs.tar (if you put them on internal memory) or .android_secure.vfat.tar (if you put them on sdcard)
SSSidGGG said:
The apps that u install after getting the device started are not in the system folder but the data folder which can be found in data.rfs.tar
and then in data folder open app u will find them either there or a backup of those somewhere in the .tar file only dnt remeber properly
Click to expand...
Click to collapse
kurotsugi said:
your downloaded app is stored in data.rfs.tar (if you put them on internal memory) or .android_secure.vfat.tar (if you put them on sdcard)
Click to expand...
Click to collapse
ty both of u.. srry culdnt press the button cuz i hav reached my limit of 8 thnks
is it safe to place the files in /system/app folder and remove the old ones??
yup...if you already have the newer one its safe to remove the old one. but make sure you delete the odex files too. no need to press that silly button. I'm just a noob here, not a dev.
You can try but when i put vending.apk when 1st open it installing again on /data and operamini.apk can't put on system always force close in my case.
in DXLB and newer firmware market in system app is named phonesky.apk. vending.apk is the older version used in older firmware. we don't need them if we already have phonesky.apk.
Does someone knows is there EFS folder on LG G3 because I cant find it with RootExplorer. I was looking on SdCard and through whole device but theres no trace of it. I've made a backup with adbshell comands and got modemst1.img and modemst2.img but I want to copy and save EFS manually.
bpodnar said:
Does someone knows is there EFS folder on LG G3 because I cant find it with RootExplorer. I was looking on SdCard and through whole device but theres no trace of it. I've made a backup with adbshell comands and got modemst1.img and modemst2.img but I want to copy and save EFS manually.
Click to expand...
Click to collapse
It's not manual but there is an app called efs backup that backs both the efs file and the modem for you
My phone is GT-N7105 (Samsung Note 2)
=============SHORT STORY=============
TWRP can't recognize my backup folder name which I am trying to restore
=====================================
=============LONG STORY=============
I had a nandroid backup before, then I copied the backup to PC, still have it. Then I flashed lineage 13. I deleted the nandroid backup on the phone storage. Now I want to restore the backup so I copied the backup files from the PC.
Now when I go to TWRP Restore mode, no backups are found.
I already searched through the internet and found the renaming method but there's a problem:
this is my original backup:
TWRP/backups/42f7491d7b409fc7/2017-03-01--05-28-34_JZO54K.N7105XXDMB
I tried to make a new backup of my current lineage (just to see if the folder name changed based on the new folder the backup process will create), here is what the resulting folder was:
TWRP/backups/42f7491d7b409fc7/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
As you can see, only the innermost folder name changed. So from what I found through searching, it said to rename the old backup folder to the new backup folder's name, meaning :
I changed
2017-03-01--05-28-34_JZO54K.N7105XXDMB
to
2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
TWRP still can't see the original backup.
So what should I rename the original backup folder for TWRP to recognize it and make it appear?
EDIT:
I already updated my TWRP but problem still exists.
Create a new backup with your current rom, then remove it and add the old one instead.
futchy4u said:
Create a new backup with your current rom, then remove it and add the old one instead.
Click to expand...
Click to collapse
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
/TWRP/BACKUPS/4d00475b004150de/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
Click to expand...
Click to collapse
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
sgn15 said:
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
Click to expand...
Click to collapse
futchy4u said:
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
Click to expand...
Click to collapse
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
sgn15 said:
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
Click to expand...
Click to collapse
You're welcome. I think it's ok to be left here so that it could help others.