Related
Hey all,
Are nandroid restores specific to one particular device or can they be interchanged between two G1's? I have a spare G1 that I play around with that has root while my other G1 doesn't have root. I am thinking about rooting the other one and wanted to know if I could just go through the rooting process, (radio, spl, cyanogen recovery etc) throw on a cyanogenmod or JF, then do a nandroid restore from the spare device with all my settings on it. I know that nandroid creates a unique numerical folder that has your latest backup in it so I wasn't sure if this folder would be seen by nandroid on a different phone.
Any thoughts?
EDIT:
Just wanted to update this thread in case anyone else wanted/needed to do this. As I suspected, I ran into folder name problems when trying to copy one nandroid restore to my spare phone and trying a restore. There is a simple fix however....
1) Perform a nandroid backup on the phone you WANT to backup.
2) Copy that nandroid folder from the phone to your PC.
3) Perform a nandroid backup on the phone you DON'T WANT to backup.
4) Copy that nandroid folder from the phone to your PC.
5) Compare the nandroid subfolder name (should be alpha-numeric starting with HT) of the backup you want to the name of the one you don't.
6) Change the name of the nandroid subfolder on the backup you want to restore to the same name of the folder you don't want. This way you fool nandroid into thinking that the backup was originally done on that phone.
7) Copy the entire nandroid folder (with the newly changed subfolder name) to the sdcard of the phone you want to restore.
8) Boot into recovery (power+home) and perform the nandroid restore. If the restore fails, you probably don't have the correct subfolder name. Return to step 5 and 6.
9) If the restore is successful, reboot and you should be all set!
Good question. I wouldn't have thought there would be issues with it bar of course your settings etc but then a wipe before would resolve that. Just make sure to do what you've said though (upgrade radio, SPL, recovery etc) first.
DirectMatrix said:
Hey all,
Are nandroid restores specific to one particular device or can they be interchanged between two G1's? I have a spare G1 that I play around with that has root while my other G1 doesn't have root. I am thinking about rooting the other one and wanted to know if I could just go through the rooting process, (radio, spl, cyanogen recovery etc) throw on a cyanogenmod or JF, then do a nandroid restore from the spare device with all my settings on it. I know that nandroid creates a unique numerical folder that has your latest backup in it so I wasn't sure if this folder would be seen by nandroid on a different phone.
Any thoughts?
Click to expand...
Click to collapse
It won't upgrade your SPL, radio, and recovery. If you look in the nandroid folder, you'll see exactly what is backed up. I think its the /system folder and the /data folder as well as something else. But if you have another phone that is already rooted and has the correct SPL, radio, and recovery, this will work.
Should be fine then as he's planning on doing the usual steps up until flashing the desired ROM of choice. Tell us how it goes DirectMatrix and if it works, please change your thread title to include [SOLVED] so we all know ^_^
NeoBlade said:
Should be fine then as he's planning on doing the usual steps up until flashing the desired ROM of choice. Tell us how it goes DirectMatrix and if it works, please change your thread title to include [SOLVED] so we all know ^_^
Click to expand...
Click to collapse
Gonna start rooting the other phone now so I'll keep this thread updated with whether nandroid backups are swappable between phones. I hope so as that will save me quite a bit of settings/data calibrations.
@h.nocturna... LOL, you have been dealing with n00bs too long in the Q&A section....of course nandroid won't upgrade my radio, SPL, and recovery, but I had a good laugh anyways. Thanks all for the advice
Have NC rooted (thecube Monster Root) w/eclair. Want to install new CWM to eMMC but have yet to find thread on this. Anyone seen such a thread?
Well the way I did it was I got Rom Manager from the market, then hit the flash clockwork option. My B&N software version before I rooted was 1.1 so I had to update CWM to 3.0.1 so that it would actually work right, there's a thread in the development section if you need to do that too. I don't know if this is the quickest or best way to get it done, but it worked for me.
Read the threads on CWM 3.x...
It doesn't install correctly from ROM Manager, and if you do it that way it won't work correctly when making and restoring ext4 backups (big blue text in the link below).
http://forum.xda-developers.com/showthread.php?t=971197
I used MrMuffin's flashable zip to install...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Read the threads on CWM 3.x...
It doesn't install correctly from ROM Manager, and if you do it that way it won't work correctly when making and restoring ext4 backups (big blue text in the link below).
http://forum.xda-developers.com/showthread.php?t=971197
I used MrMuffin's flashable zip to install...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Yes, specifically, you need a microSD card, but it is easy after that. From the thread referenced above:
Yes it can and it just took the right man to create the update.zip that updates CWM. Thanks to MrMuffin there is one now.
cwmr_3.0.1.0.zip - md5: d7a550d683e54732bcb55eff24ada704
Place onto your sdcard and flash like you would a rom and reboot back into recovery! Please give MrMuffin thanks if you find this useful!
Worked for me first time.
glg
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
tramp20 said:
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
Click to expand...
Click to collapse
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
N00BY0815 said:
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
Click to expand...
Click to collapse
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
tramp20 said:
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
Click to expand...
Click to collapse
The link I provided is for CWM touch 5 only. This version will make the "normal/full-sized" backups. I think you're right about the new update, but I gotta confess, I dont really understand it myself yet... I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
If your not sure about the old version, just install the one from the link I provided.
Hope it helped you, if not, you may also PM me.
N00BY0815 said:
I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
Click to expand...
Click to collapse
To test:
I made a backup, installed a new app, then after another backup I looked in the blobs dir: only a few subdirs are new, all other remain unchanged.
So all files in blobs are cumulative and important for a restore, but bad for a later extern backup on my pc.
The old method of CWM was better.
Perhaps I will try the link from you.
I was trying a backup and found under "choose backup format" the following points:
- dup (default)
- tar
-
-
So I can choose
I did a backup (dup format) and all is working again.
Hi everybody!
I rooted my Nook Color about two years ago and never looked back (that was two weeks after launch day...I think it was 2.1 Eclair back then). The other day I was futzing about and deleted all my system data. Gak. I attempted to restore using Clockwork Recovery, but alas, I didn't realize until too late that my "newest" backup was from April of 2011. In retrospect, I should have tried to restore from my weekly Titanium Backup, first. As it turns out, the old Clockwork image overwrote the Titanium backup. Bummer.
Anyway, after the restore, the Nook still works perfectly with Google Market et al, but can no longer download any of my purchased books (and the Store doesn't work, either). It has my "Owner Name" and "Account" info correct in "Settings -> Device Info -> About Your NOOKcolor" but I get an error when trying to sync ("nook color internal error exception executing the command").
Is there a way to repair the damage I've done without taking the device back to the stock firmware, wiping it clean, and starting all over from scratch?
If I *do* have to start over, what's the latest and greatest STABLE way of rooting a Nook Color these days?
Any thoughts are much appreciated!
riffrafff said:
Hi everybody!
I rooted my Nook Color about two years ago and never looked back (that was two weeks after launch day...I think it was 2.1 Eclair back then). The other day I was futzing about and deleted all my system data. Gak. I attempted to restore using Clockwork Recovery, but alas, I didn't realize until too late that my "newest" backup was from April of 2011. In retrospect, I should have tried to restore from my weekly Titanium Backup, first. As it turns out, the old Clockwork image overwrote the Titanium backup. Bummer.
Anyway, after the restore, the Nook still works perfectly with Google Market et al, but can no longer download any of my purchased books (and the Store doesn't work, either). It has my "Owner Name" and "Account" info correct in "Settings -> Device Info -> About Your NOOKcolor" but I get an error when trying to sync ("nook color internal error exception executing the command").
Is there a way to repair the damage I've done without taking the device back to the stock firmware, wiping it clean, and starting all over from scratch?
If I *do* have to start over, what's the latest and greatest STABLE way of rooting a Nook Color these days?
Any thoughts are much appreciated!
Click to expand...
Click to collapse
That CWM restore should not have wiped out your Titanium Backup backup files. They should still be on sdcard or emmc media, wherever you saved them. It may have wiped out the installation files but not the backup files. Reinstall TB and see if the backups are still there.
And the best way to start over is to flash the latest ROM (1.4.3) and use Manual Nooter 5.08.20 to root it. Get a cwm flashable version of 1.4.3 in the link in my tips thread linked in my signature. Look at item A15.
Sent from my Nook Color running CM10 and Tapatalk.
Trying to restore from the old Titanium files was a no-go. Even tried from a backup on a different SD card (August 2012)... same result. Tried deleting the /data/system/accounts.db file and rebooting; that just removed my BN login info AND Google login.
So, I've decided to try your suggestion and have run the format 5-6-7 zip file from CWM, and then your 1.4.3 file, also from CWM. So far so good. Many thanks.
Any caveats I need to watch for from here going forward? I have re-registered with BN, and everything looks good.
At this point, I'm faced with some options. From the "Manual Nooter 5.08.20" page, I see:
1. Download one of the Following ManualNooter 5 files based on your needs:
*manualnooter-5.08.20.basic.zip - It doesn't include apps2sd support, and doesn't block B&N updates. Doesn't replace any system files
*manualnooter-5.08.20.basic.block_updates.zip - It doesn't include apps2sd support, but has B&N updates blocked. Doesn't replace any system files
*manualnooter-5.08.20.apps2sd.zip - Includes apps2sd support, but doesn't block B&N updates. It will replace a system file, making it firmware version specific
*manualnooter-5.08.20.apps2sd.block_updates.zip - Includes apps2sd support, and has B&N updates blocked. It will replace a system file, making it firmware version specific.
If you will be flashing with apps2sd support, you will also need to download one of the following kernel images to fully utilize apps2sd support.
Dalingrin OC kernel - Dalingrin 090111 OC kernel
OR Stock kernel - Stock. kernel with apps2sd support
Phew! I assume there are advantages/disadvantages with the firmware-specific stuff? I also assume that BN updates have the potential to wreak havoc with a rooted Nook? I further assume "OC" stands for Over-Clocked?
Which combination would you recommend?
Thanks again!
I would use the basic but block updates. No apps2sd.
leapinlar said:
I would use the basic but block updates. No apps2sd.
Click to expand...
Click to collapse
CWM seems to be gone. Do I need to re-install it in order to load "manualnooter-5.08.20.basic.block_updates.zip?"
riffrafff said:
CWM seems to be gone. Do I need to re-install it in order to load "manualnooter-5.08.20.basic.block_updates.zip?"
Click to expand...
Click to collapse
Installing the stock rom erased it. It is best if you make a bootable SD with CWM on it. See item A10 in my tips thread.
Got it. Running Verygreen's agnostic image with the newest nightly of 7.2. Wow. Things have really changed in the last two years! I can barely find my way around. The learning curve begins. Now I'm trying to find the "gapps...zip" file. From this thread http://forum.xda-developers.com/showthread.php?t=1000957 it says this link should take me there...
"Go to http://wiki.cyanogenmod.com/index.ph...Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip."
Link: http://wiki.cyanogenmod.com/index.php?title=Latest_Version
I dunno. Not seeing it. More searching is called for. :good:
Okay, found the gapps stuff at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
...the world is bright and gay again! Happy, happy, joy, joy.
Coolness. Thanks for your help. Now to see if I can't finger out some of this new-fangled stuff!
Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?
riffrafff said:
Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?
Click to expand...
Click to collapse
To back up... shut nook down... take SD out and put it in computer... use win32diskimager or winimage to create an image of the SD
DizzyDen said:
To back up... shut nook down... take SD out and put it in computer... use win32diskimager or winimage to create an image of the SD
Click to expand...
Click to collapse
Thanks. I'll try that, excepting that I'll use 'dd' seeing as how I don't do Windows.
riffrafff said:
Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?
Click to expand...
Click to collapse
You can use my modified CWM to do nandroid backups of the SD install. Look in my tips thread linked in my signature and look at item B5.
leapinlar said:
You can use my modified CWM to do nandroid backups of the SD install. Look in my tips thread linked in my signature and look at item B5.
Click to expand...
Click to collapse
Cool. I'll do that. Thanks! :good:
Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app