Hi,
If I create Nandroid Backup Img File of my phone (which I have) is this img file a 'ROM' or is it not the same type of thing?
Reading android Wiki v slowly....sorry...
Thanks
Phil
Ignore this.... 'ROM Image' so same thing I guess. Was not sure of the terminology used here.
haha, thanks! i thought this was the case but it's good to see it clarified somewhere ;-)
Related
Hi there,
I have some previous backups (nandroid.md5) files and I would like to explore them in order to retreive some files.
I am looking for a way through mac or win 7. I do not want to restore te back up version.
Any ideas ?
I don't know about files but you can get apps from a nandroid via appextractor
And PLZ!!!!!! QUESTIONS IN THE GENERAL SECTION...... EVEN IF THEY ARE DEV RELATED!!!
The md5 contains only the files' checksum which is used to check if is corrupt or not. You really can't extract any information from them.
The main content lies in the other files.
You can use unyaffs to extract and view the files.
The sd-ext partition is backed up in tar format so you extract it using tar.
Sent from my Wildfire S
Search the market (play store)
'nandroid browser'
Great tool for extracting single files/folders from a nandroid backup without restoring.
It's been very usefully for me.
sorry guys my mistake.
I need to retrieve all camera photos from a backup image.
I just noticed that the md5 file is too small to contain images and I found some .img files.
Is there a way I can extract them straight to my pc and not from the phone?
I find it hard to locate the files through nandroid browser.
Thanks a lot for you help and apologise for the incovenience.
ThoDis said:
sorry guys my mistake.
I need to retrieve all camera photos from a backup image.
I just noticed that the md5 file is too small to contain images and I found some .img files.
Is there a way I can extract them straight to my pc and not from the phone?
I find it hard to locate the files through nandroid browser.
Thanks a lot for you help and apologise for the incovenience.
Click to expand...
Click to collapse
Your camera pictures are saved to the sdcard and not a nandroid backup look in the DCIM folder on your SD card :thumbup:
Sent from my HTC Wildfire S A510e using Tapatalk 2
I made a backup with ClockworkMod recovery and was able to restore from it later. Then I renamed the folder to something more meaningful. Next time I tried to restore I got a message about bad MD5 file. Is there anyway to fix this? I do not remember the original folder name of the backup.
anichin said:
I made a backup with ClockworkMod recovery and was able to restore from it later. Then I renamed the folder to something more meaningful. Next time I tried to restore I got a message about bad MD5 file. Is there anyway to fix this? I do not remember the original folder name of the backup.
Click to expand...
Click to collapse
Found the answer here:
http://forum.xda-developers.com/showpost.php?p=7004747&postcount=2
anichin said:
I made a backup with ClockworkMod recovery and was able to restore from it later. Then I renamed the folder to something more meaningful. Next time I tried to restore I got a message about bad MD5 file. Is there anyway to fix this? I do not remember the original folder name of the backup.
Click to expand...
Click to collapse
it needs to be named as it was set by cwm
LG G2 EFS Backup Zip
Background
The G2 has no built in EFS backup partitions. EFS contains things like your MEID or IMEI... your data profiles.. radio settings. The EFS cannot be replaced... it is unique to your phone only... backing up your OWN EFS is highly recommended.
I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up. Backing up EFS
In TWRP, flash the LG_G2_Backup_EFS.zip attached in this thread. LG_G2_Backup_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/. Please check to make sure the backup zip worked and actually made a .zip file. Any issues please list what recovery and version you are using and please post the recovery.log.
Backup your efsbackupflashable.zip somewhere else besides your internal SD!!! Email.. cloud.. PC..
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflashable.zip in your /sdcard/EFS_Backup folder.
If flashable zip wasn't created or to manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
Backup ALL Partitions
Well almost all... I am attaching another zip which backs up most of your phones partitions.. excluding system/data/cache and some other useless partitions. Backing up all partitions isn't as important as backing up the EFS but it can't hurt. Never know when you may need it.. especially those who like to poke around with their phone and try new things.
Run the zip in recovery.. it will make backup .img files on your internal sdcard in a new folder named "backupz"... remember to copy your backups off the internal sdcard.
Wow nice find and quick work! I wonder what the chances are of messing you current info up, so your backup would actually be necessary?
drkow19 said:
Wow nice find and quick work! I wonder what the chances are of messing you current info up, so your backup would actually be necessary?
Click to expand...
Click to collapse
Even if the chances are really small, it is always nice to have a backup.
Having to restore with QPST or other similar methods is not fun at all.
Thanks autoprime.
this was pretty fast considering i just saw you post this in irc
I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer
bckrupps said:
I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer
Click to expand...
Click to collapse
Same situation here.
bckrupps said:
I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer
Click to expand...
Click to collapse
jasonsf said:
Same situation here.
Click to expand...
Click to collapse
hmm k... this happened on the LG OG as well... then some people had it working on CWM.. some people had to flash an AOSP rom first.. seems random. If someone can provide me the recovery.log after flashing the efs zip that would help. I'm going to bet its an issue with 7z packing the zip the new flashable zip for some reason or another.
i uploaded a new zip which will still try to make the flashable zip.. while also backing up the individual efs partitions.
redownload the new zip to backup efs img files.
To manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st2
autoprime said:
hmm k... this happened on the LG OG as well... then some people had it working on CWM.. some people had to flash an AOSP rom first.. seems random. If someone can provide me the recovery.log after flashing the efs zip that would help. I'm going to bet its an issue with 7z packing the zip the new flashable zip for some reason or another.
i uploaded a new zip which will still try to make the flashable zip.. while also backing up the individual efs partitions.
redownload the new zip to backup efs img files.
To manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st2
Click to expand...
Click to collapse
I have the recovery boot loop issue and was just using your zip to test out ADB Sideload in TWRP. I'll wait until my phone is working before I give your tool another try. Too many variables right now.
Jason
For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")
jasonsf said:
Same situation here.
Click to expand...
Click to collapse
Same thing happens to me on VZW. Here is the recovery.log
http://pastebin.com/jhyHJ0Yz
jug6ernaut said:
For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")
Click to expand...
Click to collapse
I can confirm this information on my AT&T G2. Maybe the script can be modified as such (unconfirmed):
Code:
# backup partitions
EFS_PREFIX=modem_st # Assume Verizon model (with underscore)
if [ -e /dev/block/platform/msm_sdcc.1/by-name/modemst1]; then # Use AT&T model nomenclature
EFS_PREFIX=modemst
fi
/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/${EFS_PREFIX}1 of=/tmp/efs1.img;
/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/${EFS_PREFIX}2 of=/tmp/efs2.img;
jug6ernaut said:
For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")
Click to expand...
Click to collapse
Ugh.. sorry about this. I must have been in HTC mode.. they use the "_" derpppp.
updated the zip.. see how that goes.
mine did not create a .zip file. On At&t, but still thanks a ton! will keep these two efs.img's stored on my dropbox so that I always have a backup.
Anyway to make these two into a flashable zip manually? I'm sure the code is in the script somewhere I just don't feel like looking haha
This now works for me autoprime. It created efs1.img, and efs2.img on VZW. Thx!
Got my two image files, both 3mb....thanks! I am on ATT.
im on verizon. works great. kudos
Confirm works on ATT.
Sent from my LG-D800 using Tapatalk 2
I have updated the zip in the OP... it now creates a proper flashable backup zip as well as teh 2 efs img files.
thanks to @jug6ernaut for testing all of my broken zips :highfive:
In TWRP the zip fails every time..... attached photo of error.
Sent from my VS980 4G using XDA Premium HD app
anyone else have the error that @mouf32 is having? I have some users on IRC that say it's working just fine. And there's been 50+ downloads with no other issues.
@mouf32 have you tried to redownload the file? maybe the zip got messed up or is corrupted?
Hi all, I'm using M9 (CID - 621, Software no - 2.10.709.1). My phone installed TWRP and rooted.
But I've backuped the stock firmware (Unroot) of HTC M9 via TWRP.
I want to make sure myself about some issues with OTA update.
Let's suppose if I found my correct recovery (with correct CID no. and Software no. Eg- HTC__621, 2.10.709.1 thanks to flippy498 from http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 and I restored the stock firmware (that I backuped earlier) to my phone, would my phone be able to get OTA update?? or not???
if not where can I find my phone's RUU ??
winkhant said:
Hi all, I'm using M9 (CID - 621, Software no - 2.10.709.1). My phone installed TWRP and rooted.
But I've backuped the stock firmware (Unroot) of HTC M9 via TWRP.
I want to make sure myself about some issues with OTA update.
Let's suppose if I found my correct recovery (with correct CID no. and Software no. Eg- HTC__621, 2.10.709.1 thanks to flippy498 from http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 and I restored the stock firmware (that I backuped earlier) to my phone, would my phone be able to get OTA update?? or not???
if not where can I find my phone's RUU ??
Click to expand...
Click to collapse
There are no working RUUs for the 2.XX.XXX.X firmware versions (yet). Take a look at my google sheet (a link can be found in my signature). There you find working backups and the needed instructions for restoring the ability of installing OTAs.
Flippy498 said:
There are no working RUUs for the 2.XX.XXX.X firmware versions (yet). Take a look at my google sheet (a link can be found in my signature). There you find working backups and the needed instructions for restoring the ability of installing OTAs.
Click to expand...
Click to collapse
Thanks for your reply. I'm noob in this field so let me ask one question
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. I can not understand in this step
My TWRP backup folder contain too many files
(eg - boot.emmc.win, boot.emmc.win.md5, data.ext4.win000 etc)
So, must I delete this all files and replace with the downloaded backup???
winkhant said:
Thanks for your reply. I'm noob in this field so let me ask one question
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. I can not understand in this step
My TWRP backup folder contain too many files
(eg - boot.emmc.win, boot.emmc.win.md5, data.ext4.win000 etc)
So, must I delete this all files and replace with the downloaded backup???
Click to expand...
Click to collapse
You don't have to delete your backup. If it contains at least a boot image, a system image and the stock recovery of a not-rooted system that is mounted as read-only then you can use it with my instructions, too. The thing is that I do know that my backups work whereas I'm not sure about your one as I do not know under which circustances you created it.
I wrote my instructions with all information people need to know if they downloaded my backups . Step 6 is only a continuation of Step 4 and 5. All in all those three say: Download the correct (zipped) backup. Unzip it. Copy the folder that was placed inside the zip file to the right directory.
Flippy498 said:
You don't have to delete your backup. If it contains at least a boot image, a system image and the stock recovery of a not-rooted system that is mounted as read-only then you can use it with my instructions, too. The thing is that I do know that my backups work whereas I'm not sure about your one as I do not know under which circustances you created it.
I wrote my instructions with all information people need to know if they downloaded my backups . Step 6 is only a continuation of Step 4 and 5. All in all those three say: Download the correct (zipped) backup. Unzip it. Copy the folder that was placed inside the zip file to the right directory.
Click to expand...
Click to collapse
Very thank you. Now I understand. really thanks
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.